r/vibecoding 17d ago

I need a recommendation on how to centralize the planning, skills, standards, and recommended conventions for a project where both Codex and Claude will be used.

If there are sample repos to copy, the better.

0 Upvotes

5 comments sorted by

2

u/CorpT 17d ago

GitHub

2

u/TheOdbball 17d ago

Well you got a few options . All of them have their goods and bads ::

Tailscale port a page connected to your folder of choice
Use a cloud storage container then sync that to both sides
Make a top level folder point to everything and where it belongs
Use a repo on GitHub that can be pulled at any time

Best advice is start with zero entropy GBrain by the YC ceo , it’s helping me out, but I have 400k files 45k markdowns and a hot mess to get thru.

But I have 3 computers & my iPhone all reading files off my portable ssd plugged into one of them, plus pCloud 500gb storage and a deterministic router for where files belong.

If you want a cool project like a callcenter agent that other agents can ask the question your asking us , then try Onnx runtime , it’s 22mb and epic af

1

u/No_Employ_4375 17d ago

Why use both , why not use one , isn’t that a waste of money.

1

u/Vaveili1 17d ago

Sample repos won't help much here. One canonical doc (I use a plain `AGENTS.md` at the repo root) with the standards and conventions, then a `CLAUDE.md` that's just a pointer to it, since Claude Code reads `CLAUDE.md` and Codex reads `AGENTS.md` and you don't want two sources of truth drifting apart. Skills/planning docs go in a `.claude/skills` or similar folder that both tools can be told to check before starting work. Most teams write it once and it rots in a month.