Turn documented app journeys into a test plan covering normal use, edge cases, and failures. Run automated browser tests where possible, check remaining steps manually, and record reproduced bugs with severity, evidence, and fix status.
中文简介正在准备中。当前显示英语简介。
Clicks through every flow of an app clone and tests it for bugs: a test plan generated from the recon flows with happy paths and edge cases, Playwright end-to-end tests where possible, a browser click-through where not, and bug reports in a fixed format with severity, steps and evidence. Use when the user says "test my clone", "find bugs", "QA this", "click through everything", "write e2e tests", "does it work", or after /replica-build or /replica-backend.
安装前可以查看交给 AI 代理的指令内容。
Reads the flows in replica/recon.md. Writes replica/test-plan.md,
replica/bugs.md, and end-to-end tests in the project (e2e/). Templates in
this folder: test-plan.md, bug-report.md, e2e.example.spec.ts.
Test your clone, not the original. Never load test, fuzz, script or hammer the original app's servers. Using the original by hand, as a normal user, to see how it behaves is fine.
For every flow F01, F02... in the recon map, write:
4000 0000 0000 0002), permission denied, deleted record.Number every case: F01-H1, F01-E3, F01-N2.
Playwright, one spec per flow, against the local dev server with seed data.
Use roles and labels for selectors (getByRole('button', { name: 'Book' })),
never CSS classes. See e2e.example.spec.ts.
npm i -D @playwright/test && npx playwright install chromium
npx playwright test
Add to every spec: fail on console errors, fail on any 5xx response, and an
axe accessibility scan (@axe-core/playwright) on each screen.
What cannot be automated (emails arriving, OAuth with real providers, payments end to end, visual glitches) gets a manual pass. If a browser tool is available, drive the local clone with it and screenshot each step. Otherwise give the user the checklist and wait for answers.
Every bug goes in replica/bugs.md in the bug-report.md format: an ID, a
severity, exact steps, expected, actual, evidence. Severity:
| means | |
|---|---|
| S1 | data loss, security hole, payments wrong, core flow blocked |
| S2 | a feature broken, no workaround |
| S3 | broken with a workaround, or visibly wrong |
| S4 | cosmetic |
Only report what you reproduced. "Might be an issue" goes in a separate "to check" list.
Fix S1 and S2 first. For every fix: write the failing test first, fix, watch
it pass, keep the test. Re-run the whole suite after each batch. Update
bugs.md with the commit that fixed each one.
test-plan.md, the specs, bugs.md, and a summary: cases run, passed,
failed, bugs by severity, fixed so far. Ship nothing with an open S1. Next:
/replica-diff.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Turn research about an existing app into a technical plan for a new implementation. Choose technologies, define database tables and access rules, map API routes, and order development around a small, complete core workflow.
中文简介正在准备中。当前显示英语简介。
Build the backend for an app modeled on an existing service, including login, database access rules, Stripe test payments, email, and integrations through official APIs. Track implementation and security checks in a dedicated checklist.
中文简介正在准备中。当前显示英语简介。
Develop an app’s own identity through name candidates, a distinct color palette, a logo brief, and writing guidance. Track name screening checks and scan project files for leftover names, domains, and colors from the original app.
中文简介正在准备中。当前显示英语简介。
Implement an app screen by screen from research and design documents, starting with its core workflow. Write fresh code and interface text, cover loading and error states, and track progress with a feature matrix and screenshots.
中文简介正在准备中。当前显示英语简介。
Prepare and publish an app built from an existing reference, covering release checks, production services, domain and email records, payments, sign-in, monitoring, and mobile distribution. It records results and requires user approval before going live.
中文简介正在准备中。当前显示英语简介。
Rebuild an app’s visual system as reusable design values and component specifications. It covers typography, spacing, component states, implementation, and contrast checks while replacing the original app’s branded assets with independent alternatives.
中文简介正在准备中。当前显示英语简介。