What problem does it solve? Implementing a gameplay mechanic in Unity involves many failure points: unconfirmed design intent, magic numbers scattered across prefabs, broken compilation discovered too late, and silent asset corruption. This Skill enforces a disciplined workflow that takes a mechanic from its design document to a verified, review-ready implementation. ## Core Features & Use Cases - Doc-driven implementation: Reads the mechanic's design document first, blocks work on unconfirmed (status: proposed) specs, and pulls tuning numbers from the doc instead of inventing them silently. - Code architecture conventions: Enforces single-responsibility components, ScriptableObject balance configs, Input System abstraction, object pooling, and correct Update/FixedUpdate separation. - Cheap verification loop: Validates compilation per-script before full builds, checks the console for errors, and confirms prefab field values and pool cleanup by reading actual state rather than trusting code. - Placeholder and handoff handling: Ships honest placeholder primitives with TODO markers and handoff files when art or audio assets are missing, so tasks can still close. - Use Case: You receive a design doc for a shooting mechanic. The Skill guides you to write the shooter component, wire it into prefabs via editor tooling, verify compilation and console cleanliness, then hand the user a concrete playtest script for acceptance. ## Quick Start Implement the shooting mechanic described in its design doc, following the gameplay-mechanic workflow, and report what to playtest.
