StepGleam logoStepGleam
Coding shelf

Coding guides.

Build, debug, and understand code faster.

13 guides
Coding clay illustration

Guides

Illustration for Make a coding agent write the failing tests first, then implementCoding
CodingIntermediate30 min

Make 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.

Illustration for Set up Claude Code hooks for formatting, tests and protected filesCoding
CodingIntermediate30 min

Set 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.

Illustration for Debug with an agent: reproduce, hypothesise, log, then fixCoding
CodingIntermediate30 min

Debug 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.

Illustration for Get a second-opinion review from a fresh session or another modelCoding
CodingIntermediate20 min

Get 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.

Illustration for Plan in Obsidian, build with Claude Code: the PRD-to-tasks loopCoding
CodingIntermediate45 min

Plan 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.

Illustration for Ship a feature with a coding agent: spec, tests first, then review the diffCoding
CodingIntermediate60 min

Ship 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.