Background pages explaining the design decisions that shape this repo. Read these to understand why the schema and category structure look the way they do, before you start submitting your own files.

Pages in this section:

  • Scope rubric — when to use universal, team, or personal-share, with worked examples from the seed.

  • Mechanism and data — the requires-companion pattern, demonstrated by github-narrative-location + user-maintained-gems.

  • Instructions vs memory — the operational distinction between auto-loading instruction files and reference-only memory files.

  • Settings-fragments — how JSON snippets deep-merge into your ~/.claude/settings.json, preserving hand-curated entries.

  • Why hooks are deferred to v2 — the CVE history that motivates the staged rollout.

Table of contents