A taste-engine for frontends
What good looks like, and why.
experentia answers the two questions an AI agent cannot get from a component library alone. The answers are backed by empirical research, distilled into machine-readable taste profiles with assertions an agent can actually run, and a record of how the decisions were made.
Three layers, no templates
experentia is an evidence base, a set of machine-readable taste profiles, and a record of how the decisions were actually made. It ships no reference templates: a template is a snapshot that rots, and the point is the reasoning that produces one.
Colour, style and pattern doctrine with citations, plus the raw and verified claim sets from a deep-research pass. Every rule downstream traces back here, and a claim with no citation says it is experience.
Read the evidence →One JSON profile per genre: tokens with precomputed contrast pairs, type roles, an ordered layout grammar, and assertions phrased as pass/fail tests an agent can actually run.
Read the profiles →How the calls were made, and how to work with an LLM so it produces work you can trust: verify rather than assume, put guardrails in code not prompts, and never report a success you did not check.
Read the method →How the taste is made
Every rule downstream traces back to the evidence base. Nothing ships on opinion alone.
Evidence
Color, style, and pattern doctrine with citations, plus raw and adversarially verified claim sets.
Profiles
One JSON per genre: tokens with precomputed contrast pairs, type roles, layout grammar, and assertions as pass/fail tests.
Method
How the calls were made, and how to work with an LLM so its output is worth trusting. Verify rather than assume; guardrails in code, not prompts.
Pre-ship
The defect classes found in real shipped work. An agent walks it before calling any build done.
Start here if you are an agent
experentia is meant to be read by a machine before it builds. AGENTS.md is the contract: what to read, in what order, and the refusals that are not negotiable. Accessibility floors are checked before any taste judgement, a rule that must hold goes in code rather than a prompt, and anything you could not verify is reported as unverified rather than folded into a pass.
The build contract. Read first, every time. Three layers, the order to read them in, and the non-negotiables.
Read the contract →A verified index of where frontend design intelligence lives: galleries, design systems, craft references and the accessibility floor. Every URL status-checked, including the ones that block automation.
Browse the library →Suggest, do not dictate. Algorithmic layout over breakpoints, fluid scales via clamp(), and what the 2026 CSS baseline finally makes safe.
Read the doctrine →