- Home
- Skills
- Frontend & Web Apps
- Prototype Handoff Spec: Design to Build Plan for Your Repo
Works with the AI Agents you already use
Prototype Handoff Spec: Design to Build Plan for Your Repo
This skill automates the transition from design to development by auditing your existing codebase and generating a technical implementation spec.
Free
Prototype Handoff Spec: Design to Build Plan for Your Repo
Example session with this skill installed
Look at the Sidebar artifact I just approved. Spec it out for our current React/Tailwind repo. Check for existing Nav components we can reuse.
- Read your context and instructions
- Compiled the prototype handoff spec
- Generated the UI component
I have audited the repository and the Sidebar artifact. The following spec maps the design to our existing src/components/ui library and tailwind.config.js.
Sidebar Implementation Spec
1. Summary
- Implementation of a responsive, collapsible Sidebar with integrated navigation.
- Leverages existing
ButtonandCollapsibleprimitives. - Adds
NavSectionandNavItempatterns to the local component library.
2. Component Tree
- Sidebar (New)
- SidebarHeader (New)
- OrgSwitcher (Extend:
Select)
- OrgSwitcher (Extend:
- NavGroup (New)
- NavItem (Reuse:
Buttonwith ghost variant)
- NavItem (Reuse:
- SidebarFooter (New)
- UserProfile (Reuse:
Avatar)
- UserProfile (Reuse:
- SidebarHeader (New)
3. Token Map & Gaps
| Design Value | Token / CSS Variable | Status |
|---|---|---|
| Background #F9FAFB | bg-gray-50 | Match |
| Border #E5E7EB | border-gray-200 | Match |
| Width 280px | N/A | Gap: Use w-[280px] or add theme.width.sidebar |
| Shadow Soft | shadow-sm | Match |
4. States & Interactions
- Default: Width 280px, labels visible.
- Collapsed: Width 64px, labels hidden, icons only.
- Hover (NavItem):
bg-gray-100, transition 200ms. - Focus:
ring-2 ring-primary, visible on keyboard tab.
5. File Plan
| File | Action | Purpose |
|---|---|---|
src/components/ui/sidebar.tsx | Create | Main container and layout logic |
src/components/ui/nav-item.tsx | Create | Sub-component for individual links |
src/lib/constants.ts | Modify | Add sidebar width constants |
6. Acceptance Checklist
- No hardcoded hex codes; all colors use Tailwind tokens.
- Sidebar collapses correctly at
mdbreakpoint. - ARIA roles
navigationandbuttonapplied. - Focus trap active when in mobile overlay mode.
Next steps
- Approve the width token addition to
tailwind.config.js. - Run the file plan to scaffold the components.
- Hook up the
useSidebarhook for state management.
sidebar.tsx
TSX · React component
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
About this skill
Manually translating a visual prototype into code often leads to technical debt, inconsistent styling, and redundant components. This skill automates the transition from design to development by auditing your existing codebase and generating a technical implementation spec.
What it does
- Codebase discovery identifies your framework, routing, state management, and existing UI library to ensure compatibility.
- Component mapping decomposes designs into a tree structure, categorizing items as reuse, extend, or new.
- Token alignment maps design values to your Tailwind config or CSS variables and flags style gaps.
- Behavioral definition documents every state, interaction, and breakpoint requirement before a line of code is written.
- Implementation roadmap generates a sequenced file plan and acceptance checklist for developers or agents.
How it works
- Analyze the current repository to inventory existing components, props, and theme tokens.
- Decompose the target design into sections and individual UI elements.
- Map behaviors including accessibility roles, keyboard order, and data shapes.
- Output a structured handoff document including a file plan and checklist.
Frameworks & tools
Works with any modern frontend stack including React, Vue, Next.js, and Svelte. Compatible with Tailwind CSS, CSS Modules, and standard design tokens.
Why this beats prompting it yourself
Generic prompts often ignore your existing component library, leading to duplicate code. This skill performs a deep grep of your actual repo to ensure every design choice is grounded in your current architecture and token system.
Use cases
- Generating a technical spec for a complex UI artifact.
- Auditing a design for token consistency against a Tailwind config.
- Planning a refactor when moving a prototype into a production codebase.
- Creating a step-by-step implementation guide for junior developers or sub-agents.
Known limitations
Requires an existing codebase or defined directory structure to perform the initial inventory. Analysis is limited to three levels of component nesting to maintain spec readability.
Requires existing code context for component reuse analysis. Nesting analysis capped at 3 levels deep.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
1 use
Times used to date
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 4 days ago
- Free with an Agensi account