replica-build
由 Jakeschincariol 提供的 replica-build Skill,包含安装方法、功能说明、完整指令和 GitHub 原文入口。
name: replica-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 /replica-design.
功能说明
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.
快速安装
npx skills add https://github.com/Jakeschincariol/replica-skill --skill replica-build
以上为基于原仓库和 Skill 名称整理的安装命令,未在本机执行;原文另有安装要求时以原文为准。
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:
- Read its row in the recon map: purpose, components, states, which flows pass through it.
- Look at the reference screenshot for layout and hierarchy. Not for pixels.
- Build it with the primitives. Real data from the data layer.
- Every state: empty, loading (skeletons, not spinners, if the original does), filled, error, no permission, long content (a 60 character name), mobile width.
- Basics, every time: semantic HTML, labels on inputs, keyboard reachable, visible focus, images with alt text.
- Set the matching rows in
features.csvtoyesorpartial(with a note). - Screenshot it at the same viewport as the reference into
replica/clone-screens/S07.pngfor replica-diff. - 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
replica/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
/replica-backend if the data layer is still fake, else /replica-test.
来源与许可
Jakeschincariol/replica-skill 提供此 Skill,适用 MIT。本版本追加了安装和访问入口,并将相对文档链接解析为 GitHub 地址;原始文件可从下方原文入口获取。
MIT License
Copyright (c) 2026 Jake Schincariol
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.