explainx.ainewsletter3.4k
Frontend

web-design-methodology▌

jezweb/claude-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/jezweb/claude-skills --skill web-design-methodology
0 commentsdiscussion
summary

Production-grade HTML/CSS built with BEM, semantic tokens, mobile-first responsive design, and optional dark mode.

  • ›Enforces BEM naming conventions, CSS custom properties for all design values, and semantic HTML structure to ensure maintainability and consistency
  • ›Mobile-first workflow: design for 375px, enhance upward with four breakpoints (640px, 768px, 1024px, 1440px); includes hamburger navigation and 44x44px touch targets
  • ›Optional three-state dark mode via JavaScript class toggle
skill.md

Web Design Methodology

Universal patterns for building production-grade HTML/CSS. This skill covers implementation methodology — pair with web-design-patterns for specific component designs.

What You Produce

Production-ready HTML/CSS prototypes with:

  • Semantic CSS custom properties (tokens)
  • BEM-named components
  • Mobile-first responsive design
  • Accessible markup
  • Optional three-state dark mode

File Structure

prototype/
├── index.html
├── about.html
├── services.html
├── contact.html
├── favicon.svg
├── css/
│   ├── variables.css     # Tokens: colours, typography, spacing
│   ├── styles.css        # All component styles (BEM)
│   └── mobile-nav.css    # Mobile menu styles
├── js/
│   ├── theme.js          # Dark mode toggle (only if requested)
│   └── mobile-menu.js    # Hamburger menu
└── media/
    └── images/

Build order:

  1. variables.css — tokens first
  2. favicon.svg — simple SVG from brand colour
  3. styles.css — all BEM components
  4. mobile-nav.css — responsive navigation
  5. JS files — from assets/ templates
  6. index.html — homepage first
  7. Inner pages — about, services, contact
  8. Mobile check — verify at 375px

BEM Naming

Use Block-Element-Modifier naming. No exceptions.

/* Block */
.hero { }
.card { }
.nav { }

/* Element (child of block) */
.hero__title { }
.hero__subtitle { }
.hero__cta { }
.card__image { }
.card__content { }

/* Modifier (variation) */
.hero--split { }
.hero--minimal { }
.card--featured { }
.btn--primary { }
.btn--lg { }

Rules:

  • Blocks are standalone components
  • Elements are children, connected with __
  • Modifiers are variations, connected with --
  • Never nest more than one level: .hero__content__title is wrong
  • Never use element without its block: .card__image only inside .card

CSS Custom Properties

Use semantic tokens. Never hardcode colours, spacing, or typography values.

See references/css-variables-template.md for the complete token template.

/* Always this */
.card {
  background: var(--card);
  color: var(--card-foreground);
  border: 1px solid var(--border);
  border-radius: var(--radius);
  box-shadow: var(--shadow-sm);
  padding: var(--space-6);
}

/* Never this */
.card {
  background: #ffffff;
  color: #333333;
  border: 1px solid #e5e5e5;
  border-radius: 8px;
  box-shadow: 0 1px 3px rgba(0,0,0,0.1);
  padding: 24px;
}

Dark Mode (Optional)

Dark mode is optional — only add if the brief requests it. Most business sites ship faster as light-only.

When to include:

  • Brief explicitly requests it
  • Tech/developer audiences (expected)
  • Portfolio/creative sites (aesthetic choice)

When to skip:

  • Trades, hospitality, professional services
  • When simplicity and fast shipping matter more

If Adding Dark Mode

Use class-based toggle, never CSS media queries.

/* Light mode (default) */
:root {
  --background: #F9FAFB;
  --foreground: #0F172A;
  --card: #FFFFFF;
  --card-foreground: #1E293B;
}

/* Dark mode (via .dark class on html) */
.dark {
  --background: #0F172A;
  --foreground: #F1F5F9;
  --card: #1E293B;
  --card-foreground: #F1F5F9;
}

Rules:

  • .dark class on <html>, toggled via JavaScript
  • NEVER use @media (prefers-color-scheme: dark) — JS handles system preference
  • Every background token needs a paired foreground token
  • Brand colours get lighter/more saturated in dark mode
  • Backgrounds: #0F172A to #1E293B range (not pure black)
  • Every text-on-background combo must pass WCAG AA (4.5:1)

Use assets/theme-toggle.js for the three-state toggle implementation.

Responsive Design

Mobile-first. Design for 375px, enhance upward.

Breakpoints

/* Base: 375px (mobile) — no media query needed */
@media (min-width: 640px) { /* sm — large phone */ }
@media (min-width: 768px) { /* md — tablet */ }
@media (min-width: 1024px) { /* lg — small desktop */ }
@media (min-width: 1440px) { /* xl — standard desktop */ }

Mobile Priorities

  1. Phone number visible and tappable without scrolling
  2. Primary CTA visible without scrolling
  3. Navigation works via hamburger menu
  4. Touch targets minimum 44x44px
  5. No horizontal scrolling ever
  6. Images scale properly (no overflow)

Wide Screen Constraints

.prose { max-width: 65ch; }
.hero__content { max-width: min(640px, 45vw); }
.container {
  max-width: 1280px;
  margin-inline: auto;
  padding-inline: var(--space-4);
}
.section { padding: clamp(3rem, 6vw, 6rem) 0; }

Use assets/mobile-nav.js for the hamburger menu implementation.

Typography Rules

  1. Dramatic size contrast. Headlines 3-4x body size. clamp(2.5rem, 6vw, 5rem) for hero titles.
  2. Weight variety. Mix 300 and 800 weights. Uniform weight is boring.
  3. One display moment per page. One oversized word, one dramatic headline, one pull quote. Not three.
  4. Left-align body text. Centre only for heroes and short statements. Never centre paragraphs.
  5. Letter spacing on uppercase. Add letter-spacing: 0.05em minimum.

Colour Usage

The 80/20 rule:

  • 80% neutral tones (backgrounds, text, cards)
  • 15% secondary/muted brand tones
  • 5% primary brand colour (CTAs, one accent per viewport)

If primary is on every heading, border, icon — nothing stands out.

Spacing System

Not uniform padding. Sections breathe differently:

/* Tight section (service list, FAQ) */
.section--compact { padding: clamp(2rem, 4vw, 4rem) 0; }

/* Standard section */
.section { padding: clamp(3rem, 6vw, 6rem) 0; }

/* Breathing room (editorial break, testimonial) */
.section--spacious { padding: clamp(4rem, 8vw, 10rem) 0; }

Shadow System

Element Shadow
Cards at rest --shadow-sm
Cards on hover --shadow-md
Dropdowns --shadow-lg
Modals --shadow-xl

Not everything needs shadow. Use sparingly.

Icons

Use Lucide icons via inline SVG:

  • Size: 24px inline, 32-48px for feature blocks
  • Stroke width: 1.5 or 2 (consistent throughout)
  • Colour: currentColor (inherits text colour)
  • Each icon should communicate something specific

Accessibility

Non-negotiable:

  • Semantic HTML: <header>, <nav>, <main>, <section>
how to use web-design-methodology

How to use web-design-methodology on Cursor

AI-first code editor with Composer

1

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-methodology
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/jezweb/claude-skills --skill web-design-methodology

The skills CLI fetches web-design-methodology from GitHub repository jezweb/claude-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/web-design-methodology

Reload or restart Cursor to activate web-design-methodology. Access the skill through slash commands (e.g., /web-design-methodology) 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.

Additional Resources

›View source code on GitHub›Skills CLI documentation›Learn more about Cursor›What are agent skills?

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

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. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 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▌

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.6★★★★★70 reviews
  • ★★★★★Olivia Bansal· Dec 28, 2024

    Registry listing for web-design-methodology matched our evaluation — installs cleanly and behaves as described in the markdown.

  • ★★★★★Jin Khan· Dec 16, 2024

    web-design-methodology reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • ★★★★★Shikha Mishra· Dec 12, 2024

    Solid pick for teams standardizing on skills: web-design-methodology is focused, and the summary matches what you get after install.

  • ★★★★★Valentina Garcia· Nov 19, 2024

    Useful defaults in web-design-methodology — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • ★★★★★Hassan Smith· Nov 7, 2024

    I recommend web-design-methodology for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • ★★★★★Yash Thakker· Nov 3, 2024

    We added web-design-methodology from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • ★★★★★James Shah· Oct 26, 2024

    Useful defaults in web-design-methodology — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • ★★★★★Dhruvi Jain· Oct 22, 2024

    web-design-methodology fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • ★★★★★James Sharma· Oct 10, 2024

    web-design-methodology has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • ★★★★★Hana Jain· Oct 10, 2024

    Solid pick for teams standardizing on skills: web-design-methodology is focused, and the summary matches what you get after install.

showing 1-10 of 70

1 / 7