claude-design-inbound

What problem does it solve?

Importing design artifacts (tokens, components, and screen specs) into a codebase often causes large, hard-to-review changes where token and UI implementation churn break in-flight reviews.

Core Features & Use Cases

• Stacked PR landing with enforced merge order: creates PRs for tokens first, implementation second, and optional assets last to prevent token/consumer mismatches.
• Artifact triage and scope control: inventories tokens, components, screens, and assets, and requires selecting the actual redesign scope instead of attempting to land the entire design system at once.
• Token-diff-driven updates: adds new tokens, updates changed values, and deprecates removed tokens for continued reference stability until consumers migrate.
• Implementation that consumes tokens only: ensures visual changes in components/screens reference tokens instead of hard-coded values, with explicit token-gap reporting back to the tokens PR.
• Optional asset generation handoff: routes asset generation to chatbot-asset-pipeline so art work doesn’t block implementation PR approval and merge.

Quick Start

Use this skill when you have a Claude Design handoff and tell it which redesign scope to land, and it will split the work into a tokens-first, implementation-second, optional-assets-third PR stack in the correct merge order.