Production-grade HTML/CSS built with BEM, semantic tokens, mobile-first responsive design, and optional dark mode.
Works with
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
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionweb-design-methodologyExecute the skills CLI command in your project's root directory to begin installation:
Fetches web-design-methodology from jezweb/claude-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate web-design-methodology. Access via /web-design-methodology in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
697
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
697
stars
Universal patterns for building production-grade HTML/CSS. This skill covers implementation methodology — pair with web-design-patterns for specific component designs.
Production-ready HTML/CSS prototypes with:
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:
variables.css — tokens firstfavicon.svg — simple SVG from brand colourstyles.css — all BEM componentsmobile-nav.css — responsive navigationassets/ templatesindex.html — homepage firstUse 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:
__--.hero__content__title is wrong.card__image only inside .cardUse 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 is optional — only add if the brief requests it. Most business sites ship faster as light-only.
When to include:
When to skip:
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@media (prefers-color-scheme: dark) — JS handles system preference#0F172A to #1E293B range (not pure black)Use assets/theme-toggle.js for the three-state toggle implementation.
Mobile-first. Design for 375px, enhance upward.
/* 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 */ }
.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.
clamp(2.5rem, 6vw, 5rem) for hero titles.letter-spacing: 0.05em minimum.The 80/20 rule:
If primary is on every heading, border, icon — nothing stands out.
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; }
| Element | Shadow |
|---|---|
| Cards at rest | --shadow-sm |
| Cards on hover | --shadow-md |
| Dropdowns | --shadow-lg |
| Modals | --shadow-xl |
Not everything needs shadow. Use sparingly.
Use Lucide icons via inline SVG:
currentColor (inherits text colour)Non-negotiable:
<header>, <nav>, <main>, <section>Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
jezweb/claude-skills
anthropics/claude-code
leonxlnx/taste-skill
sickn33/antigravity-awesome-skills
erichowens/some_claude_skills
hyperb1iss/hyperskills
Registry listing for web-design-methodology matched our evaluation — installs cleanly and behaves as described in the markdown.
web-design-methodology reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: web-design-methodology is focused, and the summary matches what you get after install.
Useful defaults in web-design-methodology — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend web-design-methodology for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added web-design-methodology from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in web-design-methodology — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
web-design-methodology fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
web-design-methodology has been reliable in day-to-day use. Documentation quality is above average for community skills.
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