AAgentic Design School
Field Notes

Experiments, tool tests, and workflow observations.

Field notes are the publication layer for the school: short, practical dispatches from testing tools, designing workflows, reviewing artifacts, and turning examples into lessons. Every note follows the same spine — signal, what we tried, what changed, evidence, and one test to run this week.

Latest field notes

Dated dispatches from real experiments in this project and signals worth re-grounding for designers working with agents. Notes that outgrow the format graduate into full articles.

Tool experiment
2026-06-02
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.

Tool experiment
2026-06-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.

Signal
2026-06-02
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.

Signal
2026-06-02
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.

Workflow note
2026-06-02
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.

Formats for the publication layer

Format
Tool experiments

What changed when an agent was given real design constraints.

Format
Workflow notes

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

Format
Case studies

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

Subscribe path

Field notes go out through the newsletter: workflow templates, tool tests, critique examples, and practical updates from the school.

Processed by Buttondown. You can unsubscribe from any email.