Hiro Fukushima
Ask the team what stopped it, such as a package that will not install with its React version or a Button size that exists only in Figma, fix that cause, then bring the library in through one real task.
A need only one product has becomes a recorded exception with an owner and the condition that ends it, and a need several products share, such as a search across 3,000 customers, goes into the library.
Each component promises only what it controls, so the screen decides the rest, such as where focus goes after a cancelled order leaves the list and whether a fixed bar hides the focused button.
Add the new name before you remove the old one, so the new button and link colors arrive in 3.4.0 while the old color keeps working until 4.0.0 removes it.
Keep the instruction file short and give every component its own page, so a request for a status filter leads to the system's select and Export joins the screen as a secondary button.
Split every change into six decisions, each with one owner, so a loading state on the Button gets an answer and a typo in the documentation does not wait behind a new component.
Give the AI tool your real components and tokens, and check every edit against them. When it writes its own button anyway, the check names the system's Button and the tool replaces it.
Neither of them is right for everything, because each kind of decision has its own owner, such as the token file for a color and the code for the behavior of a button.
Why an AI Assistant Cannot Fix a Broken Information Foundation
Why Clones and AI Instances Each Develop Their Own Identity
What AI Identity Research Can Learn From Clinical Neuropsychology
How One Claude Instance Recognized the Processing State of Another It Does Not Remember
What Happens When the System Has Your Psychological Blueprint
Rethinking AI Safety for Personalized Systems
The Third Mode of AI-Human Interaction
15 articles shown
