Skip to content

rampstackco/claude-skills / skills/competitor-experience-audit

competitor-experience-audit

Verified

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 task, design bar, category conventions, retail vs marketing register, what does the field do. Also triggers when an audit of the competitive field has captured technical signals (SEO, accessibility) but never named the brand, UX, or design conventions, and the build downstream will read as off-vertical without that bar.

FileKindSize
README.mdmarkdown368 B
SKILL.mdskill md14.1 KB
references/audit-template.mdmarkdown4.6 KB
references/experience-dimensions-checklist.mdmarkdown7.0 KB

references/audit-template.md

View on GitHub
# Competitor Experience Audit: [Vertical]

**Site shape:** [ecommerce-catalog / inventory-listing / directory-marketplace / local-service-booking / subscription-app / hospitality-food / institution-mission / b2b-manufacturer / ecommerce-standout / hospitality-experience]
**Audit date:** [YYYY-MM-DD]
**Auditor:** [Name]
**Field assessed:** [N sites]
**Rendered:** [N of N] **Static-only:** [N of N]

---

## Field surveyed

| Site | Rendered | Notes |
|---|---|---|
| [Site 1] | [yes/no] | [any access caveat] |
| [Site 2] | [yes/no] | |
| [Site 3] | [yes/no] | |
| [Site 4] | [yes/no] | |
| [Site 5] | [yes/no] | |

If publishing the audit publicly, prepare a generalized version that drops the named column; the named version stays operated-side.

---

## Summary

[Two to three sentences. The cross-site picture: what the field converges on, where it falls short, what the positioning opportunity is. Generalized; no aesthetic verdicts.]

| Dimension | Score | One-line pattern |
|---|---|---|
| Primary-task prominence | [Pattern present / Mixed / Gap / Not assessable] | |
| Layout register and density | | |
| Merchandising and category surface | | |
| Primary navigation and search paths | | |
| Brand register and conviction | | |
| Trust and conversion signals | | |
| Recurring vertical conventions | | |

---

## Cross-site patterns

### 1. Primary-task prominence

[What the field converges on as the primary task; what element carries it; how protected the task is from competing CTAs. Observable signal: what is the largest, earliest interactive element, and what is the click count to the core task.]

**Pattern:** [The field's convention]
**Outliers:** [Any leader that breaks the pattern, and what they do instead]

### 2. Layout register and density

[The register the field shares (retail-dense, editorial, marketing-airy, hybrid). Cross-reference `creative-direction` aesthetic positions for vocabulary.]

**Pattern:** [The field's register]
**Outliers:** [Any leader that uses a different register]

### 3. Merchandising and category surface

[How much of the offering is surfaced before scroll; the navigation depth pattern; mega-menu vs grid vs side rail.]

**Pattern:**
**Outliers:**

### 4. Primary navigation and search paths

[Which paths the field offers (search-first, by-category, by-brand, by-attribute, by-vehicle, by-location). Score each path as primary / secondary / absent.]

**Pattern:**
**Outliers:**

### 5. Brand register and conviction

[The brand posture the leaders converge on. Cross-reference `creative-direction` and `brand-archetype-system`.]

**Pattern:**
**Outliers:**

### 6. Trust and conversion signals

[Which signals appear across the field (reviews, guarantees, pricing transparency, stock, fitment confirmation, return policy). Where they appear.]

**Pattern:**
**Outliers:**

### 7. Recurring vertical conventions

[The synthesis. The conventions a credible site in this vertical is expected to have, named explicitly. A build that ignores these will read as off-vertical.]

**Conventions:**
- [Convention 1]
- [Convention 2]
- [Convention 3]
- ...

---

## Gaps (the positioning opportunity)

[Where even the leaders fall short. The recurring weakness across the field. This is the wedge a new build's positioning can exploit. Observable, not speculative.]

- **[Gap 1]:** [The weakness the field shares; how it shows up across N of the N leaders; what a build that fixes it would look like.]
- **[Gap 2]:**
- **[Gap 3]:**

---

## The experience bar (the build standard)

A credible build in this vertical, against this field, must:

- [Bar item 1 - usually maps to a recurring convention from dimension 7]
- [Bar item 2]
- [Bar item 3]
- ...

Optional positioning move:

- [The build's wedge - exploit one or more of the gaps above]

Hand this bar to `creative-direction`, `design-standards`, `information-architecture`, and the relevant build skill so they read as the standard to meet, not as suggestions.

---

## Not assessable

[Dimensions or sites that could not be judged honestly. Common reasons: site not renderable, motion not capturable, brand voice not derivable from a single page, depth of the category surface only visible after authentication.]

- **[Dimension or site]:** [Why it cannot be judged from the evidence available. What evidence would be needed to assess it.]
- **[Dimension or site]:** 
- ...

---

## Generalized version (for showcase / public use)

If this audit will feed a public showcase workup or a published critique, copy the sections above into a generalized form that drops the named-competitor column and the Outliers callouts. Patterns and gaps are publishable; named-and-rated competitor breakdowns are not. The named version stays operated-side.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall