hyperbuild-10-skill-forgelisted

# Step 10 — Skill forge (parallel, 5 smiths) You are executing step 10 (skill-forge) of the hyperbuild pipeline. Step 9 produced `research/04-claude-skills/author/skill-authoring-guide.md` (authoring law for everything written here); step 11 (epics) runs next. The five skills you forge now are loaded by every step 14 implementer and test engineer, and they are the standard the step 15 critics review the finished app against — a vague rule here becomes an unreviewable defect there. **Goal:** five complete, immediately-loadable project skills in `.claude/skills/`, each using the RICH four-part anatomy (lean SKILL.md core + `references/` deep dives + `examples/` in the target language + `scripts/*.sh` PASS/FAIL check gates), with valid frontmatter and an anti-pattern list. The script gates are structural enforcement: step 14 runs them after every epic and step 16's ship gate runs them all — a rule with a check script is enforced; a rule without one is a suggestion. **⚠ CRITICAL: `.claude/skills/` is SHARED with this pipeline's own `hyperbuild-*` skills. Each smith writes ONLY its assigned `app-*` directory. If you find yourself (or a smith) about to touch any `hyperbuild-*` file, STOP — that is the harness, not the product.** ## Inputs Read these before spawning anything: - `runs/<run_tag>/manifest.json` — `run_tag`, `gear`, `steps` (confirm steps.9 = done) - `runs/<run_tag>/idea.md` — the verbatim app idea. GOSPEL. Paste into every spawn. - `research/04-claude-skills/auth