Works with the AI tools you already use
Claude Code
Cursor
Codex CLI
GitHub Copilot
Gemini CLI+20 moreClaude CodeCursorCodex CLIGitHub CopilotGemini CLI
OpenClaw
Manus
Grok+17 agentsFigma-to-Frontend Specification Builder
Translates Figma designs into implementation-ready frontend specs, component maps, and responsive logic.
$9.99
Figma-to-Frontend Specification Builder
Example session with this skill installed
Generate a frontend spec for a responsive 'User Profile Card' based on this design: it has a cover photo, avatar, bio, and a 'Follow' button. It needs to handle long bios and mobile views.
- Read your context and instructions
- Compiled the figma-to-frontend specification builder
- Generated the image
Processed the User Profile Card design. Decomposed layout into 4 sub-components and defined responsive behavior.
Frontend Specification: User Profile Card
1. Handoff Summary
- Purpose: Display user identity and social actions at a glance.
- Primary Goal: Provide a summary of user info with a clear CTA.
- Key Dependencies: Avatar image hosting, social API for follow status.
2. Component Map
| Component | Purpose | Variants | States | Reusable? |
|---|---|---|---|---|
| ProfileCard | Main container | Standard, Compact | Default | Yes |
| Avatar | User photo | Large, Small | Loading, Error | Yes |
| FollowButton | Primary action | Solid, Outlined | Hover, Active, Loading | Yes |
3. Layout Specification
- Structure: Vertical flex container with absolute-positioned Avatar overlapping the CoverPhoto.
- Spacing: 24px internal padding; 12px gap between text elements.
- Overflow: Bio section should handle multi-line text with a 3-line clamp limit.
4. Responsive Specification
| Element | Desktop | Tablet | Mobile |
|---|---|---|---|
| Card Width | 400px fixed | 100% (max-width: 400px) | 100% |
| Avatar Size | 120px | 100px | 80px |
| Layout | Side-by-side text/image | Stacked | Stacked (centered) |
5. Interaction & State Specification
| Component | State | Behavior | Visual Change |
|---|---|---|---|
| FollowButton | Hover | Background transition | 10% brightness reduction |
| FollowButton | Loading | Disable pointer events | Replace text with Spinner |
| Bio | Empty | Render placeholder | Italicized 'No bio provided' |
6. Design Tokens
- Recommended:
radius-lg: 12px,shadow-md: 0 4px 6px -1px rgb(0 0 0 / 0.1). - Missing: Exact hex for 'Primary Brand Blue' needs designer confirmation.
7. Accessibility Requirements
- Use
aria-pressedfor the Follow button toggle state. - Ensure the Avatar has
alttext provided by the user profile data. - Maintain a minimum 4.5:1 contrast ratio for bio text against card background.
8. Suggested Frontend Structure
UserProfileCard.tsx(Root)ProfileHeader.tsx(Cover + Avatar)ProfileContent.tsx(Name + Bio)ProfileActions.tsx(Buttons)
9. Acceptance Criteria
- Card maintains layout integrity when bio text exceeds 500 characters.
- Follow button enters a disabled state during API transit.
- Component is navigable via keyboard Tab key.
Next steps
- Confirm the primary brand color hex code with the design team.
- Define the image aspect ratio for the cover photo to prevent layout shift.
- Verify if 'Followers count' should be included in the data contract.
figma-to-frontend-specification-builder.png
PNG · 1536×1024
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
What you get
About this skill
The problem
Static Figma frames often lack the interaction details, responsive logic, and edge-case definitions needed for production-ready code. Developers are frequently forced to make assumptions about component states and layout behavior, leading to design debt and back-and-forth cycles.
What it does
- Decomposes Figma layouts into reusable component hierarchies and state maps.
- Translates visual design intent into explicit layout specifications using flexbox or grid logic.
- Defines responsive stacking strategies and typography scaling across desktop, tablet, and mobile.
- Maps design elements to developer-friendly tokens for colors, spacing, and shadows.
- Generates testable acceptance criteria covering accessibility, error states, and data truncation.
Why this beats prompting it yourself
General-purpose LLMs often focus on aesthetic descriptions rather than implementation logic. This skill enforces a structured handoff workflow that prioritizes component reusability, state management, and accessibility considerations that designers might omit from a static frame.
Use cases
- Converting a high-fidelity Figma mockup into a detailed technical specification for a sprint.
- Defining the data contract and component props for a complex form or dashboard.
- Documenting responsive behavior and breakpoint transitions for a multi-device web app.
- Creating an accessibility and interaction guide for a new design system component.
Known limitations
Requires manual input of design descriptions or screenshots. Does not perform pixel-perfect measurement extraction or direct repository code changes.
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.
Skills folder by agent
Click the path to copy it. Create the folder if it does not exist yet.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
30-day refund
Not a fit? Get your money back
Trust & safety
Security scanned
Verified clean 6 days ago
- Passed all security checks, Safe to install