← ClaudeAtlas

handoff-to-claude-codelisted

Use when the user asks to hand a finished design off to a developer or a coding agent for implementation in a real codebase. Produces a self-sufficient handoff folder with a spec README, zipped for download.
stritar/skills · ★ 0 · AI & Automation · score 60
Install: claude install-skill stritar/skills
Loaded when the user asks to hand a finished design off to a developer or a coding agent for implementation in a real codebase. The output of this skill is a self-sufficient handoff folder, zipped and presented to the user for download. ## Folder setup - Create a folder at `./opendesign/handoffs/<feature-slug>/`. Slug describes the feature (e.g. `onboarding-flow`, `settings-redesign`). Never `handoff/`, `export/`, or similar generics at the project root. - Copy every relevant HTML prototype, component file, image, font, and referenced asset into the folder. The developer must not have to trace paths back into the main project tree. - Generate `README.md` at the root of the folder. Everything the developer needs to act on lives in the README. ## README structure Every section below is required. Use these exact headings in this order. 1. **Overview.** One short paragraph: what the feature is and what it accomplishes. No design history. 2. **About the design files.** Disclaimer up front, verbatim in spirit: the HTML files in this bundle are *design references*, not production code to copy directly. The developer's task is to recreate the designs in the target codebase's existing framework (React, Vue, SwiftUI, native, etc.) using its established patterns and libraries. If no codebase exists yet, pick the most appropriate framework for the project. 3. **Fidelity.** State explicitly whether the designs are high-fidelity (pixel-perfect; recreate exactly) or low-fidelity (wiref