First, I’m more on the product side than the engineering side, and I’ve been building with AI for about more than a year now. In my last personnal project, my biggest concern was “instruction drift” : multiple agents creating contradictory config files until the repo became a mess. I’ve read quite a bit in this sub, tried many of the solutions in here, and from my work with agile product teams, so today I’d like to share my own experimentation. I put together a lightweight repo-level harness to keep instructions explicit and synced. I’ve open-sourced the blueprint here: https://github.com/GuiomeB/simple-ai-harness-blueprint What’s inside:
- a scalable Structure: Three tiers (S, M, L) so you don’t over-engineer from day one.
- explicit Configs: AGENTS.md (roles) and CLAUDE.md (project rules) to prevent agents from hallucinating their own standards.
- a
.agents/structure for keeping agent memory and precise context - skills: Ready-to-use Claude desktop skills.
- no paid product, no newsletter. I just wanted a clean starting point for my own projects and thought it might help others. Feel free to give feedback…
- does the “S, M, L” approach feel intuitive or still too much?
- anything here that would break your specific stack?
- what instruction patterns have worked better for you? submitted by /u/guib3r
Originally posted by u/guib3r on r/ClaudeCode
You must log in or # to comment.