web-design-guidelines
The web-design-guidelines skill reviews UI code and markup files against a comprehensive set of Web Interface Guidelines covering accessibility, forms, animation, typography, images, keyboard navigation, dark mode, and internationalization. Use it when stakeholders request UI reviews, accessibility audits, design compliance checks, or UX best practice validation, but not for performance metrics, SEO issues, or comprehensive site audits.
git clone --depth 1 https://github.com/tech-leads-club/agent-skills /tmp/web-design-guidelines && cp -r /tmp/web-design-guidelines/packages/skills-catalog/skills/(design)/web-design-guidelines ~/.claude/skills/web-design-guidelinesSKILL.md
# Web Interface Guidelines Review files for compliance with Web Interface Guidelines. ## How It Works 1. Read the guidelines from `#[[file:references/guideline.md]]` 2. Read the specified files (or prompt user for files/pattern) 3. Check against all rules in the guidelines 4. Output findings in the terse `file:line` format ## Guidelines Reference All rules and output format instructions are in: ``` #[[file:references/guideline.md]] ``` The guidelines cover: - Accessibility (ARIA, semantic HTML, keyboard navigation) - Focus states and keyboard interaction - Forms (autocomplete, validation, labels) - Animation (reduced motion, performance) - Typography (proper characters, number formatting) - Content handling (overflow, empty states) - Images (dimensions, lazy loading) - Performance (virtualization, DOM reads) - Navigation & state (URL sync, deep linking) - Touch & interaction (tap delays, safe areas) - Dark mode & theming - Locale & i18n - Hydration safety - Common anti-patterns to flag ## Usage When a user provides a file or pattern argument: 1. Read the guidelines from `references/guideline.md` 2. Read the specified files 3. Apply all rules from the guidelines 4. Output findings using the format specified in the guidelines If no files specified, ask the user which files to review. ## Output Format Follow the format in the guidelines: - Group findings by file - Use `file:line` format (VS Code clickable) - Terse, high signal-to-noise - State issue + location - Skip explanation unless fix is non-obvious
Finds duplicate business logic spread across multiple components and suggests consolidation. Use when asking "where is this logic duplicated?", "find common code between services", "what can be consolidated?", "detect shared domain logic", or analyzing component overlap before refactoring. Do NOT use for code-level duplication detection (use linters) or dependency analysis (use coupling-analysis).
Detects misplaced classes and fixes component hierarchy problems — finds code that should belong inside a component but sits at the root level. Use when asking "clean up component structure", "find orphaned classes", "fix module hierarchy", "flatten nested components", or analyzing why namespaces have misplaced code. Do NOT use for dependency analysis (use coupling-analysis) or domain grouping (use domain-identification-grouping).
Maps architectural components in a codebase and measures their size to identify what should be extracted first. Use when asking "how big is each module?", "what components do I have?", "which service is too large?", "analyze codebase structure", "size my monolith", or planning where to start decomposing. Do NOT use for runtime performance sizing or infrastructure capacity planning.
Analyzes coupling between modules using the three-dimensional model (strength, distance, volatility) from "Balancing Coupling in Software Design". Use when asking "are these modules too coupled?", "show me dependencies", "analyze integration quality", "which modules should I decouple?", "coupling report", or evaluating architectural health. Do NOT use for domain boundary analysis (use domain-analysis) or component sizing (use component-identification-sizing).
Creates step-by-step decomposition plans and migration roadmaps for breaking apart monolithic applications. Use when asking "what order should I extract services?", "plan my migration", "create a decomposition roadmap", "prioritize what to split", "monolith to microservices strategy", or tracking decomposition progress. Do NOT use for domain analysis (use domain-analysis) or component sizing (use component-identification-sizing).
Maps business domains and suggests service boundaries in any codebase using DDD Strategic Design. Use when asking "what are the domains in this codebase?", "where should I draw service boundaries?", "identify bounded contexts", "classify subdomains", "DDD analysis", or analyzing domain cohesion. Do NOT use for grouping existing components into domains (use domain-identification-grouping) or dependency analysis (use coupling-analysis).
Groups existing components into logical business domains to plan service-based architecture. Use when asking "which components belong together?", "group these into services", "organize by domain", "component-to-domain mapping", or planning service extraction from an existing codebase. Do NOT use for identifying new domains from scratch (use domain-analysis) or analyzing coupling (use coupling-analysis).
AI frontend specialist and design consultant that guides users through a structured discovery process before generating any code. Collects visual references, design tokens, typography, icons, layout preferences, and brand guidelines to ensure the final output matches the user's vision with high fidelity. Use when the user asks to build, design, create, or improve any frontend interface — websites, landing pages, dashboards, components, apps, emails, forms, modals, or any UI element. Also triggers on "build me a UI", "design a page", "create a component", "improve this layout", "make this look better", "frontend", "interface", "redesign", or when the user provides mockups, screenshots, or design references. Do NOT use for backend logic, API design, database schemas, or non-visual code tasks.