recreate-build
/recreate-build
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 /recreate-design.
- Author
- KomeilAsli ↗
- Repository
- recreate ↗
- Licence
- MIT
- Last repository change
- 05.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 05.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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 /recreate-design.
Triggers from the description
Original author description
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 /recreate-design.
How it works
- The rules
- Step 1: the shell
- Step 2: the vertical slice
- Step 3: screen by screen
- Definition of done, per screen
- Step 4: the build log
- When you are stuck on how something works
- Output
SKILL.md preview
--- name: recreate-build description: >- 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 /recreate-design. --- # recreate-build Reads `recreate/recon.md`, `recreate/architecture.md`, `recreate/design/`. Updates `recreate/features.csv` (the `clone` column) and keeps `recreate/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 recreate-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 recreate-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: 1. Read its row in the recon map: purpose, components, states, which flows pass through it. 2. Look at the reference screenshot for layout and hierarchy. Not for pixels. 3. Build it with the primitives. Real data from the data layer. 4. **Every state**: empty, loading (skeletons, not spinners, if the original does), filled, error, no permission, long content (a 60 character name), mobile width. 5. Basics, every time: semantic HTML, labels on inputs, keyboard reachable, visible focus, images with alt text. 6. Set the matching rows in `features.csv` to `yes` or `partial` (with a note). 7. Screenshot it at the same viewport as the reference into `recreate/clone-screens/S07.png` for recreate-diff. 8. One commit per screen: `build: S07 booking page`. ## Definition of done, per screen - [ ] every state from the recon map, plus empty, error and loading - [ ] works at 390px and 1440px wide - [ ] keyboard only: can complete the flow - [ ] no console errors - [ ] no hard-coded copy borrowed from the original - [ ] features.csv updated - [ ] screenshot saved for diff ## Step 4: the build log `recreate/build-log.md`, one line per screen: ID, date, done or partial, what is missing, what was harder than expected. When a feature is bigger than it looked, say so in the log and in the chat. Do not quietly ship half of it. ## When you are stuck on how something works Go back to the original as a user: read its help article, watch its public walkthrough, use the user's own account. Do not dig into its code or network calls. Then build your own version of the behaviour. ## Output Screens built, the feature matrix updated, screenshots saved, and a summary: screens done of total, must-haves done of total, what is next. Then `/recreate-backend` if the data layer is still fake, else `/recreate-test`. Then record the stage, so `/recreate-status` and every later skill know it happened: ```bash python3 recreate/u.py record build \ --summary "14 of 18 screens, all must-haves" \ --artifact build-log.md \ --artifact features.csv ```
Versions
The database has no other skills named recreate-build.
Database snapshot: 13.11.2026 · package version 942f8148ab3a (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90fxreplica-build
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… - 90replica-build
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… - 90replica-build
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… - 90replica-build
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… - 90replica-build
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… - 90replica-build
Rebuild an app clone screen by screen from the recon map: the shell first, then the core flow as a vertical slice, then every screen with all its states, ticking off the feature matrix, every line written fresh. Use for 'build the clone', 'build screen S07', 'start building',…