Coding guides.
Build, debug, and understand code faster.
15 guides
Guides
CodingKeep a Claude Code session running on a remote box and steer it from your phone
Run Claude Code inside tmux on a server, use mosh for flaky links, connect Remote Control so you can steer and approve from your phone, and keep your SSH keys out of the agent's reach.
CodingShip AI-written code you can still explain: own the design, make the agent show its assumptions
Decide the abstractions yourself, pin them in a sketch or diagram, have the agent describe every change and flag what it assumed, then ask it to explain the diff before you commit.
CodingRun parallel Claude Code agents in git worktrees without merge hell
Give each agent its own worktree, scope tasks so their files do not overlap, merge one stream at a time, and rebase the rest on the new main.
CodingMake a coding agent write the failing tests first, then implement
Split the work into separate prompts: tests only, confirm they fail for the right reason, commit, then implement without touching the tests.
CodingSet up Claude Code hooks for formatting, tests and protected files
Add PostToolUse hooks that format and test after edits, a PreToolUse hook that blocks protected files, and a notification for long runs.
CodingTurn a checklist you keep forgetting into a Claude Code skill
When you catch yourself re-typing the same multi-step instructions, put them in .claude/skills/<name>/SKILL.md and run them with a slash command.
CodingHand a well-scoped issue to GitHub Copilot's cloud agent and review its PR
Write the issue like a ticket for a junior engineer, assign it to Copilot, steer it with @copilot comments on the PR, and review it like any other contribution.
CodingDebug with an agent: reproduce, hypothesise, log, then fix
Don't just ask the agent to fix it. Make it reproduce the bug, state a testable hypothesis, prove the root cause with logging or a failing test, and only then change code.
CodingLet the agent check its own UI with Playwright MCP
Stop pasting screenshots. Add the Playwright MCP server so the agent can open your dev server, read the page structure and compare it with what you asked for.
CodingGet a second-opinion review from a fresh session or another model
Review the agent's diff in a session that didn't write it, either a fresh Claude Code session or Codex on the PR, and act only on findings that affect correctness.
CodingWrite Cursor project rules that actually load when you need them
Put rules in .cursor/rules as .mdc files, set alwaysApply, globs and the description on purpose, and test that the agent picks each rule up.
CodingShip a feature with a coding agent: spec, tests first, then review the diff
The loop experienced developers describe on r/ExperiencedDevs: write the spec, plan the smallest steps, have tests written from the spec, implement, then review against the spec before anything merges.
CodingReview AI-written pull requests against an acceptance contract
A reviewer's method from r/ExperiencedDevs: a short scope contract at the top of the PR, the diff checked against it first, no extra behavior, plus Copilot code review as a first pass.
CodingKeep agent PRs small: one concern per branch
A developer's setup from r/ExperiencedDevs: the agent plans a feature into small chunks, writes the approved plan to the repo, and ships one stacked PR per concern.
CodingPlan in Obsidian, build with Claude Code: the PRD-to-tasks loop
How practitioners on r/hermesagent run projects: requirements and task lists in an Obsidian vault, small tasks handed to a coding agent, every diff reviewed by a human.
No guides match that yet.
Try a broader tool or level, or clear the filters and browse the whole library.
Clear filters