cc-agents-kit: Instructions file for Claude Code

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

What this repo is

A Claude Code plugin marketplace — not an application. Nothing here is imported or built; the artifacts are shell hooks plus the JSON manifests that make an installer find them. Every change is therefore judged on two things: does the manifest still resolve, and does the hook still hold its contract.

Commands

shellcheck plugins/*/hooks/*.sh
cd plugins/guard-hooks/hooks && for t in *.test.py; do python3 "$t" || exit 1; done
python3 plugins/guard-hooks/hooks/<name>.test.py     # a single suite
/bin/bash -n plugins/guard-hooks/hooks/<name>.sh     # macOS system bash 3.2, not your shell's bash

There is no build, no package manager, and no test framework. Suites are plain python3 scripts requiring bash and jq; shellcheck is optional (shellcheck-on-edit.test.py skips its findings checks and asserts the silent no-op instead). .github/workflows/ci.yml runs exactly the commands above plus manifest validation.

Layout contract

.claude-plugin/marketplace.json   # marketplace.json ONLY — no plugin.json here
plugins/<plugin>/
  .claude-plugin/plugin.json      # each plugin carries its own manifest
  hooks/hooks.json                # auto-discovered; commands reference ${CLAUDE_PLUGIN_ROOT}
  hooks/*.sh
  hooks/*.test.py                 # beside its hook, never in a tests/ directory
  hooks/_optout.py                # shared suite helper; leading _ keeps it out of the *.test.py glob

This mirrors Anthropic's own multi-plugin marketplace (claude-code-plugins), which is the layout to check against — not rn-agents-kit, whose single plugin uses "source": "./" and says nothing about nesting.

Two placements are load-bearing:

• A source in marketplace.json that names a missing directory breaks installation for every user of the marketplace. Add the entry and the directory in the same commit.
• Each suite resolves its hook with Path(__file__).resolve().with_name(...), and imports _optout as a plain sibling module. Moving either into its own directory silently breaks that, so they stay next to the scripts.