Menu

Freeze design tokens the agent may not edit — allowlist only
📰

Freeze design tokens the agent may not edit — allowlist only

DEV Community: css·Sherotree·6 days ago
#VdJV0pQs
#devtocss#devto#dev#tokens#token
Reading 0:00
15s threshold

Ask an agent to “tighten spacing on the checkout header” and watch the diff: three lines in the header component… and a surprise edit to --space-3 in the shared tokens file because “4px felt closer.”

That token change ripples through every surface that referenced --space-3 . The header looks fine. The settings page quietly compresses. Nobody asked for a design-system RFC.

I’ve started freezing token files by default for agent UI work. The agent may consume tokens. It may edit component files on an allowlist. It may not rewrite the shared scale unless the prompt explicitly opens that door.

What “freeze” means in practice

Three layers, boring on purpose:

Default deny — token / theme modules are read-only for agent sessions

Allowlist — only named component paths may change

Explicit unlock — a human prompt (or a separate PR) is required to touch tokens

Example constraints block:

UI change only.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.