Systems & primitives — Field Notes

DESIGN SYSTEMS COLLECTIVE

LDLR DESIGN FIELD NOTES

Encode Intent, Not Just Components

When agents author your design system, intent must live in tokens and metadata, not only in a practitioner's head.

JUN 29, 2026

The System Knows What You Built. Does It Know What You Meant?

AI has lowered the floor on execution. The ceiling on judgment is still yours.

Why it matters

— The question moved from can AI use your system to can it write it.

— Agents connected to metadata make decisions about what to reach for.

— Discoverability isn't documentation coverage; it's intent legibility where decisions get made.

— Tokens should carry purpose, not just values; metadata should explain what's for.

— Unresolved ambiguity gets filled by the agent's best guess, everywhere, unnoticed.

Read on Substack →

Systems & primitives Critique & decision-making

FIGMA

LDLR DESIGN FIELD NOTES

Designing agents people can trust

Sheta Chatterjee walks through the design calls behind Gemini Enterprise: a shared AI inbox, team project spaces, and keeping people in control.

BY SHETA CHATTERJEE / APR 29, 2026

How to design agentic tools for work

the user's focus should always be on their goal, not on managing AI

Why it matters

— One brand language up top, real differentiation down at the feature level.

— The guiding rule: keep focus on the goal, not on managing AI.

— An AI Inbox shows what each agent is doing and needs.

— Chat threads become shared project spaces, so the AI joins the team.

— Transparency and an obvious way to intervene, since the stakes are real.

Read on Figma →

Systems & primitives Cross-functional & process Craft & detail

JAMIESON ROTHWELL

LDLR DESIGN FIELD NOTES

Shipping binaries, not just mockups

After three decades built around the handoff, Jamieson Rothwell now ships working software and treats those build choices as design decisions.

MAY 11, 2026

Product Design in 2026: Am I still a designer?

Shipping is the new designing.

Why it matters

— The old ritual, design then hand off blueprints, is over for him.

— LLMs and coding agents turn static design into active construction.

— Local-first as a design choice: his tool Warren guards data ownership.

— A small cross-platform system, Sitka, keeps React, HTML, and Swift aligned.

— Barrier to entry collapsed; the barrier to greatness is still taste.

Read on Medium →

Prototyping & exploration Systems & primitives Craft & detail

GEORGE XING

LDLR DESIGN FIELD NOTES

Shipping Solo With Agent Workflows

A solo builder lays out the agent framework, test automation, and remote setup that made his product workflow far faster.

MAY 6, 2026

Prototyping & exploration Systems & primitives

JAKOB NIELSEN

LDLR DESIGN FIELD NOTES

Profit Comes From Workflow Redesign

Citing a 515-startup field experiment, Nielsen argues AI pays off when teams redesign whole workflows, not single tasks.

APR 9, 2026

Cross-functional & process Systems & primitives

VIOLETTA BONENKAMP

LDLR DESIGN FIELD NOTES

Design as Executable Knowledge

A founder argues the real shift is encoding brand rules and taste into reusable files non-designers can run.

JUN 1, 2026

Systems & primitives Craft & detail

DESIGN MAVERICKS

LDLR DESIGN FIELD NOTES

Design is becoming leadership literacy

Forty design leaders in Amsterdam reach the same conclusion: the role is dissolving while the capacity becomes foundational to leadership.

JUN 4, 2026

When AI Builds Everything, Design Becomes Everything

We are training people for a job. We should be cultivating a capacity.

Why it matters

— Intercom now ships over 90% of pull requests authored by Claude Code

— When execution costs nothing, judgment about direction becomes the product

— Atlassian runs 64% ICs, every designer a platform designer, demo before memo

— Frigieri's upstream conditions: workflows, data pathways, decision rights, controls

— The Frozen Middle: everyone experimenting alone without strategic guidance from above

Read on Design Mavericks →

Hiring & team Critique & decision-making Systems & primitives

GITHUB

LDLR DESIGN FIELD NOTES

Accessibility as an operating system

GitHub's five-year accessibility program turns outward, with audit data, design tooling, and AI agents making inclusion operational rather than aspirational.

BY ED SUMMERS / MAY 21, 2026

Building GitHub's next chapter in accessibility

Accessibility is never done.

Why it matters

— Audit analysis found 48% of issues preventable in the design phase

— Figma Annotation Toolkit documents accessibility intent before a line of code

— Copilot triage auto-populates 80% of metadata, cutting resolution time 62%

— Pull request files-changed page rebuilt accessibly across seven shipped updates

— Copilot CLI shipped screen reader mode and colorblind themes from day one

Read on GitHub →

Systems & primitives Craft & detail Cross-functional & process

GOOGLE LABS

LDLR DESIGN FIELD NOTES

Vibe design gets a canvas

Stitch evolves into an AI-native infinite canvas: design agents, voice critique, and DESIGN.md portability between design and code tools.

BY RUSTIN BANKS / MAR 18, 2026

Introducing "vibe design" with Stitch

Close the gap from idea to reality in minutes rather than days.

Why it matters

— Start from business objective and intended feeling, not a wireframe

— An agent manager tracks parallel explorations across the infinite canvas

— DESIGN.md exports design rules as agent-friendly markdown between tools

— Voice critique makes real-time updates while you stay in flow

— Stitch screens together and press play to preview full journeys

Read on Google Labs →

Prototyping & exploration Systems & primitives

POSTHOG

LDLR DESIGN FIELD NOTES

When FOMO Ships It Too Early

PostHog's CEO on shipping AI before it worked, the architecture fix that turned it around, and betting the product on agents.

BY JAMES HAWKINS / MAY 1, 2026

PostHog's next chapter

FOMO came ahead of progress.

Why it matters

— A one-shot assistant shipped early, returned empty graphs, and felt half-useful.

— The fix was a single query loop so the agent could iterate.

— Agents now create most new dashboards, with MCP usage roughly doubling monthly.

— The bet: a headless, proactive product that ships fixes while you sleep.

— Hawkins is candid about UX churn, and why the short-term pain is worth it.

Read on PostHog →

Prototyping & exploration Critique & decision-making Systems & primitives

BOOTCAMP (MEDIUM)

LDLR DESIGN FIELD NOTES

Stop Designing Outputs, Design Relief

An early-career designer makes the case for building leverage: encode taste into tools and remove friction instead of polishing more screens.

DEC 18, 2025

Stepping Into 2026 as a Designer (When You're Still Early in Your Career)

I wasn't designing outputs anymore. I was designing relief.

Why it matters

— Polished screens are cheap now, so execution alone no longer carries value.

— He stopped refining artifacts and started building small tools that remove friction.

— A junior's edge: no fixed identity, so quiet experiments come easier.

— Taste still matters, but it scales only once you encode it.

— The move is from producing screens to shaping how they get produced.

Read on Bootcamp (Medium) →

Systems & primitives Prototyping & exploration

DESIGN SYSTEMS COLLECTIVE

LDLR DESIGN FIELD NOTES

Fully Machine-Readable Design Systems

AI reads your design system differently; structured metadata beats prose documentation. · Foundations should be always-on; components served on demand through an MCP.

MAY 14, 2026

Fully Machine-Readable Design Systems

Why it matters

— AI reads your design system differently; structured metadata beats prose documentation.

— Foundations should be always-on; components served on demand through an MCP.

— At Indeed, JSON cost five times less than Markdown for the same query.

— Progressive disclosure maps what AI needs without flooding its context window.

— The system you wrote for designers won't work for agents without a rewrite.

Read on Design Systems Collective →

Systems & primitives Craft & detail Research & validation

DESIGN SYSTEMS COLLECTIVE

LDLR DESIGN FIELD NOTES

Your System Can't Explain Itself. That's the Problem.

Most design systems are a shared palette and a Confluence page nobody trusts. · A real system enforces its contracts; agents expose every gap you papered over.

MAY 18, 2026

Your System Can't Explain Itself. That's the Problem.

Why it matters

— Most design systems are a shared palette and a Confluence page nobody trusts.

— A real system enforces its contracts; agents expose every gap you papered over.

— Can your system explain itself to an LLM without hallucinating your brand?

— AI didn't create this problem; it's revealing the documentation debt you already had.

— Legibility is the work. Not the components. Not the tokens. The clarity.

Read on Design Systems Collective →

Systems & primitives Craft & detail Storytelling & narrative

BOOTCAMP (MEDIUM)

LDLR DESIGN FIELD NOTES

The Design System You Didn't Choose

shadcn became the default behind every AI-generated UI. A developer built it. Most design teams never noticed they're now competing with it.

MAY 11, 2026

The most important Design System in 2026 that designers missed was built by a developer.

Every shadcn project is a fork.

Why it matters

— AI tools converged on shadcn as the default shape of generated UI.

— It lives in GitHub and React templates, not Figma, so designers missed it.

— The MCP server turned accidental convergence into installed infrastructure.

— The work isn't fighting the default. It's reading it, then deciding what to override.

Read on Bootcamp (Medium) →

Systems & primitives Critique & decision-making

DESIGN SYSTEMS COLLECTIVE

LDLR DESIGN FIELD NOTES

Agents Don't Read Your Documentation

Agents read structure and naming, not docs or goodwill. The informal contract that held design systems together becomes a hard boundary.

MAY 11, 2026

Systems & primitives Craft & detail

MICROSOFT DESIGN

LDLR DESIGN FIELD NOTES

The system is the handoff

Microsoft consolidated Copilot into four surfaces tied together by a 'Throw and Catch' pattern. The pattern, not the components, is the system.

BY JON FRIEDMAN / MAY 12, 2026

A simplified system

Intelligence without continuity can feel like an interruption instead of a thought partner.

Why it matters

— Four canonical Copilot surfaces, not scattered features per app.

— 'Throw and Catch' governs handoff between the four surfaces.

— Context persists across apps. The conversation does not restart.

— On-canvas narrows from exploration to document focus on selection.

Read on Microsoft Design →

Systems & primitives Prototyping & exploration Craft & detail

GITHUB (ENGINEERING & DESIGN)

LDLR DESIGN FIELD NOTES

When 'feels instant' is the spec

Most performance work chases tail latency. GitHub Issues reframed it around distribution shape, then named 4.7% server/cache divergence as the price of feeling instant.

BY ALEXANDER LELIDIS / MAY 14, 2026

From latency to instant: Modernizing GitHub Issues navigation performance

We are willing to serve data that may be slightly stale if that allows the navigation to complete near instantaneous

Why it matters

— Reframed the goal: shape the distribution, not chase p99.

— Five layers: in-memory cache, IndexedDB, preheat, service worker, code-split.

— Accepted 4.7% server/cache divergence as the operating envelope.

— Cache hit went from 33% to 96%. P10 dropped to 70ms.

Read on GitHub (Engineering & Design) →

Craft & detail Systems & primitives Critique & decision-making

DESIGN SYSTEMS COLLECTIVE

LDLR DESIGN FIELD NOTES

AI didn't add to the spec

AI-readiness isn't a separate category. The same fundamentals (tokens, layout intent, accessibility, governance, handoff contracts) finally have to read clearly to a non-human.

APR 27, 2026

Legible by Design: What AI Readiness Actually Demands of a Design System

The best systems are the ones that remain coherent even when the people who built them have moved on

Why it matters

— AI doesn't need a new system. It exposes the broken one.

— Five load-bearing properties: tokens, layout intent, a11y, governance, handoff.

— Legibility to machines reveals what was always opaque between humans.

— Stewardship beats generation. The system has to outlive its authors.

Read on Design Systems Collective →

Systems & primitives Critique & decision-making Cross-functional & process

WEBFLOW

LDLR DESIGN FIELD NOTES

Where the AI code debt lands

AI-generated code defers cost, it doesn't reduce it. Seven debt categories concentrate far from where the velocity gain was booked, including reviewer fatigue and security debt.

BY ANKIT AGRAWAL / MAY 12, 2026

The cleanup cost of ungoverned AI-generated code

It costs a contributor five minutes to generate a low-quality AI pull request, and hours for the maintainer to verify and reject it.

Why it matters

— Seven debt categories, segmented by who actually pays the bill.

— Time-to-exploit window collapsed from months to days.

— Five minutes to generate a PR. Hours to reject one.

— Triage PRs by risk class. Output is the wrong metric.

Read on Webflow →

Critique & decision-making Cross-functional & process Systems & primitives

FIGMA

LDLR DESIGN FIELD NOTES

When the canvas reads the code

Most teams treat canvas, code, and PRD as three competing artifacts. Brett McMillin's reframe: a connected system, with an agent translating between them and the designer's judgment moving through both.

BY BRETT MCMILLIN / APR 30, 2026