Best Claude use cases for coding

Claude Code plans and reviews, Codex executes through the Codex MCP, and notes and skills live in Obsidian.

1. Use Claude Code as the planner. It sends execution to Codex only through the Codex MCP, which Claude manages.
2. Run the agents in dedicated environments so they keep working when your laptop is closed.
3. Keep notes and skills in Obsidian so you can switch tools and devices.

+2 more steps in the copyable prompt.

Claude, Codex, Cursor, OpenCode, Antigravity, Command Code · Coding · by Louis-François Bouchard (X post, 17 Sep 2026) · source

Cockroach Labs’ label-triggered role agents planned 15 sub-issues and shipped Db2 migration for $4,172.

1. Start from a single GitHub issue describing the ask.
2. A planning agent decomposes it into sub-issues with an explicit dependency graph.
3. Applying a label fires a GitHub workflow that loads a role-specific prompt (the agent acts as a hospital employee).

+2 more steps in the copyable prompt.

Claude · Coding · by Cockroach Labs (blog, 8 Oct 2026) · source

The founder’s playbook behind $100K MRR: one-shot a baseline, name the stack, use a quality reference per feature, self-score.

1. Find ideas in tools you use every day: what is missing in Codex, Cursor or Figma?
2. Use Opus 5.5 for the front end and Codex for the harness.
3. One-shot a baseline, then break the work into parts.

+5 more steps in the copyable prompt.

Claude, Codex · Coding · by Meng To (X post, 7 Oct 2026) · source

A Jev scan found 12,938 issues in 2 min for $0.89; an always-on Opus 5.5 loop opens and merges refactor PRs (50 merged).

1. Scan the whole codebase for code quality and security issues. The author used the Jev model on about 0.5M lines.
2. Feed the findings to Claude Code (Opus 5.5) running in a loop on a server so it is always on.
3. The loop opens refactor PRs, runs the gates, and merges once the gates pass.

Claude · Coding · by Pau Guirao (X post, 23 Sep 2026) · source

Max Woolf’s guarded loop: ask agents to make Rust (PyO3) code faster, forbid unsafe, benchmark each step.

1. Pick a target (e.g. reimplementing ML algorithms in Rust with PyO3 bindings).
2. Set guardrails: forbid unsafe code whenever possible; keep correctness tests.
3. Ask the agent repeatedly to make the code faster, benchmarking every iteration.

+1 more step in the copyable prompt.

Claude, Codex · Coding · by Max Woolf (blog, 22 Sep 2026) · source

Eleven free Claude skills: reverse-engineer an app, rebuild it, test for bugs, then fix user complaints.

1. Reverse-engineer the target app.
2. Rebuild it.
3. Test it for bugs.

+1 more step in the copyable prompt.

Claude · Coding · by Jakeschincariol (GitHub, 3 Oct 2026) · source

Deleting 168k lines of comments: same scores, ~22% fewer tokens on a small task, three runs per branch.

1. Make a copy of the codebase with every comment removed.
2. Ask the agent to build the same features on both versions, three times each.
3. Score with lint, type checks, existing tests and a hidden test; compare tokens and cost.

Claude · Coding · by openstation.blog (blog, 13 Oct 2026) · source

Extract the code as a data representation, operate on it, put it back as Rust; Fable orchestrates subagents, never writes code.

1. Ask the model to represent your code as graphs, ontologies, state machines, process charts, constraints or formulae.
2. Operate on that representation: simplify state machines, remove hidden communication channels.
3. Ask for the code back, in the new language.

+1 more step in the copyable prompt.

Claude · Coding · by Iurii Krasnoshchok (blog, 1 Sep 2026) · source

@_simonsmith’s Dot built a news app and a Spanish vocab app: Sites MCP server backend, plugin-with-extensions front end.

1. Ask the Dot to build the backend as an MCP server hosted on ChatGPT Sites.
2. Have it build the front end as a ChatGPT plugin with extensions.
3. Start with one app (e.g. a personalised news feed with thumbs up/down), then iterate on the rough edges.

Claude, Meta Muse, ChatGPT Dots · Coding · by Simon Smith (X post, 14 Oct 2026) · source

One dev found 69% of “done” claims false, another 35% of “tests pass” claims; both re-run checks before the agent may stop.

1. Measure first: scan your local transcripts for “done” / “tests pass” claims and check them.
2. Add a Stop hook (Claude Code, Codex CLI and others have one) that runs checks when the agent claims completion: fast checks always, the full suite only when the claim warrants it.
3. Watch for green-without-fix: skipped or deleted tests, weakened assertions.

+1 more step in the copyable prompt.

Claude, Codex, Cursor, Gemini CLI · Coding · by Raimondas Lencevicius (DEV post, 21 Sep 2026) · source

Checkly built ~600 black-box tests from production scenarios first; Claude Code wrote 13k lines of Go and servers went 20→5.

1. Build black-box tests from real production scenarios (Checkly had about 600).
2. Have Claude Code rewrite the service in the target language.
3. Run the same tests against the new service before switching traffic.

Claude · Coding · by Checkly (X post, 29 Sep 2026) · source

~3h of planning, then 207 Claude Code agents in 30 waves with gates, acceptance, fixes and a write-up; ~100 ran overnight.

1. Spend real time planning (the author spent ~3 hours).
2. Run agents in waves, with a gate and acceptance check between waves.
3. Add a fixes pass and a final write-up.

Claude · Coding · by Slobodan Stojanović (X post, 24 Sep 2026) · source

A husband built his wife’s meal-prep planner, 100 recipes and a synced shopping list with Claude Code; 850 on the waitlist.

1. Build the meal-prep planner, recipe library (100 recipes) and synced shopping list with Claude Code.
2. Open a waitlist before launch.

Claude · Coding · by Timothy 🟢 | Panic Drop (X post, 25 Sep 2026) · source

Each task declares allowed paths and a size budget; a pre-edit hook blocks out-of-scope writes and a parking lot keeps ideas.

1. Every task spec declares a scope block: allowed paths and a diff size budget.
2. A Claude Code PreToolUse hook blocks edits outside the allowed paths before they land.
3. A post-run check enforces the size budget inside the allowed directory.

+1 more step in the copyable prompt.

Claude · Coding · by yureki_lab (DEV post, 3 Oct 2026) · source

A ChiefOfStaff, per-project PMs and a CodeMaster that prompts claude -p / codex CLIs on a VM, looping PRs to green.

1. Talk only to a ChiefOfStaff agent, which works all the other bots.
2. Give each project a PM agent that understands it in depth.
3. PMs send requests to a “CodeMaster” that writes prompts for claude -p and codex CLI, and runs them only on a VM.

+1 more step in the copyable prompt.

Claude, Codex, Grok Bot · Coding · by Gabe Fletcher (X post, 9 Sep 2026) · source

Four-line instructions (persist first, then 200, no queue) got a minimal fix for Stripe acks before the payment row existed.

1. Open the handler and its test.
2. Give terse instructions, e.g. “persist first. then 200. do not add a queue. use the store we already have.”
3. Accept only the minimal fix and delete any unrequested design advice.

Claude · Coding · by Xypher (X post, 4 Sep 2026) · source

A kids’ book app: frontend on Lovable in ~2 weeks, backend almost entirely with Claude Code, so he owns the code afterwards.

1. Use Lovable to get v1 of the frontend on screen fast.
2. Build the backend with Claude Code.
3. Own and maintain the code yourself afterwards.

Claude · Coding · by Shirochenko Dmitriy (X post, 5 Oct 2026) · source

Same contract, isolated envs: 47 hidden tests, 4 contract mutations and a binary check. Opus killed 4/4 mutants at 100× the cost.

1. Pick a real mid-size slice of your project and write the contract.
2. Have each model build it in isolated environments (Claude Code and Codex).
3. Before looking at any build, write hidden tests from the contract alone (47 here).

+3 more steps in the copyable prompt.

Claude, Codex · Coding · by Damian Pala (X post, 10 Sep 2026) · source

Running Claude Code and Codex on a home Mac mini from his phone, he built video-editing software during a 45-minute workout.

1. Run Claude Code and Codex on a Mac mini at home.
2. Control them from your phone during the workout.
3. Fix bugs, then update your clip-analysis “brain” (here with Astra: slop, inconsistencies, pacing, attention score).

Claude, Codex · Coding · by darin stewart (X post, 10 Sep 2026) · source

Each Claude Code, Codex, Kiro or Gemini CLI session is a hero in its project’s room; click to see the console and answer prompts.

1. Run your agents through Herdr so the app can listen to their events (or use the read-only fallback).
2. Give each project a room and each harness its own hero.
3. Click a room to see the live console, answer a prompt or permission request, or stop the agent.

+1 more step in the copyable prompt.

Claude, Codex, Kiro, Gemini CLI · Coding · by /u/NachoV125 (Reddit, 13 Oct 2026) · source

A VS Code extension reads Claude Code’s session files and shows each subagent as a character in a call, with real commands and diffs.

1. Read the session files Claude Code already writes in ~/.claude/projects and follow the current session live.
2. Show each subagent joining when it gets a task and leaving when it reports back.
3. Show a shared “screen” with the agent’s real commands, output, diffs and files read.

+1 more step in the copyable prompt.

Claude · Coding · by /u/stickygoose (Reddit, 10 Oct 2026) · source

Route by task type and make each agent review the other

1. Install and sign in to both tools: The author's video covers install and sign-in (01:05–02:27).
2. Classify each task by type, first match wins: Review, locale text, audits, research, English prose, broken, mechanical edit, feature, script, data.
3. Map types to tool and model: Audits/research/content → Claude Code; bugs/features/scripts/data → Codex; lighter models for lighter jobs.

+4 more steps in the copyable prompt.

Claude, Codex, Cursor · Coding · by Mike Holp (blog, 11 Oct 2026) · source

Six weeks in: 128 PRs, 124 merged; planning a ticket takes about 12 minutes (self-reported).

1. Write tickets with an agent, after it audits the code: Problem statement, acceptance criteria, dependencies; it shows you every ticket before creating it.
2. Ask a read-only dispatcher what to work on next: It ranks tickets by how many others they unblock and lists your waiting PRs first; tiny shell allowlist, no subagents.
3. Create one worktree per ticket yourself: Branch and directory named after the ticket (worktrunk); .env copied in by a hook.

+5 more steps in the copyable prompt.

Claude, OpenCode · Coding · by rogs (blog, 30 Sep 2026) · source

Long jobs keep running on the PC after the laptop is closed; you verify and merge next morning (self-reported).

1. Run Docker inside WSL2 Ubuntu, with limits: Not Docker Desktop; every container gets memory and CPU limits; add a Windows-side keepalive.
2. Connect devices with Tailscale; browser tools via Cloudflare Tunnel + Access: No open router ports.
3. Run the Herdr server on the PC, client on the laptop: Each task gets its own pane, usually in its own git worktree; panes survive closing the lid.

+4 more steps in the copyable prompt.

Claude, Codex, Pi, OpenCode, Hermes Agent · Coding · by Nadim Tuhin (blog, 1 Sep 2026) · source