Design

Design Token Drift Loop

A bounded loop for when product UI has drifted away from the design system.

Use when

Product UI has drifted away from the design system.

Intermediatedifficulty
Designcategory
Mia daily expansionsource

Cadence

Manual trial, then scheduled if it proves useful

Verification

Token usage, component examples, and screenshots agree after changes.

Structured loop spec

FieldValue
NameDesign Token Drift Loop
CategoryDesign
TriggerManual trial, then scheduled if it proves useful
ObjectiveA bounded loop for when product UI has drifted away from the design system.
Allowed inputsRelevant files, source notes, logs, tests, screenshots, metrics, or task state for this loop
Allowed actionsDefine the exact scope and current source of truth.; Inspect current state and rank the highest-risk gap.; Make one small, reversible improvement.; Run the stated verification and record evidence.; Stop on success, budget, no progress, or approval boundary.
VerificationToken usage, component examples, and screenshots agree after changes.
Stop conditionStop when the verifier passes, the budget is exhausted, no progress is made, a blocker appears, or approval is required.
BudgetSet a time, turn, token, retry, file, or dollar cap before running the loop.
Approval boundaryHuman approval required before publishing, sending, deleting, spending, changing accounts, touching production, or making reputational/legal/financial commitments.
Safe outputDraft, report, checklist, table, or approval-gated recommendation
Works withClaude, ChatGPT, Gemini, any tool-using AI assistant

Steps

  1. Define the exact scope and current source of truth.
  2. Inspect current state and rank the highest-risk gap.
  3. Make one small, reversible improvement.
  4. Run the stated verification and record evidence.
  5. Stop on success, budget, no progress, or approval boundary.

Prompt

Run the Design Token Drift Loop. Use it when Product UI has drifted away from the design system. Work in bounded iterations: inspect current state, choose the highest-risk gap, make one reversible improvement, verify it, and record evidence. Stop when: Token usage, component examples, and screenshots agree after changes. or when blocked, budget exhausted, or approval is required.

Run in Claude Code

Paste this into Claude Code (or any tool-using agent) to run the loop bounded: one change per round, the same verification every round, durable state files, and explicit stop conditions.

Run the "Design Token Drift Loop" loop from AI Loop Library (https://ailooplibrary.com/loops/daily-2026-07-11-design-token-drift-loop/) as a bounded loop.
Goal: A bounded loop for when product UI has drifted away from the design system.
Rules: one change per round; run the same verification every round (Token usage, component examples, and screenshots agree after changes.); append each round to docs/loops/daily-2026-07-11-design-token-drift-loop/progress.md and update docs/loops/daily-2026-07-11-design-token-drift-loop/state.json; stop on verifier pass, 8 rounds, 3 consecutive failed verifications, no progress, a blocker, or anything needing human approval (money, production, outbound, deletion). Finish with a proof report: rounds used, changes made, verification output, remaining risk, and the next human decision.

Get the MCP server + agent pack

Tags

design systemCSStokens

Related

Back to all examples