@getollie/cli 0.0.1

package/library/game_development-role-playing/text-based-character-homepage-attribute-panel-xiao-ke.json

@@ -0,0 +1,68 @@
+{
+  "index": 1269,
+  "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 display purposes. Create a text-based character homepage attribute panel for a character named Xiāo Kè.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the basic character attribute panel structure properly implemented?",
+      "description": "Check if the code implements the fundamental structure of a character attribute panel including name display (Xiāo Kè), basic attributes (e.g., strength, agility, intelligence), health/mana indicators, and level information. Score 0 if there is no clear panel structure, 5 if only basic name and limited attributes are shown, and 10 if a complete and well-organized attribute panel is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the text-based visualization properly executed?",
+      "description": "Evaluate whether the code effectively utilizes text characters (ASCII art, Unicode symbols, or other text elements) to create visual appeal without relying on images. Check for proper alignment, consistent spacing, and meaningful use of symbols to represent different attributes. Deduct 5 points if alignment is inconsistent, 3 points if spacing issues exist, and 5 points if the visualization is barely readable.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the character name 'Xiāo Kè' correctly displayed with proper formatting?",
+      "description": "Verify if the character name 'Xiāo Kè' is properly displayed with the correct diacritical marks and appropriate prominence in the panel. Check if the name is styled to stand out from other elements and whether proper character encoding is used for the special characters. Deduct 5 points if diacritical marks are missing or incorrect, 3 points if the name doesn't stand out visually.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the implementation include interactive elements for the attribute panel?",
+      "description": "Check if the code includes interactive features like hovering for additional information, expanding/collapsing attribute sections, ability to edit/update attributes, or keyboard navigation through the panel. Score 0 if no interaction is implemented, 5 if minimal interactions exist, and 10 if comprehensive interactive features are included.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as missing data, wrong input types, browser compatibility issues, 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. ASCII art animations 2. Dynamic attribute changes based on time/actions 3. Terminal-like effects or typewriter animations). 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 display functions 2. Feature modules unrelated to character attributes 3. Fancy effects that affect readability or performance. 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 data/view/controller layers), 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 naming conventions are inconsistent or unclear. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the text-based design follows clear visual principles: 1) Consistent character usage for borders and separators 2) Logical grouping of related attributes 3) Proper use of whitespace and alignment principles. Deduct 3 points for inconsistent character usage, 5 points for illogical attribute grouping, and 5 points for poor spacing that affects readability. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the dynamic effects (if any) conform to human perception characteristics: 1) Immediate feedback for user interactions 2) Appropriate animation timing for text effects (150-300ms) 3) Clear focus states and navigation cues. Deduct 5 points for each operation without feedback, 3 points for overly long animations that delay information display, and 5 points for confusing navigation. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Role-Playing",
+  "difficulty": "easy"
+}

package/library/game_development-role-playing/text-based-immortality-pill-game.json

@@ -0,0 +1,68 @@
+{
+  "index": 748,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable when presented. Help me write a text-based game about cultivating immortality and pill refining that can be used directly in WeChat Developer Tools without any errors.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core cultivation system properly implemented?",
+      "description": "Review whether the code accurately implements the cultivation levels, skill progression, and attribute system. Check if there are clear advancement mechanisms with distinct stages (e.g., Qi Condensation, Foundation Establishment, Core Formation). Score 0 if cultivation mechanics are absent, 5 if basic levels exist but lack depth, and 10 if there's a comprehensive system with meaningful progression choices.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the pill refining gameplay loop complete?",
+      "description": "Evaluate the implementation of the pill refining system, including ingredient collection, recipe discovery, refining process, and success/failure mechanics. Check for variables that affect outcomes (ingredient quality, player skill, equipment). Deduct 5 points if the refining process is overly simplistic, 3 points if ingredient variety is limited. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the game state management properly implemented?",
+      "description": "Check whether the code includes proper game state persistence using WeChat storage APIs (wx.setStorage/wx.getStorage). Verify save/load functionality works correctly and handles different game states appropriately. Deduct 5 points if state is lost between sessions, 3 points if critical game elements aren't preserved. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the WeChat Mini Program integration complete?",
+      "description": "Assess whether the code properly integrates with the WeChat Developer Tools environment, using appropriate WeChat APIs and following Mini Program best practices. Check for proper page structure, lifecycle hooks implementation, and adherence to WeChat's restrictions. Deduct 5 points for improper API usage, 5 points for incompatible code patterns. 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 invalid inputs, unexpected user actions, 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 events based on real-world time 2. Random encounters with other cultivators 3. Special secret techniques discovery 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 inventory systems coexisting) 2. Function modules unrelated to cultivation/refining (e.g., a built-in calculator) 3. Features that affect performance unnecessarily (e.g., excessive animations in a text-based game). 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/data layers), 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 there's no clear structure for game components. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface text meet professional design standards?",
+      "description": "Evaluate whether the text presentation follows good design principles: 1) Consistent terminology for cultivation terms 2) Proper text spacing and formatting 3) Clear distinction between different information types (status, actions, narrative). Deduct 3 points for inconsistent terminology, 5 points for cluttered text presentation, and 5 points for confusing navigation instructions. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the game interaction intuitive and responsive?",
+      "description": "Judge whether the game controls and feedback conform to user expectations: 1) Clear command options 2) Immediate feedback after actions 3) Intuitive navigation between game sections. Deduct 5 points for confusing controls, 3 points for delayed feedback, and 5 points for hidden or difficult-to-access core functions. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Strategy",
+  "difficulty": "easy"
+}

package/library/game_development-role-playing/web-rpg-post-apocalyptic-combat-game.json

@@ -0,0 +1,68 @@
+{
+  "index": 1079,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable when possible. Create a web-based RPG game featuring a lone warrior wandering through a post-apocalyptic world. The game mechanics should include real-time combat from a top-down perspective, with the character gaining experience and leveling up after defeating enemies. During their journey, the player will acquire numerous treasures. The art style should be realistic.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core RPG character system fully implemented?",
+      "description": "Review whether the code accurately implements the character attributes (health, experience, level, attack/defense stats), progression system, and realistic character rendering. Check if the level-up mechanics include stat improvements and provide visual feedback. Score 0 if the core character system is missing, 5 if only basic attributes are implemented, and 10 if the complete progression system with balanced difficulty curves is present.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the top-down real-time combat system properly implemented?",
+      "description": "Evaluate the combat system implementation including hitbox detection, damage calculation based on character stats, combat animations, and player control responsiveness. Check if the system includes attack cooldowns, dodge/block mechanics, and combat feedback effects. Deduct 5 points if hit detection is inaccurate, and 3 points if combat animations don't match actions. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the post-apocalyptic world environment well-designed?",
+      "description": "Assess whether the game includes a properly rendered post-apocalyptic environment with appropriate visual elements (ruins, wasteland, etc.), obstacle collision detection, and interactive objects. Check if the world has distinct areas/zones with varying challenges. Deduct 5 points if the environment lacks thematic consistency, and 3 points if collision detection is buggy. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the treasure and inventory system complete?",
+      "description": "Examine whether the code implements a functional inventory system with diverse treasures/items that have different effects, proper item categorization, and item usage mechanics. Check if treasures appear at appropriate intervals and if there's a balanced reward system. Deduct 5 points if the inventory UI is dysfunctional, and 3 points if item effects aren't 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 invalid player inputs, asset loading failures, 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. Dynamic weather system affecting gameplay 2. Moral choice system affecting story outcomes 3. Procedurally generated environments for replayability). 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 inventory systems coexisting) 2. Function modules unrelated to a post-apocalyptic RPG (e.g., a built-in social media feed) 3. Graphics effects that severely impact 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 for web environments. 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 optimization for mobile/desktop differences. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the realistic art style meet professional standards?",
+      "description": "Evaluate whether the visuals achieve the required realistic style: 1) Consistent lighting and shadow effects 2) Appropriate texture resolution and detail 3) Cohesive post-apocalyptic aesthetic across all elements. Deduct 3 points for inconsistent art styles between characters and environment, 5 points for low-quality textures in prominent areas, and 5 points for animations that break immersion. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the game performance and responsiveness optimized?",
+      "description": "Judge whether the game runs smoothly in a browser environment: 1) Maintains consistent 30+ FPS during combat 2) Input response time under 100ms 3) Efficient asset loading with appropriate preloading strategy. Deduct 5 points for each noticeable frame rate drop during standard gameplay, 3 points for input lag over 200ms, and 5 points if the game causes browser crashes when testing on mid-range devices. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Role-Playing",
+  "difficulty": "hard"
+}

package/library/game_development-role-playing/ywt-adventure-pokemon-style-game.json

@@ -0,0 +1,68 @@
+{
+  "index": 1662,
+  "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. Create an HTML game with the theme of \"YWT Adventure,\" using a style similar to Pokemon. Ideally the game interface should be 3D, with characters having health bars and being controllable.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the 3D game world and rendering system fully implemented?",
+      "description": "Review whether the code accurately implements 3D rendering using WebGL/Three.js or similar technologies, including proper 3D scene setup, camera controls, lighting systems, and terrain/environment models. Check if the 3D world has depth, proper perspective projection, and realistic spatial positioning. Score 0 if only 2D sprites are used, 5 if basic 3D elements exist but lack proper lighting/shadows, and 10 if a complete 3D environment with professional rendering quality is achieved.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the character system with health management properly designed?",
+      "description": "Evaluate whether characters have fully functional health bar systems, including real-time HP display, damage calculation, healing mechanisms, and visual feedback for health changes. Check if health bars are properly positioned above characters, have smooth animations for health changes, and include status effects visualization. Deduct 5 points if health bars are static or poorly positioned, 3 points if damage calculations are incorrect or missing. Full score requires Pokemon-style health management with smooth transitions and visual polish.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are the character controls responsive and adventure mechanics implemented?",
+      "description": "Check whether the character movement system includes smooth WASD/arrow key controls, collision detection with environment, interaction with NPCs/objects, and adventure progression mechanics. Evaluate if the controls feel responsive (input lag < 50ms), include animations for different movement states, and support exploration features like item collection, dialogue systems, or quest mechanics. Deduct 5 points if movement is choppy or unresponsive, 5 points if collision detection is missing or buggy.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the game capture the Pokemon-style adventure essence?",
+      "description": "Assess whether the game successfully implements Pokemon-inspired gameplay elements such as creature encounters, turn-based or real-time combat systems, character progression, inventory management, or exploration rewards. Check for thematic consistency in art style, UI design, and game mechanics that evoke the Pokemon adventure experience. Score 0 if no Pokemon-style elements exist, 5 if basic encounter/combat mechanics are present, and 10 if comprehensive adventure systems with proper game flow are implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust and handles edge cases properly?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid user inputs, browser compatibility issues, performance drops, collision edge cases, etc.) and provide friendly error handling or recovery mechanisms. Code with strong robustness should gracefully handle WebGL context loss, memory management, and various device capabilities. Give 10 points if fully robust, 5 points if basic error handling exists, and 0 points if no exception handling is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there innovative features that enhance the adventure experience?",
+      "description": "Check whether the code includes creative features that elevate the gaming experience (e.g., 1. Dynamic weather/day-night cycles 2. Procedural terrain generation 3. Advanced particle effects for abilities 4. Mini-map or compass navigation 5. Audio-reactive elements). Add 2-3 points for each well-implemented innovative feature that genuinely improves gameplay immersion (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant or performance-hindering features?",
+      "description": "Strictly identify three types of issues: 1. Redundant implementations of similar functionality (e.g., multiple rendering loops or duplicate input handlers) 2. Unnecessary features unrelated to the adventure game core (e.g., unrelated mini-games or excessive UI elements) 3. Performance-heavy effects that cause frame drops (e.g., excessive particle systems, unoptimized 3D models). Deduct 3 points for each redundancy found, and deduct 10 points if core gameplay is negatively affected.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code demonstrate proper engineering practices?",
+      "description": "Review modular architecture (separation of game logic/rendering/input systems), code organization, performance optimization techniques, and asset management. Check for proper use of design patterns, efficient memory usage, and clean code structure. Deduct 5 points for global variable pollution or lack of proper class/module structure; deduct 5 points if code duplication exceeds 30%; deduct 5 points for poor performance optimization (frame rate < 30fps on average hardware).",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the visual design meet professional game UI standards?",
+      "description": "Evaluate whether the game interface follows modern game UI principles: 1) Cohesive color palette suitable for adventure theme 2) Proper HUD layout with health bars, inventory, and controls clearly visible 3) Consistent visual hierarchy and readable typography (font size ≥ 12px for UI elements). Deduct 3 points for each cluttered UI element, 5 points for poor contrast or readability issues, and 5 points for inconsistent visual style that breaks immersion.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Are the game interactions fluid and provide proper feedback?",
+      "description": "Judge whether the interactive elements provide satisfying user feedback: 1) Character actions have immediate visual/audio response (≤ 100ms) 2) Smooth animation transitions for movements and UI changes (200-400ms duration) 3) Clear visual indicators for interactable objects and game state changes 4) Consistent 60fps performance during gameplay. Deduct 5 points for each unresponsive interaction, 3 points for choppy animations or frame drops, and 5 points for unclear interaction affordances that confuse players.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Role-Playing",
+  "difficulty": "hard"
+}

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

@@ -0,0 +1,68 @@
+{
+  "index": 414,
+  "question": "You are a coding expert, please utilize your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable. Create a 3D shooting game similar to Game for Peace (PUBG Mobile) using HTML.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "3D Rendering Engine Implementation",
+      "description": "Check whether the code implements a functional 3D rendering engine using WebGL/Three.js or equivalent technology. Score 0 if no 3D rendering is implemented, 5 if basic 3D objects are displayed without proper lighting/shading, and 10 if the engine supports proper 3D terrain, dynamic lighting, shadows, and object rendering with appropriate performance optimization.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "First-Person Shooter Core Mechanics",
+      "description": "Evaluate the implementation of core FPS mechanics including character movement (WASD controls), aiming mechanism (mouse look), weapon system (multiple weapons with different characteristics), shooting mechanics with recoil and bullet physics, and hit detection. Deduct 2 points for each missing core mechanic. Score 10 if all core mechanics are implemented with realistic physics.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Battle Royale Game Loop",
+      "description": "Assess whether the code implements the complete battle royale game loop: player parachuting, shrinking play zone, looting system, and last-player-standing victory condition. Score 0 if the game loop is absent, 5 if only basic elements are implemented, and 10 if the full game cycle is present including shrinking zone damage, proper timing, and end-game scenarios.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "AI Bot Implementation",
+      "description": "Review whether the game includes AI opponents with appropriate behaviors: pathfinding, combat decision-making, looting, and using cover. Score 0 if no AI is implemented, 5 if bots only have basic movement and shooting, and 10 if bots demonstrate tactical behaviors including flanking, using cover, and adapting to player strategies.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Code Robustness",
+      "description": "Evaluate whether the code can handle common abnormal situations (browser compatibility issues, variable screen sizes, resource loading failures, unexpected user inputs). Code with strong robustness should handle these edge cases with graceful degradation and informative error messages, scoring 10 points. If robustness is average, give 5 points, and if no exception handling exists, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Innovative Features",
+      "description": "Check whether the code includes surprising features that enhance the experience (e.g., 1. Destructible environment 2. Weather effects affecting gameplay 3. Vehicle physics 4. Advanced hitbox system with damage zones). Add 2.5 points for each practical innovative feature implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Absence of Redundant Features",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple movement control systems) 2. Function modules unrelated to the core FPS experience 3. Excessive visual effects that severely impact performance. Deduct 3 points for each redundancy found, and directly deduct 10 points if core functions are compromised by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Engineering Quality",
+      "description": "Review modular design (separation of rendering engine, game logic, input handling, physics), asset loading optimization, and memory management. Deduct 3 points if global state pollution exists; deduct 3 points if framerate drops below 30fps on standard hardware; deduct 4 points if no asset preloading or progressive loading is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Visual Design and UI",
+      "description": "Evaluate whether the game interface follows professional gaming UI principles: 1) Minimalist HUD that doesn't obstruct gameplay 2) Clear visual indicators for health, ammo, and minimap 3) Proper scaling on different devices. Deduct 3 points for cluttered UI elements, 3 points for poor contrast making information hard to read, and 4 points for non-responsive design elements.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Game Feel and Responsiveness",
+      "description": "Judge whether the game controls and feedback create satisfying game feel: 1) Input lag under 50ms 2) Visual feedback for all player actions including hits, damage taken, and healing 3) Appropriate sound effects synchronized with actions. Deduct 3 points for sluggish controls, 3 points for missing feedback on critical actions, and 4 points if weapon handling lacks weight or impact.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Shooting",
+  "difficulty": "hard"
+}

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

@@ -0,0 +1,68 @@
+{
+  "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

@@ -0,0 +1,68 @@
+{
+  "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

@@ -0,0 +1,68 @@
+{
+  "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"
+}