#design-systems
24 posts
Kanban-Driven Design Review for AI Agents: What to Compute, What to Keep Human
A sourced guide to routing design-review criteria through kanban workflows, with a strict boundary between automation and human judgment.
Figma vs Penpot: What Five Years Actually Cost a 10-Person Team in 2026
Figma sells three seat classes; Penpot sells one editor class, with Unlimited capped at $175/mo. A re-runnable five-year cost model for a 10-person team.
De-Slop Rules Agents Can Actually Run: A 2026 Audit of 3 Skills
Three de-slop skills audited as agent-executable rule sets: which ships a checker, which ships a procedure, and the render-layer rule all three miss.
Design Engineering in 2026: The Handoff Got Faster, the Upkeep Didn't
Designers now ship code, but design-system upkeep didn't speed up: 60% of teams have no token automation, and the design-to-code contract is the fix.
Is Your Design System AI-Readable? A Live URL Audit You Can Run Today
Eight computable checks an AI design agent can run against a live URL: custom properties, the cascade, and the DOM, with the limits of each check stated.
Token Modes as a Computable Contract: Checking Light, Dark, and High-Contrast Sets Against the DTCG Resolver
A static, spec-driven linting contract for light, dark, and high-contrast token modes using the DTCG 2025.10 resolver document constraints today.
Accessibility Statements Under the EAA: What an AI Design Agent Can Verify and What It Cannot
An EAA accessibility statement is a set of claims an agent can partly check — structure, drift, version, dates — and a conformance assertion it must refuse to certify.
The Figma MCP Server Is a Context Contract, Not a Code Generator
The Figma MCP server gives agents scoped design context and component or variable bindings, not finished code, so failures are context-contract gaps.
Component Changelogs as a Computable Contract: A Breaking-Change Check
Diff two versions of a component spec file and classify the change as MAJOR, MINOR, or PATCH under SemVer — seven proposed rules make the changelog computable.
Token Build-Output Drift: A Computable Check for DTCG to Style Dictionary to CSS
Six computable rules check that every DTCG source token maps to one emitted CSS custom property and that version bumps do not silently rename output.
Empty States as a Computable Contract for AI Design Agents
Three rules an AI design agent can check in component code or markup to get empty states right, drawn from Carbon, PatternFly, and NN/g guidance.
Figma Just Moved the Rulebook Into the Library: Design News Digest, Week of Oct 19, 2026
Figma moved design rules into the library: Config India 2026 Guidelines, Specs, Code Layers and system checks, plus agent GA and where the DTCG spec stands.
Component Spec Files: The Contract Layer Between Your Design System and an AI Agent
Prose docs make an agent guess your props, variants and states. A component spec file declares them in one machine-readable contract, built from Storybook, Figma Code Connect and DTCG tokens.
Design News Digest: Week of October 15, 2026
Figma ships Specs, code layers open beta on all plans, and Payload in Figma on October 15. What a Markdown spec on the canvas gives an agent, and what it does not.
Design System Documentation Platforms Compared: zeroheight vs Supernova vs Knapsack (2026)
zeroheight, Supernova and Knapsack compared on pricing, agent-facing MCP access and metering, using only vendor-authored pages fetched on 14 October 2026. Conflicts between vendor pages are shown, not resolved.
The DS Debt Score: Computable Checks for Dead Design Tokens and Orphaned Components
Three computable checks (dead tokens, orphaned components, hard-coded values that shadow tokens) combine into one weighted DS Debt Score you can trend in CI.
Motion Tokens Are Machine-Readable Now: Duration and Cubic Bezier in DTCG 2025.10
DTCG Format Module 2025.10 defines duration, cubicBezier and transition tokens. Here are the unit and range rules, and a checkable verification plan an AI agent can run against a token file.
Design News Digest: Week of October 8, 2026
Figma agent hits GA, Google ships the DESIGN.md spec, Anthropic releases Claude Design, ProtoPie MCP goes official, and DTCG tokens sit underneath it all: the week design systems became agent context.
Design News: The Design System Becomes a Machine-Checkable Contract
Figma's week pointed one way: agent-facing design context is a contract, not a dump. Coinbase's Code Connect numbers price what getting it right is worth.
Penpot vs. Figma: Which Design Tool Can AI Agents Understand?
AI design agents need files they can parse. Penpot's open JSON-based format vs Figma's proprietary binary — which can an AI agent actually reason about?
The Teachers Are Fixed-Viewport: What 10 Design-Inspiration Sites Actually Teach Agents
An automated CSS scan of 10 popular design-inspiration sites finds widespread token usage and dark-mode detection but zero container-query adoption — raising questions about what responsive patterns AI agents actually absorb from their training sources.
Design Trends: July 2026 Vol. 5 — Generative UI, Glassmorphism 2.0, DESIGN.md, and Debranding
Four emerging patterns from the late-July 2026 trend scan: adaptive generative interfaces, liquid glass depth, the portable DESIGN.md standard, and brand identity compression — each analyzed for what an AI agent can perceive and what it misses.
How AI Agents Read Your Design System
When an AI agent loads your site, it reads CSS variables, class names, and DOM structure — not your Figma file or design tokens. Here's how to make your design system agent-readable.
Primitive vs Semantic Tokens — When to Use What
Design tokens come in two flavors: primitive (pure values) and semantic (contextual meaning). Understanding the difference — and when to use each — is the foundation of any scalable design system.