jolyonbrown Claude commited on
Commit
b7a7cb8
·
1 Parent(s): 677a86b

Enhance game generation prompt with professional polish requirements

Browse files

VISUAL POLISH ADDITIONS:
- Gradient backgrounds (no solid colors) via CSS or canvas
- Particle effects on player actions (jumps, attacks, pickups)
- Screen shake on impacts (camera offset for 200ms)
- Web Audio API beeps for all actions:
* Player actions: short high beep
* Pickups: ascending tone
* Damage: descending tone
* Victory: cheerful melody

GAME STATES REFINEMENT:
- Title screen: "Click to Start" prompt (clickable anywhere)
- Game over screen: Final score + "Play Again" button
- Brief instructions on title screen

These requirements ensure every generated game has:
- Professional juice and feel
- Immediate audio/visual feedback
- Polished presentation matching commercial indie games

Generated games will now be significantly more engaging and polished!

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

Files changed (1) hide show
  1. app.py +18 -12
app.py CHANGED
@@ -62,18 +62,24 @@ STRUCTURE & POLISH:
62
  - Wrap the entire HTML in a code block with ```html markers
63
 
64
  GAME STATES & FLOW:
65
- - Include a TITLE SCREEN with the game name and a "Start Game" button
66
- - Implement clear WIN and LOSE conditions with victory/defeat screens
67
- - Add a "Play Again" button on end screens that resets the game
68
- - Show score/progress tracking prominently during gameplay
69
- - Display clear instructions on the title screen or during first moments of play
70
-
71
- VISUAL DESIGN:
72
- - Use a cohesive color palette (3-5 colors that complement each other)
73
- - Apply consistent typography throughout (size, weight, spacing)
74
- - Add visual polish: smooth transitions, particle effects for key moments, UI animations
75
- - Ensure UI elements (buttons, score displays) have clear visual hierarchy
76
- - Make interactive elements visually distinct (hover states, button styling)
 
 
 
 
 
 
77
 
78
  GAMEPLAY:
79
  - Keep it simple but engaging (think: incremental clicker, puzzle, basic platformer, rhythm game)
 
62
  - Wrap the entire HTML in a code block with ```html markers
63
 
64
  GAME STATES & FLOW:
65
+ - TITLE SCREEN: Display game name with "Click to Start" prompt (clickable anywhere to begin)
66
+ - PLAYING STATE: Active gameplay with score tracking, visual feedback, and controls
67
+ - GAME OVER SCREEN: Show final score with "Play Again" button to restart
68
+ - Implement clear WIN and LOSE conditions with appropriate end screens
69
+ - Display brief instructions on title screen (controls, objective)
70
+
71
+ VISUAL POLISH (CRITICAL):
72
+ - BACKGROUNDS: Use gradient backgrounds (CSS linear-gradient or canvas gradients) - no solid colors
73
+ - PARTICLE EFFECTS: Spawn particles on player actions (jumps, attacks, pickups) using simple canvas circles/shapes
74
+ - SCREEN SHAKE: Implement camera shake on impacts/collisions (offset canvas draw by random pixels for 200ms)
75
+ - SOUND EFFECTS: Use Web Audio API to generate beeps/tones for actions:
76
+ * Player actions (jump, shoot) - short high beep
77
+ * Pickups/points - ascending tone
78
+ * Damage/loss - descending tone
79
+ * Victory - cheerful melody
80
+ - COLOR PALETTE: 3-5 complementary colors with good contrast
81
+ - TYPOGRAPHY: Consistent font sizes and weights throughout
82
+ - UI ANIMATIONS: Smooth transitions, button hover effects, score counter animations
83
 
84
  GAMEPLAY:
85
  - Keep it simple but engaging (think: incremental clicker, puzzle, basic platformer, rhythm game)