What problem does it solve?
It prevents inconsistent, inaccessible, and hard-to-maintain UI by enforcing practical rules for semantic HTML, design tokens, responsive layouts, and BEM/ naming discipline.
Core Features & Use Cases
- Semantic HTML & Accessibility (WCAG AA): choose correct elements, add ARIA only when needed, ensure keyboard focus, and meet contrast and alt-text requirements.
- Responsive, mobile-first UI: apply mobile-first breakpoints, container queries, and fluid typography/spacing to avoid layout regressions.
- Design tokens & theming: use CSS custom properties for colors, spacing, radii, and shadows to support consistent light/dark themes.
- BEM and naming conventions: keep class structures predictable with
.block__element--modifier and avoid deep or leaky naming.
- Use Case: when implementing a new settings panel or component library card, follow this discipline to ship markup and styles that are accessible, themable, and responsive across common UI frameworks and templating setups.
Quick Start
Use frontend-craft while generating or updating any HTML/CSS/JSX/Vue/Svelte/Astro UI so that markup, styling, tokens, responsiveness, and accessibility meet the skill’s checklist.