design-handoff-spec

Generate developer-ready UI component specifications from Figma annotations.

19|5|Updated Nov 23, 2025
One-click install
npx skills add https://github.com/Nir-Bhay/markups --skill design-handoff-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-handoff-spec
Source: https://github.com/Nir-Bhay/markups/tree/main/.agents/skills/design-handoff-spec
Command: npx skills add https://github.com/Nir-Bhay/markups --skill design-handoff-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of translating design mockups into actionable specifications for developers, ensuring pixel-perfect implementation and reducing ambiguity.

Core Features & Use Cases

  • Detailed Component Specs: Generates comprehensive documentation for UI components, including layout, typography, colors, and states.
  • Asset Requirements: Defines clear guidelines for asset formats, sizes, and naming conventions.
  • Use Case: A designer can use this Skill to generate a detailed specification for a new button component, including its different states (hover, active, disabled), color variations, typography, and export requirements for icons, ensuring developers have all necessary information.

Quick Start

Generate a design specification for a primary button component.

Frequently Asked Questions about design-handoff-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate developer handoff specifications from Figma annotations?

To generate developer handoff specifications from Figma annotations, you can use this Skill to translate design mockups into structured markdown and YAML, covering layout, typography, colors, states, and accessibility for precise implementation.

What is the best way to document UI component states for developer handoff?

The best way to document UI component states for developer handoff is to generate detailed specifications that include hover, active, and disabled variations, alongside asset requirements and export guidelines, ensuring developers have actionable, unambiguous instructions.

Does this design handoff specification include accessibility requirements?

Yes, this design handoff specification includes accessibility requirements. It generates comprehensive documentation covering layout, typography, color, states, and assets, ensuring that accessibility standards are explicitly translated into developer-ready instructions.

Can I use structured markdown and YAML for component documentation?

You can use structured markdown and YAML for component documentation. This Skill outputs detailed UI specifications utilizing these formats to ensure clarity and machine readability, bridging design and development workflows seamlessly.

How do design tokens fit into UI specifications for developers?

Design tokens fit into UI specifications by standardizing layout, typography, and color values. This Skill translates Figma annotations into developer-ready documentation, ensuring these tokens are precisely defined for accurate component implementation.

Why do I need detailed asset requirements in a design handoff?

You need detailed asset requirements in a design handoff to define clear guidelines for formats, sizes, and naming conventions. This ensures developers receive exact export requirements for icons and other assets, reducing implementation ambiguity.