competitor-experience-audit
Audit the brand, UX, and site design of the leading sites in a vertical as a set of observable cross-site patterns, producing the experience bar a new build must meet or beat. Use this skill whenever the user wants to assess the competitive design field, capture vertical conventions, identify the design and UX bar of a category, or set the experience standard before a build. Triggers on competitor experience audit, UX audit, site design audit, brand audit, design conventions, what makes these sites good, vertical conventions, storefront patterns, merchandising patterns, layout density, primary
Profile →npx skills add rampstackco/claude-skills --skill competitor-experience-audit --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Competitor Experience Audit Capture the brand, UX, and site design that the leading sites in a vertical observably share, and where they fall short. The output is the experience bar a new build must meet or beat, grounded in cross-site patterns rather than aesthetic opinion. Stack-agnostic. Works on any SiteShape (ecommerce-catalog, inventory-listing, hospitality-food, b2b-manufacturer, and so on). Auto-parts catalogs are the first test case, not the only target. This skill is the brand / UX / design counterpart to a technical audit like `seo-onpage` or `accessibility-audit`. Technical findings are objective (a missing canonical is missing). Design is more subjective, so this skill is deliberately written to make the subjective assessable: every dimension is judged by observable questions about what the leading sites actually do, reported as patterns and gaps, and marked `not_assessable` whenever the evidence does not support a judgment. --- ## When to use - Setting the experience bar for a new build in a vertical you have not built in before - Capturing the design and UX conventions a credible site in the category is expected to carry - Auditing the competitive field for a criti
- When to use
- When NOT to use
- Required inputs
- Static vs rendered
- The framework: 7 experience dimensions
- 1. Primary-task prominence
- 2. Layout register and density
- 3. Merchandising and category surface
- 4. Primary navigation and search paths
- 5. Brand register and conviction
- 6. Trust and conversion signals
- 7. Recurring vertical conventions (the synthesis)
- The honesty guardrail (load-bearing)
- Workflow
What does the competitor-experience-audit skill do?
Audit the brand, UX, and site design of the leading sites in a vertical as a set of observable cross-site patterns, producing the experience bar a new build must meet or beat. Use this skill whenever the user wants to assess the competitive design field, capture vertical conventions, identify the design and UX bar of a category, or set the experience standard before a build. Triggers on competitor experience audit, UX audit, site design audit, brand audit, design conventions, what makes these sites good, vertical conventions, storefront patterns, merchandising patterns, layout density, primary
How do I install it?
Run `npx skills add rampstackco/claude-skills --skill competitor-experience-audit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.