JD
// cd ..
AI Lab · live

    

Most of my work ships through a tight loop with Claude. The differentiator isn't the tool; it's the plan I bring to it. Below: the workflow, the tools, real case studies, and a live playground you can try yourself.

Powered by Claude Sonnet 4.6 · streamed in real time

Live playground

Ask Claude about my work

This playground is briefed on me: my stack, my workflow, the kinds of projects I've built. Ask anything. Streams from Claude Sonnet 4.6. Eight prompts per visitor per day.

Claude Sonnet 4.60 tokready
Ask anything about how Jagadhis builds. Pick an example below or type your own.
⌘↵ to run · 0/1200

The loop

How a brain dump becomes shipped code

Five steps, on a continuous loop. Tap any step to see how the work actually moves.

01Brain dump

Start vague, on purpose

A new task almost never arrives as a clean spec. The first move is to get the half-formed idea out of my head and into Obsidian: bullets, a screenshot, a sentence. Structure comes later.

The stack

The tools, honestly

A short stack on purpose. I'd rather know a few tools deeply than dabble in twenty.

Claude Code

Primary IDE-grade agent

The workhorse. Lives in the terminal, sees the whole repo, runs my work-plan skill, fans out subagents. Almost every commit in this repo passed through it.

Cu

Cursor

Editor + inline AI

Where I write, read diffs, and do quick refactors. Tight loop between selection and prompt, the thing a terminal agent can't do as well as a real editor can.

Bb

Cursor BugBot

Adversarial code review

Reviews every diff before it ships. Catches the silly stuff that the model and I both rationalized past: unused effects, missing null guards, naive perf.

Obsidian

Thinking, before code

Where the vague idea becomes a working brain dump. By the time something reaches the agent, the rough shape already exists in a note.

Supporting stack
Claude APIproduction LLM calls
T3T3 Chatmulti-model lookups
Supabasedatabase + auth
Cloudflareedge + DNS

Case studies

How I'd build it for you

Three AI-native patterns I work with most often. For each: the brief, the plan I'd open it with, and what would ship.

01rag + vector-search

Semantic Search Over a Knowledge Base

Ask

A growing team has Notion pages, Slack archives, and a wiki nobody can find anything in. Keyword search is useless. They need search that understands intent.

Plan
/work-plan: design a RAG-style semantic search over a multi-source knowledge base. Embed Notion + Slack + wiki content into a vector store. Wrap a clean search UI on top. Constraint: low maintenance, runs on existing Postgres.
Ship

pgvector on the existing Postgres, Claude for both embeddings and rerank, single-bar Next.js search UI. The plan ruled out a separate vector DB before any infra was provisioned. Engineers find answers in seconds.

Claude APIpgvectorNext.jswork-plan skill
02agent fan-out

Multi-Agent PR Reviewer

Ask

Pull requests get rubber-stamped under load. They need a tireless first-pass reviewer that catches bugs, suggests refactors, and flags security issues, but doesn't block on style nits.

Plan
/work-plan: automated PR reviewer using parallel Claude agents. One for correctness, one for security, one for refactor opportunities. Synthesize into a single PR comment. Skip style. Run as a GitHub Action.
Ship

A GitHub Action fans out three Claude agents per PR and synthesizes one structured comment in ~90 seconds. Catches real bugs the team missed in a meaningful share of pilot-week PRs.

Claude APIGitHub Actionsagent orchestrationwork-plan skill
03embedded claude

SaaS Onboarding Copilot

Ask

New users churn before they hit the third screen of a complex product. They need a Claude-powered guide that explains features in plain language and adapts to the user's role.

Plan
/work-plan: embed a Claude assistant in the onboarding flow. Briefed on product docs + the user's selected role + their progress. Conversational, not modal. Streams responses. Lives in a sidebar.
Ship

A stateful sidebar chat with role-aware context and streaming responses on Vercel edge. Activation improved, first-week support tickets fell. The plan kept conversation history out of v1, shipping in days, not weeks.

Claude APIstreamingNext.js Edgework-plan skill

Want this kind of AI fluency on your team?

Hire me to architect agents, embed Claude into your product, or train your team on a workflow that actually ships.

Start a conversation