Skip to content

docs: activation guidance, generated catalog, and roadmap#16

Merged
SchnappAPI merged 1 commit into
mainfrom
feat/orientation-and-catalog
May 30, 2026
Merged

docs: activation guidance, generated catalog, and roadmap#16
SchnappAPI merged 1 commit into
mainfrom
feat/orientation-and-catalog

Conversation

@SchnappAPI
Copy link
Copy Markdown
Owner

Closes the orientation/legibility gaps surfaced by the question "if I started a fresh session pointed at this repo, would it be clear what to do and what rules/hooks/skills are in place?"

The core finding: being pointed at the repo ≠ having the plugin installed. A bare repo session loads CLAUDE.md and .claude/settings.json, but the 134 skills / 39 agents / 59 commands / hooks are inert until the kit is installed as a plugin. Yet CLAUDE.md described the branch-workflow guards (no-commit-to-main, auto-PR, auto-merge) as if always active — a trust gap, since Claude might assume main is protected when it isn't.

Changes

Activation clarity (the trust-gap fix)

  • CLAUDE.md: new "Activation — installed vs. just open in the repo" section — components are inert until /plugin install; the repo-local git hooks need git config core.hooksPath .githooks.
  • Made the Branch workflow guards explicitly conditional ("When the kit is installed as a plugin…").

Legibility — generated catalog

  • docs/CATALOG.md: full inventory (134 skills · 39 agents · 59 commands · 7 hook events · 34 rule files) with one-line descriptions, generated by tests/gen-catalog.py.
  • tests/validate-catalog.sh (in run-all.sh + CI) fails if the catalog drifts; refresh with python3 tests/gen-catalog.py.

Standing intent

  • ROADMAP.md: north-star (current focus / recently done / reviewed-but-unchosen candidates / manual owner follow-ups), referenced from CLAUDE.md → Activation.

README: catalog pointer, the installed-vs-open caveat, and a "Developing this repo" setup note.

Verification

tests/run-all.sh green — all six validators pass, including the new catalog freshness check. CI (validate.yml) will run the same suite on this PR.

https://claude.ai/code/session_01U6H3oa4GEngboKuc8jvwC3


Generated by Claude Code

… and roadmap

A fresh session pointed at the repo loads CLAUDE.md but NOT the plugin
components — skills/agents/commands/hooks are inert unless the kit is installed.
CLAUDE.md previously described the branch-workflow guards as if always active,
which is misleading in a bare repo session. Close the orientation gaps:

- CLAUDE.md: new "Activation — installed vs. just open in the repo" section
  (components are inert until /plugin install; git hooks need
  `git config core.hooksPath .githooks`). Make the Branch-workflow guards
  explicitly conditional on the plugin being installed.
- docs/CATALOG.md: generated inventory of every skill/agent/command/hook/rule
  via tests/gen-catalog.py. tests/validate-catalog.sh (wired into run-all.sh +
  CI) fails if it drifts; refresh with `python3 tests/gen-catalog.py`.
- ROADMAP.md: standing north-star (current focus, recently done, candidates,
  manual follow-ups) so a fresh session has persistent direction, not just
  conventions. Referenced from CLAUDE.md → Activation.
- README: catalog pointer, the installed-vs-open caveat, and a "Developing this
  repo" setup note.

https://claude.ai/code/session_01U6H3oa4GEngboKuc8jvwC3
@SchnappAPI SchnappAPI merged commit aa43a94 into main May 30, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants