claude-design-outbound

What problem does it solve?

It solves the problem of design drift by exporting what is actually rendering in the current implementation into a Claude Design–consumable artifact pack.

Core Features & Use Cases

• Screenshots with actionable annotations: Produces annotated screenshots (callouts that map pixels to tokens and components) so designers can iterate on what shipped.
• Component variant matrices: Generates a per-component variant inventory to highlight present variants, missing spec variants, and ad-hoc code-only variants.
• Token dump with intent vs runtime provenance: Exports computed token values from code intent and runtime verification, including notes when runtime differs due to resolved fallbacks; iOS runtime color spot-checking can use pixel sampling and typography is captured with explicit provenance.
• Spec-shaped reality snapshot: Creates a DESIGN.snapshot.md in the shape of an existing DESIGN.md so the next design round can compare against reality.
• Use cases: Run after an audit, before a design feedback round, when exporting the current app state for a designer review, or when needing a periodic “current state” archive.

Quick Start

Ask for an export of the current implementation back to Claude Design using the provided skill so you receive a design/outbound/<date>/ pack containing annotated screenshots, token dumps, component matrices, and a DESIGN.snapshot.md.