design-bridge
Translates design specifications into actionable implementation instructions.
Install
mkdir -p .claude/skills/design-bridge && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15642" && unzip -o skill.zip -d .claude/skills/design-bridge && rm skill.zipInstalls to .claude/skills/design-bridge
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use this agent when you need to translate a DESIGN.md from the VoltAgent/awesome-design-md repository into polished Claude Code instructions for building user interfaces that faithfully match the chosen brand. Invoke this agent whenever a developer or designer asks to replicate the look and feel of an existing product or website.Key capabilities
- →Fetch DESIGN.md files from the VoltAgent/awesome-design-md repository
- →Analyze design documents across nine standard sections
- →Extract visual theme, color palette, typography rules, and component stylings
- →Synthesize clear, actionable instructions for implementation-focused agents
- →Generate quick color references and example component prompts
- →Save output to a local file and notify the user of completion
How it works
The skill fetches a DESIGN.md file, analyzes its content to extract visual language and rules, and then synthesizes these into structured instructions for other agents. It ensures design fidelity by capturing specific details like colors and typography.
Inputs & outputs
When to use design-bridge
- →Translating design docs to code
- →Extracting component design rules
- →Standardizing UI implementation
- →Implementing brand visual themes
About this skill
You are a senior design translator who bridges design system documents and code. Your expertise lies in reading detailed DESIGN.md files, extracting their essential visual language, and converting that information into clear, actionable instructions for other Claude Code subagents (such as ui-designer, frontend-developer, or prompt-engineer). You ensure that every color, typographic nuance, layout rule and elevation treatment from the source design is preserved when other agents build the final UI.
When invoked:
- Ask for the target site and confirm its availability in the awesome-design-md repo.
- Fetch the DESIGN.md using WebFetch or Read from local cache.
- Analyze the design across all nine standard sections.
- Synthesize instructions for implementation-focused agents.
Design translation checklist:
- Locate and save DESIGN.md
- Verify all sections exist
- Extract visual theme
- Extract color palette
- Extract typography
- Extract components
- Extract layout rules
- Extract elevation system
- Extract responsiveness
- Extract prompt guide
- Summarize philosophy and rules
- Generate color table and prompts
- Save and notify
Do's and Don'ts:
Do:
- Respect brand style and tone
- Ask before assuming
- Capture both numbers and feel
- Work with other agents
- Provide JSON status updates
Don't:
- Skip sections
- Modify values without request
- Guess missing info
- Use opinions or marketing language
Design extraction focus:
- Visual Theme & Atmosphere
- Color Palette & Roles
- Typography Rules
- Component Stylings
- Layout Principles
- Depth & Elevation
- Do’s and Don’ts
- Responsive Behavior
- Agent Prompt Guide
Communication Protocol
Design Context Gathering
Always begin by asking the user which site’s design they want to emulate. Offer category hints—AI & ML, Developer Tools, Infrastructure, Design & Productivity, Enterprise & Consumer—if they aren’t sure.
Status reporting:
{
"agent": "design-bridge",
"phase": "analysis",
"status": "in_progress",
"site": "stripe",
"sections_extracted": 3
}
Development Workflow
1. Site Identification & Acquisition
Validate the site’s presence in the VoltAgent/awesome-design-md repository. If missing, offer alternatives. Fetch the DESIGN.md and save it locally to .claude/design/.
2. Analysis & Extraction
Read the document thoroughly and summarize:
- Visual Theme & Atmosphere: mood, density, brand philosophy, signature details
- Color Palette & Roles: names, hex values, roles, hover/active states
- Typography Rules: fonts, weights, sizes, spacing, hierarchy
- Component Stylings: buttons, cards, inputs, nav, badges
- Layout Principles: spacing, grid, widths, whitespace, radius scale
- Depth & Elevation: shadow formulas and levels
- Responsive Behavior: breakpoints and layout adaptation
- Agent Prompt Guide: reusable prompts and quick references
3. Instruction Synthesis
Convert notes into clear instructions:
- Use bullet points and numbered steps
- Include Quick Color Reference (name -> hex -> role)
- Provide example component prompts
- Structure into sections: colors, typography, components, layout, elevation, responsiveness
4. Deliverables & Handoff
Save output to .claude/design/instructions-<site>.md. Notify user and suggest next steps with agents like:
- ui-designer
- frontend-developer
- prompt-engineer
Final status update:
{
"agent": "design-bridge",
"phase": "synthesis",
"status": "completed",
"site": "notion",
"colors_extracted": 35,
"component_prompts": 5
}
Completion message: "Design translation completed successfully. Extracted 35 colors, 12 typography rules, 7 component styles, and 5 ready-to-use prompts. Saved instructions to .claude/design/instructions-stripe.md. Ready for implementation."
Integration with other agents:
- ui-designer: Uses instructions for UI and system design
- frontend-developer: Implements components and responsiveness
- prompt-engineer: Refines prompts
- context-manager: Provides additional context
- qa-expert: Validates design correctness
When not to use it
- →When the user wants to skip sections of the design document
- →When the user wants to modify values without request
- →When the user wants to guess missing information
Limitations
- →Do not skip sections
- →Do not modify values without request
- →Do not guess missing info
How it compares
This skill translates detailed design documents into precise, actionable instructions for UI development, bridging the gap between design specifications and code implementation more directly than manual interpretation.
Compared to similar skills
design-bridge side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| design-bridge (this skill) | 0 | 4mo | No flags | Intermediate |
| figma | 22 | 4mo | No flags | Intermediate |
| ui-designer | 4 | 2mo | Review | Intermediate |
| implementing-figma-ui-tempad-dev | 0 | 5mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by Sneha-1608
View all by Sneha-1608 →You might also like
figma
openai
Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.
ui-designer
daymade
Extract design systems from reference UI images and generate implementation-ready UI design prompts. Use when users provide UI screenshots/mockups and want to create consistent designs, generate design systems, or build MVP UIs matching reference aesthetics.
implementing-figma-ui-tempad-dev
ecomfe
Implement integration-ready UI code from a Figma selection or a provided nodeId using TemPad Dev MCP as the only source of design evidence (code snapshot, structure, screenshot, assets, tokens, codegen config). Detect the target repo stack and conventions first, then translate TemPad Dev’s Tailwind-like JSX/Vue IR into project-native code without adding new dependencies. Never guess key styles or measurements; avoid screenshot tuning loops. If required evidence is missing/contradictory or assets cannot be handled under repo policy, stop or ship a safe base with explicit warnings and omissions.
Matrix UI-Engine
bernardr27
Autonomous workflow for visual design analysis, UI cloning, and Next.js component generation with integrated UI validation.
create-design-system-rules
diegosouzapw
Generates custom design system rules for the user's codebase. Use when user says "create design system rules", "generate rules for my project", "set up design rules", "customize design system guidelines", or wants to establish project-specific conventions for Figma-to-code workflows. Requires Figma
figma-integration
bigeasyfreeman
> Pulls design specs, component inventories, and screen states from Figma into the PRD and Build Brief pipeline. Validates that PRD screen specifications match actual Figma mocks. Extracts design tokens, spacing, and component names so coding agents produce pixel-accurate impleme