replica-test
/replica-test
Test an app clone for bugs: a test plan from the recon flows with happy paths and edge cases (Cyrillic input, time zones, double submit, a second user's data), Playwright end-to-end specs, a click-through for the rest, and bug reports by severity until no S1 or S2 is open. Use for 'test my clone', 'find bugs', 'QA this', 'write e2e tests'; RU: протестируй, найди баги, тесты, проверь приложение.
- Author
- dmminga1983 ↗
- Repository
- minga-replica ↗
- Licence
- MIT
- Last repository change
- 28.10.2026
Assessment and security
- Files in this package
- 4
- Scripts
- 1
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 28.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 1 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: e2e.example.spec.ts
What it does and when to use it
Test an app clone for bugs: a test plan from the recon flows with happy paths and edge cases (Cyrillic input, time zones, double submit, a second user's data), Playwright end-to-end specs, a click-through for the rest, and bug reports by severity until no S1 or S2 is open. Use for 'test my clone', 'find bugs', 'QA this', 'write e2e tests'; RU: протестируй, найди баги, тесты, проверь приложение.
Triggers from the description
Original author description
Test an app clone for bugs: a test plan from the recon flows with happy paths and edge cases (Cyrillic input, time zones, double submit, a second user's data), Playwright end-to-end specs, a click-through for the rest, and bug reports by severity until no S1 or S2 is open. Use for 'test my clone', 'find bugs', 'QA this', 'write e2e tests'; RU: протестируй, найди баги, тесты, проверь приложение.
How it works
- The rule
- Step 1: the plan
- Step 2: automate
- Step 3: click through the rest
- Step 4: bugs
- Step 5: fix loop
SKILL.md preview
--- name: replica-test description: "Test an app clone for bugs: a test plan from the recon flows with happy paths and edge cases (Cyrillic input, time zones, double submit, a second user's data), Playwright end-to-end specs, a click-through for the rest, and bug reports by severity until no S1 or S2 is open. Use for 'test my clone', 'find bugs', 'QA this', 'write e2e tests'; RU: протестируй, найди баги, тесты, проверь приложение." --- # replica-test Reads the flows in `replica/recon.md`. Writes `replica/test-plan.md`, `replica/bugs.md` and specs in `e2e/` (templates in this folder). ## The rule **Test your clone, never the original.** No load testing, fuzzing or scripting against the original's servers. Using it by hand to see how it behaves is fine. ## Step 1: the plan For every flow: the happy path; the edge cases that apply (empty input, very long input, emoji, Cyrillic and accents, two tabs, double submit, back and refresh mid-flow, slow network, offline, expired session, a second user's data must be invisible, time zones and daylight saving, 390px, keyboard only, screen reader labels); the negative cases (wrong password, payment declined with the provider's test card, permission denied, deleted record). Number them: F01-H1, F01-E3, F01-N2. ## Step 2: automate Playwright, one spec per flow, against the local dev server with seed data, selectors by role and label. Every spec fails on console errors and on any 5xx, and runs an axe accessibility scan on each screen. ```bash npm i -D @playwright/test @axe-core/playwright && npx playwright install chromium npx playwright test ``` ## Step 3: click through the rest Emails arriving, real OAuth, payments end to end, visual glitches: a manual pass, with a browser tool on the local clone if one is available, screenshots per step, or a checklist for the user. ## Step 4: bugs `bugs.md` in the `bug-report.md` format. S1 data loss, security, payments, core flow blocked; S2 broken without a workaround; S3 with a workaround or visibly wrong; S4 cosmetic. Only what you reproduced; "might be" goes to a separate list. ## Step 5: fix loop S1 and S2 first. Failing test, fix, pass, keep the test, re-run the suite. Ship nothing with an open S1. Next: /replica-diff.
Files in this package (4)
- SKILL.md 2 KB
- bug-report.md 1 KB
- e2e.example.spec.ts 1 KB
- test-plan.md 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · dmminga1983/minga-replica | 95 | MIT |
| lucasouzadev/agent-kit-skill | 100 | MIT |
| letmefind/replica-skill-cursor-grok | 100 | MIT |
| letmefind/replica-skill-cursor-grok | 100 | MIT |
| jakeschincariol/replica-skill | 100 | MIT |
Database snapshot: 13.11.2026 · package version 5698f0964fea (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100fxreplica-test
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… - 100recreate-test
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… - 100test-flows
[Orbit 2.6.7 Quality checks] Walk the app's flows: test plan, Playwright e2e, bug reports with evidence. Use when: «протестируй приложение», «e2e», «playwright», «прогони сценарии»; e2e testing, test flows, browser testing. - 100swap-test
Tests the replacement by walking every in-scope flow, writing automated specs for the happy paths and the edge cases that bite (time zones, two people at once, double submit, empty and error states, permissions), and logging each bug by severity until no S1 or S2 remains open.… - 86e2e-test
Writes end-to-end tests for a user journey through the running app, Playwright preferred. Use when user requests e2e, end-to-end, Playwright, or Cypress tests. - 100replica
Runs the Replica pack in order: recon, architect, design, build, backend, test, diff, entrepreneur, brand, launch, deploy. Use when the user wants to clone an app, asks where to start, or asks which step is next. Each step reads what the previous one wrote under replica/.