Concepts

These pages explain how Tostada thinks. Six short reads. Skim them once; the rest of the docs assume the model.

• The orchestrator model — why Tostada sits on top of a component library, not inside one
• Three-tier tokens — primitive → semantic → component binding
• Light and dark — the resolution algorithm
• Layout principles — what shells and layouts mean
• Application rules — Do / Don't / Notes per component and per variant
• The design-system.md export — why this is the artifact AI agents consume

If you only read one, start with the orchestrator model — it explains where Tostada fits in the broader picture of design systems and AI tooling.