fix(skills): resolve cross-skill rule inconsistencies (1.24.1)

[shinpr]

Summary

Resolves a set of conflicting normative rules surfaced by a read-through of the skills, mirroring the kind of cleanup done upstream in the plugin repo. No rules were loosened; changes either resolve an internal contradiction or complete an incomplete rule. Patch version bumped to 1.24.1.

Changes

• documentation-criteria — the Creation Decision Matrix made ADR unconditionally required at 6+ files while the AI Automation Rules suggested ADR at 5+. Aligned both: ADR is conditional at 6+ ([ADR if conditions apply]), Design Doc + Work Plan are the required items, the automation rule now keys off 6+ and routes back to the ADR conditions, and the 3-5 row is Required (matching subagents-orchestration-guide and the controlled Mandatory / Not required / Conditionally mandatory vocabulary — Recommended was an orphan term).
• coding-standards — the comment policy said "describe what the code does," contradicting typescript-rules ("comment the why, not the what"). Reframed to code-first with a why/limitation/public-API test, in positive form (BP-001) and without the bullet-1/bullet-2 overlap (Principle 2).
• frontend-technical-spec — the class-component rule said "deprecated" with no exception, while frontend-typescript-rules allows class components solely for Error Boundaries. Added the Error Boundary exception so the two agree.

Applied across en/ja.

Validation

• check-skills-index: all 26 skills consistent across en/ja.
• Pre-commit hooks pass.

🤖 Generated with Claude Code