rampstackco/claude-skills / skills/vertical-site-conventions
vertical-site-conventions
VerifiedCompose 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.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 366 B |
| SKILL.md | skill md | 18.7 KB |
| references/shape-b2b-manufacturer.md | markdown | 14.4 KB |
| references/shape-conventions-checklist.md | markdown | 6.3 KB |
| references/shape-directory-marketplace.md | markdown | 1.5 KB |
| references/shape-ecommerce-catalog.md | markdown | 12.7 KB |
| references/shape-ecommerce-standout.md | markdown | 1.8 KB |
| references/shape-hospitality-experience.md | markdown | 1.7 KB |
| references/shape-hospitality-food.md | markdown | 10.7 KB |
| references/shape-institution-mission.md | markdown | 1.9 KB |
| references/shape-inventory-listing.md | markdown | 1.5 KB |
| references/shape-local-service-booking.md | markdown | 11.0 KB |
| references/shape-subscription-app.md | markdown | 1.5 KB |
references/shape-institution-mission.md
View on GitHub# Shape: institution-mission
Nonprofits, museums, foundations, public-interest organizations. The reader arrives wanting to understand what the institution does and decide whether to give, attend, volunteer, or read further.
## Status
Stub. Fill when the first institution-mission 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:** depends on the moment. Donate during a campaign; visit / attend for an institution with a physical presence; sign up or read for a research or advocacy group. The hero CTA matches the institution's primary ask.
- **Layout register:** editorial-considered. More text than a catalog, less than a long-form publication. Trust load is heavy; expressive maximalism is rare in this shape.
- **Merchandising:** the cause or mission is the merchandising. Programs, impact, and recent work carry the page.
- **Paths:** by program primary; by impact / outcomes primary for established institutions; news / press / blog secondary; financials / 990 secondary but conventional for nonprofits.
- **Brand register:** institutional, considered, mission-led. Premium-considered for arts and culture; restrained-authoritative for advocacy.
- **Trust signals:** mission statement, board / leadership, financial transparency (for nonprofits, the 990 or audit), accreditations, named donors or partners, recent impact numbers with sources.
- **Synthesis (provisional):** mission statement above the fold, a clear primary ask (donate, attend, sign up), program or impact surface, leadership and governance reachable from the chrome, financial transparency linked (for nonprofits), no over-emotive imagery that reads as manipulative.
Until this shape is built into a demo, treat the above as observation defaults to verify against an audit, not as ship-ready conventions.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |