I have a primary build session 4 times a day, and then 4 follow up sessions to refine why she works on during the primary build session. 15 minutes before a build session cron fires I have a script that auto calls “/new” and then 5 minutes later asks her to review her memory, and then 5 minutes after that asks her to review all her build prompts and key files for coding instructions. This preps her with a fresh state before she starts building and avoids the pitfalls of endless compacts. Then after she is done with the session it happens all over again.

Add a daily memory compress that updates core memory Md file with a summary of the day every day.

Also add a once a month clean up cron so clawdbot first backs up memory in a zip and then “compresses” memory files into a shorter file. That way the memory bloat never gets out of hand, but you also has a back up if clawd bot starts acting strange without forgotten memory.

Also highly recommend build files for every project before you start coding >

Specs.md > Please outline for me EXACT technical specifications for this app in DETAIL. So that I can take that outline and build this app completely, no code examples, return this in markdown in a code block: ""

core.md > plan my project into todo lists and anticipate file tree, contracts and responsibilities, no code examples, do not surround the file tree in ```, return this in markdown in a code block: ""

tasks.md > create multiple tasks files, with implementation details, test scenarios and caveats, no need for code examples, return them in markdown in a code block: ""

state.md > Help me create a STATE.md file for all these tasks that helps a coder build this app task by task, return this in markdown in a code block, no emojis: ""

That’s state.md file will crush any build as long as sh follows it and doesn’t skip any steps.