Wreck Personas

Derive realistic user personas (the app's ideal customers plus built-in normal-user, rushed-beginner and chaos-monkey) and their missions for wreck-it testing, saved to .wreck-it/personas.md. Use as stage 3 of a wreck-it run, or when the user asks "who would use my app", "make test personas", or wants to edit the personas used for testing.

Testing & QA Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add miyannishar/wreck-it

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add miyannishar/wreck-it --skill wreck-personas
Manual install
git clone --depth 1 https://github.com/miyannishar/wreck-it.git /tmp/wreck-it
mkdir -p ~/.claude/skills
cp -r /tmp/wreck-it/skills/wreck-personas ~/.claude/skills/wreck-personas

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# wreck-personas

`WRECK` means `npx @miyanishar/wreck-it`.

Output: `.wreck-it/personas.md`. The user may edit this file. If it already exists, **reuse it unchanged** and just summarize it. Regenerate only when the user asks.

## Inputs

Read these. Skim them, don't study them.
- `README*`, landing/home page copy (open the home page in the browser), `package.json` description
- `.wreck-it/discovery.json`: pages, API routes, forms, auth
- The database schema, if one exists (`prisma/schema.prisma`, `drizzle/`, `supabase/migrations`, `models/`, SQL files). Entity names reveal what users actually do.

## Write 2–3 ICP personas

Base each on who the product is clearly for. Give each one these fields:

```markdown
## <slug, e.g. busy-freelancer>
- **Who:** one line
- **Goal:** what they came to do
- **Tech-savviness:** low | medium | high
- **Patience:** low | medium | high   (low = abandons after ~2 failed attempts or 10 s spinners)
- **Device/viewport:** desktop 1280x800 | mobile 390x844 | tablet 820x1180
- **Network:** fast | slow-3g | flaky
- **Priority features:** routes/flows they care about (use real routes from discovery)
- **Missions:**
  1. "<concrete task phrased like a user, e.g. Sign up and create your first invoice for $120>"
  2. …(3–5 missions, mixing core flows with the persona's priority features)
```

## Always add the built-ins
Read the full skill on GitHub

Details

Skill name
wreck-personas
Path
skills/wreck-personas/SKILL.md
License
MIT
Repo updated
25 October 2026

FAQ

What does the Wreck Personas skill do?

Derive realistic user personas (the app's ideal customers plus built-in normal-user, rushed-beginner and chaos-monkey) and their missions for wreck-it testing, saved to .wreck-it/personas.md. Use as stage 3 of a wreck-it run, or when the user asks "who would use my app", "make test personas", or wants to edit the personas used for testing.

How do I install the Wreck Personas skill?

Claude Code plugin: /plugin marketplace add miyannishar/wreck-it. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Related skills

Wreck Chaos

miyannishar/wreck-it

Chaos-test a running local web app as the chaos-monkey persona, using a page sweep, an API fuzzer (plus Schemathesis when there's an OpenAPI spec), hostile form inputs, double-submits, back/forward/refresh mid-flow, multiple tabs, offline/slow/500-injected network, expired or tampered sessions, an axe-core scan and keyboard-only navigation. Records reproducible bugs with wreck-it. Use as stage 6 of a wreck-it run, or when the user asks to "break my forms", "chaos test", "try weird inputs", "test offline", or "check accessibility".

Testing & QAIn 1 list

Wreck Explore

miyannishar/wreck-it

Explore a running local web app through Playwright MCP as a normal user (every core flow plus data-integrity checks) and then in character as each persona from .wreck-it/personas.md, recording reproducible bugs with wreck-it. Use as stages 4–5 of a wreck-it run, or when the user asks to "click through my app like a user", "test the happy paths", "try my app as a beginner", or "check my core flows".

Testing & QAIn 1 list

Wreck It

miyannishar/wreck-it

Full wreck-it run against a locally running web app. It tests like normal users, ICP personas, rushed beginners, chaos monkeys and traffic spikes, then writes a scored bug report with source file:line and regression Playwright tests. Use when the user says "wreck my app", "wreck it", "test my app like a user", "find bugs before launch", "is my app ready to ship", or asks for a readiness score. Also for one feature, such as "test the checkout", "just test signup", "check the coupon flow" (a focused run). For a single stage ("just stress test my API", "only check accessibility"), use the matchin

Testing & QAIn 1 list

Smoke

danybgoode/golden-frijoles

Verifies real, rendered behavior on this project's frontend (local/preview/staging/prod, unauthed or authed) via a real headless-Chromium Playwright browser — the DEFAULT way to check "does this render correctly / does this look right / is this actually live" for any coding agent, not just Claude Code. Use when asked to "smoke test", "verify the live/prod page", "check if X actually rendered", "run a browser smoke", "does this look right on preview", "verify an authed role's flow", or as a post-merge/pre-PR verification step. Wraps the project's scripts/live-smoke.mjs — a real screenshot + JSO

Testing & QAIn 1 list

Wreck Load

miyannishar/wreck-it

Page speed and load testing for a local web app with the wreck-it CLI. It measures each page with Lighthouse on a simulated phone (LCP, CLS, TBT), diagnoses slow pages with Chrome DevTools performance traces when available, runs ramp, spike and soak load profiles (p50/p90/p99 latency, error rate, breaking point, memory trend), then traces slow endpoints to causes such as N+1 queries, missing indexes or blocking work. Use as stage 7 of a wreck-it run, or when the user asks to "stress test my API", "load test", "how many users can my app handle", "find slow endpoints", "check page speed", or "ru

Testing & QAIn 1 list

Prove It Ran

agentkitco/agentkit-dev-skills

Verify that tests, builds and checks actually ran and exercised the changed code, before claiming a task is done. Use before reporting completion, or when asked to prove tests ran or verify a fix.

Testing & QAIn 1 list

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.