Build · Create · Engineering
AI coding session brief and context file
The founder gets a structured session-brief template plus a populated project-context document so each AI coding session executes against fixed architectural guardrails and logs what it changed, preventing the compounding drift the book warns about.
You receive: A JSON object: { projectContext: { patternsToFollow: [string], dependenciesToAvoid: [string], tradeoffsAccepted: [{ tradeoff, rationale }], outOfScope: [string] }, sessionBrief: { contextDocRef, taskForThisSession, constraints: [string], filesInScope: [string] }, sessionLogTemplate: { built, decisionsMade, assumptionsIntroduced } }
Part of Choose Business Model
What you receive
The shape of your delivered file. Your result is generated for your inputs.
Your deliverable is a structured document carrying these fields:
- Constraints
- Context Doc Ref
- Dependencies To Avoid
- Patterns To Follow
- Project Context
- Rationale
- Session Brief
- Session Log Template
- Task For This Session
- Tradeoff
- Tradeoffs Accepted
Some fields carry set values, drawn from:
built, decisionsMade, assumptionsIntroduced
yes, true, 1
Opens soon
STUD opens runs for everyone soon, on every play at once.
Scope of the check
What's verified: STUD verifies the brief and context document are structurally complete (required sections present, minimum counts met, tradeoffs each carry a rationale, log template has its three fields). STUD does NOT verify the patterns are good architecture, that the dependencies-to-avoid are the right ones, or that following the brief produces working code. It checks the scaffold's completeness, not engineering correctness.
Get early access to STUD the day it goes live.