The Foundry
I said in the manifesto that I will build, a lot, and release something every two weeks if I have my way. These are the releases, and below them is how I build them on my own.
Released
Nine releases since May 2026, five of them from September 2026 or later. The open-source ones are MIT licensed: use them, fork them, or read how they were made.
- Sep 2026claude-computerA template that sets up a Mac for a solo developer working in Claude Code.Open source · claude-computer.com · Source
- Sep 2026Wet WicketCricket through data, great matches, games and essays.Product · wetwicket.com · Open data
- Sep 2026Adjust MaadiA Namma Bengaluru potboiler. A new scene every visit.Open source · adjustmaadi.com · Source
- Sep 2026Four SkiesA wry virtual sage who reads your chart in four traditions at once.Product · fourskiesastro.com · How it was built
- Sep 2026DunlinA white-label platform for media companies to launch and run a streaming service.Product · dunlin.media
- Aug 2026AEO visibilityWhat Claude tells buyers about your brand, sent to you as a report.Free tool · marain.space/tools
- Jun 2026skillkitA per-project skill manager for Claude Code. Keep a registry of skills and install the ones a project needs.Open source · github.com/narendranag/skillkit
- May 2026Global Energy MapWho loses oil and gas when a chokepoint closes or a pipeline is cut.Open source · energymap.marain.space · Source
- May 2026TuiTrisTetris in the terminal, written in Python with Textual.Open source · github.com/narendranag/tui-tris
How I build, as one person
I work alone, with Claude Code as the operator of my machines. Most people set up the machine, then the tools, then add AI. I install Claude Code first and have it do the rest.
The whole setup is published as a template, claude-computer. It has three parts: a stack, a way of organizing the machine, and a process. What follows is the short version.
The stack
- Claude Code
- Tailscale
- GitHub
- Bitwarden
- Cloudflare
- Obsidian
- Homebrew
Three jobs I keep
- AuthenticateClaude never handles a credential. I sign in, and the keys stay in the password manager.
- Set the modeClaude runs in auto mode with the guard rails on: an ask list for pushes, deletions and sudo, and a deny list for force-pushes and raw credential access.
- DecideClaude proposes and I choose, for anything destructive, costly or involving a credential.
The habits
- A brain per folderEvery folder that needs automation has a CLAUDE.md and a TASKS.md, and I start Claude where the work is.
- The mapSix top-level folders, with repositories one level down and never nested. A script compares the machine with the recorded map, and drift is treated as a bug.
- The session loopA hook pulls the shared repository when a session starts, and another commits and pushes the notes when it stops, so every machine has the same memory.
- CLI first, MCP lastSmall command-line wrappers for search, the browser, mail, calendar and files read their keys from the password manager. That keeps tool schemas out of every session.
- If it can be a scriptIt is one. Slash commands are kept for steps that need judgment, and they call the scripts.
- The second brainObsidian, as plain markdown in a git repository. Everything lands in an inbox and Claude does the filing.
It is opinionated, built for macOS first, and young. The guard rails cut down the prompts; they are not a security boundary, and none of it works if I stop paying attention.
One command stands up an idea
Provisioning a new idea takes a single command. It creates the repository, wires up hosting and a database, and inherits a business template that every spin-out starts from, so the setup work that usually eats the first fortnight is already done and identical each time.
When standing an idea up costs almost nothing, building it becomes an experiment, and I stop arguing about ideas that shipping would settle.