gameplay-system

Lumina — Gameplay System

Add proven, reusable gameplay systems instead of writing each one from scratch. You describe the intent (engine-agnostic); this skill maps it to the target engine. For Unity, see reference.md for ready-to-adapt C# patterns. For Unreal (v1), a parallel reference.unreal.md will hold the C++/Blueprint mapping.

Requested system: $ARGUMENTS

Available systems (intents)

Intent	What it provides
player-controller-3d	WASD/stick movement + jump on a CharacterController/Rigidbody capsule
player-controller-2d	Horizontal move + jump for a 2D Rigidbody
pickup	Trigger-based collectible that raises score and despawns + plays a sound
score-ui	Canvas HUD showing score / a target count, updated via events
enemy-patrol	Simple waypoint/seek AI that damages the player on contact
game-manager	Tracks win/lose state, spawn points, restart

How to apply

1. Resolve intent → engine. Read the project's recorded engine (Unity for MVP).
2. Reuse, then adapt. Pull the matching pattern from reference.md. Adjust names, speeds, layers, and references to fit the actual scene — do not paste blindly.
3. Write the script into Assets/Scripts/ via Write/Edit.
4. Wire it through the engine MCP: create/attach the component to the right GameObject, set serialized fields, connect references (e.g. the score UI text, the player transform).
5. Hand back to the loop. Building/verifying is the orchestrator's job (build-verify); after wiring, let it compile and playtest.

Design rules

• Keep systems small and event-driven (e.g. pickups raise a ScoreChanged event the UI listens to) so they compose without tight coupling.
• Prefer serialized fields over hardcoded values so non-coders can tweak in the Inspector.
• Every system you add should be reachable in the playtest (don't add dead code).