Field notes
Field notes on spec-driven frontend
How we write specs, check agent-built code and keep frontends private, written down in full. Two notes a month, no newsletter, no tracking.
What spec-driven development means for a frontend
Spec-driven development means the written spec is the source of truth, and code, tests and coding agents all trace back to it. For a frontend, that spec has to cover what most backend specs skip: every state a screen can be in, what each user can perceive and operate, and what the browser stores and sends.
Read the noteSpec Kit or OpenSpec: how we choose for each project
We choose by asking what already exists and how change will arrive. If most of the product is still to be written, we use Spec Kit. If most of it is live and changes come in small pieces, we use OpenSpec. Many engagements use both, at the same time, for different parts of the product.
Read the note