All skills
jakeschincariol avatar

/replica-build

@77c9436
by Jake Schincarioljakeschincariol/replica-skill995 stars
123

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.

Requires /replica-backend /replica-test
Use this Skill: https://skilld.dev/gh/jakeschincariol/replica-skill/replica-build

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈108 tokens for metadata: the name and description. ≈809 when used: this file.

Description uses 5.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈434 characters, or 5.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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:

  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 replica/clone-screens/S07.png for replica-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

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.

Source: SKILL.md on GitHub

Skill behaviors

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

Third-party checks

No alerts4d3 checks · Risk SAFE
  • Gen Agent Trust Hub4d

    The replica-build skill automates application rebuilding from design specifications and reconnaissance maps. While it incorporates 'clean room' protocols to avoid direct copying of assets, it is vulnerable to indirect prompt injection because it processes untrusted external design data to generate application code without explicit boundary markers or input sanitization.

  • Socket4d

    No alerts

  • Snyk4d

    Risk: LOW · No issues

Provenance

Signed by skilld at 77c9436. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 45 minutes ago.

Activeupdated 5 days ago

README badge

README badge for jakeschincariol/replica-skill/replica-build