In the Skill's Own Terms
A guide for designing real interfaces in Penpot through the penpot/penpot-mcp server, written for designers and developers whose agent drives the Penpot plugin API. Rather than giving generic advice, it specifies a working sequence: check whether the MCP server is already running, discover the file's existing colours, text styles and components, inspect hierarchy with penpotUtils.shapeStructure, then create boards, rectangles and text and apply addFlexLayout containers.
It supplies fallback 8px spacing and typography scales, a mobile 375x812 and dashboard 1440x900 layout, checklists for buttons, forms and navigation, WCAG contrast and touch target limits, board placement spacing, Penpot API pitfalls such as read-only width and height, and validation through analyzeDescendants, fontSize filtering and export_shape.
What it produces
- New or modified Penpot designs created through JavaScript executed in the plugin context.
- PNG or SVG renders of selected shapes, used to look at the design rather than guess.
- CSS extracted from a selection, including children, for handoff.
How It Works
- 01Confirm the Server Is Running
The first move is a trial call to penpot_api_info, so nobody gets walked through installation when the connection already works.
- 02Find the Existing Design System
Before drawing, it asks about brand guidelines and reads the current file for components, colours and patterns already in use.
- 03Inspect the Page Structure
shapeStructure returns the existing hierarchy so new elements can be placed relative to what is already on the canvas.
- 04Create the Elements
Boards, rectangles and text are made through plugin calls in the Penpot plugin context rather than described in prose.
- 05Validate by Exporting
Every change ends with an export so the result is looked at as an image, not trusted from code alone.