Project case study
Workspace Kit
I wanted to stop explaining my projects from scratch every time I opened a new AI chat. Workspace Kit gives the work a place to live, a way to stay current, and a starting point for the next conversation.
My role: Product architecture, workflow design, testing and iteration with AI-assisted implementation across Claude and Codex.
Watch the interactive walkthroughHow it works
Capture the meeting
Meeting notes become dated evidence.
The workflow saves the source note before extracting commitments, dates and people updates into typed records.
Route each fact
Each update lands in its owning record.
A project registry selects the owner. The workflow stores the fact once and adds source pointers to the relevant project inboxes.
Rebuild the project brief
A short briefing reflects the latest verified work.
The maintenance workflow reconciles open inbox entries against owning records before regenerating the compact project briefing.
Resume with context
A fresh chat starts with the project and its next action.
Startup instructions select the relevant briefing and open inbox. Detailed evidence is loaded when needed, not copied into every prompt.
Give every fact a home.
I built a portable workspace around a simple rule: a fact should have one authoritative home. Project briefs stay short, detailed evidence stays in its own records, and new updates enter an inbox before they are reconciled. I use the same approach in personal and professional work, with different implementations for Claude and Codex.
- Focus
- File-based context, Python tools, routing, skills and host-specific automation
- Status
- Reusable kit; configured personal and work implementations
How it works
Rules select the project; owning files hold durable records; inboxes carry new source pointers; compact briefings give the next chat a starting point. Python checks validate the workspace structure and configuration, while hooks and schedules depend on the host implementation.
A decision that mattered
My earlier work setup collected more information than a new chat could use. The redesign separated rules, briefings, records, evidence and inboxes. The useful question became who reads each file and what they need from it. A clean install also has to prove it can recover context, rather than declaring success because the folders exist.
Two implementations, one approach
I use this approach in both Claude and Codex, with different host-specific hooks and automation. The clean kit is shareable; my configured workspace and personal records are not part of that package.