rigc ingest, normalise, re-pivot or rename it, and extend it with an animation it does not have. Use when the input is an existing skeleton.json with its .atlas and page images rather than loose part PNGs. Not for Live2D file conversion or runtime tracking.\nlicense: MIT\ncompatibility: Requires Bun 1.2 or later and the npm package rig-c.Load this when what you were handed is already a skeleton: a skeleton.json\nwith its .atlas and page images, and a request to understand it, answer a\ncomplaint about it, re-express it, or extend it. Every rule below is owned by\nINGEST.md; this file says when to open it and what it will\nnot do for you.
\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.
validate reads a foreign file as it is, and\nbuild writes nothing on a red gate — AUTHORING §0.rigc ingest obeys the same rule from the other side —\nwhat it cannot read out of the skeleton is a named finding, never a guess —\nINGEST §2.0 and §2.rigc ingestrigc ingest hero.json --out specs/\nrigc build --rig specs/rig.json --motion specs/motion.json --images parts/ --out build/\nIt reads the skeleton — only the skeleton — and writes the rig spec and motion\nspec that rebuild it: byte for byte for a skeleton rigc emitted, and for an editor\nexport the weaker claim diff measures, with three kinds of benign difference left —\nINGEST §2.3. Two values it will not guess: the\nstage (a skeleton that declares none is carried as declaring none, and --stage\nadds a box to one — an editor export may be such a file, though every one in the\nexample corpus carries a box, and passing the flag at a file that declares a box is\nrefused rather than ignored) and each animation's duration (the largest key time,\nrecorded as a finding).\nRead findings.json: a BLOCK line means the rebuild will be missing something and\nthe command exits non-zero. Every code it can print — gutter, exit, meaning, what to\ndo — is the finding-code table in INGEST §2.0. Keep the note both specs carry.
rigc still cannot edit a skeleton: there is no command that opens one and\nchanges it, so every change is expressed in the specs — INGEST §0. diff's ratios\nsay how much of a reference's structure a candidate reproduces, so extending or\nrenaming a foreign skeleton lowers them by design, and neither validate nor diff\nhas a pass bar — INGEST §0 and §4.
⚠️ This section said \"there is no route from it to specs, so every change goes\nthrough transcription\" until 2026-09-17. That route exists now and it is the first\nthing to reach for; transcription by hand is what you fall back on for a construct\ningest reports as a blocker.
ingest and transcription (§2), what each validator\ncomplaint means on an export (§3), and the re-pivot, rename and extend\nrecipes (§4).Every 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.