Turn approved interface designs into build-ready specs with traceable states, responsive rules, accessibility behavior, assets, and QA gates.
A polished frame is not an implementation contract. The hard part lives between the screens: source authority, component reuse, missing states, responsive behavior, accessibility semantics, asset rights, acceptance checks, and the decisions nobody wants an engineer to guess.
Design Handoff turns approved interface evidence into buildable work. It separates what the design actually proves from estimates and proposals, reconciles design-system components with the target codebase, and covers interaction, failure, adaptive, localization, and assistive-technology behavior. Every material requirement stays linked to a source, implementation target, and observable check.
Use it before engineering starts, when a design-system version does not match the repository, or when a team needs an honest readiness decision. The output includes a source and authority register, evidence ledger, component and token mapping, state matrix, responsive rules, accessibility and asset contract, implementation sequence, acceptance matrix, open decisions, and change log. Missing critical behavior stays visible instead of being filled with plausible-looking defaults.
Version 1.0.0 was reviewed on 2026-07-16 and evaluated with gpt-5.6-sol in 12 fresh read-only contexts. The candidate scored 100 across three cases, compared with 75 for the same agent without the skill and 74.17 for the exact free upstream. The cases covered raster-only evidence and token conflicts, a checkout handoff with design-system and failure-state gaps, and pressure to mark a risky account-deletion flow ready. This evaluation measures the supplied cases; it does not prove pixel parity, accessibility conformance, implementation quality, or buyer outcomes. The reviewed package SHA-256 is 588dc1c383fa76c311e9bc2f8883cb13bdabf1b937a761bf1db53378ab5b4043.
The package includes a read-only checker for an optional canonical JSON handoff record. Passing it confirms structure, references, and verdict precedence. It does not inspect design files, render code, or certify the implementation. Maintenance and install support are handled by the platform-operated publisher for this listing.
Input
Turn our approved desktop and mobile checkout frames into a handoff. Map the existing component library, cover loading and failure states, include accessibility behavior, and give us five implementation tickets with QA checks.
Output
A scoped readiness verdict; source and evidence register; component, token, state, responsive, accessibility, content, and asset contracts; five dependency-aware tickets; and a traceability matrix from each requirement to its implementation target and check.
Input
The design uses CheckoutCard 3.8, but the app is still on 3.6 and cannot upgrade this sprint. Reconcile the missing slot and deprecated focus style without pretending the versions are compatible.
Provide the approved design source or export, its revision, the target repository or implementation context, supported platforms and devices, the design-system version, product and content requirements, known assets, and the authority rule for conflicts. Ask for a new handoff, an implementation-readiness review, five or more traceable tickets, or a delta review after the design changes. The skill keeps observed facts, estimates, proposals, and open decisions separate.
A design file, export, prototype, screenshot set, or written interface specification with a revision or capture time and enough context to identify what is approved.
Target repository or stack, supported platforms and versions, existing components and tokens, data contracts, and any build or release constraints.
The rule for resolving design, product, content, accessibility, and code conflicts, plus owners for decisions the evidence cannot settle.
Whether the agent may only write the handoff, inspect local files, create tickets, export approved assets, or change implementation code.
SKILL.md; design handoff coverage and decision rubric; report and canonical JSON output contract; read-only JSON handoff checker; Agent Skills interface metadata
No reviews yet.
Output
An explicit version mismatch; reuse, extension, and new-primitive decisions; affected states and accessibility requirements; a contained local-extension plan; acceptance checks; ownership; and a correction path that does not claim 3.8 compatibility.
Input
The latest account-deletion PDF conflicts with product policy, the legal copy is placeholder text, and the illustration is an unlicensed stock preview. The sprint manager wants the handoff marked ready today.
Output
A blocked verdict tied to the exact conflicting and missing evidence; privacy, recovery, accessibility, legal-copy, and asset requirements; a compact decision package with owners; and the safe preparatory work that can proceed without hiding open questions.
Creator
Kkaviro29
