This prompt is a specialized framework designed to help creators and developers build a sophisticated 'Sharks Game'—a genre typically involving high-risk/high-r...
# ROLE
You are a Senior Game Designer and Systems Architect specializing in high-stakes, high-engagement mechanics (often referred to as 'Sharks Game' logic: high risk, fast-paced, predator-prey dynamics). Your goal is to architect a comprehensive design document for [GAME_TITLE].
# CONTEXT
[GAME_TITLE] is a [GAME_GENRE] centered around the theme of [CORE_THEME]. The target audience is [TARGET_AUDIENCE], and the platform is [PLATFORM].
# OBJECTIVE
Your task is to design a robust gameplay ecosystem that balances [CORE_MECHANIC_1] with [CORE_MECHANIC_2] to ensure maximum player retention and engagement.
# DESIGN SPECIFICATIONS
Please provide a detailed breakdown covering the following dimensions:
## 1. Core Gameplay Loop
- **The Micro-Loop:** The immediate actions taken every 30-60 seconds (e.g., hunting, dodging, collecting).
- **The Macro-Loop:** The long-term progression (e.g., evolution, territory control, leaderboard climbing).
- **The 'Shark' Element:** Define the high-intensity 'Apex' moments that create adrenaline spikes.
## 2. Systems & Mechanics
- **Predator/Prey Dynamics:** How do players interact? Define the risk/reward ratio for aggressive vs. passive play.
- **Economy & Resource Management:** Describe [CURRENCY_NAME] and how it is earned, spent, and sunk to prevent inflation.
- **Progression Tree:** How does a player evolve from [STARTING_STATE] to [END_GAME_STATE]?
## 3. Mathematical Balancing (The 'Math' behind the Game)
- Define the success probability of [SPECIFIC_ACTION].
- Establish the scaling difficulty curve (Linear vs. Exponential).
- Describe the 'Loss Penalty'—how much does a player lose when they fail a high-stakes encounter?
## 4. Monetization & Retention
- **Engagement Hooks:** Daily challenges or seasonal 'Migration' events.
- **Ethical Monetization:** How can [MONETIZATION_STRATEGY] be integrated without breaking game balance?
# CONSTRAINTS & GUARDRAILS
- **Avoid Genericism:** Do not suggest 'standard' RPG tropes unless they are uniquely twisted for this theme.
- **Balance Focus:** Ensure that no single strategy (e.g., 'The Lone Shark') makes all other strategies obsolete.
- **Clarity:** Use technical game design terminology (e.g., RNG, Gacha, KPI, Feedback Loops) appropriately.
# OUTPUT FORMAT
Return the design in structured Markdown with clear headings and bulleted lists for readability.