penpot-uiux-design▌
github/awesome-copilot · updated May 24, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Professional UI/UX design creation in Penpot with MCP tools, design systems, and accessibility standards.
- ›Four MCP tools enable design creation, modification, export, and API access within Penpot's plugin context
- ›Includes discovery workflow to identify existing design systems, components, and tokens before building new designs
- ›Covers responsive layouts for mobile (375×812), desktop (1440×900), and platform-specific guidelines (iOS, Android, Material Design)
- ›Provides default design
Penpot UI/UX Design Guide
Create professional, user-centered designs in Penpot using the penpot/penpot-mcp MCP server and proven UI/UX principles.
Available MCP Tools
| Tool | Purpose |
|---|---|
mcp__penpot__execute_code |
Run JavaScript in Penpot plugin context to create/modify designs |
mcp__penpot__export_shape |
Export shapes as PNG/SVG for visual inspection |
mcp__penpot__import_image |
Import images (icons, photos, logos) into designs |
mcp__penpot__penpot_api_info |
Retrieve Penpot API documentation |
MCP Server Setup
The Penpot MCP tools require the penpot/penpot-mcp server running locally. For detailed installation and troubleshooting, see setup-troubleshooting.md.
Before Setup: Check If Already Running
Always check if the MCP server is already available before attempting setup:
-
Try calling a tool first: Attempt
mcp__penpot__penpot_api_info- if it succeeds, the server is running and connected. No setup needed. -
If the tool fails, ask the user:
"The Penpot MCP server doesn't appear to be connected. Is the server already installed and running? If so, I can help troubleshoot. If not, I can guide you through the setup."
-
Only proceed with setup instructions if the user confirms the server is not installed.
Quick Start (Only If Not Installed)
# Clone and install
git clone https://github.com/penpot/penpot-mcp.git
cd penpot-mcp
npm install
# Build and start servers
npm run bootstrap
Then in Penpot:
- Open a design file
- Go to Plugins → Load plugin from URL
- Enter:
http://localhost:4400/manifest.json - Click "Connect to MCP server" in the plugin UI
VS Code Configuration
Add to settings.json:
{
"mcp": {
"servers": {
"penpot": {
"url": "http://localhost:4401/sse"
}
}
}
}
Troubleshooting (If Server Is Installed But Not Working)
| Issue | Solution |
|---|---|
| Plugin won't connect | Check servers are running (npm run start:all in penpot-mcp dir) |
| Browser blocks localhost | Allow local network access prompt, or disable Brave Shield, or try Firefox |
| Tools not appearing in client | Restart VS Code/Claude completely after config changes |
| Tool execution fails/times out | Ensure Penpot plugin UI is open and shows "Connected" |
| "WebSocket connection failed" | Check firewall allows ports 4400, 4401, 4402 |
Quick Reference
| Task | Reference File |
|---|---|
| MCP server installation & troubleshooting | setup-troubleshooting.md |
| Component specs (buttons, forms, nav) | component-patterns.md |
| Accessibility (contrast, touch targets) | accessibility.md |
| Screen sizes & platform specs | platform-guidelines.md |
Core Design Principles
The Golden Rules
- Clarity over cleverness: Every element must have a purpose
- Consistency builds trust: Reuse patterns, colors, and components
- User goals first: Design for tasks, not features
- Accessibility is not optional: Design for everyone
- Test with real users: Validate assumptions early
Visual Hierarchy (Priority Order)
- Size: Larger = more important
- Color/Contrast: High contrast draws attention
- Position: Top-left (LTR) gets seen first
- Whitespace: Isolation emphasizes importance
- Typography weight: Bold stands out
Design Workflow
- Check for design system first: Ask user if they have existing tokens/specs, or discover from current Penpot file
- Understand the page: Call
mcp__penpot__execute_codewithpenpotUtils.shapeStructure()to see hierarchy - Find elements: Use
penpotUtils.findShapes()to locate elements by type or name - Create/modify: Use
penpot.createBoard(),penpot.createRectangle(),penpot.createText()etc. - Apply layout: Use
addFlexLayout()for responsive containers - Validate: Call
mcp__penpot__export_shapeto visually check your work
Design System Handling
Before creating designs, determine if the user has an existing design system:
- Ask the user: "Do you have a design system or brand guidelines to follow?"
- Discover from Penpot: Check for existing components, colors, and patterns
// Discover existing design patterns in current file
const allShapes = penpotUtils.findShapes(() => true, penpot.root);
// Find existing colors in use
const colors = new Set();
allShapes.forEach(s => {
if (s.fills) s.fills.forEach(f => colors.add(f.fillColor));
});
// Find existing text styles (font sizes, weights)
const textStyles = allShapes
.filter(s => s.type === 'text')
.map(s => ({ fontSize: s.fontSize, fontWeight: s.fontWeight }));
// Find existing components
const components = penpot.library.local.components;
return { colors: [...colors], textStyles, componentCount: components.length };
If user HAS a design system:
- Use their specified colors, spacing, typography
- Match their existing component patterns
- Follow their naming conventions
If user has NO design system:
- Use the default tokens below as a starting point
- Offer to help establish consistent patterns
- Reference specs in component-patterns.md
Key Penpot API Gotchas
width/heightare READ-ONLY → useshape.resize(w, h)parentX/parentYare READ-ONLY → usepenpotUtils.setParentXY(shape, x, y)- Use
insertChild(index, shape)for z-ordering (notappendChild) - Flex children array order is REVERSED for
dir="column"ordir="row" - After
text.resize(), resetgrowTypeto"auto-width"or"auto-height"
Positioning New Boards
Always check existing boards before creating new ones to avoid overlap:
// Find all existing boards and calculate next position
const boards = penpotUtils.findShapes(s => s.type === 'board', penpot.root);
let nextX = 0;
const gap = 100; // Space between boards
if (boards.length > 0) {
// Find rightmost board edge
boards.forEach(b => {
const rightEdge = b.x + b.width;
if (rightEdge + gap > nextX) {
nextX = rightEdge + gap;
}
});
}
// Create new board at calculated position
const newBoard = penpot.createBoard();
newBoard.x = nextX;
newBoard.y = 0;
newBoard.resize(375, 812);
Board spacing guidelines:
- Use 100px gap between related screens (same flow)
- Use 200px+ gap between different sections/flows
- Align boards vertically (same y) for visual organization
- Group related screens horizontally in user flow order
Default Design Tokens
Use these defaults only when user has no design system. Always prefer user's tokens if available.
Spacing Scale (8px base)
| Token | Value | Usage |
|---|---|---|
spacing-xs |
4px | Tight inline elements |
spacing-sm |
8px | Related elements |
spacing-md |
16px | Default padding |
spacing-lg |
24px | Section spacing |
spacing-xl |
32px | Major sections |
spacing-2xl |
48px | Page-level spacing |
Typography Scale
| Level | Size | Weight | Usage |
|---|---|---|---|
| Display | 48-64px | Bold | Hero headlines |
| H1 | 32-40px | Bold | Page titles |
| H2 | 24-28px | Semibold | Section headers |
| H3 | 20-22px | Semibold | Subsections |
| Body | 16px | Regular | Main content |
| Small | 14px | Regular | Secondary text |
| Caption | 12px | Regular | Labels, hints |
Color Usage
| Purpose | Recommendation |
|---|---|
| Primary | Main brand color, CTAs |
| Secondary | Supporting actions |
| Success | #22C55E range (confirmations) |
| Warning | #F59E0B range (caution) |
| Error | #EF4444 range (errors) |
| Neutral | Gray scale for text/borders |
Common Layouts
Mobile Screen (375×812)
┌─────────────────────────────┐
│ Status Bar (44px) │
├─────────────────────────────┤
│ Header/Nav (56px) │
├─────────────────────────────┤
│ │
│ Content Area │
│ (Scrollable) │
│ Padding: 16px horizontal │
│ │
├─────────────────────────────┤
│ Bottom Nav/CTA (84px) │
└─────────────────────────────┘
Desktop Dashboard (1440×900)
┌──────┬──────────────────────────────────┐
│ │ Header (64px) │
│ Side │──────────────────────────────────│
│ bar │ Page Title + Actions │
│ │──────────────────────────────────│
│ 240 │ Content Grid │
│ px │ ┌─────┐ ┌─────┐ ┌─────┐ ┌─────┐ │
│ │ │Card │ │Card │ │Card │ │Card │ │
│ │ └─────┘ └─────┘ └─────┘ └─────┘ │
│ │ │
└──────┴──────────────────────────────────┘
How to use penpot-uiux-design on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add penpot-uiux-design
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches penpot-uiux-design from GitHub repository github/awesome-copilot and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate penpot-uiux-design. Access the skill through slash commands (e.g., /penpot-uiux-design) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★55 reviews- ★★★★★Nikhil Gupta· Dec 24, 2024
penpot-uiux-design fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Emma Johnson· Dec 20, 2024
penpot-uiux-design has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Aisha Ghosh· Dec 20, 2024
Keeps context tight: penpot-uiux-design is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Min Brown· Dec 4, 2024
I recommend penpot-uiux-design for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Neel Taylor· Nov 23, 2024
penpot-uiux-design reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Soo Garcia· Nov 15, 2024
penpot-uiux-design is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Rahul Santra· Nov 11, 2024
penpot-uiux-design has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Isabella Ndlovu· Nov 11, 2024
We added penpot-uiux-design from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Mia Sethi· Oct 14, 2024
Registry listing for penpot-uiux-design matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Soo Liu· Oct 6, 2024
Keeps context tight: penpot-uiux-design is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 55