agentsclimarketplace

Css architecture

Skill Amey-Thakur/AI-SKILLS/skills/css-styling/css-architecture

Plug-and-play skills and prompts for every AI coding agent

Install
npx -y skills add Amey-Thakur/AI-SKILLS --skill css-architecture

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 19 days oldThe repository was created 19 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Organize stylesheets with scoping, co-location, and layer order so CSS stays deletable as the codebase grows. Use when structuring styles for a growing app or auditing a stylesheet nobody dares touch.

SKILL.md

2.4 KB, as published. Nobody here has run it

CSS architecture

The health metric for CSS is deletability: when a component dies, its styles must die with it, provably. Every practice here serves that.

Method

  1. Co-locate styles with components. One style unit per component, living next to it (CSS Modules, scoped SFC styles, utility classes in markup, or a .css imported by the component). Global stylesheets accumulate; co-located ones get deleted with their component.
  2. Pick one scoping mechanism and hold it. CSS Modules or scoped styles for build-time isolation; utility classes for token-constrained markup styling; Shadow DOM only for embeddable widgets. Mixing idioms per-feature multiplies the knowledge needed to touch anything.
  3. Define the global layer order once. @layer reset, tokens, base, components, utilities; in the entry stylesheet. Globals are exactly: reset, token definitions, element defaults (base), and shared utilities. Anything else claiming global status needs an argument.
  4. Style through stable interfaces. Components expose modifiers (data-variant, props) and semantic tokens; parents size and position children (grid-area, width on the slot), never reach inside them (.parent .child-internal is the coupling that makes CSS undeletable).
  5. Keep specificity flat inside a scope. One class or attribute selector deep (see css-cascade); state via data-* or aria attributes ([aria-expanded="true"]), which doubles as an accessibility contract.
  6. Delete with tooling, not archaeology. Scoped styles make unused CSS visible (unimported file, unreferenced local class); CI can run coverage or lint for orphaned modules. A quarterly "grep the class name, delete the rule" pass keeps the base honest even without tooling.

Boundaries

  • Naming conventions (BEM) solved scoping before build tools did; adopt them only where no build-time scoping exists (CMS themes, legacy server-rendered apps).
  • Print styles, email HTML, and rendered user content are separate stylesheets with their own rules; do not fold them into the app system.
  • Architecture cannot fix an undesigned system; without tokens and components, organizing files is rearranging the pile.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.