Follow-up to my post a few weeks ago about splitting my system prompt into 27 files ( that thread ). People kept asking if they could use it, so I packaged the architecture into a starter kit. GitHub: https://github.com/ataglianetti/context-management-starter-kit It’s an Obsidian vault with Claude Code rules, commands, hooks, and a memory layer. The thing that actually matters: two markdown files that update at session close and load on start — so Claude knows what you were working on yesterday instead of starting from zero. Session state, decisions, project context. It carries over. Run /setup and it interviews you about your role, your projects, how you work — then generates the rules, memory, and context structure from your answers. Tip: use dictation so you can really give it context without it feeling like a form. Worth noting: this is a PKM system, not a coding tool. Knowledge work might not resonate with everyone here, but if you take notes and manage projects, it might be worth a look. Try it and tell me what breaks. submitted by /u/echowrecked
Originally posted by u/echowrecked on r/ClaudeCode