Design patterns for website sections — heroes, cards, CTAs, trust signals, testimonials. Principle-based patterns that avoid AI-generated aesthetics. Pair with web-design-methodology for implementation.
Generates principle-based website sections like heroes and CTAs that avoid AI-generated aesthetics and match business context.
npx claudepluginhub jezweb/claude-skillsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/card-patterns.mdreferences/cta-patterns.mdreferences/hero-patterns.mdreferences/testimonial-patterns.mdreferences/trust-signals.mdPrinciple-based patterns for designing website sections that feel human-designed, not AI-generated. Each pattern teaches WHY and WHEN, not just templates to copy.
Well-designed website sections: heroes, card layouts, CTAs, trust signals, and testimonials that match the business context and avoid the "AI skeleton" look.
| Building this... | Read this reference |
|---|---|
| Homepage hero, page headers, landing pages | references/hero-patterns.md |
| Service cards, team grids, pricing tiers, portfolios | references/card-patterns.md |
| Conversion sections, buttons, banner CTAs | references/cta-patterns.md |
| Credibility: badges, licences, reviews, guarantees | references/trust-signals.md |
| Customer reviews, social proof, quote sections | references/testimonial-patterns.md |
Load on demand — don't read all five for every project. Read the one(s) relevant to the current section.
These apply to ALL patterns. Internalise these before reading any reference file.
The "AI skeleton" that signals template-generated design:
Non-negotiable across all patterns:
On lead-gen sites (no real business data), NEVER fabricate:
Safe alternatives for lead-gen:
The same section type looks completely different for different businesses:
| Business type | Design feel |
|---|---|
| Emergency services | Direct, immediate, phone-first |
| Luxury/hospitality | Spacious, refined, atmospheric |
| Trades/local services | Trustworthy, capable, genuine |
| Professional/corporate | Confident, clean, structured |
| Creative/agency | Distinctive, bold, personality-driven |
Image-dominant (strong photography available):
Typography-dominant (no strong imagery):
Split/balanced (strong copy + strong imagery):
Match CTA urgency to business context:
Golden rule: Make your case first, then ask for action. CTA appears AFTER value.
| Tier | Type | Example |
|---|---|---|
| 1 (Strongest) | Specific, verifiable | "QBCC License #1234567" |
| 2 | Third-party validation | "4.8 stars (127 Google Reviews)" + link |
| 3 | Self-claimed | "Fully licensed and insured" |
| 4 (Weakest) | Generic assurances | "Quality guaranteed" |
One Tier 1 signal beats three Tier 4 signals. Distribute trust throughout the page — don't isolate in one section.
| Situation | Approach |
|---|---|
| One powerful testimonial | Single featured quote, make it big |
| 3-6 good testimonials | Grid with variety, one featured |
| No real testimonials | Service promises, guarantees, process descriptions |
Never use carousels — users see 1 of 5 testimonials, <1% click controls. Show all or curate the best 3.
Each reference is a deep-dive (300-470 lines) with full principles, anti-patterns, implementation patterns, and business-specific guidance.
| File | Lines | Covers |
|---|---|---|
hero-patterns.md | ~470 | Approach selection, constraint-based creativity, overlay techniques, responsive behaviour, page-specific heroes |
card-patterns.md | ~550 | Layout decision framework, anti-sameness strategies, grid math, orphan handling, CSS patterns, business context |
cta-patterns.md | ~420 | Action hierarchy, placement strategy, copy principles, visual design, mobile considerations, context-specific CTAs |
trust-signals.md | ~490 | Trust psychology, trust hierarchy, context-sensitive trust, lead-gen vs client, placement strategy, anti-patterns |
testimonial-patterns.md | ~350 | Social proof psychology, lead-gen ethics, design approach selection, content principles, placement, alternatives |
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.