replica-build turns the recon map, architecture plan and design tokens into working screens. It builds the app shell first, then the core flow end to end, then each remaining screen in the order the architecture sets.
Every line is written fresh. The skill never pastes the original’s code, assets or copy, and when it is stuck it goes back to the original as a user, using help articles and your own account.
What You Get
- An app shell with routing for every screen, layout, tokens wired in and seed data
- A working vertical slice of the core loop, on a fake data layer if the backend is not built yet
- Each screen with empty, loading, filled, error, no-permission and long-content states
- Rows in
features.csvset to yes or partial, plus a screenshot per screen for the diff step - A
replica/build-log.mdwith one line per screen
Common Use Cases
- Building a clone screen by screen from a recon map
- Keeping a feature matrix current as screens are finished
- Capturing reference-sized screenshots to feed a parity comparison
What Makes It Unique
It carries a per-screen definition of done: every state, 390px and 1440px widths, keyboard-only completion, no console errors and no borrowed copy. It also bans raw hex or pixel values in components, so every value traces to a token.
Under The Hood
The skill is instructions only. The agent writes source code into your project, makes one git commit per screen, updates the feature CSV and build log, and saves screenshots, which means it writes files and runs git and build commands. It tells the agent to read the original app’s help articles and public walkthroughs as a user, but not its code or network calls.