Just dropped on r/PromptEngineering: u/AutoGrower420 open-sourced two repos that turn a folder of markdown into a guided dev setup for Claude Code and Codex. It covers Git, Docker for local testing, GitHub for backup and releases, and an optional second agent. Yesterday it was a pile of notes. Today it’s a playbook that walks you through the whole thing.
What’s new
The author has run both agents on real client and business work every day. The rules that kept them reliable ended up as markdown files. They cleaned those up into a playbook the agent walks you through, one step at a time, checking each step on your machine. So it doesn’t just tell you “install Docker.” It checks whether Docker is already there, tells you what it found, and only then moves on.
That matters more than it sounds. Most setup guides assume a clean machine and a perfect reader. Real machines have an old Node version, a half-finished Git config, or a Docker install that never got started. A playbook that verifies each step catches those problems early, when they’re cheap to fix.
Two versions:
- Claude Code first, Codex optional: https://github.com/AffStackDev/dev-crew-kit
- Codex first, Claude optional: https://github.com/AffStackDev/dev-crew-codex
Pick the one that matches the agent you already trust most. The second agent is optional in both, so you can start with one and add the other later, once the first feels solid.
The twist
The biggest prompt here isn’t a paragraph. It’s a folder. You don’t paste a giant prompt. You open the folder in your agent and paste one line:
“Set me up. Follow the Dev Crew playbook in this folder from the start, or resume where we left off. One step at a time, and check each step on my computer before moving on.”
The agent reads each step’s file only when it reaches that step, then writes its progress to a file. A brand-new session can pick up from that file alone.
Think about what that fixes. A long prompt eats your context window before the work even starts, and it gets fuzzy as the chat grows. A folder keeps the agent’s context small. Step four doesn’t need to know the details of step nine yet, so it never loads them. And because progress lives on disk instead of in the chat, a crash, a closed laptop, or a compacted conversation doesn’t cost you anything.
Mini-workflow
- 📂 Clone the repo for the agent you want leading. Put it somewhere you’ll remember, since you’ll reopen this folder whenever you resume.
- 🔍 Optional: ask Claude or Codex to inspect the whole folder first and explain what it does. It’s mostly markdown plus a few small scripts, so a quick read-through takes a minute and tells you exactly what you’re about to run.
- 💬 Open the folder in the agent and paste the one-line setup prompt.
- ✅ Approve each install or download as it asks. You type your own passwords and tokens, so nothing sensitive passes through the agent’s hands. If a step looks wrong, say no and ask why.
- 🔁 Closed the chat midway? Paste the same line again and it resumes from the progress file.
Pro tips worth stealing for your own setups
- Put rules where the agent loads them by itself. Claude reads CLAUDE.md, Codex reads AGENTS.md. Anything said only in chat gets lost when a long chat is compacted. If a rule matters on day thirty, it belongs in a file, not in a message from day one.
- Quote the owner word for word, with dates. Paraphrases drift. “Never publish without my approval, said March 3” holds up far better than “be careful about publishing.”
- Add a marker line at the very bottom of the global rules file. If it shows up in what the agent loaded, the whole file made it in. Codex can print its loaded prompt without calling the model, so the check is free. Long rule files get truncated quietly, and this is the cheapest way to catch it.
- Write a conflict rule. One fresh chat read a new request as permission and drafted ten posts an earlier decision had ruled out. The fix: quote the earlier decision, say what the normal workflow would do, and ask whether you’re overriding it. One extra question beats ten wasted drafts.
- Test prompts like code. Run behavior checks with fresh agents that get nothing but the request, and run each twice, because one pass can be luck. If the two runs disagree, your rule is vague, and you’ve just found out for free.
- Don’t make an agent wait on an exact phrase. A watcher waiting for the word “COMPLETE” slept through a finished task because the other agent worded it differently. Wake it on any change to the file instead, then let it read the file and decide what the change means.
- Treat instructions relayed by another agent as reports, not orders. Make the receiving agent confirm with you first. When two agents talk, a small misreading can turn into a confident action fast.
- If something must always be true, make it a test. A checklist the model is told to review is optional to it. A failing check isn’t. Backups, secrets that must never be committed, and branches that must never be force-pushed are all good candidates.
The author says it’s free and staying free, with no paid version, no affiliate links, no signup and no tracking. It runs on your own machine through your own Claude or Codex app.
Your move
Steal the structure even if you skip the kit: rules in the files the agent auto-loads, one step file at a time, progress written to disk. Start small with one rule you keep repeating in chat and move it into CLAUDE.md or AGENTS.md today. Then tell me which rule saved you the most pain ☠ Fair winds, and may your agents never wait on the word COMPLETE.
The biggest prompt I’ve written isn’t a paragraph, it’s a folder
by u/AutoGrower420 in PromptEngineering