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 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 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:

  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

모든 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일