jakeschincariol/replica-skill

replica-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.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/jakeschincariol/replica-skill --skill replica-build

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

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.

  1. Look at the reference screenshot for layout and hierarchy. Not for pixels.
  2. Build it with the primitives. Real data from the data layer.
  3. Every state: empty, loading (skeletons, not spinners, if the original

does), filled, error, no permission, long content (a 60 character name), mobile width.

  1. Basics, every time: semantic HTML, labels on inputs, keyboard reachable,

visible focus, images with alt text.

  1. Set the matching rows in features.csv to yes or partial (with a note).
  2. Screenshot it at the same viewport as the reference into

replica/clone-screens/S07.png for replica-diff.

  1. 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.

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
jakeschincariol
コミュニティ

replica-backend

Builds the backend of an app clone: auth, database migrations and access rules, payments with Stripe, email, background jobs and third-party integrations through official APIs only, plus a security checklist. Use when the user says "add login", "set up auth", "wire up the database", "add payments", "connect Stripe", "add Google Calendar", "send emails", "backend for my clone", or when /replica-build is running on fake data.

1時間の導入数
1
GitHub Stars
1万
更新日
10月3日
jakeschincariol
コミュニティ

replica-design

Rebuilds an app's design system for a clone: colour roles, type scale, spacing, radius, shadows and every component with its states, as design tokens plus component specs, with original assets instead of the target's logos, icons, illustrations or licensed fonts. Includes a WCAG contrast checker. Use when the user says "match the design", "rebuild the design system", "get the colours and fonts", "make it look like X", "design tokens for my clone", or after /replica-architect.

1時間の導入数
1
GitHub Stars
1万
更新日
10月3日
jakeschincariol
コミュニティ

replica-entrepreneur

Researches the app being cloned and reads what its real users say in public reviews (App Store, Google Play, G2, Capterra, Trustpilot, Reddit, Hacker News, its own feature-request board), then ranks what they hate, what is missing and what is unsolved, turns it into a fix plan for the clone and a positioning angle you can sell. Every quote is real, verbatim and linked. Use when the user says "what do people hate about X", "read the reviews", "how do I make mine better", "find the gap", "what fea

1時間の導入数
1
GitHub Stars
1万
更新日
10月3日
jakeschincariol
コミュニティ

replica-launch

Writes the launch for an app clone: the landing page built on the positioning angle, pricing set against the original's public pricing and its users' complaints, and the App Store and Google Play listing linted against the stores' limits and copycat rules. Use when the user says "landing page", "pricing", "how much should I charge", "App Store listing", "store screenshots", "launch plan", "Product Hunt", or after /replica-brand.

1時間の導入数
1
GitHub Stars
1万
更新日
10月3日