Better than another spreadsheet.
Everyone on my team tracked their work in an Excel file. I wanted something better — built for the work we actually do, and something I'd want to open every day.
One rule shaped the whole thing: it had to stay local, like a spreadsheet. No servers, no accounts, no sign-up. Your data lives in your browser, and a one-click backup file is the entire sync story.
A complete product, not a snippet.
Fieldbook is a working task tracker for a real team's daily use: tasks and subtasks, priorities, due dates, a focus mode, and backup/restore — all keyboard-accessible.
The whole thing is one hand-authored HTML file. No build step, no framework, nothing to install.
Architect first, then direct.
I started by specifying the design system — tokens, the press metaphor, the motion language — then directed the coding agent to build each component against that spec, reviewing and correcting every pass.
The hard calls were mine: the button-press shadow math (the face translates while the shadow shrinks so its outer edge stays planted), a two-layer reduced-motion strategy, and the discipline of keeping it all in one file.
“I architect and make the calls; the agent does the typing. That's not less engineering — it's more leverage.”
14 colors, 2 shadows, 19 motions.
One :root defines the whole language: an earthy palette, a hard-offset shadow scale, a serif/sans split, and a CSS-variable button-press system — plus 19 keyframe micro-interactions, all gated behind a reduced-motion strategy.
A complete, polished product — design system and all — shipped solo in a weekend.
That's the whole pitch in one project.