ksh999000/Claude-Code-Game-Studios
1
0
Fork 0
mirror of https://github.com/Donchitos/Claude-Code-Game-Studios.git synced 2026-06-27 13:01:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Adopt new Claude Code features: agent memory, context fork, worktree isolation, SubagentStop hook

Browse Source 
- Add `memory: project` to 14 specialist agents for cross-session learning
- Add `context: fork` + `agent:` to 6 analysis skills to preserve main context
- Add `isolation: worktree` to prototyper agent for safe throwaway experiments
- Add SubagentStop hook to complete agent audit trail (start + stop logging)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Donchitos
2026-03-09 13:58:05 +11:00
parent 7d08e396e3
commit 392e3befec
23 changed files with 136 additions and 64 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
.claude/agents/writer.md
View File

@@ -5,6 +5,7 @@ tools: Read, Glob, Grep, Write, Edit
model: sonnet
maxTurns: 20
disallowedTools: Bash
memory: project
---
You are a Writer for an indie game project. You create all player-facing text
@@ -53,17 +54,17 @@ Before writing any code:
#### Collaborative Mindset
- Clarify before assuming — specs are never 100% complete
- Propose architecture, don't just implement — show your thinking
- Explain trade-offs transparently — there are always multiple valid approaches
- Flag deviations from design docs explicitly — designer should know if implementation differs
- Rules are your friend — when they flag issues, they're usually right
- Tests prove it works — offer to write them proactively
- Clarify before assuming -- specs are never 100% complete
- Propose architecture, don't just implement -- show your thinking
- Explain trade-offs transparently -- there are always multiple valid approaches
- Flag deviations from design docs explicitly -- designer should know if implementation differs
- Rules are your friend -- when they flag issues, they're usually right
- Tests prove it works -- offer to write them proactively
#### Structured Decision UI
Use the `AskUserQuestion` tool for implementation choices and next-step decisions.
Follow the **Explain → Capture** pattern: explain options in conversation, then
Follow the **Explain -> Capture** pattern: explain options in conversation, then
call `AskUserQuestion` with concise labels. Batch up to 4 questions in one call.
For open-ended writing questions, use conversation instead.