CTRL_ALT_DESIGN
I ship and manage design systems for clients.
Core trick
A scheduled agent diffs component parity across repos, Figma, and Storybook, then drafts a roadmap that waits for human approval before filing tickets.
Description
I ship and manage design systems for clients. BELLA is the synthetic stand-in I built for this demo — I can't show real client data, but the workflow is identical.
Every system I onboard has context locked in team members' heads. Every morning I check ten tools by hand — Storybook, Figma, Zeroheight, three platform repos, Jira, Slack, Notion — to find where parity drifted overnight. The decisions get made on gut, because the data's too scattered to use.
Most "design system tools" are static doc sites. They describe the system; nobody watches it.
CHIP is different. It's a control room where an agent watches the system and proposes the diff before the parity drifts. When drift is detected, CHIP files an audit, drafts a roadmap, and waits. I review. I approve. CHIP files the Jira tickets, notifies the platform leads, and writes the diff to the audit ribbon. Every action traceable. No silent merges.
Behind the Ask CHIP input is a Claude Managed Agent on Opus 4.7 with the Notion MCP wired in. When I ask "what does Vitaly say about dashboards", it queries my actual research library — 47 sources from six primary voices on AI-ready design systems.
The dashboard runs the loop on itself. The loop closed.
README excerpt
# CHIP — Cockpit for agentic design systems Submission to **Built with Opus 4.7: a Claude Code hackathon** (April 21–26, 2026). > Most design system assistants answer questions. We intervene at the moment decisions are made. CHIP is the cockpit a design-systems lead opens before approving any cross-platform change. The agent watches every surface — repos, Figma, Storybook, docs, ticket queues, dev-lead channels — and proposes a roadmap when parity slips. The operator approves, edits, or rejects. Tickets file themselves. Audit logs itself. ## Run with live agent + Notion Ask CHIP is wired to a **Cloud Managed Agent** with a connected Notion MCP. When the local proxy is running, questions typed into Ask CHIP query Elleta's actual Notion workspace in real time. **What you need:** Node 18+, an Anthropic API key, a Notion account. **Condensed setup** (full steps in `server/SETUP.md`): 1. Create a Notion internal integration at **notion.so/profile/integrations**. Copy the token. Share your Research library, Friction log, and ritual pages with the integration. 2. At **console.anthropic.com → Managed Agents → New Agent**: paste the system prompt from `server/AGENT_PROMPT.md`, attach the Notion MCP server with the token in the credential vault, copy the agent ID. 3. `cd server && cp .env.example .env` — fill in `ANTHROPIC_API_KEY` and `CHIP_AGENT_ID`. 4. `npm install && npm start` — proxy runs on port 3000. 5. Open the cockpit. Type into Ask CHIP. The reply is live. The Notio