Skip to content

rampstackco/claude-skills / skills/vertical-site-conventions

vertical-site-conventions

Verified

Compose pages and sites that read as their vertical: ecommerce-catalog storefronts that look like storefronts, hospitality-food sites that look like restaurants, b2b-manufacturer sites that look industrial. Use this skill whenever the user wants to build a site that looks like the vertical it serves, fix a build that reads as generic or off-vertical, build to an experience bar produced by competitor-experience-audit, or compose pages with the merchandising, density, and layout conventions a credible site in the category is expected to carry. Triggers on vertical conventions, storefront layout, ecommerce layout, retail conventions, merchandising layout, category page composition, site composition, build to the experience bar, make it look like the vertical, off-vertical, looks generic, build conventions for a vertical, site grammar. Also triggers when a build that is technically clean reads wrong for its category, and the cause is composition, not visual taste.

references/shape-directory-marketplace.md

View on GitHub
# Shape: directory-marketplace

Service-provider directories, home services marketplaces, freelance / contractor matching. The reader arrives wanting to find a provider for a need they can name.

## Status

Stub. Fill when the first directory-marketplace demo is built, or when a `competitor-experience-audit` for one has produced an experience bar.

## Provisional conventions (until filled from a real audit)

- **Primary task:** describe the need (service, location, urgency) and surface ranked providers. Often a wizard pattern (service picker, then ZIP, then refine).
- **Layout register:** trust-led and service-led. Photos of providers, ratings, and quoted response time carry the page.
- **Merchandising:** the provider list is the merchandising. Hero often carries a service-picker plus a band of top categories.
- **Paths:** by service category primary; by location primary; by provider (named) secondary.
- **Brand register:** marketplace-neutral or strongly opinionated (premium-curated vs widest-net). Cross-reference `creative-direction`.
- **Trust signals:** verified, licensed, insured, response time, ratings with review count, dispute resolution promise.
- **Synthesis (provisional):** service picker as the first interaction, location capture early, provider ratings with substantive review counts, response-time signal, clarity on what is curated vs open.

Until this shape is built into a demo, treat the above as observation defaults to verify against an audit, not as ship-ready conventions.
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: 472kUpdated 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: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated 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