design-import

Featured

Scaffolds React components from a Claude Design handoff bundle and stops at files on disk: no stories, no tests, no pull request. Use when handed a claude.ai/design URL or a local bundle file; when that same scaffold should carry on through test generation, browser verification and an opened PR, run /ork:design-ship instead.

AI & Automation 229 stars 25 forks Updated today MIT

Install

View on GitHub

Quality Score: 89/100

Stars 20%
79
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Design Import Turn a Claude Design handoff bundle into scaffolded React components, with provenance and dedup against the existing codebase. ```bash design-import https://claude.ai/design/abc123 # From handoff URL design-import /tmp/handoff-bundle.json # From local file ``` ## When to use After exporting a handoff bundle from claude.ai/design. This skill is the **entry point** — it does NOT open a PR, run tests, or deploy. For the end-to-end flow (import → tests → PR), use `design-ship` instead. ## Pipeline ``` Handoff bundle (URL or file) │ ▼ ┌──────────────────────────────┐ │ 1. PARSE + VALIDATE │ via claude-design-orchestrator agent │ - Fetch bundle │ Schema validation │ - Compute bundle_id (sha) │ Surface deviations └──────────┬───────────────────┘ │ ▼ ┌──────────────────────────────┐ │ 2. RECONCILE TOKENS │ Diff bundle tokens vs project tokens │ - Read project tokens │ Conflicts → AskUserQuestion │ - Apply additions │ Additions → write to design-tokens.json └──────────┬───────────────────┘ │ ▼ ┌──────────────────────────────┐ │ 3. DEDUP COMPONENTS │ For each proposed component: │ Storybook MCP first │ • exact match → reuse (skip) │ 21st.dev next │ • similar match → adapt │ Filesystem grep last │ • no match → scaffold └──────────┬───────────────────┘ │ ▼ ┌──────────...

Details

Author
yonatangross
Repository
yonatangross/orchestkit
Created
8 months ago
Last Updated
today
Language
TypeScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

design-ship

One-shot pipeline turning a claude.ai/design link into a pull request: scaffold via /ork:design-import, stories and specs via /ork:cover, browser verification via /ork:expect, then open the PR. Use when a design link should come back as a PR with no intermediate steps; if all you need is the components written to disk, run /ork:design-import instead.

229 Updated today
yonatangross
Web & Frontend Listed

claude-design-handoff

Implement designs handed off from Claude Design (claude.ai/design) into a real Next.js/TypeScript/React codebase with 1:1 visual fidelity AND working integration with live data and AI features. Use this whenever the user wants to build, implement, port, or "make real" a design that came from Claude Design: a handoff bundle (a folder whose README starts with "CODING AGENTS: READ THIS FIRST"), an exported .zip or standalone HTML, a set of .jsx prototype files plus a primary .html, or the user says things like "implement this design," "build this 1:1," "pixel-perfect," "I exported this from Claude Design," or "wire this design into the app." Trigger it even when the user only attaches a screenshot or PDF of a Claude Design mockup and asks to build it, and even when they describe a dashboard/report/genome/page design rather than naming Claude Design explicitly. Do not skip this skill in favor of eyeballing a screenshot and free-handing components: the failure mode it exists to prevent is exactly that.

0 Updated 1 months ago
andrewr303
AI & Automation Featured

design-sync

Push a React design system to claude.ai/design. This runs a converter that bundles the real component code (from Storybook or a bare package) and uploads it. Use when the user runs /design-sync or says "sync my design system to Claude Design".

64,796 Updated yesterday
asgeirtj