
From a reference / Apollo Avionics
Can a component keep its character while making every state clear?
Keep identity through change.
Explore the connection & keep your decisions
The chosen system provides a visual language. Follow the same control through focus, loading, error and disabled states before judging the language by its resting appearance.
What this experiment representsThe matrix presents implemented component states. It is a design inspection, not a substitute for testing a complete product with people.
Read the study and its source notesTry one considered change.
- Choose one component and record its current system.
- Compare focus, error and disabled states using the same component.
- Keep the material cues that support state recognition; note any cue that competes with it.
Your judgement / optional
Keep the reason with the result.
Notes stay on this device when saved. Copying a study link includes them. The reference guides your thinking; choosing it does not apply a palette.
The selected component, view, hour and active system travel with the settings link.
Choose a component and follow it from focus to saved.
State Matrix & System Comparison
Inspect interactive pseudo-state transitions across all UI primitives, and cross-examine multi-brand token resolution across Midnight Editorial, Glass Garden, and Warm Minimal.
Keep one. Try another.
Pin a plate before changing the controls. Each pin keeps its own recipe and lighting context.
Carry this specimen into another tool
The image travels locally in this tab with its source recipe. This is a flattened plate: the destination does not recreate fluid motion or convert material coefficients.
Keep the reference and your decisions
Download the starting reference, current settings and your decision notes alongside your specimen. Add notes in the reference panel.
Further reading
Questions & notes
A closer look at the ideas, materials and methods behind the work.
Design Tokens Community Group format, rulefiles and checks that help a system stay coherent as it grows.
1 questionAI coding assistants can introduce colors, spacing values, and component treatments that fall outside an established system. Project rulefiles can give an assistant the same semantic token vocabulary and radius, type, motion, and attribution constraints used by the human team. These constraints reduce visual drift, but they do not guarantee conformance: generated work still needs automated checks and human review in context.
Related questions
The Design Tokens Community Group (DTCG) format defines a shared JSON vocabulary where tokens can declare $value, $type, and $description. Chromologium exports that compatible format for tools such as Figma, Style Dictionary, iOS Swift, and Tailwind; the community-group report is not itself a W3C Standards Track standard.
{
"color": {
"accent": {
"$value": "oklch(0.724 0.122 85.099104)",
"$type": "color",
"$description": "Solar Ochre primary accent with OKLCH ASCII cipher."
}
}
}Global tokens declare primitive values (e.g. color-gold-500). Semantic tokens map intentional roles (e.g. color-action-primary -> {color-gold-500}). Component tokens bind specific instances (e.g. button-primary-bg -> {color-action-primary}). Swapping themes only requires remapping semantic aliases, leaving component code entirely untouched.