Load this when the request is a skeleton rather than a movement: loose part\nPNGs in, a bone hierarchy out. Every rule below is owned by\nRIGGING.md; this file says when to open it and what it\nwill not do for you.
\n\uD83D\uDCD6 A failure line ends with the command that prints its row of the guide —\n (see rigc guide <RULE>). Run that command first, before reading anything else:\nit prints that rule's row of the shipped guide and nothing else. rigc guide §<n>\n(and §<n>.<m>, §<n>.<m>.<k>) prints the section's heading, own prose and\nsubsection index from docs/AUTHORING.md; add --all to include subsection\nbodies. A leaf prints its full text either way. Sizes describe full ledger spans;\n--all with a rule name is refused, exit 2. A compile error points at its stable\nCE_ code row. rigc guide §5.1.<k> prints a numbered compile-error group of\nat most 30,000 UTF-8 bytes, and rigc guide §5.1 prints the introduction and\nindex within that same limit; only legacy uncoded library errors point at §5.1.
build writes nothing on a red gate, and there\nis no flag that changes that — AUTHORING §0.parent, a slot's bone, a\nconstraint's target resolve by name and a miss is refused by name; a missing\nnumber is a CompileError naming the field — AUTHORING §2 and §3.Nothing grades a hierarchy. A rig with its head off its torso passes the gate, the\npixels are nearly blind to structure, and the two instruments that see it at all\nare named in RIGGING §11 — neither as a pass bar.
\nEvery guide linked here is in the installed package at node_modules/rig-c/docs/,\nwhich is the copy that matches the rigc you run; the links go to the repository's\nmain. Inside the Claude Code plugin the same files are at ${CLAUDE_PLUGIN_ROOT}/docs/.
The install line and the build → validate → render → check loop are in the rigc\nskill.