Jalil Baker · Builder · Claude Corps
These aren't mockups. They're running right now.
Three production systems I designed, built, and operate solo, with Claude: a homelab cockpit, an agentic ops engine, and an AI resume studio. The page you're reading is the fourth.
The work
Three systems, one builder.
Not a portfolio of concepts. Each one is built, runs on my own infrastructure, and does real work for me today.
- 01 Homelab cockpit Mission Console A self-hosted operator console that runs my whole homelab from one screen: live service health, an in-pane shell into the host over Tailscale SSH, every tool nested without leaving the page.
- 02 Agentic ops engine Ops Command Center An agentic ticketing system where none existed. It turns a noisy MSP workspace into pre-vetted onboarding, offboarding, and task tickets, each with its own auto-generated playbook.
- 03 AI resume studio Resume Gold A self-hosted studio where a chat-driven Claude workflow turns a base resume plus a real posting into tailored, ATS-scored materials, with provenance rules so it can never invent experience.
01 · Homelab cockpit
Mission Console
A self-hosted operator console that runs my entire homelab from one screen. It boots like a machine, locks behind a PIN, then opens into a live cockpit: service health, an in-pane terminal straight into the host, and every other tool nested in place. No new tabs, no leaving the page.
The bridge, end to end
The console runs in a container but joins the tailnet as its own node and drives the host purely over Tailscale SSH. No sshd on the host, no exposed port, no docker socket mounted. One identity-based bridge for the shell, health checks, and quick actions.
02 · Agentic ops engine
Ops Command Center (+ LLM Wiki)
At Personified I support non-technical teams who had no ticketing system at all — so I built one that builds itself. A Claude triage copilot watches the intake (Slack, Notion, Drive), scores each request against a living playbook plus an LLM wiki I keep in Obsidian, then writes the steps into per-ticket docs in parallel — onboarding, offboarding, access changes — all sorted into categories on the daily dashboard before anyone lifts a finger.
How a ticket builds itself
03 · AI resume studio
Resume Gold
Scoped, designed, and built end to end: a studio where a chat-driven Claude workflow turns a base resume plus a real job posting into tailored, ATS-scored application materials. The generation step is a strict contract with provenance rules, so the model can sharpen the truth but never invent it.
Intake interview
Confirm-gated chat captures the base resume + the real posting.
ATS evaluation
A deterministic engine scores keyword + structure fit.
Provenance-locked generation
Strict-JSON contract: every claim traces to the source. No invention.
Designed output
Claude-generated print designs rendered to PDF, headless.
How I build
Solo, with Claude, end to end.
No team behind these. I scope, design, build, deploy, and run them myself, on my own infrastructure. The method is the product.
Agentic by default
I run a multi-agent harness: several Claude agents in parallel — planning, building against the real source, and reviewing — inside isolated git worktrees.
Evals, not vibes
Every real-world miss becomes a test case. A looping validation pattern scores the work and iterates until it passes before output is accepted.
Built for handoff
Good tools shouldn't stay locked to the technical. I build so the person who needs the tool can use it, regardless of how much code they know — plain runbooks, sane defaults, handoffs that outlast me. The point was never that I built it; it's that it keeps working for whoever needs it next.
The close
The work isn't done until someone else can own it.
Jalil Baker · Illinois · open to relocate for Claude Corps
Built from scratch in SvelteKit + GSAP. No template, no page builder.
This page is the fourth system.