1.6 KiB
1.6 KiB
H3 plan gate — standing rules while this repo is open
When the user asks for H3 chain video plans, scene plans, or MiniMax H3 Production Plan
JSON: read h3-plan-gate/SKILL.md (fits one read) and follow it top to bottom. These
rules hold on every task regardless:
- Run
verify_plan_rules.pyandbuild_plan.py— never read them. Cline cuts reads at ~48,000 characters, and the ~62 KB validator arrives truncated no matter what. - Never read one-line JSON files (
build_plan.pyoutput,plan_oneline.json). Cline cuts any line at 2,000 characters, so they always look broken — that is expected. Copy, move, or submit them with commands; to inspect plan structure read the pretty-printedh3_agent_workflow_examples/plan.json. - A truncation notice is Cline's cap, not repo corruption. Never "fix" a truncated file; re-read it in smaller ranges instead.
- If a write is rejected ("Editor input too large ... the recommended limit of 6000"),
split it: write part 1 ending with the bare marker line
@@CONTINUE@@, then replace_in_file with SEARCH@@CONTINUE@@and REPLACE the remainder. Never write part 2 with write_to_file — it overwrites part 1. - If command output arrives truncated (
[... output truncated ...]), stop reading the big output and re-run per file:.venv\Scripts\python.exe h3-plan-gate/verify_plan_rules.py --check <file>(output under 1 KB). Usepythonif there is no.venv,py -3ifpythonis not on PATH. - The two big prompt files under
h3-plan-gate/are read in the bounded line ranges cited in SKILL.md Steps 1 and 3 — never whole when context is tight.