What is LSCSS?
Start here if you need the short explanation before choosing a route.
Search
Search by problem, pattern, or architectural decision. Useful searches include specificity, utilities, state, modifiers, legacy CSS, @scope, Tailwind, tokens, and hacks.
Search for the question you have, not only the page title.
Try terms like specificity, state,
utility, legacy, scope,
or tokens.
Check layers, ownership, and selector intent before increasing specificity.
Use practical rules when repeated utility stacks start looking suspicious.
Separate permanent variants from temporary UI behaviour.
Contain old styles and improve active work without rewriting everything.
Recognise specificity ladders, random values, utility overload, and permanent hacks.
Review ownership, tokens, components, state, legacy, hacks, and delivery risk.