A place to study
how interfaces feel.

Historical objects and buildings have their own contexts. Image credits identify the media source; the palettes and interface behaviours are contemporary interpretations.

For the ideas behind the experiments, read the curatorial monographs or follow a term through the Lexicon.

References & attribution

Atlas images have source and rights information attached to their provenance controls. Monographs connect arguments to cited work. The essays are curatorial research; citations alone do not establish external peer review.

Measurements & simulations

Contrast tools calculate results for a specified colour pair. Spring and material controls explore authored settings. A score or simulation is one part of a design decision, and does not establish comfort or accessibility for every person. Inspect the perception tools

Exports & dependencies

CSS variables describe a palette; they do not need a JavaScript runtime to declare colours. The interactive website and components have their own dependencies. Check the format and implementation you intend to use. Explore the components

Review in context

Try light and dark formulations, keyboard navigation, small screens and reduced motion alongside your actual content. Automated checks support that review; they do not replace testing with the people who will use your interface.

Human & agent roles

The MCP server lets an assistant inspect the same movements, sources and tools that a person can inspect here. An agent can retrieve tokens, run named checks and prepare editable code; it should preserve the chosen intent, identify authored interpretations and report the checks it actually performed. The person remains responsible for the brief, cultural context and final judgement. Make a shared study