Skip to content
Field notes / 05

Experiments,
evidence, and
what changed.

Short, practical dispatches from testing tools, designing workflows, reviewing artifacts, and turning examples into lessons.

Latest field notes

Signals worth
testing now.

Dated dispatches from real experiments in this project. Notes that outgrow the format graduate into full articles.

01

Syncing the school's design system to OpenPencil

We wired agenticdesign.school so that DESIGN.md, the components folder, and the live pages continuously rebuild a file-backed OpenPencil canvas: token layers, shadcn primitives, custom components, and full-length page snapshots, regenerated on every watched change.

Format
Tool experiment
Published
2026-06-02
Read field note
02

Pushing the design system into Figma over MCP

The same payload that rebuilds the OpenPencil canvas also targets Figma: a generated canvas payload, a local plugin that writes native frames and page snapshots, and a remote MCP path that is partly blocked. This note documents what worked, what is blocked, and the workaround that ships today.

Format
Tool experiment
Published
2026-06-02
Read field note
03

HTML artifacts are becoming design deliverables

A growing share of agent-assisted design work ships as a single self-contained HTML file: prototypes, slides, review boards, even motion studies. This note re-grounds that signal for designers — when an HTML artifact is the right deliverable, and when it quietly becomes unreviewable debt.

Format
Signal
Published
2026-06-02
Read field note
04

Extracting design systems from live websites

New agent tools can pull a live site's tokens, type scale, spacing, and brand assets straight from the terminal. That is genuinely useful for audits, migrations, and competitive teardowns — and it raises rights questions a designer should answer before the extracted system touches production work.

Format
Signal
Published
2026-06-02
Read field note
05

Field notes as a publication layer

What field notes are, how they differ from the long-form articles, and the five-part spine every note follows: signal, what we tried, what changed, evidence, next test.

Format
Workflow note
Published
2026-06-02
Read field note
Publication formats

A consistent spine
for fast learning.

01

Tool experiments

What changed when an agent was given real design constraints.

02

Workflow notes

Reusable operating loops for briefing, critique, revision, and QA.

03

Case studies

Before-and-after examples from product work, books, and prototypes.

Subscribe path

Get the next
field note.

Workflow templates, tool tests, critique examples, and practical updates from the school.

Processed by Buttondown. You can unsubscribe from any email.