Lean and efficient with no boilerplate or explanation of concepts Claude already knows; every section adds domain-specific guidance and assumes competence.

Concrete, specific instruction-only guidance (e.g., 'define: startup, active window, recovery, cancellation rules, resource cost, contact shape ...') and enumerated test cases; absence of code is not penalized for actionable instruction skills.

Sections sequence a clear process (specify verbs -> authoritative outcomes -> tune -> test deterministically -> verify in play) with explicit 'Test' and 'Verify in play' checkpoints acting as validation steps.

Under 50 lines with no need for external bundle files (none exist); content is split into well-organized, clearly headed sections, satisfying the simple-skill top anchor.

Lists multiple concrete actions ('Design, implement, tune, or test') plus a detailed enumeration of combat elements (attack timing, guard/dodge windows, hit contact, posture, lock-on, weapons, boss phases).

Explicitly answers both 'what' (design/implement/tune/test readable tactical action combat for web games) and 'when' (an explicit 'Use for ...' trigger clause), satisfying the top anchor.

The 'Use for ...' clause covers natural terms a user would say (attack timing, guard and dodge windows, lock-on, boss phases, combat feedback, deterministic combat tests), matching the strong anchor.

The niche 'readable tactical action combat for web games' with its specific trigger terms is clearly distinct and unlikely to fire for unrelated skills.