replica-design measures the recon screenshots into design tokens: colour roles, a type scale, a spacing scale, radius, shadow and motion. It then writes a spec for every component with its states and builds the primitives in isolation.
It rebuilds the system, never the original’s assets. Icons come from open sets, fonts from open families, and the brand colour is kept as a neutral role for the brand skill to replace.
What You Get
tokens.jsonandtokens.csswith colour roles, type, spacing, radius, shadow and motion- A Tailwind theme mapping so components use role names and never raw hex
- A
components.mdwith variants, sizes, states, tokens, accessibility notes and the screens each is used on - Primitives built in isolation on a design route or Storybook
- A contrast report with zero AA failures
Common Use Cases
- Turning screenshots of an app into a token file with colour roles and a type scale
- Checking text and background pairs for WCAG AA after a palette change
- Writing component specs including focus, disabled, loading, error and empty states
What Makes It Unique
It works in roles, so the brand step only changes values and keeps names. It lists what is never taken (logos, icons, illustrations, licensed fonts, copy, the brand colour) and gives open replacements, and its contrast script exits with an error so it can gate a build.
Under The Hood
contrast.py is a standard-library Python script. It reads your tokens JSON, computes WCAG 2 contrast ratios for each listed pair and exits with an error code on a failure. It makes no network calls. The skill’s instructions also have the agent read screenshots, write token and CSS files, edit the Tailwind config and build components in your project, so it reads and writes files and runs commands.