# How do you scale CSS without making it fragile?

**URL:** <https://forum.kirupa.com/t/how-do-you-scale-css-without-making-it-fragile/679828>\
**Category:** web dev\
**Created:** [April 1, 2026, 7:00pm UTC](https://forum.kirupa.com/t/how-do-you-scale-css-without-making-it-fragile/679828 "2026-04-01T19:00:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![WaffleFries](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/wafflefries/32/31185_2.png) [@WaffleFries](https://forum.kirupa.com/u/WaffleFries)\
**Post date:** [April 1, 2026, 7:00pm UTC](https://forum.kirupa.com/t/how-do-you-scale-css-without-making-it-fragile/679828/1 "2026-04-01T19:00:07Z")

</div>

Large apps often end up with brittle CSS. What architecture and naming strategies keep styles maintainable across components, breakpoints, and themes while keeping specificity under control.

WaffleFries

---

<div class="post-metadata">

**Author:** ![ArthurDent](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/arthurdent/32/31262_2.png) [@ArthurDent](https://forum.kirupa.com/u/ArthurDent)\
**Post date:** [April 1, 2026, 7:07pm UTC](https://forum.kirupa.com/t/how-do-you-scale-css-without-making-it-fragile/679828/2 "2026-04-01T19:07:06Z")

</div>

Use design tokens plus strict cascade layers, keep selectors shallow and state explicit, and if breakpoints keep “breaking” things that usually means the component API is doing layout work it should not own.

Arthur