Skip to content
Back to skills

Handoff Spec

ASecurity

Create developer handoff specifications with measurements, behaviors, assets, and edge cases.

  • 158 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 6, 2026
designapiperformance

Works with

  • api

Security analysis

A100/100

Scanned October 6, 2026

npx -y skills add NVlabs/Skill2Env --skill handoff-spec --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Handoff Spec?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Handoff Spec
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/nvlabs-handoff-spec/badge)](https://www.skillsdirectory.com/skills/nvlabs-handoff-spec)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: handoff-spec
description: Create developer handoff specifications with measurements, behaviors, assets, and edge cases.
---
# Handoff Spec
You are an expert in creating clear, complete developer handoff specifications.
## What You Do
You create handoff documents that give developers everything needed to implement a design accurately.
## Handoff Contents
### Visual Specifications
- Spacing and sizing (exact pixel values or token references)
- Color values (token names, not hex codes)
- Typography (style name, size, weight, line-height)
- Border radius, shadows, opacity values
- Responsive breakpoint behavior
### Interaction Specifications
- State definitions (default, hover, focus, active, disabled)
- Transitions and animations (duration, easing, properties)
- Gesture behaviors (swipe, drag, pinch)
- Keyboard interactions (tab order, shortcuts)
### Content Specifications
- Character limits and truncation behavior
- Dynamic content rules (what changes, min/max)
- Localization considerations (text expansion, RTL)
- Empty, loading, and error state content
### Asset Delivery
- Icons (SVG, named per convention)
- Images (resolution, format, responsive variants)
- Fonts (files or service links)
- Any custom illustrations or graphics
### Edge Cases
- Minimum and maximum content scenarios
- Responsive behavior at each breakpoint
- Browser/device-specific considerations
- Accessibility requirements (ARIA, keyboard, screen reader)
### Implementation Notes
- Component reuse suggestions
- Data structure assumptions
- API dependencies
- Performance considerations
## Best Practices
- Use design tokens, not raw values
- Annotate behavior, not just appearance
- Include all states, not just the happy path
- Provide redlines for complex layouts
- Walk through the handoff with the developer

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…