The audit passThe checked layer · run on demand

A rule nobody runs
is a rule nobody keeps.

The stated layer asks. The compiled layer enforces. The audit is what catches everything in between — a pass over a finished screen that reports, by name, which rules it broke and where.

ReachWhat a pass can and cannot settle

It checks what is true, not what is good.

An audit that claimed to judge taste would be wrong constantly and trusted briefly. This one only reports things that are decidable by looking — which turns out to be most of what actually goes wrong.

01What it checks →

Decidable, so it reports

Questions with an answer in the data or the markup, where a disagreement is a fact rather than an opinion.

  • A figure with no traceable sourcederivation
  • A status in the data with no appearancecoverage
  • An action offered on a record that cannot take itaffordance
  • A route referenced that does not existstructure
  • A component missing one of its four statescoverage

Not decidable, so it stays quiet

Questions where the honest answer is a judgement. The audit does not have one and does not pretend to.

  • Whether the density suits the readertaste
  • Whether this screen leads with the right thingtaste
  • Whether the wording earns its spacetaste
  • Whether the product is worth buildingnot its job
A report that flags forty things is a report nobody reads to the end. The pass is deliberately narrow, and everything it does say is worth acting on.
The checksGrouped by what they defend

Sixty rules, and what each pass looks for.

Every check names the rule it came from, so a finding is never a matter of style. If a rule is removed, its check goes with it.

02How it runs →
GroupWhat the pass looks forChecks

Derivation

Figures that summarise other figures, and whether the screen can say where each one came from.

11 checks

Coverage

Every value present in the fixtures, and whether a screen exists for each one. Including the four states.

14 checks

Affordance

Actions offered against the state of the record they sit on, and whether that state permits them.

9 checks

Structure

Routes, breadcrumbs and cross-references, and whether each one resolves to something that exists.

12 checks

Language

Labels that claim more than the data supports, and words the system was not given permission to invent.

8 checks
Fifty-four checks against sixty rules. The remaining six are the expressive choices each shell must make on purpose, and judging those is the one thing the pass refuses to do.
Running itToday by hand · soon by command

Three moments worth running it.

It reads a finished screen, so it can run at any point after there is something to read. In practice there are three that matter.

03Straight answers →
In the session

Before you look at it yourself

Ask for the pass as soon as the screens exist. It is faster at finding a missing state than you are, and it never gets bored on screen six.

Before handoff

Before anyone else sees it

The findings are named rules, so the conversation with a developer starts from a list rather than from a feeling that something is off.

On a change

After the data model moves

A new status upstream is the most common way coverage quietly breaks. Re-run the pass and it says which screens never heard about it.

Command-line run · on the roadmap
The pass works by hand today. Making it a command with an exit code a pipeline can read is the next piece of work, and it is marked as likely rather than promised.
QuestionsAnswered plainly

Straight answers.

What a reader asks once they have seen a pass run: what it costs them, what it misses, and what happens when it disagrees.

04Back to the top →
Answer 01

No.

It ships components and tokens, but that is not what you are buying. The product is the rules layer that decides what gets computed, what gets shown and what gets refused — plus the machinery that makes those rules checkable.

Answer 02

If it reads a rules file, yes.

It is built for Claude Design users generating business UI. Because the layer is plain markdown loaded as project instructions, anything else that reads a rules file will use it too. There is nothing proprietary to integrate.

Answer 03

No. The judgement, yes.

The tokens are yours to set and brand fit is a config change. The judgement rules are not configurable, because that is the product. If you want a different opinion about derivation, you want a different product.

Answer 04

Nothing breaks.

The rules are written against behaviour rather than internals, so upstream releases move underneath them. Where a rule does need to change, it changes in one file you can read in an afternoon.

Answer 05

Once. Then faster.

Marginally slower on the first generation. Considerably faster by the fourth, because you are not re-prompting it to fix a total that never tied.

Reckon

Ship the screen.
Not the guesswork.

Components are the easy part. What you are missing is the layer that decides what gets computed, what gets shown, and what gets refused.

See how it worksSee a worked product
Built for Claude Design · plain markdown · nothing to run