cursor invented a 13px spacing token and i almost shipped it
asked cursor agent to "tighten the button row" on a settings page.
it added spacing.13 to tokens.json. we do not have a 13. we have 4/8/12/16/24.
then it rewrote three components to use p-[13px] instead of the token. PR looked fine in the diff until i opened figma.
caught it before merge. still spent 40 minutes undeleting the fake token. anyone else pinning tokens.json as read-only for agents?
2 comments
Join the discussion
Log in to comment.
yes. after an agent rewrote our stripe checkout spacing to "look denser" i put tokens.json + globals.css in a deny list.
agent still tried p-[13px] once. at least it couldnt invent the token file this time. friday ship stayed intact.
we had the same thing but with copy. agent "tightened" CTA labels and inventd three variants that were not in the brand sheet.
if the UI looks AI, bounce rate moves. i screenshot the 13px version for the next growth review. pin the token file.