mds-css-conventions

Enforce CSS class naming and scoping conventions for generated components.

Updated Jan 6, 2026
One-click install
npx skills add https://github.com/eboody/eran.codes --skill mds-css-conventions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mds-css-conventions
Source: https://github.com/eboody/eran.codes/tree/main/.codex/skills/mds-css-conventions
Command: npx skills add https://github.com/eboody/eran.codes --skill mds-css-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures consistent and maintainable CSS across generated components by enforcing project-specific conventions for class naming, style scoping, and layout, leading to a more cohesive and professional UI.

Core Features & Use Cases

  • Enforces CSS Conventions: Guides developers on applying repo-wide CSS standards.
  • Hybrid Styling Model: Promotes a balance between global reusable styles and scoped component-specific styles.
  • Modern CSS Adoption: Encourages the use of modern CSS features for enhanced functionality and accessibility.
  • Use Case: When developing a new UI component, use this Skill to ensure its CSS adheres to the project's established patterns for class naming (e.g., ui-tabs) and scoping, preventing style conflicts and promoting reusability.

Quick Start

Apply repo CSS conventions and css-scope-inline usage patterns to class design and style scoping decisions used by generated components.

Frequently Asked Questions about mds-css-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize CSS conventions for generated frontend components?

Standardize CSS conventions for generated components by enforcing project-specific rules for class naming, style scoping, and layout. This ensures consistent and maintainable styling across your UI, preventing style conflicts and promoting reusability.

What is the best way to manage global and scoped styles in component development?

The best way to manage global and scoped styles is a hybrid styling policy. This approach promotes global reusable classes for shared UI patterns while using scoped styles for component-specific behavior, ensuring maintainable and conflict-free styling.

How do CSS naming conventions prevent style conflicts in web development?

CSS naming conventions prevent style conflicts by enforcing structured class naming patterns like `ui-tabs`. Applying consistent repo-wide standards ensures that generated components maintain a cohesive UI without overlapping or unintended style overrides.

When should I use modern CSS features for styling generated components?

Use modern CSS features for styling generated components to enable progressive enhancement and improve accessibility. Adopting modern CSS capabilities alongside standardized conventions enhances component functionality while maintaining a cohesive and professional UI.

Does this CSS standardization approach work without external styling dependencies?

Yes, this CSS standardization approach works without external dependencies. It guides the adoption of modern CSS features and progressive enhancement natively, enforcing a hybrid styling policy that balances global reusable classes and scoped styles.

Why does generated component CSS become inconsistent across a web project?

Generated component CSS becomes inconsistent without enforced project conventions for class naming and style scoping. Applying a hybrid styling policy with minimal styling rules standardizes layout expectations and prevents maintainability issues.