styling-guidelines

Best practices for component CSS, design system consistency, and layout patterns. Use when authoring component styles.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 1, 2026

When & Why to Use This Skill

This Claude skill provides comprehensive guidelines and best practices for authoring component-based CSS. It ensures design system consistency by leveraging design tokens, scoped styling, and modern CSS features like layers and responsive mobile-first patterns, enabling developers to build maintainable and scalable frontend architectures.

Use Cases

  • Ensuring design system consistency by applying standardized CSS patterns and design tokens during component development.
  • Authoring scoped, modular CSS for components to prevent global style conflicts and improve maintainability.
  • Implementing responsive, mobile-first layouts using semantic HTML and modern CSS layout techniques.
  • Organizing complex stylesheets using CSS layers to manage specificity and improve code structure.
namestyling-guidelines
descriptionBest practices for component CSS, design system consistency, and layout patterns. Use when authoring component styles.
licenseMIT
authorAI Agents
version"1.0"

Summary

Guidelines for writing component CSS consistent with design system principles.

Key principles

  • Component styles are scoped locally (no global class names)
  • Use design tokens for spacing, colors, and sizes (rather than hardcoding)
  • Use semantic HTML selectors (element and attribute selectors)
  • Implement CSS layers for organization and specificity control
  • Support responsive design with mobile-first approach

When to use this skill

Use this skill when authoring component CSS to ensure design consistency, maintainability, and proper layout behavior.

See also

For project-specific design tokens and styling conventions, refer to .context/CLAUDE.md or .context/COPILOT.md.

For full guidelines and examples see references/REFERENCE.md.