@getollie/cli 0.0.5 → 0.2.1

package/library/game_development-shooting/html-contra-style-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 434,
-  "question": "You are a coding expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the generated code is executable for demonstration. Develop an HTML format Contra-style game that can run directly in the browser.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core game mechanics completely implemented?",
-      "description": "Review whether the code accurately implements the Contra-style game mechanics including character movement (running, jumping, crouching), shooting mechanisms, and enemy AI behavior. Score 0 if the core mechanics are absent, 5 if only basic movement is implemented, and 10 if the implementation closely resembles the Contra gameplay experience with fluid controls and interactions.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the level design and environment interaction properly implemented?",
-      "description": "Evaluate whether the code includes proper level design with platforms, obstacles, terrain collisions, and scrolling backgrounds typical of Contra games. Check if the character can interact with the environment (climbing ladders, hiding behind cover). Deduct 5 points if collision detection is buggy, 3 points if scrolling mechanism is jerky, and 3 points if platform interactions are incomplete. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the weapon system and power-up mechanism fully functional?",
-      "description": "Check whether the game implements multiple weapon types (spread gun, laser, rapid fire, etc.) and power-up collection mechanics similar to the original Contra. Assess if weapon switching is implemented and if visual/audio feedback is provided when firing or collecting power-ups. Score 0 if weapons are not implemented, 5 if only basic shooting exists, and 10 if a complete Contra-like weapon system is available.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the enemy system and boss battles properly designed?",
-      "description": "Review if the code includes various enemy types with different attack patterns and behaviors (soldiers, turrets, flying enemies), and challenging boss encounters with health bars and phase-based mechanics. Deduct 3 points if enemy variety is limited, 5 points if boss battles are missing, and 3 points if enemy spawn logic is poorly implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as rapid input, window resizing, browser compatibility issues, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should implement browser detection, handle frame rate drops gracefully, and manage memory efficiently. Give 10 points for comprehensive error handling, 5 points for basic error handling, and 0 points if no exceptions are handled.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Modern visual effects while maintaining retro feel 2. Co-op gameplay via keyboard splitting 3. Custom level editor 4. Persistent high score system). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple collision detection systems) 2. Function modules unrelated to Contra-style gameplay (e.g., unnecessary social features) 3. Overly complex effects that affect performance (e.g., excessive particle systems). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating game engine/game logic/rendering layers), game loop implementation, asset loading optimization, and performance considerations. Deduct 5 points if global state pollution is found; deduct 3 points if the game loop implementation is inefficient; deduct 3 points if the code lacks comments or documentation. Check if the code follows game development best practices. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the visual design captures the essence of Contra while maintaining a clean UI: 1) Faithful pixel art style or appropriately modernized graphics 2) Clear HUD displaying lives, score and weapons 3) Proper contrast between characters, enemies and backgrounds. Deduct 3 points for cluttered UI elements, 5 points for visual elements that clash with the Contra aesthetic, and 5 points for poor readability of essential game information. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the game runs at consistent frame rates (ideally 60fps) and responsive controls: 1) Input responsiveness ≤ 50ms 2) Smooth animations for character movement and attacks 3) Proper collision feedback with visual/audio cues. Deduct 5 points for input lag, 3 points for animation stuttering, and 5 points for inconsistent collision detection. Check if the game maintains performance during intense action sequences with multiple enemies and projectiles. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Shooting",
-  "difficulty": "hard"
-}

package/library/game_development-shooting/html-cs-game-minecraft-style.json

@@ -1,68 +0,0 @@
-{
-  "index": 1745,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable for demonstration. Help me design a \"Counter-Strike\" game in HTML format, with health points, explosion effects after death, bullet trails, and character models that look like Steve from \"Minecraft\".",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core FPS gameplay mechanic implemented?",
-      "description": "Evaluate whether the code effectively implements essential first-person shooter mechanics including movement controls (WASD), targeting/aiming with mouse, shooting mechanics with cooldown, and hit detection. Score 0 if core gameplay is missing, 5 if basic movement and shooting exist but lack precision, and 10 if the implementation feels responsive with appropriate physics and hit registration.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the health point system properly implemented?",
-      "description": "Check if the health system includes visual indicators, damage calculation logic, and appropriate player feedback. The system should handle different damage types, show visual health status, and implement proper death conditions. Deduct 5 points if health regeneration or damage types are missing, 3 points if visual indicators aren't clear. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are the explosion effects after death convincing?",
-      "description": "Assess the quality of death animations and explosion effects. Effects should include particle systems, appropriate sound effects, and smooth transition to respawn state. Effects should be visually impressive without impacting performance. Score 10 for full physics-based particle systems with sound, 5 for basic animations, 0 if death effects are missing.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are bullet trails and shooting mechanics realistic?",
-      "description": "Evaluate if bullet trails use appropriate visual effects (line rendering, particle systems) with correct timing and opacity fade. Check if bullet physics include trajectory calculations, penetration logic, and hit markers. Deduct 3 points if trails don't match weapon types, 5 points if bullet physics are unrealistic. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as resource loading failures, memory management issues, input conflicts, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Dynamic lighting effects 2. Weather system affecting gameplay 3. Destructible environment components). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple shooting mechanisms coexisting) 2. Function modules unrelated to FPS gameplay (e.g., a built-in puzzle minigame) 3. Fancy effects that affect performance (e.g., excessive particle systems). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating game logic/view/input handling layers), asset loading optimization, and performance considerations. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if asset loading isn't optimized. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the Minecraft-style character design look authentic?",
-      "description": "Evaluate whether the Steve character models follow the authentic Minecraft aesthetic: 1) Proper blocky proportions with 2:1:2 body ratio 2) Pixelated textures without anti-aliasing 3) Appropriate animation that maintains the blocky feel. Deduct 3 points for incorrect proportions, 5 points for non-pixelated textures, and 5 points for animations that break the blocky aesthetic. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the game performance and responsiveness optimized?",
-      "description": "Judge whether the game maintains responsive performance: 1) Consistent 60 FPS during gameplay 2) Input latency under 50ms 3) Efficient resource management especially during effects. Deduct 5 points for frame drops below 30 FPS, 3 points for noticeable input lag, and 5 points for memory leaks or growing resource consumption. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Shooting",
-  "difficulty": "hard"
-}

package/library/game_development-shooting/html-space-shooter-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 1240,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Make sure the code you provide is executable when possible. Write an HTML code for a space shooter game.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core gameplay of the space shooter implemented?",
-      "description": "Review whether the code accurately implements the basic space shooter mechanics including player movement, enemy spawning, shooting mechanics, and collision detection. Score 0 if no core gameplay elements are implemented, 5 if only basic movement and shooting are present, and 10 if it includes enemy variety, player lives/health system, and proper game flow.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the canvas or game rendering system properly implemented?",
-      "description": "Check whether the game uses appropriate rendering techniques (Canvas API, WebGL, or DOM manipulation) with proper frame rate management. Verify that visual elements are drawn correctly with smooth animation (60fps target). Deduct 3 points if frame rate is inconsistent, 5 points if rendering has noticeable artifacts, and 5 points if no animation loop is implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are game controls responsive and appropriate?",
-      "description": "Evaluate whether the player controls (keyboard/mouse/touch) are implemented with proper event handling, including preventing default browser behaviors when needed. Controls should be responsive (≤50ms delay) and intuitive. Deduct 5 points if controls are laggy, 3 points if mobile support is missing when claimed, and 5 points if key events aren't properly managed. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the game state management and scoring system implemented?",
-      "description": "Check whether the code includes proper game state management (start screen, gameplay, game over) and scoring mechanics. The game should track player progress, display current score, and maintain high scores if applicable. Deduct 3 points for missing game states, 5 points for no scoring system, and 3 points for not persisting high scores if that feature is mentioned. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as window resizing, browser compatibility issues, rapid input changes, etc.) and provide friendly error handling. Code with strong robustness should gracefully handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Power-ups and special weapons 2. Dynamic difficulty adjustment 3. Particle effects for explosions 4. Boss battles). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple collision detection systems) 2. Function modules unrelated to a space shooter game (e.g., unnecessary UI elements) 3. Fancy effects that affect performance (e.g., excessive particle effects causing lag). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating game entities/rendering/input handling), code organization, and maintenance considerations. Deduct 5 points if global variables are excessively used or design patterns are not applied; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the code lacks comments or documentation. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern game UI principles: 1) Appropriate color scheme for space theme (dark background with contrasting elements) 2) Proper layout of game elements and HUD 3) Readable text and clear visual hierarchy. Deduct 3 points for cluttered game screens, 5 points for a color scheme that strains the eyes, and 5 points for poorly positioned UI elements that obstruct gameplay. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Input response delay ≤ 50ms 2) Smooth movement and transitions 3) Clear visual feedback for player actions and game events. Deduct 5 points for each interaction without feedback, 3 points for jerky or inconsistent animations, and 5 points for confusing visual feedback during gameplay. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Shooting",
-  "difficulty": "easy"
-}

package/library/game_development-shooting/html-tank-battle-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 1284,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the generated code is executable for demonstration. Please help me create a perfect Tank Battle game using HTML, carefully check and fix all bugs before generating the final code, with all code saved in a single HTML file.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the tank movement and control system fully implemented?",
-      "description": "Review whether the code accurately implements tank controls using keyboard input (WASD/arrow keys), with smooth movement and rotation that respects physics (acceleration/deceleration). Check for collision detection with game boundaries and obstacles. Score 0 if tank movement isn't implemented, 5 if basic movement exists but lacks physics, and 10 if movement is realistic with proper collision handling.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the combat system properly implemented with projectile mechanics?",
-      "description": "Evaluate if the shooting mechanism includes projectile trajectory calculations, cooldown timers, and hit detection. Check if bullets have proper visual feedback (animation, explosion effects) and whether the damage system is implemented. Score 0 if shooting isn't implemented, 5 if basic shooting exists but lacks collision detection, and 10 if projectiles have realistic physics with proper hit detection and feedback.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the game environment and obstacle system properly designed?",
-      "description": "Check if the game includes a well-designed map with strategic obstacles (walls, barriers, destructible objects). Review if obstacles affect gameplay meaningfully through collision detection and whether some obstacles can be destroyed. Deduct 5 points if obstacles are purely decorative with no collision, and 3 points if obstacle variety is too limited. Full score of 10 if environment is interactive and strategically designed.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the enemy AI system implemented with varying difficulty levels?",
-      "description": "Assess if the game includes AI-controlled enemy tanks with path-finding algorithms, target tracking, and difficulty progression. Check if enemies demonstrate strategic behaviors (flanking, retreating when damaged). Score 0 if no AI exists, 5 if enemies move randomly without targeting, and 10 if AI demonstrates varied tactics and adapts to player actions.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as unexpected user input, animation frame drops, resource loading failures) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Power-up system with special abilities 2. Dynamic weather effects that affect gameplay 3. Destructible environment with physics simulation). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple collision detection systems) 2. Function modules unrelated to tank battles (e.g., a built-in mini-game) 3. Fancy effects that affect performance (e.g., excessive particle systems). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating game logic/view/input handling), maintainability of code structure, and potential for expansion. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no clear separation between game components. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional game design standards?",
-      "description": "Evaluate whether the overall design follows modern game UI principles: 1) Clear, readable HUD showing health/ammo/score 2) Proper contrast between game elements and background 3) Intuitive visual feedback for hits/damage/game events. Deduct 3 points for cluttered UI elements, 5 points for poor readability during gameplay, and 5 points for inconsistent visual language. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the game performance optimized and responsive?",
-      "description": "Judge whether the game maintains stable performance: 1) Consistent framerate above 30fps 2) Efficient rendering techniques avoiding unnecessary redraws 3) Proper asset management to prevent memory leaks. Deduct 5 points for noticeable slowdowns during gameplay, 3 points for input lag above 100ms, and 5 points for increasing memory consumption over time. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Shooting",
-  "difficulty": "medium"
-}

package/library/game_development-shooting/mech-shooting-game-with-flight-mode-terrain.json

@@ -1,68 +0,0 @@
-{
-  "index": 610,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable for demonstration. Implement a shooting game where players control a mech that moves around the battlefield and shoots enemies. The mech can transform into flight mode, which increases movement speed but reduces attack power. The battlefield has varying terrain heights that affect player visibility and bullet trajectories.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the mech movement and transformation system fully implemented?",
-      "description": "Review whether the code accurately implements the mech's ground and flight movement mechanics. Check for: 1) smooth transition animations between modes, 2) appropriate speed differences between modes, 3) proper collision detection with terrain, and 4) responsive controls. Score 0 if basic movement is missing, 5 if only basic movement without transformation is implemented, and 10 if both modes with proper physics and transitions are fully included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the combat system with varying attack power implemented correctly?",
-      "description": "Evaluate the implementation of the shooting mechanics, including: 1) different attack power between ground/flight modes, 2) bullet physics and collision detection, 3) visual feedback for hits/misses, and 4) weapon cooldown systems. Deduct 3 points if attack power doesn't vary between modes, 5 points if bullet trajectories don't account for terrain, and 3 points if hit detection is inaccurate. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the terrain system with height variations properly implemented?",
-      "description": "Check whether the code implements terrain with varying heights that properly: 1) affects visibility through occlusion, 2) influences bullet trajectories (arc/gravity effects), 3) impacts player movement (climbing/descending slopes), and 4) provides tactical gameplay elements. Deduct 3 points for each missing feature. Score 0 if terrain is flat or non-functional. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the enemy AI and spawn system sufficiently challenging?",
-      "description": "Assess whether the enemy system includes: 1) varied enemy types with different behaviors, 2) appropriate difficulty scaling, 3) strategic positioning based on terrain, and 4) reasonable spawn patterns that create engaging gameplay. Deduct 3 points if enemies have no varied behaviors, 3 points if they don't interact with terrain, and 4 points if spawn patterns are random or overwhelming. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as rapid mode switching, boundary collisions, many simultaneous projectiles, rapid fire inputs, etc.) and provide friendly error handling or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Dynamic weather effects affecting gameplay, 2. Destructible environment elements, 3. Special weapons or abilities unlocked during gameplay, 4. Physics-based chain reactions from explosions). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple shooting mechanics that serve the same purpose) 2. Function modules unrelated to the game premise (e.g., unnecessary mini-games) 3. Fancy effects that affect performance (e.g., excessive particle systems that cause frame rate drops). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating game logic/rendering/input handling), component reusability, and performance optimization. Deduct 5 points if global state is overused or proper design patterns are missing; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if frame rate optimizations for bullet/enemy handling are absent. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional game design standards?",
-      "description": "Evaluate whether the visual design follows modern game UI principles: 1) Clear HUD elements (health, ammo, mode indicator) that don't obstruct gameplay, 2) Appropriate visual feedback for hits/damage/mode changes, 3) Consistent art style with clear distinction between terrain, player, and enemies. Deduct 3 points for cluttered UI elements, 5 points for inconsistent visual style, and 5 points for poor readability during intense gameplay. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the game interactions conform to player expectations: 1) Input response delay ≤ 50ms, 2) Consistent frame rate (minimum 30 FPS) even with many objects, 3) Clear visual cues for mode changes and terrain interaction. Deduct 5 points for input lag, 3 points for frame drops during transformation animations, and 5 points for unclear visual feedback when interacting with terrain. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Shooting",
-  "difficulty": "medium"
-}

package/library/game_development-shooting/mobile-shooting-game-source-code.json

@@ -1,68 +0,0 @@
-{
-  "index": 1731,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable when possible. Please create a mobile shooting game for me, with the source code.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core shooting mechanism fully implemented?",
-      "description": "Review whether the code accurately implements the shooting mechanics including weapon system, hit detection, damage calculation, and shooting effects. Score 0 if the core shooting logic is missing, 5 points if basic shooting is implemented without hit feedback, and 10 points if the full shooting system with proper collision detection, damage feedback and varying weapon types is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the mobile touchscreen control system properly designed?",
-      "description": "Evaluate whether the game uses appropriate mobile input methods such as virtual joysticks, touch gestures, gyroscope controls, etc. Check for touch event handling, multi-touch support, and responsive controls that adapt to different screen sizes. Deduct 5 points if the controls are not optimized for mobile (e.g., keyboard controls), and 3 points if touch areas are too small or overlapping. Score 10 points for intuitive mobile-first controls with alternative input methods.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the game loop and performance optimization implemented?",
-      "description": "Check whether the game implements a proper game loop with consistent frame rate handling, physics updates separate from rendering, and efficient resource management. Verify if the code includes mobile-specific optimizations like sprite batching, texture compression, and power management. Deduct 5 points if the game loop doesn't handle variable frame rates, and 5 points if there are no mobile optimization techniques. Give 10 points for a complete implementation with both features.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the game include a complete progression system?",
-      "description": "Assess whether the game includes level progression, scoring/reward systems, character/weapon upgrades, and appropriate difficulty scaling. Evaluate whether game state is properly saved between sessions using local storage or other persistence methods. Deduct 5 points if there's no progression system, and 3 points if progression exists but lacks save functionality. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as touch events outside game area, device rotation, background/foreground transitions, memory constraints, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Dynamic weather effects that affect gameplay 2. Destructible environments 3. AI opponents with adaptive difficulty). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple collision detection systems) 2. Function modules unrelated to a mobile shooting game (e.g., unnecessary mini-games) 3. Fancy effects that affect performance (e.g., excessive particle systems that cause frame drops on mobile). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating game logic/view/input handlers), asset management system, and build process for mobile deployment. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no consideration for mobile packaging and deployment. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional mobile game design standards?",
-      "description": "Evaluate whether the UI follows mobile game design principles: 1) Touch-friendly button sizes (minimum 44x44pt) 2) Clear visual hierarchy with proper contrast 3) Responsive layout that works on different screen sizes and orientations. Deduct 3 points for each element that's too small for touch input, 5 points for poor visibility under different lighting conditions, and 5 points for layouts that don't adapt to device orientation. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the mobile gaming experience optimized?",
-      "description": "Judge whether the game is truly optimized for mobile: 1) Short gameplay sessions suitable for on-the-go play 2) Battery consumption considerations 3) Offline play capability 4) Appropriate use of device vibration and audio for feedback. Deduct 5 points for each missing mobile-specific optimization, 3 points for excessive battery drain without optimization attempts, and 5 points for requiring constant network connection without offline mode. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Shooting",
-  "difficulty": "medium"
-}

package/library/game_development-shooting/multiplayer-online-shooting-game-frontend.json

@@ -1,68 +0,0 @@
-{
-  "index": 599,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure any code you generate is executable and functional.\n\n======== ROLE ========\nYou are an experienced code expert. I am providing you with a software development requirement description, and I need you to generate project code based on these requirements. Strictly follow the rules to help users generate complete project code with simple and easy-to-understand comments, without outputting anything else.\n\n======== OUTPUT RULES ========\n1. Always generate complete, runnable project code, ensuring the project is fully executable\n2. Ensure all code files you output are complete, don't omit any code\n3. Carefully review and check all code before the final output, evaluating its executability. If the code cannot be executed or contains errors, regenerate it\n4. If the requirements involve external API access or require user data (images, videos, audio, etc.), please provide mock data\n\n======== PROJECT REQUIREMENTS DESCRIPTION ========\nDevelop a multiplayer online shooting game frontend where players can battle on the same map. Need to implement real-time synchronization between players, chat functionality, scoreboard, and basic combat mechanisms.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the multiplayer shooting game core combat system fully implemented?",
-      "description": "Review whether the code accurately implements the game map and character positioning system through HTML/JavaScript/Canvas, and whether it includes collision detection for projectiles, hit registration, and damage calculation. Score 0 if the core combat logic is not implemented, 5 if only basic shooting mechanics exist, and 10 if the system includes advanced features like different weapon types, headshots, or damage falloff.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the real-time player synchronization function implemented?",
-      "description": "Check whether WebSocket/Socket.io implementation includes position synchronization, animation states, and player actions. Evaluate if the code handles network latency with techniques like client-side prediction, server reconciliation, and entity interpolation. Deduct 5 points if there's no lag compensation mechanism, and 3 points if the synchronization frequency is inadequate (<10 updates/second). The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the chat functionality properly implemented?",
-      "description": "Evaluate if the chat system supports both team and global messages, has proper UI integration that doesn't interfere with gameplay, and includes basic features like player identification and timestamps. Check if there's message sanitization to prevent XSS attacks. Deduct 5 points if chat messages aren't synchronized in real-time, and 3 points if there's no visual notification for new messages. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the scoreboard system complete and functional?",
-      "description": "Check if the scoreboard tracks and displays relevant statistics (kills, deaths, assists, score), updates in real-time, and has proper sorting functionality. Evaluate if it's accessible during gameplay without disrupting the experience and if it includes end-of-match summary features. Deduct 5 points if the scoreboard doesn't update in real-time, and 3 points if it lacks essential statistics. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as network interruption, player disconnection, browser compatibility issues, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Destructible environment elements 2. Special abilities or power-ups 3. Dynamic weather/lighting effects that impact gameplay). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple movement control systems coexisting) 2. Function modules unrelated to shooting gameplay (e.g., a built-in music playlist editor) 3. Fancy effects that affect performance (e.g., excessive particle systems when resources are already constrained). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating game logic/rendering/network layers), code organization, and performance optimization techniques. Deduct 5 points if global state is excessively used or design patterns are not applied appropriately; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no asset loading optimization or frame rate management. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface design meet professional gaming UI standards?",
-      "description": "Evaluate whether the UI follows game design principles: 1) Non-intrusive HUD elements that provide essential information without blocking gameplay 2) Clear visual feedback for hits, damage taken, and game events 3) Appropriate use of color coding for team identification and game state indicators. Deduct 3 points for cluttered UI elements, 5 points for poor readability during action sequences, and 5 points for inconsistent visual language. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the game performance and responsiveness optimized?",
-      "description": "Judge whether the game maintains smooth performance under various conditions: 1) Input response time ≤ 50ms for critical actions 2) Stable frame rate even with multiple players and effects on screen 3) Efficient resource management to prevent memory leaks. Deduct 5 points for noticeable input lag, 3 points for frame drops during intensive gameplay, and 5 points for progressive performance degradation during longer sessions. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Shooting",
-  "difficulty": "hard"
-}

package/library/game_development-shooting/multiplayer-online-shooting-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 524,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure the code you generate is functional and executable. Implement a multiplayer online shooting game where players connect via WebSocket and can see other players' positions and actions in real-time. Each player controls a character and can shoot bullets to attack other players. Players who are hit temporarily lose their ability to move. The first player to reach a specified number of kills wins the game.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the multiplayer shooting game core mechanics fully implemented?",
-      "description": "Review whether the code accurately implements player movement controls, shooting mechanics with bullet physics, collision detection between bullets and players, hit registration system, and kill/death tracking. Score 0 if core shooting interaction is not implemented, 5 if only basic movement and shooting exist without proper collision detection, and 10 if all shooting game mechanics including hit effects, temporary paralysis, and kill counting are fully functional.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is real-time multiplayer synchronization properly implemented?",
-      "description": "Check whether WebSocket implementation includes real-time position synchronization, action broadcasting, and state consistency across all clients. Evaluate if player movements, shooting actions, and game events are synchronized with minimal latency (<100ms). Deduct 5 points if interpolation/extrapolation for smooth movement is missing, and 3 points if bullet trajectories are not properly synchronized. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the server-side game state management and anti-cheat system designed?",
-      "description": "Evaluate whether server-side authoritative validation is implemented for player actions, hit detection, and game state updates. Check if the system prevents common cheats like speed hacking, teleportation, or invalid shots. Server must validate all client actions and reject invalid ones. Deduct 5 points if client-side validation is trusted without server verification, and 5 points if no rate limiting for actions exists. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is complete game session and lobby management constructed?",
-      "description": "Check whether the code includes game room creation/joining, player matchmaking, game start/end conditions, winner determination, and post-game statistics. Evaluate if disconnection handling allows players to rejoin ongoing games and if spectator mode is available. Deduct 5 points if game session persistence is not implemented, and 3 points if no reconnection mechanism exists. Give 10 points if fully implemented with proper lobby system.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as network interruption, invalid user input, WebSocket connection drops, concurrent player actions, etc.) and provide appropriate error handling or recovery mechanisms. Code with strong robustness should gracefully handle edge cases like simultaneous shots, player disconnections mid-game, and invalid movement commands, giving 10 points. If robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes engaging features that enhance gameplay experience (e.g., 1. Power-ups or special weapons 2. Mini-map showing player positions 3. Kill streak bonuses 4. Spectator mode with replay functionality 5. Real-time leaderboard). Add 3 points for each practical innovative feature implemented that adds genuine value to the gaming experience (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple collision detection systems) 2. Function modules unrelated to shooting gameplay (e.g., built-in chat system when not specified) 3. Excessive visual effects that impact performance (e.g., complex particle systems for every bullet). Deduct 3 points for each redundancy found, and directly deduct 10 points if core shooting mechanics are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (separating game logic/rendering/network layers), proper event handling architecture, and code organization. Deduct 5 points if global state pollution is found or no clear separation of concerns exists; deduct 5 points if code duplication rate is too high (over 30%); deduct 5 points if no proper error logging or debugging capabilities are implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional game design standards?",
-      "description": "Evaluate whether the game interface follows modern game UI principles: 1) Clear visual hierarchy with HUD elements (health, ammo, kills) 2) Intuitive control indicators and crosshair design 3) Consistent color scheme that doesn't interfere with gameplay visibility 4) Proper contrast for game elements against background. Deduct 3 points for each cluttered UI element, 5 points for poor color choices that affect gameplay, and 5 points for missing essential HUD components. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and responsive?",
-      "description": "Judge whether game interactions meet real-time gaming standards: 1) Input response delay ≤ 50ms for movement and shooting 2) Smooth character movement without stuttering 3) Clear visual feedback for hits, deaths, and game events 4) Consistent frame rate during intense gameplay. Deduct 5 points for each laggy interaction, 3 points for missing hit feedback effects, and 5 points for poor movement interpolation causing jerky motion. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Shooting",
-  "difficulty": "hard"
-}