The real pain today
The agent invents components. It writes a plausible button with raw colours, because it never saw the system.
Review comments arrive late. A screen passes design review, then fails a system or accessibility check in the last week.
Deprecations surprise you. A token you use disappears in a release, and you find out when the build breaks.
Exceptions are folklore. You were told you may break a rule "for now". Nobody remembers who said so.
Your week with Loom
Monday. Your home lists what moves this week: deprecated tokens and components you still use, each with its replacement and its removal date. See the front-end developer's home
Tuesday. You ask your coding agent for a settings page. It calls Loom's MCP server: search_system finds the real components with their imports, and check_composition checks the page before you see it, flagging raw values, local copies of system components and unlabelled form controls. Watch a recorded agent
Wednesday. The same checks run in CI as a command. An error fails the build; a warning is advice. Each finding names its rule and the fix.
Thursday. A change you depend on is breaking. Loom's contract diff marked it major, so it waits for the scheduled major. npm run migrate writes the codemod for renamed components, props, values and tokens, and opens the migration as a draft pull request you review, with the manual steps as a checklist. The simulator says beforehand how many call sites the codemod rewrites and how many a person must change. Both are built and tested on sample consumers and simulated git hosts, not yet in a client repository.
Friday. You need to keep a raw value for one more release. You ask for an exception with a reason; the area owner grants it with an end date of at most 90 days, and checks downgrade that finding until then.
What changes
Fewer late surprises. Loom measures drift caught before merge, the share of agent-written changes that pass the rules, and reuse of system components, and says where each number comes from. In the product tour they are sample values; in your organisation they come from your own records.
What you never have to do
You never paste the design system into a prompt. You never guess whether a value is allowed. You never remove a deprecated token by hand without knowing every place it is used: the audit lists each use with its replacement.
Coming next
Migration pull requests with before and after screenshots, and one pull request per consuming repository from a single run. A packaged CI step and editor plugins for VS Code and JetBrains will replace the command you wire up today.