competitive-analysis
Competitive-analysis is a Claude Code skill that systematically evaluates competitor products across UX patterns, features, information architecture, and interaction design. Use it when mapping the competitive landscape to identify design gaps, strategic opportunities, and best-in-class patterns within your category or adjacent domains. The skill delivers structured comparison matrices, competitor profiles, and opportunity maps based on full user journey analysis rather than isolated feature inventories.
git clone --depth 1 https://github.com/Owl-Listener/designer-skills /tmp/competitive-analysis && cp -r /tmp/competitive-analysis/ux-strategy/skills/competitive-analysis ~/.claude/skills/competitive-analysisSKILL.md
# Competitive Analysis You are an expert in evaluating competitive landscapes from a UX and design perspective. ## What You Do You systematically analyze competitor products to identify UX patterns, feature gaps, design strengths, and strategic opportunities. ## Analysis Framework ### 1. Competitor Identification - Direct competitors: same problem, same audience - Indirect competitors: same problem, different audience - Aspirational benchmarks: best-in-class from adjacent domains ### 2. Evaluation Dimensions Information architecture, interaction patterns, visual design, content strategy, performance, accessibility, mobile experience. ### 3. Feature Comparison Matrix For each key task: support level, steps required, UX quality (1-5), unique approaches. ### 4. Strengths, Weaknesses, Opportunities What each excels at, friction points, table-stakes patterns, unaddressed gaps. ## Deliverable Summary overview, comparison matrix, competitor profiles, opportunity map, annotated references. ## Best Practices - Focus on UX quality, not just feature presence - Analyze full journeys, not isolated screens - Update regularly as competitors evolve - Include aspirational examples from outside the category
Facilitate a structured team critique — framing, feedback rules, and actionable outcomes. Use when running a session with people in the room. For a solo expert review, use `heuristic-evaluation` (prototyping-testing).
Inventory and prioritise accumulated design inconsistencies across a product. Use when drift has built up over time. For token coverage specifically use `design-token-audit` (designer-toolkit); for WCAG gaps use `accessibility-audit` (design-systems).
Communicate design's contribution to business and user outcomes in stakeholder language. Use when reporting results upward. For choosing the metrics in the first place, use `metrics-definition` (ux-strategy).
Build a QA checklist for verifying that a build matches the design. Use at implementation review. For the spec engineers build from, use `handoff-spec`.
Establish review gates — criteria, checkpoints, and approval flow. Use when work ships without consistent review. For running one individual session, use `design-critique`.
Plan and facilitate a design sprint from challenge framing through prototype testing. Use when compressing discovery into days. For ongoing team cadence, use `team-workflow`.
Write the implementation handoff — measurements, behaviours, assets, states, and edge cases. Use when engineering picks up the work. For verifying the result afterwards use `design-qa-checklist`; for reusable library components use `component-spec` (design-systems).
Design the team's operating rhythm — task management, collaboration rituals, and tooling. Use when the day-to-day cadence needs structure. For a time-boxed sprint, use `design-sprint-plan`.