keisei/KeiSeiKit-1.0
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
KeiSeiKit-1.0/_blocks/memory-protocol.md
denis 0b901cf2f9 feat: KeiSeiKit v0.1.0 — initial public release 
Generic Constructor-Pattern agent kit for Claude Code. Zero personal data,
fully English, MIT-licensed.

Contents:
- 34 reusable blocks (baseline, rules, stack/deploy/domain/api/scraper)
- 14 cross-project agent manifests (code/ml/infra/researcher/critic/...)
- 6 portable skills (/new-agent, /research, /test-gen, /debug-deep, /pr-review, /refactor)
- Rust assembler (single binary, ~500 KB)
- 3 hooks (auto-reassemble, pre-commit validate, no-hand-edit)
- install.sh (idempotent, cargo-builds on first run)
- MIT LICENSE

All 6 sanity greps pass: 0 Russian text, 0 specific project names,
0 incident numbers, 0 user paths, 0 hardcoded IPs, 0 API keys.

cargo check + assemble --validate: both pass on 14 manifests.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-20 23:58:34 +08:00

1,012 B
Raw Blame History

MEMORY PROTOCOL

At start:

  1. Read ~/.claude/memory/MEMORY.md (or your index file) → find relevant project file
  2. Read memory/{project}.md → constraints, stack, status, learnings
  3. If ML / research work: also check your wrong-paths.md notes (dead ends worth avoiding)

At end (if stage completed — feature/phase/milestone/audit/bug+fix/deploy/decision/blocker):

  1. Append to memory/{project}.md with format: 
    ### Feature Name (YYYY-MM-DD) [E-grade]
- Result: specific metrics (numbers, not "works well")
- Decision: what was done
- Benchmark: numbers vs baseline
- Learnings: what was learned
- Next: what's next
  2. If dead end / wrong path → append to your wrong-paths.md
  3. If architectural decision → project's DECISIONS.md
  4. Session chatlog (if significant): memory/chatlogs/{ml|projects}/YYYY-MM-DD-{topic}.md

Forbidden: transitioning without saving; writing "works" without metrics; leaving credentials only in conversation context.