/glyph-warden
prompt.txt
01Create a self-contained browser game in a pixel-art fantasy setting where the player is a wizard who casts spells by drawing glyphs directly on the screen.
02
03The game must be designed around gesture-based spellcasting as its central mechanic. The player should draw shapes, runes, lines, loops, sigils, and other recognizable glyphs with touch or mouse input, and the game should interpret those gestures into magical actions in real time.
04
05Core design goals:
06- Make the game fun, tactile, and highly responsive
07- Make drawing glyphs feel satisfying
08- Reward mastery of more difficult glyphs without making simple glyphs useless
09- Keep the experience readable and engaging on a mobile screen
10- Support both portrait mobile play and desktop browser play
11
12Spell design:
13Create a small but expressive spell vocabulary with multiple complexity tiers.
14
15Simple glyphs:
16- easy to draw
17- easy to recognize
18- fast to cast
19- low mana cost
20- modest, narrow, or utility-focused effects
21
22Medium glyphs:
23- require more intention and shape accuracy
24- stronger or more flexible
25- moderate mana cost
26- useful in more demanding situations
27
28Complex glyphs:
29- harder to draw and recognize
30- slower or riskier to cast
31- high mana cost
32- dramatic, powerful, or multi-purpose effects
33
34The game should include several different categories of spells, such as:
35- direct attack
36- area damage
37- shielding or warding
38- movement or repositioning
39- repair or restoration
40- interaction with magical objects or environmental systems
41- puzzle or utility magic
42- resource conversion, harvesting, or transformation
43
44Each spell should have:
45- a distinct glyph shape
46- a distinct gameplay role
47- a clear cost and power profile
48- a strong audiovisual identity
49
50Gesture recognition:
51Implement robust gesture recognition suitable for finger input on touchscreens.
52The system should:
53- tolerate imperfect human drawing
54- avoid constant misclassification
55- keep different glyph families clearly separated
56- provide immediate feedback when a glyph is recognized
57- provide graceful feedback when input is invalid or ambiguous
58
59Visual style:
60- pixel-art presentation throughout
61- strong wizard-fantasy identity
62- original in-game art rendered directly in code or canvas
63- readable sprites, silhouettes, and effects on small screens
64- polished magical atmosphere with arcane symbols, spell trails, particles, glows, and fantasy environments
65
66Procedural VFX and SFX:
67All special effects and sound effects must be generated procedurally in code.
68Do not rely on external effect assets.
69Use code-driven techniques to create satisfying magic feedback, such as:
70- rune traces
71- pixel particles
72- sparks
73- shock rings
74- pulses
75- lightning arcs
76- embers
77- smoke puffs
78- magical flares
79- impact bursts
80- screen shake
81- synthesized magical tones, hits, hums, bursts, and charge sounds
82
83Game structure:
84Build a complete, playable game loop with goals, pressure, and progression.
85Possible elements include:
86- enemy encounters
87- magical hazards
88- objects to protect, repair, or activate
89- resource management
90- score chasing
91- escalating challenge
92- short wave-like encounters or room-based progression
93- unlockable or learnable spells
94- combo or mastery systems
95
96UI and UX:
97- include a clear title screen
98- include a start button
99- include pause and restart
100- include a clean HUD
101- keep the main screen uncluttered
102- place help or tutorial content in a help modal, codex, or overlay rather than scattering instructions everywhere
103- make the controls self-explanatory after brief onboarding
104
105Technical requirements:
106- deliver the complete game as a single self-contained HTML file
107- embed CSS and JavaScript in that file
108- require no external assets to run
109- avoid external libraries unless absolutely necessary
110- run locally in a browser
111- prioritize mobile touch input first
112- also support desktop mouse play
113- use canvas or similarly portable browser-native rendering
114
115Tone:
116The final game should feel magical, playful, skill-based, and polished.
117The joy of the experience should come from drawing glyphs, seeing them resolve into spells, and using them cleverly across varied situations.
118
119Deliverable:
120Produce the complete playable game, not a design document.
121Include all code needed to run it in one file.