test-write
Write Tests
Generate tests that catch real bugs and survive refactors. Every test should answer: what behavior breaks if this test fails?
Step 1: Read the Code
Before writing any test, understand the code under test. If the user provides a file or function, read it first.
| What to identify | Why it matters | Watch out for |
|---|---|---|
| Inputs | These become your test parameters | Assuming only happy-path inputs |
| Outputs / return values | These are your assertions | Testing internal state instead of outputs |
| Side effects | These need mocking or verification | Missing async side effects, event emissions |
| Edge cases | These are where bugs hide | null, undefined, empty arrays, boundary values, concurrent calls |
| Error paths | These need explicit test coverage | Only testing success cases |
Step 2: Determine Test Type
Match the code to the right kind of test.
More from kazdenc/builder-skills
design-brief
One-time setup that gathers design context for your project and saves it to your config file. Run once to establish persistent design guidelines.
30prd
Write a product requirements document from context. Covers problem statement, goals, scope, user stories, success criteria, and edge cases. Use when user says "write a PRD", "product requirements", "requirements doc", "spec this feature", "document requirements", or needs to define what to build and why.
17critique
Evaluate design effectiveness from a UX perspective. Use when user says "critique this design", "review the UX", "give design feedback", "is this good design", "design review", "evaluate this layout", or wants expert evaluative feedback on visual hierarchy, information architecture, and emotional resonance.
14security-scan
Check code for OWASP top 10 vulnerabilities including injection, XSS, auth issues, and secrets exposure. Use when user says "security audit", "check for vulnerabilities", "security scan", "is this secure", "OWASP check", "find security issues", or needs to verify code security before shipping.
13polish
Final quality pass before shipping. Fixes alignment, spacing, consistency, and detail issues. Use when user says "polish this", "final pass", "ready to ship", "fix the details", "pixel-perfect", "almost done", or when a feature is functionally complete but needs refinement.
13api-design
RESTful API design conventions covering URL structure, HTTP methods, error formats, pagination, versioning, and authentication patterns. Use when designing, reviewing, or implementing APIs. Triggers on API design, endpoint structure, REST conventions, or backend architecture tasks.
12