Six open source projects. All built with Claude Code, for Claude Code. I shipped InkTemplates (this entire site, with payments) in a single session. These are the tools that made that possible.
Each of these started as a problem I hit during real work. Not hypothetical frameworks. Working tools, tested in production, with rough edges filed down over dozens of sessions.
Infinite context orchestration for Claude Code. When your conversation hits 80% context, most people start a new session and lose everything. eaurl.ai manages handoffs, compresses intelligently, and keeps multi-hour sessions coherent. 20 tools, full test suite, used in every session I run.
Cooperative compute orchestrator for Claude Code. Named after the Navy term for sharing bunks in shifts. Pool idle Max accounts into shared capacity so no seat sits unused. Load balances sessions across accounts with health checks, automatic failover, and usage tracking.
Memory consolidation for Claude Code. Three-phase analysis: observe during the session, consolidate after it ends, recall when the next one starts. Nightly automation compresses observations into durable memory. Your Claude sessions remember what happened last week without you copy-pasting context.
Composable prompt engineering. Pipe prompt transforms together like Unix commands. Start with a base prompt, pipe it through a tone filter, then a format constraint, then a domain adapter. Each transform is a standalone module you can mix, reorder, or skip. Prompts as pipelines, not monoliths.
A Claude Code skill and CLI for dogfooding. The rule is simple: use what you build before you call it done. This tool enforces that. After every feature, it prompts you to actually use the thing you just shipped, logs what broke, and feeds the lessons back into your next session. Recursive self-improvement through forced usage.
14 AI workers across 4 engines (Claude, Gemini, Codex, local Ollama), coordinated through tmux windows on a 4-machine Tailscale mesh. I used this setup to build an entire business in a single session. One controller dispatches tasks, monitors output, and routes work to whichever engine handles it best. Not theory. Running right now.
InkTemplates (this site) went from zero to live SaaS in a single Claude Code session. Not a landing page. A working product with Stripe payments, SEO infrastructure, a social launch pipeline, blog content, and a template generation engine backed by a GPU server.
Created the repo, generated the first 5 SVG templates with Python, converted to PNG and PDF.
Dark theme, responsive layout, template gallery, pricing section, email capture. Deployed to GitHub Pages.
Stripe Checkout integration, webhook handlers, SQLite-backed credit system with plan-aware rate limiting.
Sitemap, robots.txt, JSON-LD, 7 blog posts targeting long-tail keywords, tablet-specific landing pages.
Product Hunt kit, 10-tweet launch thread, LinkedIn content sequence, community outreach plan. Ready to ship.
I run operations at a meal delivery company during the day. At night I build tools for Claude Code. Not as a hobby. As a system for getting more done in less time with fewer people.
Over the past two months: 160+ Claude Code sessions, 9 production tools deployed at work, 6 open source projects published, and a 4-machine distributed compute setup running 14 AI workers around the clock. I didn't start as an engineer. I started as someone who needed to ship things and found that Claude Code made it possible.
The tools on this page are the ones I use to stay productive at that pace. They solve real problems I hit every week: context limits, session memory, idle compute, prompt management, and the coordination overhead of running multiple AI engines at once.
If you want to learn how to do this, I teach it.
Start with the free templates. See what Claude Code can do when the input is structured right.