Builder OS Guide
In buildThe complete operating layer written out, with the templates I actually run.
/ 03Builder toolkit
The stack, with reasoning attached.
Tools earn a place by surviving real use. Each one is listed with the job it does and why it stayed.
Featured stack
Four tools carry ninety percent of the work.
Everything else is situational. If a tool has not been opened in a month it gets cut from the list — the point is a stack you can hold in your head, not a catalogue.
Core4
Claude
Long-context reasoningDrafting, refactors, and anything where the answer depends on reading a lot first.
Obsidian
Capture + system notesPlain markdown, local files. The archive outlives whatever tool is fashionable.
n8n
Flow orchestrationSelf-hosted. Used only after a flow has been run manually at least ten times.
Linear
What is actually runningOne board, two lists. If it is not here, it is not happening this week.
Situational2
Descript
Short-form assemblyFast enough to keep a weekly cadence without an editor.
Val Town
Throwaway endpointsFor the small scripts that would otherwise never get deployed.
Watching1
Cursor
Build surfaceWhere most of the actual code happens. Still evaluating against plain editors.
Drops
AI Stack Teardown
AvailableTool-by-tool reasoning, updated when something enters or leaves the stack.
Automation Toolkit
QueuedImportable versions of the flows broken down in the automation track.
Content System Checklist
QueuedThe pipeline compressed to a single sheet you can keep open while you work.
Drop notifications