rhiza-claude: Instructions file for Claude Code

CLAUDE.md

Guidance for Claude Code sessions in rhiza-claude — the Claude Code plugin marketplace providing the rhiza plugin.

Read this first: which side of the boundary you're on

This repo is the plugin. It is not a rhiza-managed repo — there is no .rhiza/ directory, no template.yml, no template.lock, and nothing here is synced from anywhere. That has two consequences worth internalising before you touch anything:

• /rhiza:quality runs here in its degraded mode. Its step-0 check looks for .rhiza/template.yml and .rhiza/template.lock; both are absent, so it skips every template-delivered gate, runs the targets this repo's own local.mk documents, and scores the design work. It used to refuse outright. Read any score it produces as what it says it is — a design-led assessment on this repo's own gates, not a Rhiza verdict, and not comparable to a managed repo's number.
• The "locally-owned vs Rhiza-owned" scoping rule doesn't apply. Every file here is locally owned. When you read that rule in plugin/prompts/scorecard.md, you're reading a rule this repo ships for other repos, not one that governs it — which is also why degraded mode inverts it: with no template, the Makefile, local.mk and workflows are this repo's own work and are squarely in scope.

Commands

The targets live in local.mk, not the Makefile. The Makefile is the shim shape rhiza's core bundle ships — front door, uv bootstrap, and a %: catch-all that delegates unknown targets to rhiza-task. Nothing here delegates: an explicit rule beats a pattern rule, so every target below is local.mk's. Add a target there, never to the Makefile.

make help           # list every target
make fmt            # all prek hooks over every file (delegated to rhiza-task)
make audit          # bandit over the scripts, zizmor over the workflows
make complexity     # radon CC/MI — the census this file quotes; reports, never fails
make test           # pytest over tests/, 100% coverage gate on scripts/
make e2e            # only the end-to-end tests, no coverage gate (template-drift's target)
make portable       # everything except e2e, no coverage gate (the cross-platform CI job's target)
make book           # build the docs site into _book/ (runs paper + test first)
make book-serve     # docs with live reload
make paper          # build the LaTeX paper (needs tectonic or pdflatex)
make paper-figures  # regenerate the paper's figures
make clean          # drop caches and build artifacts
make changelog      # regenerate CHANGELOG.md from conventional commits
make install        # install the plugin via the claude CLI