replica-test
/replica-test
Testuje klon aplikacji przez przeklikanie przepływów: scenariusze szczęśliwe i brzegowe, testy Playwright oraz raporty błędów z dowodami.
- Autor
- lucasouzadev ↗
- Repozytorium
- agent-kit-skill ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 12.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 5
- Skrypty
- 1
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 1
Brak sygnałów. Repozytorium zmienione 12.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- 1 skrypt w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: e2e.example.spec.ts
Co robi i kiedy
Testuje klon aplikacji przez przeklikanie przepływów: scenariusze szczęśliwe i brzegowe, testy Playwright oraz raporty błędów z dowodami.
Wyzwalacze z opisu
Oryginalny opis (EN)
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.
Jak działa
- The rule
- Step 1: the plan
- Step 2: automate what you can
- Step 3: click through the rest
- Step 4: report bugs
- Step 5: fix loop
- Output
Podgląd SKILL.md
---
name: replica-test
description: >-
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.
---
> Imported from [Jakeschincariol/replica-skill](https://github.com/Jakeschincariol/replica-skill) @ 77c9436 (MIT, see `LICENSE.txt` here). In agent-kit repos `AGENTS.md` and `docs/agents/standard/TRACK.md` take precedence: approval gate, evidence states, self-heal envelope, caveman output. Clean-room only: rebuild what an app does, never its code, logo, copy or content.
# replica-test
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`.
## The rule
**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.
## Step 1: the plan
For every flow F01, F02... in the recon map, write:
- **Happy path**: the steps, and what the user should see at the end.
- **Edge cases** that apply. Go down this list for every flow:
empty input, very long input, emoji and accents, two tabs at once,
double click on submit, back button mid-flow, refresh mid-flow, slow
network, offline, expired session, second user's data (must be invisible),
time zones and daylight saving, mobile width, keyboard only, screen reader
labels.
- **Negative cases**: wrong password, card declined (Stripe test card
`4000 0000 0000 0002`), permission denied, deleted record.
Number every case: F01-H1, F01-E3, F01-N2.
## Step 2: automate what you can
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`.
```bash
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.
## Step 3: click through the rest
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.
## Step 4: report bugs
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.
## Step 5: fix loop
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.
## Output
`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`.
Pliki w paczce (5)
- LICENSE.txt 1 KB
- SKILL.md 4 KB
- bug-report.md 1 KB
- e2e.example.spec.ts 2 KB
- test-plan.md 1 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · 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 |
| dmminga1983/minga-replica | 95 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 0a9e1d7969e3 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100fxreplica-test
Przeklikuje przepływy klonu aplikacji, tworzy plan testów, testy end-to-end w Playwright oraz raporty błędów. - 100recreate-test
Przechodzi wszystkie przepływy klonu, tworzy plan testów z przypadkami brzegowymi i raporty błędów z dowodami oraz poziomem wagi. - 100replica
Prowadzi kolejno pakiet Replica: od analizy wzorca po budowę, testy, markę i wdrożenie. - 100replica
Prowadzi kolejno pakiet Replica: od analizy wzorca po budowę, testy, markę i wdrożenie, gdy użytkownik pyta, od czego zacząć. - 100replica-recon
Opracowuje mapę ekranów, przepływów i modelu danych aplikacji na podstawie stron pomocy, zrzutów i własnego konta, do budowy własnej wersji. - 100replica-architect
Planuje stos, schemat bazy i API dla klonu aplikacji na podstawie wcześniejszej analizy, wybierając proste, zarządzane technologie.