2026-07-29 · CSS

Organize large stylesheets with cascade layers

Replace specificity wars in a design system with a predictable @layer order.

Introduction

When every component adds !important, your design tokens stop working. This post sets up layers for reset, tokens, components, and utilities, then migrates a legacy stylesheet one file at a time.

The mental model

  • Start from the smallest version that could work, and make it observable.
  • Write down the trade-off you are accepting, not only the feature you are shipping.
  • Revisit the decision when the team grows; most choices in CSS have a shelf life.

A practical starting point

  1. Reproduce the situation on a scratch branch, next to a measurement you trust.
  2. Change one variable at a time, and keep the diff small enough to explain in one sentence.
  3. Keep the result, throw away the scaffolding.
Terminal window
git switch -c experiment/one-thing

Closing thoughts

None of this is doctrine. Treat it as a checklist you are allowed to disagree with — ideally with an experiment of your own that settles the argument.