DEVELOPER WORKFLOW Nick Trimandylis @nitrimandylis two loops, one harness. 30 skills · 8 CLIs · 8 MCP · 4 cron Claude Code L1 skills 30 L2 CLIs 8 L3 MCP 8 L4 cron 4 L5 ships 7 academic LOOP developer LOOP pitch.nicktrim.com/workflow

Coursework and shipped software run on the same five layers. Only the contents of the cells change.

Everything below serves one of the two loops. Tools that serve neither, the terminal dashboard and the lamp and the theming and the music visualiser, are left out, so every count here equals the boxes on the card.

layeracademic loopdeveloper loop
L1skills30

writing · 3academic-voice, humanizer, writing-style

notion · 6assignments, cas, gp-examples, greek-portfolio, scene-bank, side-quests

documents · 4docx, pdf, pptx, xlsx

coursework · 5aidetect-cli, bacpack-cli, math-notes, rm-handwrite, ytx

ship & publish · 6publish-repo, write-readme, license-public-repos, shipping-clis, update-docs, pitch

build & design · 3flask-vercel, emil-design-eng, startup-research

machine & repos · 3dovetail-cli, shelf-cli, notion-coding-projects
L2CLIs8 bacpack, aidetect shelf, dt, bootlog, config-autopush, agent-wrapped, nous
L3MCP8 Notion, Things, Gmail, Google Calendar, Google Drive, reMarkable Playwright, t3-code
L4cron4 siren ManageBac deadline watcher → ntfy config-autopush, dovetail backup, siren repo sync → Notion
L5ships7 IA drafts, LaTeX answer sheets, ManageBac submissions, Notion records npm packages, Vercel deploys, GitHub repos

How the pieces connect.

22 tools, 27 data flows. Every arrow is a real pipe. Hover a node to trace its edges.

STUDY CODE COMMS MUSIC DASHBOARD + THEMING dev surface commits tracking tasks notebooks / OCR schedule assignments pipes data deliver deploy dotfiles dotfiles watches alerts alerts sync controls audio now-playing theme theme theme active theme widgets heatmap status Claude Code ManageBac bacpack Google Calendar Notion Things 3 reMarkable T3 Code GitHub Vercel siren config-autopush dovetail Discord ntfy Cider jukebox nocturne glance swatch Ghostty fastfetch

The harness itself is one repo. 48 skills and a 135-file memory store, versioned privately. Six of those skills serve neither loop because they are the harness: the planning protocol, the interview, the capture sweep, the cloud dispatch.

Where it runs. T3 Code for everything, Ghostty for the dashboard. Both are libghostty, so one palette carries across every surface.

What is not here. Nine CLIs that serve the desk rather than either loop, and six launchd jobs behind them. They are the reason the machine is pleasant, not the reason the work ships.

github.com/nitrimandylis