| These aren't that fun but sure. - https://gist.github.com/backnotprop/ca49f356bdd2ab7bb7a366ef... - https://gist.github.com/backnotprop/d9f1d9f9b4379d6551ba967c... - https://gist.github.com/backnotprop/e74b5b0f714e0429750ef6b0... - https://gist.github.com/backnotprop/91f1a08d9c27698310d63e06... - https://gist.github.com/backnotprop/7f7cb63aceb7560e51c02a9d... - https://gist.github.com/backnotprop/94080dde34bfca3dd9c48f14... - https://gist.github.com/backnotprop/ea3a5c3a31799236115abc76... Taken from 2 recent systems. 90% of my interaction is assurance, debugging, and then having claude operate within the meta context management framework. We work hard to set the path for actual coding - thus code output (even complex or highly integrated) usually ends up being fairly smooth+fast. When I "wake" CC up I usually use a prompt like this to preface any complex work: https://gist.github.com/backnotprop/d2e4547fc4546eea071b9b68... (the goal is to get all relevant context in-memory). For most planning I use Gemini. I copy either the entire codebase (if less than ~200k tokens) or select only that parts that matter for the task in large codebases. I built a tool to help me build these prompts, keep the codebase organized well in xml structure. https://github.com/backnotprop/prompt-tower |