This is for the designer who is the only designer on a team of engineers.

You open a project, run the checks, and every one says nothing. You cannot tell whether the project is fine or the checks are broken.

The project has the files the checks need, so silence means something.

Its own first version said three files were missing from a project that had all three. It had guessed where they should be instead of looking.

Try: “set this project up”

You are about to build a filter. You looked around for ten minutes and you are fairly sure there is not one already.

Now you know, because the search is written down with what it found.

Last time it ran it found seven things already built that did the job. Nothing new got made.

Try: “start work on a filter”

A page is done. Someone asks how much of it came from the design system, and you shrug.

You can list every piece on the page and say where it came from.

It gives you counts, never a percentage. “41 reused, 6 built from scratch” tells you what to do next. “87%” does not.

Try: “what is this page made of”

Two people build two buttons on two days. Side by side they do not match, and neither one is wrong.

Same parts, same sizes, same behavior. They fit together.

Its check reads five of the twelve rules and says so. The other seven need a real page on a screen.

Try: “does this button follow the system”

You hand engineering a design with a button style that was never in the system. It gets built. It ships. Nothing looks broken.

One short file says what that button can be, and design and code both follow it.

When it cannot check something, it says so instead of saying it passed.

Try: “write down what this button promises”

The page looks wrong. You read the code and the code is right.

You find out which promise got broken, and you have the proof.

Its whole point: broken design still looks like design. Nothing crashes, so nobody reports it.

Try: “check this page against the system”

A button shows a color nobody picked, and dark mode only works on half the screen.

You get a grade for the colors and sizes, and a list of what could not be checked.

Given no files at all, it used to answer “all clear”. Now “I had nothing to look at” is its own answer.

Try: “grade the colors in this project”

You made one thing you loved. Ask for the same style again and you get close, then a bit off, then generic.

The look is written down, so you can make it again. Poster, deck, page.

It rebuilds your original from the notes and compares the two. On this site it caught three misses: a rounded tag that should have been square, an underline in the wrong color, and a caption that was not there.

Try: “write down this style so I can reuse it”

A hover effect felt fine on its own. Three components later it is a tic.

Every bit of movement has a reason you can say out loud.

Three of its six checks look for repetition rather than mistakes. One bounce is a choice. The same bounce three times is a habit.

Try: “review the animation here”

An engineer explains why something is hard. You nod. You did not follow a word of it.

You get the same thing in the words you already use.

It is the only one with no automatic check, and the reason why is written down next to it.

Try: “explain this in design terms”