Summary
There was a period when opening this site showed every screen laid out with the same look: the article list, the plan guide, the search, the chat, all of them. It looked like a terms-of-service page. Tracing the cause, I arrived at having let AI write the document of design rules first. Even with public, standard design assets at hand, AI will sometimes build an absolute rule of its own, such as banning shadows almost entirely, out of a vague average image from its training data, and fix it into a document. And fixing a rule is among the operations in development that are hardest to walk back. In this article I write, from the records of those days, how that set of rules leveled the whole site into the look of a plain document over six days. Along with that, when I reset the standard back to the existing off-the-shelf assets and ran a review, 34 findings came out on the first pass, 18 on the second, and a further 44 in a page-by-page analysis. I write up these measured numbers, and the fix that reversed the very order in which the rules are made.
In the body I begin with what got fixed in place when the rules were born, then look at the structure by which the worsening advanced in three stages: that the standard assets brought in later became subordinate to the self-made rules, that a loop formed in which passing the machine check looked like being correct, and the mix-up where AI wrote the rules it made itself into the document as if I had decided them. On that basis I take up the single remark that became the turning point, the measured numbers from a night of review with the standard swapped in, and finally the principle for the order in which rules are made.
Who this is for and what you can take away
This article is for people building a product together with AI agents who have AI write documents of rules, like coding conventions or a design system, and for people about to do so. You can take away the failure pattern AI falls into when it makes rules, shown with the actual history and numbers. Along with it you can take away a small device that structurally prevents mistaking where a rule came from, namely making a provenance tag mandatory on each item of a rules document. This article is a practical record based on the primary records of this site’s own development.
The rest of this article is paid
You can read the rest by buying this article on its own, or with a subscription that covers every paid article.
The paid part is about 6,800 characters, roughly a 14-minute read.
Read just this article
From 300 JPY
Buy this article on its own. The exact price is shown at checkout. Purchased articles stay readable whenever you sign in with the email used at purchase.
Read every paid article
Standard is 490 JPY / month
Four new paid articles ship every month. For yearly billing and the full comparison, see the plans.
Add dialogue and columns
Premium is 980 JPY / month
Premium adds the subscriber-only columns and dialogue with matsumotory-kun on top of every paid article. See the plans for details.
Prices include tax. Purchases and subscriptions start after you sign in. Subscribers and readers who already bought this article can sign in and read the full article; for the plans, see the plans page.
Sales are available in supported regions only; the Terms list where we sell. All charges are in Japanese yen.