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
Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.
Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).
Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction. Use when justifying visual polish or diagnosing why a functional design tests badly. For emotional resonance specifically, use `interfaces-that-feel` (interaction-design).
Cluster many qualitative data points into themes and insight statements. Use when synthesising across multiple sessions or sources. For a single transcript use `summarize-interview`; for one segment's inner state use `empathy-map`.
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use `motion-system` (design-systems); for a full interaction spec use `micro-interaction-spec`.
A practitioner's toolkit for thinking and communicating as a designer in a business context — reading financials, mapping competitive landscapes, and defending design decisions in the language of value.
Analyse open or closed card sort results into a proposed grouping and label set. Use after running a sort study. For turning that evidence into a full structure, use `information-architecture` (ux-strategy).