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-subscription-app.md

View on GitHub
# Shape: subscription-app

Weather apps, productivity tools, news readers, fitness trackers, language learning. The reader arrives wanting to understand the app and decide whether to install or subscribe.

## Status

Stub. Fill when the first subscription-app 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:** install (App Store / Play Store buttons) or start trial. The download or trial CTA is the hero.
- **Layout register:** marketing-led with strong product imagery (device frames, screen captures). Editorial-airy is common.
- **Merchandising:** features as a vertical scroll of capability sections; not a catalog grid.
- **Paths:** by feature primary (scroll); pricing secondary (navigable but not first); blog / support tertiary.
- **Brand register:** wide range. Consumer apps lean expressive or playful; productivity leans considered or technical.
- **Trust signals:** App Store rating, install count, press logos, customer testimonials, screenshots that read as the actual product.
- **Synthesis (provisional):** install CTAs (real store buttons) in the hero and chrome, feature-by-feature scroll with real product imagery, pricing surfaced clearly with the free / paid line drawn, App Store rating and review count surfaced, no fake screenshots.

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: 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