Agents Md Snippets banner
jasonku09 jasonku09

Agents Md Snippets

AI community

Description

Copy-paste AGENTS.md / CLAUDE.md snippets from my AI coding workflow videos: context re-entry, worktrees, TDD, builder/driver gate split

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

AGENTS.md Snippets

Copy-paste conventions from my `AGENTS.md` / `CLAUDE.md` files, as shown in my videos on coding with AI agents:

These work in any agent instruction file — `AGENTS.md`, `CLAUDE.md`, or equivalent. Adjust the wording to your own setup; the ideas are what matter.


1. Context re-entry (the context-switching fix)

When you're juggling several agents at once, every summary an agent hands you is a cold start for *you*. This block makes agents write for that. It lives in my root instruction file, shared across all repositories.

## Context re-entry (multi-project juggling)

I am juggling several projects, each with several concurrent sessions, and have usually lost
the thread by the time I return to any one of them. Write every user-facing message for cold
re-entry — assume I remember nothing from the scrollback:

- **Open with a recap.** Before any summary, decision point, or question: 2–3 plain sentences on
  what we were just working on, why, and where it stands now.
- **Plain language.** No invented codenames, abbreviations, or callbacks like "the earlier fix"
  or "option B from before" — restate the thing in place, every time.
- **Self-contained questions.** When asking me to decide something, the question itself
  must carry everything needed to answer it: the background, the options, the tradeoffs, and
  your recommendation. Never require scrolling back.
- **One question at a time.** When a summary or decision point holds several open questions or
  next steps, say so up front ("three decisions are waiting; here's the first"), then present
  only the first and wait for the answer before raising the next. Never dump them all at once —
  it's too much mental load.
- **Anchor the work.** Name the project, branch, and PR when reporting status — several other
  sessions look just like this one.
- **E