Mike Wichers
2db7a35a66
- Clarified partial vs full completion in Sections 1, 2, 3, 4, 5, 6 - Section 7: Scoped Style Guidelines refresh UI/route (v2.4 pending) - Section 8 (new): Lore & Location RAG-Lite — tag beats with locations/items, build lore index in bible tracker, inject only relevant lore per chapter - Section 9 (new): Structured Story State / Thread Tracking — replace prev_sum blob with story_state.json (active threads, immediate handoff, resolved threads) - Summary updated with items 7, 8, 9 as pending v2.4/v2.5 tasks Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
15 lines
1.0 KiB
Markdown
15 lines
1.0 KiB
Markdown
# Claude Custom Instructions
|
|
|
|
## Project Context and Index
|
|
Before starting any coding task, you MUST always read the `ai_blueprint.md` file in the root directory. This file serves as the project index, architecture plan, and contains the actionable steps and versions designed by the Architect. Do not start modifying files until you have read and understood the context provided in `ai_blueprint.md`.
|
|
|
|
## Managing Documentation
|
|
Whenever you complete an implementation step outlined in `ai_blueprint.md` or make notable architectural changes, you MUST update the `README.md` and/or `ai_blueprint.md` to reflect those changes and bump version numbers if appropriate.
|
|
|
|
## Git Workflow
|
|
Every time you complete a task or make changes to files, you MUST automatically commit those changes to Git before waiting for the user's next prompt.
|
|
|
|
### Instructions:
|
|
1. Always run `git add .` to stage your changes.
|
|
2. Run `git commit -m "Auto-commit: [brief description of what was changed]"`
|
|
3. Do not ask for permission to commit, just perform the git commit automatically. |