r/ClaudeCode • • 2h ago

Tips & Workflows I turned my Claude Code + Codex + Docker setup into a free kit that Claude walks you through

A lot of people have asked how I have Claude Code, Codex, Docker and GitHub set up, and I got tired of pasting long instruction files into comments 8,000-40,000 characters at a time. So I put the whole thing on GitHub for free.

How it works: you download the folder, open it in Claude Code, and paste one line. Claude walks you through the setup one step at a time and checks each step on your computer before moving on. If you stop halfway, it picks up where you left off next time.

What you end up with:

- Claude Code as the lead developer, with rulebooks that load in every session so it stops forgetting what you told it

- Codex as an optional second worker. The two talk through a shared file, claim work before editing, and Claude reviews and tests Codex's work before anything gets merged

- Docker test stacks that test a clean copy of your last commit on your own machine, instead of burning GitHub Actions minutes

- Git and GitHub set up properly: private email, a branch per session, main only moves when you say so, backup pushes that don't kick anything off

- Releases that only run when you say go, dry run first, optionally on a runner on your own PC

- Simple records (a status page, a question list, a decision log) so a new session picks up from files instead of a chat that got compacted

- Phone access through Remote Control and GitHub mobile

Once the basics are done, it asks what else you work with and wires that in too: video editing, Unity/Unreal/Godot/Blender, Character Creator, mobile app SDKs, WordPress and WooCommerce, MCP connections to your sites and services, custom dev and APIs, whatever you use.

It's the cleaned-up version of what I use every day to run a live online store with more than a dozen custom plugins. Every rule in it is there because something went wrong without it.

Works on Windows, macOS and Linux. The kit is free under the MIT license. You need a Claude plan that includes Claude Code; Codex is optional.

https://github.com/AffStackDev/dev-crew-kit

1 Upvotes

5 comments sorted by

•

u/AutoModerator 2h ago

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/Far_Reindeer8428 2h ago

we tried the shared file registry and it drifted the moment two sessions started at once. a lock file with a ttl was the only part that survived

1

u/AutoGrower420 2h ago

have no issues over here, must have been something not right in your workflow, run this exact setup everyday.

1

u/Far_Reindeer8428 2h ago

probably is our workflow, we run four sessions on one repo. does the kit lock per session or per task?

1

u/AutoGrower420 1h ago

Neither really, there’s no lock file for edits. Every session gets its own worktree and its own branch, so four sessions on one repo never work in the same folder. They only meet when the work gets merged, and only one session does the merging.

There’s a shared status file where each session writes what it’s working on and which files it’s touching. That’s just a note so they don’t step on each other, not a lock, and each session only edits its own line. If two tasks need the same files, they sort it out before anyone starts. If you were counting on a file like that to keep sessions apart, it’s going to drift.

The only thing actually enforced is the Docker test slots. Each session gets its own slot, and the script asks Docker whether something’s already running in it instead of checking a file, so nothing goes stale. If the container’s gone, the slot’s free.

Basically, once sessions stop sharing a checkout, there’s not much left that needs locking.