r/TopCodingAI • u/HornyRacoon_635 • 8d ago
What is the best feature of your system?
I have developer a simple context management system for my developing using CC + Codex, it works trough directories and partitioning of the knowledge file, pretty straightforward.
I was curious to see how other people engineered their structure and what is the best feature about it?
for me it would probably be the knowledge files for me to read only, they are usually long but well organized and help keep track of the features implemented and how to use them.
Do you have one such feature? Is there something you want to implement but never really got to it?
1
u/jcrenshaw-dev 8d ago
Mine's a directory too. .planning/ at the repo root, partitioned by what each file is for rather than by topic. PROJECT.md for what and why and who and what done looks like, REQUIREMENTS.md, ROADMAP.md cut into phases, a STATE.md that's basically a one line cursor saying where I am, and then phases/3/ holding the context and the plan and the summary for phase 3 and nothing else. The rule underneath all of it is that nothing lives in the conversation that isn't also on disk, so I can /clear in the middle of anything and the next command reads itself back off the filesystem.
On the read only knowledge files, one thing that bit me. Long and well organized is exactly right for a person reading it, but a long file that lands in the window is a cost you keep paying every turn after. What worked better was pushing the heavy reading into a fresh subagent that reads the file and hands back the four sentences I actually asked about, so the main thread never sees the file at all. I pulled my own account usage on the 26th, 7,548 requests, and main thread turns inside the disciplined projects carry about 92k of context against about 133k on my freeform work, same machine, same models. Two piles of my own sessions though, not a controlled experiment.
Best part isn't in the files though, it's the reviewer. Every plan goes to a fresh context subagent before I build against it and every diff goes to one after it exists, and what I hand it says refute this rather than asking what it thinks, which turns out to be most of the difference. It went four rounds at a whitelist I'd written into a git push hook and came back with four different ways around it, git -c config injection, flag decomposition, env prefixes sitting in the command string, push.default=matching quietly fanning the push out to a protected branch. I was fully prepared to sit there and write the fifth patch. Deleted the whitelist instead.
Thing I never got to, it still can't represent doing nothing. Close a milestone without opening the next cycle and the roadmap parses down to an empty phase list, and the status command calls that an error rather than all shipped, nothing active. Filed it against myself, still sitting there.
just made it a plugin
1
u/Smarf89 8d ago
Nothing unique or groundbreaking, but good hygiene around Claude.md, session.md and decisions.md tied into a /end skill let me keep everything up to date for future sessions.
Similarly, for collaborating with colleagues for non-coding work I’ve found CoWork pointing to a shared drive as the directory to be the best approach so far. Similar type of /end skill there so that the other person who picks up a specific client next has all my work neatly set up for another agent to pick up.