SQUEEK – MAJOR GAME UPDATE

OVERALL INSTRUCTION

Upgrade the existing Squeek game project. Do NOT rebuild the project from scratch.

Preserve all existing working features, player data, wallet connections, domain configuration, and project structure wherever possible.

The highest priority is integrating Supabase correctly and permanently storing player data.

Before making changes:

• Inspect the entire existing codebase.
• Identify the existing Supabase project and verify its connection.
• Review the current database schema, authentication, game state, scoring system, and leaderboard.
• Identify any existing localStorage or browser-only data that needs migration.
• Prepare an implementation plan and report any risks before modifying the project.

PHASE 1 – SUPABASE & PLAYER DATA (HIGHEST PRIORITY)

This is the most important requirement.

1. Supabase must become the permanent source of truth for player data and leaderboard records.
2. Save each player’s score permanently in Supabase.
3. Maintain a lifetime score for each player, following the existing scoring rules.
4. Implement a Top 100 leaderboard that retrieves and displays the highest-ranked players from Supabase.
5. Update leaderboard rankings whenever player scores change.
6. Persist player records across browser refreshes, device changes, and returning visits.
7. When a player connects MetaMask, associate their wallet address with their player profile and save it in Supabase.
8. Returning players connecting the same wallet must retrieve their existing profile, score, and progress instead of creating duplicate accounts.
9. Use wallet signature verification for authentication. Do not require users to send transactions just to connect their wallets.
10. Implement secure database permissions using Supabase RLS.
11. Never expose Supabase service-role keys or allow unverified clients to arbitrarily modify leaderboard scores.
12. Save important game progress and player records reliably, including after game sessions end.

Important:

• Design a reliable player identity system using wallet addresses.
• Handle duplicate wallets and concurrent score updates safely.
• If existing player data is stored locally, migrate it safely without overwriting higher verified scores.
• Do not reset or delete existing player records.
• Ensure leaderboard data comes from Supabase, not local browser storage.

PHASE 2 – MAPS, BOSSES & ENEMIES

Replace the repetitive map system with four distinct environments.

Map 1

• Duration: 60 seconds.
• Boss: Cockroach.
• Enemies should fly and move through the air.
• Do not use enemies that emerge from underground.

Map 2

• Duration: 90 seconds.
• Boss: Penguin.
• Enemies should attack by shooting ice projectiles.

Map 3

• Duration: 120 seconds.
• Boss: Dragon.
• Enemies should attack by shooting fire projectiles.

Map 4

• Duration: 150 seconds.
• Boss: Shark.
• Enemies should attack by shooting water projectiles.

Additional requirements:

• Each map must have its own visual identity and atmosphere.
• Enemies must have appearances that match their respective boss and environment.
• Bosses must have distinctive appearances and attack patterns.
• Each map should feel different in terms of gameplay, not just background colors.
• Preserve balanced difficulty progression.

Map progression:

• After defeating a boss, automatically transition to the next map.
• Remove the previous unnecessary metal-fragment interaction.
• Do not require players to interact with extra objects after defeating a boss.

PHASE 3 – COLLECTIBLES & CHARACTER PROGRESSION

1. Replace chestnut collectibles with different vegetables and fruits, such as carrots and other colorful produce.
2. Collectibles should be automatically picked up when the player comes close.
3. Weapon pickups must NOT be automatic.
4. On PC, players must press E to pick up a weapon.
5. On mobile, provide a clearly visible PICK UP button for weapons.
6. Every 20 points collected from vegetables and fruits, increase the mouse character’s size.
7. Character growth must be visually noticeable and progressive.
8. Ensure character growth does not break collision detection, movement, or gameplay balance.

PHASE 4 – UI & GAMEPLAY POLISH

1. Reduce the SQK coin visual size by 30% from its current size.
2. Keep the SQK letters horizontal, clear, and readable inside the coin.
3. Improve the mobile control interface:
   • Make buttons slightly larger.
   • Increase spacing between buttons.
   • Prevent accidental simultaneous presses.
   • Ensure controls remain comfortable across different mobile screen sizes.
4. Each weapon must have a distinct firing sound.
5. Match weapon sound effects to their firing characteristics.
6. Prevent audio overlap from becoming excessively loud.
7. Preserve existing game audio settings and mute controls.

PHASE 5 – TESTING & VERIFICATION

Before considering the update complete, verify:

Supabase

• Player records are saved successfully.
• Scores persist after refreshing the page.
• Wallet reconnection retrieves the correct existing player.
• No duplicate player profiles are created for the same wallet.
• Top 100 leaderboard displays correct rankings.
• Scores are not lost when a session ends.
• Database security rules prevent unauthorized score manipulation.

Gameplay

• All four maps have the correct durations.
• Each boss appears in the correct map.
• Enemies use the correct attack types.
• Boss defeat triggers automatic map progression.
• Fruit and vegetables are automatically collected.
• Weapons require manual pickup.
• Mouse growth occurs every 20 vegetable/fruit points.

UI

• SQK coin is 30% smaller.
• Mobile controls are larger and better spaced.
• Different weapons have different firing sounds.

DEVELOPMENT RULES

• Work on the existing project.
• Do not create a new project or replace the existing backend.
• Do not reset the Supabase database.
• Do not remove existing player data.
• Do not change unrelated features.
• Do not use mock data as a substitute for actual Supabase integration.
• Build and test after each implementation phase.
• Fix regressions before proceeding.
• Report modified files, database changes, completed requirements, and remaining issues.

EXECUTION ORDER

Implement in this order:

1. Inspect project and Supabase integration.
2. Implement and verify permanent player data storage.
3. Implement wallet-based player identity.
4. Implement the Top 100 leaderboard.
5. Implement the four maps, bosses, and enemies.
6. Implement collectibles and character progression.
7. Implement mobile UI and weapon audio.
8. Run a complete regression test.

Do not claim a feature is complete unless it has actually been implemented and tested.

If a requirement cannot be completed, explain the exact blocker rather than silently skipping it.