web-design-patterns▌
jezweb/claude-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Principle-based design patterns for website sections that avoid AI-generated aesthetics.
- ›Covers five core section types: heroes, cards, CTAs, trust signals, and testimonials with context-specific guidance for different business types
- ›Teaches WHY and WHEN to use each pattern, not just templates; includes explicit anti-patterns like democratic design, perfect symmetry, and generic copy
- ›Provides cross-cutting principles on hierarchy, asymmetry, and restraint that apply across all patter
Web Design Patterns
Principle-based patterns for designing website sections that feel human-designed, not AI-generated. Each pattern teaches WHY and WHEN, not just templates to copy.
What You Produce
Well-designed website sections: heroes, card layouts, CTAs, trust signals, and testimonials that match the business context and avoid the "AI skeleton" look.
When to Read Which Reference
| 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.
Cross-Cutting Principles
These apply to ALL patterns. Internalise these before reading any reference file.
Anti-AI Patterns (Avoid These)
The "AI skeleton" that signals template-generated design:
- The sequence: Hero → trust bar → 3 identical cards → features → stats → CTA → footer
- Democratic design: Every element gets equal visual weight, no hierarchy
- Perfect symmetry: Everything centred, perfectly aligned, no intentional asymmetry
- Identical repetition: All cards same size, same structure, same padding, same shadow
- Generic copy: "Learn More" as every CTA, "Quality Service You Can Trust" as every headline
- Decoration without purpose: Floating shapes, random gradients, abstract blobs
What Makes Design Feel Human
- One element clearly dominates — hierarchy, not democracy
- Asymmetry is intentional — not everything centred or balanced
- Specific, opinionated copy — "Schedule Your Free Roof Inspection" not "Learn More"
- Visual weight guides the eye — you know where to look first, second, third
- Restraint — not every technique used, just the ones that serve the purpose
- Context-appropriate — emergency plumber looks different from luxury hotel
Ethical Rules
Non-negotiable across all patterns:
On lead-gen sites (no real business data), NEVER fabricate:
- Star ratings or review counts
- Specific years in business
- Licence or ABN numbers
- Named individuals or team members
- Exact customer counts
Safe alternatives for lead-gen:
- "Experienced Team" (not "25 Years Experience")
- "Highly Rated" (not "4.9 Stars (127 Reviews)")
- "Licensed & Insured" (not "QBCC License #1234567")
Business Context Shapes Everything
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 |
Quick Pattern Examples
Hero Approaches
Image-dominant (strong photography available):
- Let the image do the work, minimal text
- One clear focal point
- Text placement within image composition, not slapped on top
Typography-dominant (no strong imagery):
- Font choice, size, weight, spacing IS the design
- Generous whitespace as active design element
- Colour blocking or subtle texture instead of stock photos
Split/balanced (strong copy + strong imagery):
- One side dominates slightly — true 50/50 feels indecisive
- On mobile, order matters — which element first in vertical stack?
Card Layout Decision
- Count items first — wrong grid math creates orphan cards
- Check hierarchy — is one item more important? Feature it at 2x size
- Content density — image-heavy = fewer columns, text-heavy = more columns
- Orphan fix — never leave 1 card alone on a row
CTA Hierarchy
Match CTA urgency to business context:
- Emergency services: Phone number IS the CTA. Huge, high-contrast, tappable.
- Professional services: Lower commitment first. "Book a consultation."
- Creative/agency: Relationship-building. "View our work."
Golden rule: Make your case first, then ask for action. CTA appears AFTER value.
Trust Signal Hierarchy
| 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.
Testimonial Approach
| 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.
Reference File Index
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 |
How to use web-design-patterns on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add web-design-patterns
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches web-design-patterns from GitHub repository jezweb/claude-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate web-design-patterns. Access the skill through slash commands (e.g., /web-design-patterns) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★43 reviews- ★★★★★Hassan Abebe· Dec 16, 2024
Solid pick for teams standardizing on skills: web-design-patterns is focused, and the summary matches what you get after install.
- ★★★★★Mia Verma· Dec 12, 2024
web-design-patterns is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Olivia Chen· Nov 7, 2024
web-design-patterns has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Liam Yang· Nov 3, 2024
Keeps context tight: web-design-patterns is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Noah Okafor· Oct 26, 2024
web-design-patterns fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Isabella White· Oct 22, 2024
We added web-design-patterns from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Sakshi Patil· Sep 5, 2024
Solid pick for teams standardizing on skills: web-design-patterns is focused, and the summary matches what you get after install.
- ★★★★★Min Martin· Sep 5, 2024
web-design-patterns has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Zaid Rahman· Sep 5, 2024
Useful defaults in web-design-patterns — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Noah Ndlovu· Sep 5, 2024
We added web-design-patterns from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 43