Reusable Patterns & Decision Guide
This directory contains distilled, actionable game design and technical patterns for the Genies Unified Game Template. These patterns provide game-agnostic guidance derived from successful reference implementations (such as Sister Brawl).
Decision Guide: Which Pattern Do I Need?
When implementing mechanics, networking, or UI, consult the table below to find the correct pattern.
| When you are… | Use this Pattern | Why? |
|---|---|---|
| Teaching a new mechanic | Invisible Tutorial | Prevent modal walls; teach through gameplay context and safe environments. |
| Handling impacts, scoring, or damage | Hit Feedback & Juice | Make actions feel rewarding and punchy using hit-stop, shake, and audio. |
| Changing core game rules or architecture | Knowledge Base Drift | Ensure the Fun Stack and codebase remain synchronized using the Genius Sync Protocol. |
| Dealing damage, updating score, or resolving hazards | Server-Authoritative Hazards | Keep the server as the ultimate arbiter while allowing client-side prediction. |
Pattern Structure
Each pattern document follows a strict contract designed for AI agents and developers:
- Problem: The context and issue being solved.
- Pattern: The architectural or design solution.
- When to use: Specific scenarios triggering this pattern.
- Anti-patterns: Common mistakes or incorrect approaches.
- Acceptance checks: A strict checklist to verify correct implementation.
- Reference: Example references or context (e.g., Sister Brawl).
By adhering to these patterns, you guarantee consistency, maintainability, and high-quality gameplay across the Genius Engine ecosystem.