competitive
Competitive Analysis
Work through these five steps in order. Each builds on the previous one.
Step 1 — Identify Competitors
Sort every competitor into one of three buckets:
| Type | Definition | How to find them |
|---|---|---|
| Direct | Solves the same job with a similar product | Search the category name, check review sites, ask users "what else did you consider?" |
| Indirect | Solves the same job with a different approach | Ask "how did people do this before products like ours existed?" |
| Substitutes | Competes for the same budget, time, or attention | Ask "what would they do instead of solving this job at all?" |
Include "do nothing" as a substitute — it is always the strongest competitor.
List 3–7 competitors. More than that dilutes focus.
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