Start with the browser
The foundation should improve plain HTML and CSS instead of fighting them.
These are working constraints, not slogans. They exist to keep the reset small, coherent, and honest about the current phase.
These are the boundaries that keep the system legible while the foundation is still proving itself.
The foundation should improve plain HTML and CSS instead of fighting them.
Consumers should depend on semantic token names, not internal file structure.
Keep the package shape stable while allowing themes and token values to evolve.
If a layer does not remove repeated effort, do not add it yet.
Strong defaults are more useful than a large matrix of switches.
Type and spacing should scale cleanly before breakpoint-specific tuning enters the picture.
The CLI and app surfaces support the CSS foundation. They do not define it.
v1 is the foundation block only, not the whole future system.
Docs should answer real questions without turning into their own architecture.
A contributor should be able to inspect the repo and understand the shape quickly.