npx skills add https://github.com/owl-listener/designer-skills
infrasity-labs/dev-gtm-claude-skills
handoff-spec
Create developer handoff specifications with measurements, behaviors, assets, and edge cases.
Installation
npx skills add infrasity-labs/dev-gtm-claude-skills --skill handoff-spec
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Write the implementation handoff — measurements, behaviours, assets, states, and edge cases. Us…
1.5K installsGenerate developer handoff specs from a design. Use when a design is ready for engineering and …
2.9K installsHand off the current thread to a new Pulumi Neo task as a one-way transfer. Use when the user e…
1 installsHand the current conversation off to a fresh background agent that picks up the work immediatel…
248.2K installsResume the most recent agent session for the current working directory, leading with any unansw…
11.3K installsAlso in this package
Other skills from infrasity-labs/dev-gtm-claude-skills · top by installs.
npx skills add infrasity-labs/dev-gtm-claude-skills
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Also listed on
Alternate registries and mirrors of this skill.
Repository health
main
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md1,812 B -
docs
SUMMARY.md113 B
History
- First seen on skills.sh
- First recorded snapshot · 54 installs
SKILL.md
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