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-ecommerce-standout.md

View on GitHub
# Shape: ecommerce-standout

Single-product or narrow-line ecommerce where the brand and the object carry the page. Premium boots, designer goods, single-product subscriptions, expressive consumer brands. The reader arrives because of the brand, not because of a category need.

## Status

Stub. Fill when the first ecommerce-standout 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:** see the product (image-led), see the story (brand-led), buy. Hero often carries large product photography or a brand statement.
- **Layout register:** expressive or premium-considered. The opposite of a dense catalog; air and image carry the load.
- **Merchandising:** one product line, surfaced as a few SKUs or one product with options. The product story is the merchandising; spec lists are short.
- **Paths:** by SKU or by product secondary (the catalog is small); by story / about primary; press or recognition often surfaced; size / fit guides important.
- **Brand register:** expressive-maximalist or premium-considered. Cross-reference `creative-direction`; this shape is where strong register choices land.
- **Trust signals:** materials, where-made, founder story, press, reviews focused on quality and longevity, return policy generous and visible.
- **Synthesis (provisional):** large product photography in the hero, brand story or founding line surfaced early, size / fit / materials guide reachable, press logos if they exist, reviews emphasizing quality and longevity (not quantity), generous and clearly stated return policy.

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