Replica Build
Rebuilds an app screen by screen from the recon map: app shell first, then the core...
Install
npx skills add Jakeschincariol/replica-skill --skill replica-build -g -a claude-code -y- Repository
- Jakeschincariol/replica-skill7k
- Category
- Design
- Updated
- 1mo ago
- License
- MIT
- Context cost
- Lightabout 808 tokens
- Runs scripts
- No, instructions only
What it does
Rebuilds an app screen by screen from the recon map: app shell first, then the core flow as a vertical slice, then every screen with all its states, ticking off the feature matrix as it goes. Writes every line fresh, never the original's code, assets or copy. Use when the user says "build the clone", "build screen S07", "start building", "rebuild this screen", "implement the booking page", or after /replica-design.
replica-build
Reads replica/recon.md, replica/architecture.md, replica/design/.
Updates replica/features.csv (the clone column) and keeps
replica/build-log.md.
The rules
- Clean room. Every line of code is written here, from the recon map and the specs. Never paste the original's HTML, CSS, JavaScript, SVGs or images, never load anything from its domain or CDN, never "view source and adapt".
- Your words. Write every label, button, empty state and email fresh. Matching what a button does is parity. Matching its sentence is copying.
- Tokens only. No raw hex or pixel values in components. If a value is missing, add it to the tokens.
Step 1: the shell
Routing for every screen in the inventory (stub pages are fine), the layout (nav, header, sidebar), tokens wired in, the primitives from replica-design, and seed data so screens have something real to show. Commit.
Step 2: the vertical slice
The core loop from the recon map, end to end, before anything else. For a booking app: create an event type, open the public page, book a slot, see it on the dashboard. Ugly is fine. Working is the point. If replica-backend has not run yet, use the seed data and a fake data layer with the same function signatures, so swapping in the real one changes no screen code.
Step 3: screen by screen
Work in the order of architecture.md. For each screen:
