@getollie/cli 0.0.5 → 0.2.0

package/library/game_development-shooting/3d-shooting-game-threejs.json

@@ -1,68 +0,0 @@
-{
-  "index": 651,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Try to ensure that the generated code is executable for demonstration.\n\n======== ROLE ========\nYou are an experienced code expert. You are provided with a software development requirement description and asked 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. You will always generate complete, runnable project code, please ensure the project is fully executable\n2. Ensure all code files you output are complete, do not omit any code\n3. Carefully review and check all code before final output, evaluate 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 simulated data\n\n======== PROJECT REQUIREMENTS ========\nPlease create a 3D shooting game (using Three.js). The player pilots a spaceship in a space scene, using WASD to control movement and mouse to control shooting direction. Score points by destroying randomly generated asteroids, and lose shield value when hit by asteroids. Requirements: 1. Third-person camera following the player 2. Shield impact effects 3. Asteroid fragmentation effects 4. Dynamic lighting changes.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the 3D space environment fully implemented with Three.js?",
-      "description": "Check if the code correctly sets up a Three.js environment with proper scene initialization, WebGL renderer configuration, lighting, and a space-themed skybox or background. The environment should include stars or other space elements to create immersion. Score 0 if Three.js is not properly initialized, 5 if basic scene setup is present but lacks space elements, and 10 if the environment is complete with proper optimization techniques (such as frustum culling).",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the spaceship player control system effectively implemented?",
-      "description": "Evaluate if WASD keyboard controls for movement and mouse for direction/shooting are properly implemented with smooth motion physics. Check for inertia simulation, acceleration/deceleration effects, and collision boundaries. Score 0 if controls are missing, 5 if basic movement works but feels rigid or unnatural, and 10 if controls are responsive with proper physics implementation including velocity damping and rotation smoothing.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the third-person camera system properly implemented?",
-      "description": "Check if the third-person camera follows the player spaceship with appropriate smoothing and maintains proper framing. Verify camera collision avoidance, FOV settings, and whether it provides good visibility for gameplay. Score 0 if third-person camera is not implemented, 5 if basic following exists but has issues (jitter, poor positioning, clipping), and 10 if camera movement is smooth with proper lag, damping, and perspective adjustments.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are the asteroid generation and destruction mechanics fully functional?",
-      "description": "Review if asteroids are randomly generated with varying sizes, rotations, and velocities. Check for proper collision detection with projectiles, score incrementing, and asteroid fragmentation effects. Score 0 if asteroid system is missing, 5 if basic asteroids exist but lack variety or proper collision detection, and 10 if the system includes procedural asteroid generation with realistic physics and proper optimization for multiple objects.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as browser resizing, focus loss, excessive game objects, performance degradation on different devices, 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. Procedural asteroid generation with unique shapes 2. Particle-based weapon effects 3. Dynamic soundtrack that responds to gameplay intensity). 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 the space shooter (e.g., unnecessary UI elements) 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 mechanics/rendering/input handling), object-oriented structure, and event-driven architecture. 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 and scene management are not handled efficiently. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the visual design meet professional gaming standards?",
-      "description": "Evaluate whether the overall design follows modern game design principles: 1) Consistent art style with appropriate textures and models 2) Clear visual feedback for player actions and damage 3) Professional UI elements (score display, shield indicator, game over screen). Deduct 3 points for each inconsistent visual element, 5 points for poor texture quality or improper lighting, and 5 points for confusing or cluttered UI. 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 gaming standards: 1) Consistent frame rate above 30 FPS 2) Responsive controls with under 100ms input lag 3) Smooth transitions for shield impacts and asteroid destruction effects 4) Dynamic lighting changes that enhance gameplay without causing visual confusion. Deduct 5 points for frame drops during normal gameplay, 3 points for delayed visual feedback, and 5 points for effects that obscure important gameplay elements. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Shooting",
-  "difficulty": "medium"
-}

package/library/game_development-shooting/aerial-attack-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 140,
-  "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.\n\nPlease use HTML and JavaScript to implement an \"Aerial Attack\" game where players can attack in the air, striking airborne enemies or targets.\n\n**Task**: Design an aerial attack system where players can perform attacks in the air to strike airborne enemies or targets.\n\n**Hint**: You can set the range and effect of aerial attacks, and design levels that require aerial combat.\n\nPlease add some comments in your code so other developers can understand your implementation process.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core aerial attack game mechanics fully implemented?",
-      "description": "Check whether the code implements fundamental aerial game mechanics including player jumping/flying controls, gravity simulation, aerial attack triggering, collision detection for airborne targets, and hit registration. Score 0 if core aerial mechanics are absent, 5 points if basic aerial movement exists without proper attack mechanics, and 10 points if the implementation includes intuitive aerial controls with responsive attack systems.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the enemy/target systems properly designed for aerial combat?",
-      "description": "Evaluate whether the game includes airborne enemies or targets with varied movement patterns (stationary, patrolling, homing, etc.) and appropriate hit detection for aerial combat. Check if enemies have different behaviors, heights, and attack patterns requiring aerial strategy. Deduct 5 points if enemies are only ground-based, 3 points if aerial enemies exist but lack varied behavior. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the level design optimized for aerial gameplay?",
-      "description": "Assess whether the game environment encourages and necessitates aerial combat through platforms at different heights, vertical level progression, or obstacles that require aerial navigation. Check if the game provides opportunities and incentives for aerial attacks rather than just ground combat. Deduct 5 points if the game can be completed entirely on the ground, and 3 points if aerial sections feel disconnected from the core gameplay. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there a proper game progression and scoring system?",
-      "description": "Review whether the game includes meaningful progression through levels, difficulty scaling, score tracking for aerial combos/achievements, and performance metrics. Check if there are special rewards for aerial combat prowess or combo systems that encourage mastery of aerial mechanics. Deduct 5 points for lack of progression, 3 points if scoring doesn't specifically reward aerial play. 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 sequences, collision edge cases, physics anomalies, 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. Special aerial combo systems 2. Weather effects affecting aerial movement 3. Destructible environments from aerial attacks). 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 jump mechanics with overlapping purposes) 2. Function modules unrelated to aerial combat (e.g., an unnecessary inventory system) 3. Fancy effects that affect performance (e.g., excessive particle effects during standard attacks). 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/physics/input handling), code organization, reusability, and readability. Evaluate the quality of comments explaining the implementation process as requested. 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 comments are insufficient or unhelpful. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the game UI follows modern game design principles: 1) Clear visual distinction between player, enemies, and interactive elements 2) Proper HUD layout showing relevant information (health, score, etc.) 3) Visual feedback for aerial attacks and successful hits. Deduct 3 points for cluttered UI elements, 5 points for unclear visual hierarchies, and 5 points for insufficient feedback during gameplay actions. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the game animations and interactions conform to responsive gameplay standards: 1) Immediate response to player input (≤50ms) 2) Smooth transition animations for jumps/attacks 3) Clear visual effects for aerial attacks and hits. Deduct 5 points for input lag, 3 points for choppy animations during aerial movement, and 5 points for confusing or missing visual feedback during combat. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Shooting",
-  "difficulty": "easy"
-}

package/library/game_development-shooting/browser-first-person-shooter-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 759,
-  "question": "You are a coding expert. Please use your professional knowledge to generate accurate, professional responses. Make sure the code you provide is executable and displayable. Create a first-person shooter game that can be opened in a browser with a double-click.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the first-person perspective accurately implemented?",
-      "description": "Verify if the code correctly implements the first-person camera perspective with proper field of view (FOV between 75-90 degrees), mouse look controls, and head bobbing effects. Check if the camera is positioned at eye level and responds naturally to player movement. Score 0 if first-person view is not implemented, 5 if basic implementation exists but with perspective issues, and 10 if the perspective is fully immersive with proper raycasting for interaction.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the shooting mechanism well-implemented?",
-      "description": "Evaluate the shooting mechanism including gun models, recoil animation, bullet trajectory visualization, hit detection, and damage feedback. Check if there's proper weapon handling (reloading, weapon switching). Deduct 3 points if hitbox detection is imprecise, 4 points if there's no recoil or weapon feedback, and 5 points if bullet physics are unrealistic (instant hits instead of projectile physics when appropriate). The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the game environment properly constructed?",
-      "description": "Assess whether the 3D game environment includes collision detection, level design with appropriate cover and gameplay areas, and proper lighting effects. Check if the map has logical structure and performance optimization (LOD, occlusion culling). Deduct 5 points if collision is broken, 3 points if the environment lacks gameplay elements, and 3 points if rendering performance drops below 30 FPS on standard hardware. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the game playable with a simple double-click?",
-      "description": "Verify that the game can be launched by double-clicking an HTML file without requiring server setup, additional installations, or complex configurations. Check if all assets are properly bundled or loaded efficiently. Deduct 10 points if server setup is required, 5 points if there are missing assets or CORS issues, and 3 points if loading time exceeds 10 seconds on standard hardware. 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 browser compatibility issues, unexpected user inputs, resource loading failures, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle 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/lighting effects 2. Destructible environment elements 3. AI opponents with advanced behavior 4. Physics-based interaction). 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 control systems coexisting) 2. Function modules unrelated to an FPS game (e.g., unnecessary mini-games) 3. Fancy effects that affect performance (e.g., excessive particle systems or post-processing). 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), code organization, and asset management. 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 asset preloading or optimization. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the UI elements (HUD, menus, crosshair) follow modern game design principles: 1) Non-intrusive HUD elements that don't obstruct gameplay 2) Clear visual indicators for health, ammo, and objectives 3) Consistent visual language throughout all UI components. Deduct 3 points for cluttered UI elements, 5 points for poor readability during gameplay, and 5 points for inconsistent design language. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the game controls and feedback conform to FPS standards: 1) Input lag ≤ 50ms 2) Consistent frame rate above 30 FPS 3) Proper visual and audio feedback for all player actions. Deduct 5 points for noticeable input lag, 3 points for frame drops during action sequences, and 5 points for missing feedback on critical actions (shooting, taking damage, etc.). The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Shooting",
-  "difficulty": "hard"
-}

package/library/game_development-shooting/bubble-shooter-game-implementation.json

@@ -1,68 +0,0 @@
-{
-  "index": 534,
-  "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. Please implement a Bubble Shooter style game. The player controls a cannon at the bottom, adjusts the angle by moving the mouse, and clicks to shoot colored bubbles. Above is a matrix of colored bubbles arranged in hexagonal patterns. When a shot bubble connects with 3 or more bubbles of the same color, they are eliminated. Requirements: 1. Bubble physics and adhesion algorithm 2. Matrix structure detection 3. Trajectory prediction line 4. Chain elimination animation.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Bubble physics and adhesion algorithm implementation",
-      "description": "Evaluate whether the code accurately simulates bubble physics (movement, collision) and properly implements the adhesion algorithm that makes bubbles stick to the grid. Check if bubbles correctly snap to the hexagonal grid when they collide with other bubbles or the ceiling.0 points if bubble physics is missing, 5 points if basic movement is implemented but adhesion has issues, 10 points if physics behaves realistically and adhesion is pixel-perfect. Deduct 3 points if there are edge cases where bubbles behave erratically.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Hexagonal matrix structure and detection algorithm",
-      "description": "Review the implementation of the hexagonal grid structure and the algorithm for detecting connected bubbles. Check if the code efficiently identifies clusters of 3+ same-colored bubbles and properly manages the matrix state after eliminations.0 points if the hexagonal structure is not implemented, 5 points if basic structure exists but has detection flaws, 10 points if the hexagonal grid is perfectly implemented with efficient neighbor detection algorithms. Deduct 3 points if the algorithm fails in complex scenarios (e.g., bubbles becoming orphaned).",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Trajectory prediction line accuracy",
-      "description": "Assess the trajectory prediction line's accuracy in showing where bubbles will travel, including proper bounce physics off walls. The prediction should update in real-time as the player moves the mouse.0 points if trajectory prediction is missing, 5 points if basic straight-line prediction exists, 10 points if prediction handles bounces accurately. Deduct 3 points if the prediction doesn't match actual bubble movement or flickers during mouse movement.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Chain elimination animation quality",
-      "description": "Evaluate the visual feedback and animations when bubbles are eliminated. Check for smooth popping animations, proper scoring displays, and visual/audio feedback that enhances player satisfaction.0 points if no elimination animations exist, 5 points for basic disappearing effects, 10 points for professional animations with particle effects and sound synchronization. Deduct 3 points if animations cause performance issues or visual glitches.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Code robustness and error handling",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as rapid-fire clicks, extreme angles, browser resizing, etc.) and provide friendly error prompts or recovery mechanisms.Code with strong robustness should 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. Deduct 3 points for each uncaught exception that breaks gameplay.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Innovative features that enhance gameplay",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Power-ups/special bubbles 2. Difficulty progression 3. Score multipliers 4. Visual/audio feedback systems).Add 3 points for each practical innovative feature implemented (maximum 10 points). Features must be fully functional and meaningfully impact gameplay to receive points.",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Code optimization and performance",
-      "description": "Assess whether the game maintains stable 60 FPS performance even with many bubbles and animations. Check for optimization techniques like object pooling, efficient collision detection, and proper canvas rendering.Deduct 3 points for each performance issue (e.g., frame drops during animations, input lag, memory leaks). Deduct 5 points if the game becomes unplayable on standard hardware when the grid fills up. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Engineering quality and code organization",
-      "description": "Review modular design (separation of game logic/view/physics), use of appropriate design patterns, and code reusability. Check for proper encapsulation and minimal global state.Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if code duplication rate is too high (over 30%); deduct 5 points if there's no clear separation between game logic and rendering. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Visual design and user interface quality",
-      "description": "Evaluate whether the overall design follows game design principles: 1) Consistent bubble color scheme with clear differentiation 2) Proper UI layout with score/level information 3) Readable fonts and intuitive controls.Deduct 3 points for each unclear visual element, 5 points for poor color choices that make matching difficult, and 5 points for unintuitive UI that hinders gameplay. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Game feel and interaction responsiveness",
-      "description": "Judge whether the game controls feel satisfying and responsive: 1) Cannon rotation follows mouse smoothly 2) Shooting has immediate feedback 3) Bubble collisions feel impactful with appropriate sound/visual effects.Deduct 5 points for input lag exceeding 100ms, 3 points for jerky animations, and 5 points for unclear feedback when shooting or eliminating bubbles. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Shooting",
-  "difficulty": "hard"
-}

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

@@ -1,68 +0,0 @@
-{
-  "index": 1514,
-  "question": "You are a coding expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable for demonstration. Write code for a game similar to the NES/Famicom Contra game.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core game character movement and control system fully implemented?",
-      "description": "Review whether the code accurately implements the classic Contra character movement mechanics including running, jumping, crouching, and aiming in 8 directions. Score 0 if core movement is missing, 5 if basic movement is implemented but lacks fluidity, and 10 if the character control feels responsive with proper acceleration/deceleration and matches the original NES Contra feel.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the shooting and weapon system thoroughly developed?",
-      "description": "Check if the code implements the iconic Contra weapon system with different weapon types (regular gun, machine gun, spread gun, laser, flame thrower). Evaluate bullet physics, collision detection, and weapon switching mechanism. Deduct 5 points if fewer than 3 weapon types are implemented, and 3 points if weapon pickup mechanics are missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the enemy AI and spawn system properly implemented?",
-      "description": "Assess whether the code includes varied enemy types with distinct movement patterns and attack behaviors similar to the original Contra. Check if the enemy spawn system follows logical patterns based on level progression. Deduct 5 points if enemies have no AI variation, 3 points if spawn patterns are random rather than designed. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are the level design and stage progression mechanics implemented?",
-      "description": "Evaluate if the code includes at least 2 different stage types (side-scrolling and pseudo-3D perspective stages) with proper checkpoints, boss encounters, and scene transitions. Check for implementation of the iconic level features like destructible environments and vertical scrolling sections. Score 0 if only a single static level exists, 5 for basic scrolling levels, and 10 for complete level progression system.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as rapid input combinations, collision edge cases, game state persistence during browser refresh, 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. Modern visual effects while maintaining retro feel 2. Customizable character skins 3. Level editor functionality 4. Co-op multiplayer support). 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 coexisting) 2. Function modules unrelated to a Contra-style game (e.g., unnecessary RPG elements) 3. Fancy effects that affect performance (e.g., excessive particle effects causing framerate 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/view/input handlers/physics), sprite management efficiency, and performance optimization. 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 rendering optimization techniques are missing (e.g., sprite batching, object pooling). The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the visual design capture the authentic NES/Famicom Contra aesthetic?",
-      "description": "Evaluate whether the visual design faithfully reproduces the iconic Contra pixel art style: 1) Proper use of limited color palette (NES-like constraints) 2) Authentic sprite animations matching the original game's frame counts 3) Appropriate screen resolution and scaling (maintaining proper pixel ratio). Deduct 3 points for inconsistent art style, 5 points for modern visual effects that break the retro aesthetic, and 5 points for improper scaling causing visual artifacts. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the audio and game feel implementation authentic to the original?",
-      "description": "Judge whether the game successfully recreates the iconic Contra audio-visual experience: 1) Implementation of the classic sound effects and music 2) Screen shake and visual feedback on hits/explosions 3) Appropriate game difficulty curve and death mechanics. Deduct 5 points for missing sound effects, 3 points for inconsistent game feel compared to the original, and 5 points if the iconic Contra jingles and music themes are absent. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Shooting",
-  "difficulty": "hard"
-}

package/library/game_development-shooting/first-person-shooter-game-with-obstacles-and-enemies.json

@@ -1,68 +0,0 @@
-{
-  "index": 691,
-  "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. Implement a first-person shooter game where the player controls the view direction with the mouse and fires bullets by clicking. The scene will have both static and dynamic obstacles, with bullets able to penetrate some obstacles. Enemies will appear from random locations and approach the player. The player needs to destroy all enemies to advance to the next level.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the first-person view perspective and mouse control properly implemented?",
-      "description": "Check if the code accurately implements first-person camera mechanics with proper quaternion rotation for smooth view transitions. The mouse should control both horizontal (yaw) and vertical (pitch) camera rotations with configurable sensitivity. Verify that pitch constraints prevent camera flipping (typically -89° to 89° pitch limit). Give 5 points for basic mouse look implementation, 8 points if it includes smooth damping, and 10 points if it also handles edge cases like frame rate independence and has proper constraints.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the shooting mechanism fully functional?",
-      "description": "Evaluate the implementation of bullet firing, including raycasting for hit detection, bullet physics (if applicable), and visual feedback. Check for proper mouse click handling, cooldown/rate of fire implementation, and recoil effects. The shooting should include proper collision detection with different obstacle types. Award 4 points for basic shooting, 7 points if it includes appropriate sound effects and visual feedback, and 10 points if it also handles penetrable vs. non-penetrable obstacles correctly with appropriate physics.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are the obstacle types and bullet penetration mechanics well-implemented?",
-      "description": "Review how different obstacle types are defined and handled. The code should distinguish between penetrable and non-penetrable obstacles, with appropriate visual and physical properties for each. Check if bullet penetration mechanics include factors like material types, thickness, bullet velocity degradation, and potential trajectory changes. Award 10 points if all these aspects are properly implemented, 5 points if only basic penetration is handled, and 0 points if obstacles are not differentiated.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the enemy AI and spawning system properly designed?",
-      "description": "Assess the enemy spawning algorithm (should use proper randomization without unfair clustering), pathfinding implementation (A* or NavMesh), and approach behavior. Enemies should navigate around obstacles intelligently while approaching the player. Verify level progression logic after all enemies are destroyed. Award 3 points for basic spawning, 3 points for proper pathfinding, 2 points for enemy behavior variation, and 2 points for level progression implementation.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as rapid multiple inputs, edge collisions, performance spikes, etc.) and provide graceful 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 lighting effects for gunshots 2. Enemy damage visual feedback system 3. Environmental destruction mechanics 4. Player health regeneration system). Add 2.5 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 systems coexisting) 2. Function modules unrelated to FPS gameplay (e.g., unnecessary RPG elements) 3. Fancy effects that affect performance (e.g., excessive particle systems that cause frame 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/input/rendering layers), component organization, and code reusability. 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 proper optimization techniques (object pooling, LOD, etc.) are not implemented for performance-critical sections. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the HUD design follows modern FPS design principles: 1) Non-intrusive elements that don't obstruct gameplay visibility 2) Clear ammunition/health indicators positioned in screen corners 3) Subtle hit markers and damage indicators 4) Enemy highlighting that doesn't break immersion. Deduct 3 points for each obstructive UI element, 5 points for visual clutter during intense gameplay, and 5 points for missing critical information (ammo count, health). 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 FPS game standards: 1) Input response delay ≤ 50ms for shooting 2) Consistent frame rate above 30 FPS minimum 3) Appropriate weapon recoil and movement animations 4) Smooth enemy death animations without breaking gameplay flow. Deduct 5 points for input lag exceeding 100ms, 3 points for frame drops during normal gameplay, and 5 points for jarring transitions between animations. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Shooting",
-  "difficulty": "hard"
-}

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

@@ -1,68 +0,0 @@
-{
-  "index": 950,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code when possible. Create an HTML-based airplane battle game.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core game mechanics fully implemented?",
-      "description": "Evaluate whether the code implements the essential airplane battle game mechanics: player movement, enemy spawning, bullet firing, collision detection, and scoring system. Score 0 if the core interaction logic is missing, 5 if only basic movement and shooting are implemented, and 10 if all essential battle mechanics (including enemy AI patterns and power-ups) are fully included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the game loop and rendering system properly designed?",
-      "description": "Check whether the game implements a proper game loop using requestAnimationFrame or similar technique, with separate update and render cycles. Verify that sprite rendering is optimized (using canvas or efficient DOM manipulation). Deduct 5 points if the game has performance issues above 30 FPS, 3 points if animation is jerky, and 3 points if there's no frame rate management. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are the game controls responsive and intuitive?",
-      "description": "Assess whether the game provides responsive controls (keyboard/touch/mouse) with proper event handling and input buffering. Test if the player airplane responds within 50ms of input, and if there are alternative control schemes for different devices. Deduct 5 points if controls feel laggy, and 5 points if the game isn't playable across different input methods. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there a complete game progression system?",
-      "description": "Review whether the game includes a progression system with increasing difficulty levels, waves of enemies, boss battles, and game states (start screen, gameplay, game over, pause). Check for score persistence and level advancement logic. Deduct 5 points if difficulty never increases, 3 points if there's no pause functionality, and 5 points if game state transitions are abrupt or missing. 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 browser resizing, focus loss, unexpected user input, 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. Special weapons or power-ups 2. Dynamic weather effects 3. Procedurally generated enemy patterns 4. Interactive background elements). 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 the airplane battle game (e.g., an unnecessary settings menu with too many options) 3. Fancy effects that affect performance (e.g., excessive particle effects that cause 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 entity classes, rendering engine, input handling), code organization, and maintainability. Deduct 5 points if global state pollution is found or if proper object-oriented/functional 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 logic and presentation. 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 design principles: 1) Consistent visual style and theme 2) Clear visual hierarchy with important elements (player health, score) easily visible 3) Proper contrast between game elements and background 4) Readable text elements even during intense gameplay. Deduct 3 points for each cluttered UI element, 5 points for poor contrast making gameplay difficult, and 5 points for inconsistent visual style. 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 game feel principles: 1) Visual feedback for all player actions (shooting, taking damage, power-ups) 2) Enemy destruction animations and effects 3) Screen shake and other juice elements for impactful moments 4) Smooth transitions between game states. Deduct 5 points for each action without feedback, 3 points for jarring or missing transitions, and 5 points for confusing visual feedback during gameplay. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Shooting",
-  "difficulty": "medium"
-}

package/library/game_development-shooting/html-airplane-shooting-game-with-images.json

@@ -1,68 +0,0 @@
-{
-  "index": 1279,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure that the code you generate is executable for display. Create a computer airplane game shooting monsters code with images (in HTML format).",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core game mechanics of airplane shooting fully implemented?",
-      "description": "Review whether the code accurately implements player movement, shooting mechanics, enemy generation, and collision detection. Score 0 if the core gameplay is not implemented, 5 points if only basic movement and shooting exists, and 10 points if the game includes varying enemy types, different weapons, and proper game difficulty progression.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the game graphics and visual elements properly implemented?",
-      "description": "Check whether the game uses appropriate images for the player airplane, enemies, bullets, explosions, and background. Evaluate image quality, animation smoothness, and visual feedback. Deduct 3 points if images are missing or placeholder graphics are used, 3 points if animations are jerky, and 3 points if visual feedback for events (hits, explosions, power-ups) is inadequate. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the game loop and state management properly implemented?",
-      "description": "Evaluate if the code includes proper game loop implementation (requestAnimationFrame or similar), game states (start screen, playing, game over), score tracking, and level progression. Deduct 5 points if the game loop causes performance issues, 3 points if game states are incomplete, and 3 points if score/level management is missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the game have proper controls and user interaction?",
-      "description": "Check if the game implements responsive keyboard/mouse controls for the airplane, with proper event handling for multiple simultaneous inputs. Evaluate if touch controls are included for mobile devices. Deduct 5 points if controls are laggy or unresponsive, 3 points if only keyboard or only mouse control is implemented, and 5 points if mobile touch support is missing. 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 tab switching, input device disconnection, 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. Power-up systems with special weapons 2. Boss battles with unique mechanics 3. Dynamic difficulty adjustment 4. Particle effects for visual flair). 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 algorithms) 2. Function modules unrelated to the airplane game (e.g., unnecessary mini-games) 3. Fancy effects that affect performance (e.g., excessive particle systems that cause 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 logic/rendering/input handling), code organization, and maintainability. 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 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 design principles: 1) Harmonious color matching with appropriate contrast for game elements 2) Proper UI layout with clear visibility during gameplay 3) Professional text display (score, lives, level information) that doesn't interfere with gameplay. Deduct 3 points for each cluttered UI element, 5 points for poor visual hierarchy, and 5 points for text that is difficult to read during gameplay. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the game's performance and responsiveness meet standards: 1) Consistent frame rate above 30fps 2) Input response time ≤ 100ms 3) Smooth animations for game elements. Deduct 5 points for frame rate drops during normal gameplay, 3 points for delayed response to player input, and 5 points for jerky animations that affect gameplay. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Shooting",
-  "difficulty": "medium"
-}