Coming soon

Does your site look AI-generated?

There are about a dozen tells, and once you know them you cannot unsee them. Kata already checks for all of them on every pull request. This points the same checks at a URL and tells you what it finds.

https://

Live checks are not open yet. These are real reports, run by hand.

What it looks for

The tells, written down.

None of these are bugs. Every one is a default a model reaches for when it has never seen your product, and every one is already a rule in a compiled Kata file.

The sparkle

A four-point star on anything intelligent. The universal badge for "a machine made this".

no-sparkle
Fake window chrome

Three traffic-light dots around a demo that is not in a browser. Nobody asked for a window.

no-traffic-lights
Emoji as iconography

Typed, not drawn. They break at every size, sit differently on every platform, belong to no brand.

no-emoji-icons
The indigo gradient

Indigo into violet, on the badge and the button and the hero. A default that a great many pages share.

no-gradient-titles
Headlines that break anywhere

Lines filled greedily until one word is stranded. It reads as careless because it is.

balanced-display-lines
Values that should be tokens

A hex typed inline because the model did not know you had a variable for it. Your system quietly rots.

no-raw-hex
Shadows doing a border's job

A soft drop shadow under everything, on a system whose elevation is a hairline.

no-shadows
Components rebuilt from scratch

A hand-rolled modal when yours exists. This is how design systems quietly die.

patterns
Contrast the brand promised

Text under 4.5:1, focus rings removed, meaning carried by colour alone.

accessibility

After the check

A score is a diagnosis, not a cure.

Knowing your site has six tells is useful once. The reason they are there is that nothing told your tools otherwise, and that comes back the next time anyone generates a screen.

The check

Names what is generic

Points at a URL, reports the tells with evidence and a line number where it can find one. Free, no account, nothing stored.

The compile

Writes down what is yours

Reads your codebase and records the colours, composition rules and refusals that make your work look like your work, including the parts nobody wrote down.

The review

Keeps it that way

The same checks run on every pull request against your own file, so the tells never come back and neither does the drift.

Coming soon

Tell me when the checker opens.

One email when it goes live, and nothing else. The checker will be free and will not ask you to sign in.

Free and open source, like the rest of Kata. Nothing leaves your machine when you run it yourself.