@getollie/cli 0.0.1

package/library/game_development-action_rhythm/gorilla-chase-parkour-running-game.json

@@ -0,0 +1,68 @@
+{
+  "index": 752,
+  "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. Create a web game where a person is being chased by a gorilla from behind - a parkour/running game.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core parkour game mechanics fully implemented?",
+      "description": "Review whether the code implements the basic parkour/running mechanics including player movement, jumping, obstacles generation, collision detection, and scoring system. The character must be able to run forward with the gorilla chasing from behind. Score 0 if the core mechanics are absent, 5 if basic movement and obstacle detection exist but without proper chase dynamics, and 10 if the complete parkour system with difficulty progression is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the gorilla chase AI behavior properly designed?",
+      "description": "Evaluate the gorilla's AI behavior - it should dynamically pursue the player with appropriate difficulty scaling (increasing speed over time or when player performs well). Check if the gorilla has realistic animations and movement patterns. Deduct 5 points if the gorilla moves in a straight line without any intelligence, 3 points if the chase animation lacks smoothness, and 2 points if there's no difficulty progression. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are the game controls responsive and intuitive?",
+      "description": "Check if the game implements touch/keyboard controls that respond within 50ms, allowing the player to jump, slide, or dodge obstacles. Controls should be clearly explained and consistent. Deduct 5 points if input lag exceeds 100ms, 5 points if controls are not explained in-game, and 3 points if the control scheme is overly complicated. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the game environment properly generated and infinite?",
+      "description": "Assess whether the code implements procedural generation of the game environment for endless running, with appropriate memory management (removing off-screen elements). Check if obstacle patterns are varied and thematically appropriate. Deduct 5 points if the environment is static/finite, 3 points if obstacles are too repetitive, and 5 points if there are performance issues with environment generation. 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 changes, browser resizing, device orientation changes, 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. Power-ups that temporarily slow the gorilla 2. Environmental interaction like swinging vines 3. Different biomes/environments as the game progresses). 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 that serve the same purpose) 2. Function modules unrelated to parkour gameplay (e.g., an unnecessary inventory system) 3. Fancy effects that affect performance (e.g., excessive particle systems causing 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/view/input handling layers), asset management, 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 there's no asset preloading strategy. 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) Consistent visual theme (jungle/urban environment) 2) Clear UI elements that don't obstruct gameplay (score display, distance meter) 3) Appropriate visual feedback for actions (jump animations, collision effects). Deduct 3 points for each interfering UI element, 5 points for inconsistent visual style, and 5 points for hard-to-read text 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 maintains consistent frame rate (minimum 30 FPS) and whether animations are fluid: 1) Character animation transitions are smooth 2) Obstacle appearance and removal are seamless 3) Game speed changes gradually rather than abruptly. Deduct 5 points for frame rate drops below 30 FPS, 3 points for jerky animations during critical gameplay moments, and 5 points for abrupt visual changes that disrupt gameplay flow. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Action/Rhythm",
+  "difficulty": "medium"
+}

package/library/game_development-action_rhythm/html-game-character-sprints-forward.json

@@ -0,0 +1,68 @@
+{
+  "index": 91,
+  "question": "You are a code expert. Please use your professional knowledge to provide accurate and professional responses. Make sure the generated code is executable. Create a game using HTML where a character sprints forward, ensuring it can run directly in the frontend.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the basic game character and movement system implemented?",
+      "description": "Check whether the code implements a character that moves forward continuously with proper animation frames. Verify if the character maintains consistent forward movement (sprinting) without stopping. Score 0 if there's no character movement, 5 if there's basic movement without animation, and 10 if the character has smooth sprinting animation with proper frame transitions.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the game environment and background properly implemented?",
+      "description": "Evaluate if the game has a scrolling background or environment elements that create the illusion of the character moving forward. Check for parallax scrolling effects (multiple layers moving at different speeds) and if the environment repeats seamlessly. Score 0 if there's no background, 5 if there's a static or basic scrolling background, and 10 if there's a well-implemented parallax scrolling effect with seamless transitions.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are the game controls responsive and intuitive?",
+      "description": "Review if the game includes user input handling (keyboard/touch controls) for actions like jumping, ducking, or changing lanes. Test the responsiveness of controls (input lag <50ms) and verify if there are visual cues for available actions. Score 0 if there are no controls, 5 if basic controls exist but feel sluggish, and 10 if controls are responsive and intuitive with appropriate feedback.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is there a game loop with proper frame management?",
+      "description": "Check if the code implements a proper game loop using requestAnimationFrame() or similar methods, maintaining consistent frame rates (ideally 60fps) and including time-based movement calculations instead of frame-based to ensure consistent speed across different devices. Score 0 if there's no game loop, 5 if there's a basic loop without performance optimization, and 10 if there's a well-optimized game loop with frame timing.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as browser resizing, tab switching, device orientation changes, 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 difficulty adjustment 2. Character customization 3. Special power-ups or abilities 4. Weather/time effects that affect gameplay). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple collision detection systems) 2. Function modules unrelated to the sprint game (e.g., unnecessary mini-games) 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 logic/view/input handling layers), asset preloading, and code organization. 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 assets are loaded during gameplay causing stutters. 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) Consistent visual style and theme 2) Clear distinction between game elements and UI elements 3) Professional font system (readable text during movement, appropriate size for game context). Deduct 3 points for each inconsistent visual element, 5 points for confusing UI/game element boundaries, and 5 points for poorly implemented text elements. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Character responds to input within 100ms 2) Animation transitions are smooth without flickering 3) Clear visual feedback for player actions and collisions. Deduct 5 points for each operation without feedback, 3 points for frame drops during animation transitions, and 5 points for unclear collision feedback. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Action/Rhythm",
+  "difficulty": "easy"
+}

package/library/game_development-action_rhythm/html-javascript-drift-mechanism-implementation.json

@@ -0,0 +1,68 @@
+{
+  "index": 123,
+  "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 and demonstrable.\n\nPlease implement a drift mechanism using HTML and JavaScript.\n\n**Task**: Design a drift mechanism where players can drift to make quick turns or avoid obstacles.\n\n**Hint**: You can set up the drift trigger method and effects, and design tracks or scenarios that require drifting skills.\n\nPlease create a game and include some comments in your code to help other developers understand your implementation process.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core drift mechanism properly implemented?",
+      "description": "Check whether the code accurately implements a realistic drift physics model that includes friction, inertia, and weight transfer. The drift should feel different from normal turning and require skill. Score 0 if no drift mechanic exists, 5 if basic drift is implemented but feels unrealistic, and 10 if the drift mechanism includes proper physics calculations with variables for different surfaces.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the drift trigger and control system intuitive?",
+      "description": "Evaluate the drift activation method (e.g., handbrake button, double-tap direction key) and the control system during drift. Check if there's proper input feedback and if the drift can be controlled mid-execution. Deduct 5 points if drift activation is unintuitive or inconsistent, 3 points if the drift control is too simplified without nuance, and 2 points if there's no visual or audio feedback when drifting. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are meaningful drift scenarios or tracks implemented?",
+      "description": "Check whether the code includes challenging tracks or scenarios where drifting provides a tangible advantage (tight corners, obstacle courses, time trials). Deduct 5 points if there are no specific scenarios that encourage drifting, 3 points if the track design doesn't require skill to navigate with drifts, and 2 points if there's no variety in the course design. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is there a meaningful scoring or feedback system for drifting?",
+      "description": "Evaluate if the implementation includes a scoring system, time bonuses, or other rewards for successful drifting. Check if the system provides feedback on drift quality (perfect drift, over-drift, etc.). Deduct 5 points if there's no scoring/reward system tied to drifting, 3 points if feedback is minimal, and 2 points if the scoring system doesn't reflect drift skill accurately. 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 changes, extreme speed conditions, collisions during drift) 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. Drift boost mechanics 2. Variable terrain effects on drift performance 3. Visual drift lines or tire marks 4. Drift combo 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 movement controls (e.g., multiple drift calculation systems coexisting) 2. Function modules unrelated to the drift mechanic (e.g., unnecessary weather effects) 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 physics engine, input handling, and rendering), code documentation, and 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 there are no comments explaining the drift physics calculations. 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 gaming UI principles: 1) Clean HUD that doesn't obstruct gameplay 2) Clear visual indicators for drift status and performance 3) Appropriate use of motion blur or visual effects during drift. Deduct 3 points for cluttered UI elements, 5 points for distracting visual effects that make drifting harder to control, and 5 points for poor contrast that makes track boundaries difficult to see. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the drift mechanics feel responsive and natural: 1) Input response delay ≤ 50ms 2) Smooth transition between normal driving and drift state 3) Consistent frame rate during drift animations. Deduct 5 points for input lag during critical drift moments, 3 points for jittery vehicle movement during drift transitions, and 5 points for inconsistent physics behavior at different speeds. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Action/Rhythm",
+  "difficulty": "easy"
+}

package/library/game_development-action_rhythm/html-javascript-platform-jumping-game.json

@@ -0,0 +1,68 @@
+{
+  "index": 111,
+  "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.\n\nPlease use HTML and JavaScript to implement a platform jumping game where players need to jump and climb to pass through levels while avoiding traps. Set up jumping and climbing controls, and design various platforms and traps. Please include comments in your code so that other developers can understand your implementation process.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core platform jumping mechanic fully implemented?",
+      "description": "Review whether the code accurately implements jumping physics with gravity simulation, variable jump height based on button press duration, and proper collision detection with platforms. Score 0 if basic jumping is missing, 5 if only basic jumping is implemented without physics refinement, and 10 if jumping feels responsive with polished physics (e.g., terminal velocity, jump buffering, coyote time).",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the climbing mechanic properly implemented?",
+      "description": "Check whether the climbing mechanics include proper collision detection with climbable surfaces, smooth transitions between climbing and jumping states, and appropriate control limitations while climbing. Score 0 if climbing is not implemented, 5 if basic climbing exists but feels clunky or has collision issues, and 10 if climbing is smooth with proper animation transitions and intuitive controls.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are various platforms and traps designed and functional?",
+      "description": "Evaluate the diversity and functionality of platforms (static, moving, disappearing, bouncy) and traps (spikes, falling objects, timing-based hazards). Deduct 3 points if fewer than 3 platform types are implemented, 5 points if traps have no visual warning indicators, and 3 points if collision detection with hazards is inconsistent. Score 10 if at least 5 different interactive platform/trap types are implemented with clear visual distinction.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is level design and progression implemented?",
+      "description": "Check whether the game includes multiple levels with increasing difficulty, clear objectives for level completion, and smooth transitions between levels. Score 0 if only a single static level exists, 5 if multiple levels exist but lack progression in difficulty or design variety, and 10 if the game has thoughtful level progression with checkpoint systems and escalating challenges.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as rapid input changes, framerate fluctuations, boundary conditions at level edges, etc.) and provide friendly error handling. 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-ups with special abilities 2. Environmental interactions like destructible objects 3. Dynamic camera effects that respond to gameplay 4. Particle effects for movement feedback). 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 platform jumping gameplay (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/physics/rendering layers), code readability through comments as requested, and maintainable structure. Deduct 5 points if global state pollution is found; deduct 5 points if the code lacks the requested comments explaining the implementation; deduct 5 points if there's significant code duplication instead of reusable functions. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional game design standards?",
+      "description": "Evaluate whether the game follows professional game design principles: 1) Clear visual hierarchy between background, platforms, hazards and player character 2) Consistent art style throughout elements 3) Proper use of visual feedback for player actions (jumping, landing, taking damage). Deduct 3 points for poor contrast between interactive and non-interactive elements, 5 points for inconsistent visual style, and 5 points for lack of feedback animations. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and responsive?",
+      "description": "Judge whether the game controls feel responsive and smooth: 1) Input response time ≤ 50ms 2) Consistent framerate with no stuttering during animations 3) Appropriate game speed and character movement velocity. Deduct 5 points for input lag, 3 points for jerky animations during transitions, and 5 points for inconsistent game speed affecting gameplay. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Action/Rhythm",
+  "difficulty": "hard"
+}

package/library/game_development-action_rhythm/html-javascript-rhythm-game-custom-music-levels.json

@@ -0,0 +1,68 @@
+{
+  "index": 54,
+  "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.\n\nPlease use HTML and JavaScript to implement an action game - rhythm game: custom music and level generation.\n**Task**: Design a custom music mode that allows players to import their own music and automatically generate levels based on the audio tracks.\n**Hint**: You can use audio analysis tools to extract rhythm information and generate corresponding key press points.\n\nPlease include comments in your code so that other developers can understand your implementation process.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the music import functionality fully implemented?",
+      "description": "Review whether the code implements file upload capabilities that support common audio formats (MP3, WAV, OGG), and includes proper validation and error handling for file size and format. Score 0 if music import is not implemented, 5 if only basic file upload is available, and 10 if it includes advanced features like progress indicators and drag-and-drop functionality.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the audio analysis system properly implemented?",
+      "description": "Evaluate whether the code uses Web Audio API to analyze the imported audio track, including beat detection, frequency analysis, and amplitude variation. Check if it extracts meaningful rhythm information such as BPM, beat timing, and intensity changes. Deduct 5 points if only basic amplitude analysis is implemented, and 3 points if the analysis doesn't account for different music genres. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the level generation algorithm effective and aligned with the music?",
+      "description": "Check if the algorithm maps audio analysis data to gameplay elements (note placement, timing, patterns) that match the rhythm and intensity of the music. Verify if it creates a balanced difficulty curve and handles transitions between different music sections. Score 0 if level generation is random/unrelated to the music, 5 if it only follows basic beat patterns, and 10 if it creates varied and musically-coherent gameplay experiences.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the gameplay mechanic responsive and synchronized with the music?",
+      "description": "Assess whether the game maintains proper synchronization between visuals, input detection, and audio playback. Check for techniques to minimize audio latency and ensure visual cues appear at the correct time. Deduct 5 points if there's noticeable desynchronization, 3 points if there's no calibration system for different devices. 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 unsupported audio formats, processing large files, unexpected user interactions, 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. Real-time visual effects synchronized with music 2. Customizable note appearance and effects 3. Social sharing of created levels). 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 audio analysis methods performing the same task) 2. Function modules unrelated to rhythm gameplay (e.g., unnecessary social features) 3. Fancy effects that affect performance (e.g., excessive particles 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 audio analysis/game logic/rendering layers), unit test coverage, and build process automation. 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 build process is not automated. 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 design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Input response delay ≤ 50ms (crucial for a rhythm game) 2) Visual feedback aligned precisely with audio events 3) Consistent frame rate without drops during intensive sections. Deduct 5 points for perceptible input lag, 3 points for misaligned visual/audio elements, and 5 points for frame rate issues during gameplay. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Action/Rhythm",
+  "difficulty": "hard"
+}

package/library/game_development-action_rhythm/html-javascript-sliding-challenge-game.json

@@ -0,0 +1,68 @@
+{
+  "index": 15,
+  "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.\n\nPlease use HTML and JavaScript to implement a Sliding Challenge game where players can slide down slopes or on icy surfaces and need to avoid obstacles. You can set the sliding speed and direction, and design sliding routes that require quick reactions.\n\nPlease include comments in your code to help other developers understand your implementation process.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core sliding mechanics fully implemented?",
+      "description": "Review whether the code accurately implements the physics of sliding (acceleration/deceleration) through HTML/JavaScript, and whether it handles different surface types (slopes vs. icy surfaces). Score 0 if the sliding mechanics are not implemented, 5 if only basic sliding is implemented without differentiation between surfaces, and 10 if the physics feels realistic with proper friction coefficients for different surfaces.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are the obstacle avoidance mechanics well-designed?",
+      "description": "Check whether collision detection with obstacles is properly implemented, and whether the player feedback on collision is clear. Obstacles should have varying difficulty levels and require different reaction speeds. Deduct 5 points if collision detection is inaccurate or buggy, 3 points if all obstacles have the same difficulty level, and 2 points if visual feedback on collision is poor. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the sliding speed and direction control intuitive?",
+      "description": "Evaluate whether the controls for adjusting sliding speed and direction are intuitive and responsive. The game should provide clear visual feedback when changing direction or speed. Deduct 5 points if the controls feel sluggish, 3 points if there's no visual feedback on direction changes, and 5 points if the control system is too complex for a sliding game. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are the sliding routes designed with progressive difficulty?",
+      "description": "Check whether the sliding routes are designed with progressive difficulty, requiring increasingly quicker reactions from players. Routes should include varied challenges and interesting path choices. Deduct 5 points if the routes are too linear without branches, 3 points if the difficulty progression is too steep or nonexistent, and 3 points if the routes lack visual distinction. 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 changes, browser resizing, device rotation, 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. Power-ups that affect sliding physics 2. Weather effects that change surface conditions 3. Dynamic camera angles that react to speed). 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 sliding gameplay (e.g., unnecessary mini-games) 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 logic/physics/rendering layers), code commenting quality, and optimization for different devices. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code commenting is insufficient despite the requirement; deduct 5 points if the game performs poorly on mobile devices. 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 that distinguishes different surfaces and obstacles clearly 2) Proper layout for UI elements that don't obstruct gameplay 3) Appropriate visual cues for speed and direction. Deduct 3 points for each hard-to-see obstacle, 5 points for confusing visual language, and 5 points for 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 human perception characteristics: 1) Control response delay ≤ 50ms 2) Smooth animations at minimum 30fps 3) Clear visual feedback for surface transitions. Deduct 5 points for each sluggish control response, 3 points for frame drops during critical gameplay moments, and 5 points for lack of visual/audio feedback when transitioning between surfaces. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Action/Rhythm",
+  "difficulty": "medium"
+}

package/library/game_development-action_rhythm/html-javascript-sound-reaction-game.json

@@ -0,0 +1,68 @@
+{
+  "index": 63,
+  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable for demonstration.\n\nPlease use HTML and JavaScript to implement a Sound Reaction system.\n\n**Task**: Add a sound reaction mechanism to the game where players need to react to specific sound effects to avoid dangers or seize opportunities.\n\n**Hint**: You can play specific sound effects and set up events that require players to react quickly, such as avoiding traps or attacking enemies.\n\nPlease include comments in your code so other developers can understand your implementation process.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Sound Loading and Management System",
+      "description": "Evaluate whether the code implements a comprehensive sound asset management system with preloading capabilities, format compatibility checks, and fallback mechanisms for unsupported formats.0 points if sound loading is not implemented, 5 points if basic audio loading exists but without error handling, 10 points for a complete system with preloading, multiple format support, and proper error handling.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Sound-based Event Triggering",
+      "description": "Check if the code effectively connects sound events to gameplay mechanisms, including accurate sound detection timing windows and appropriate feedback when reactions are required.0 points if sound events don't connect to gameplay, 5 points if basic sound-to-action connections exist but timing windows are too rigid, 10 points for well-calibrated reaction timing with clear user feedback.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Player Reaction Input Mechanisms",
+      "description": "Evaluate the implementation of input detection for player reactions to sounds, including keyboard/mouse/touch controls with appropriate debouncing and accessibility options.0 points if reaction inputs aren't implemented, 5 points for basic input detection without accessibility features, 10 points for comprehensive input options with accessibility support and precise timing validation.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Audio-Visual Feedback System",
+      "description": "Review how the system provides visual cues that correspond to audio signals, ensuring players can identify required reactions even with sound-off or for hearing-impaired users.0 points if no visual accompaniment to audio cues exists, 5 points if basic visual indicators are present, 10 points for a complete synchronized audio-visual system with accessibility considerations.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Code Robustness",
+      "description": "Evaluate whether the code handles common abnormal situations (such as browser audio API limitations, autoplay restrictions, audio device changes, etc.) and provides friendly error prompts or recovery mechanisms.0 points if no exceptions are handled, 5 points if some but not all key edge cases are addressed, 10 points for comprehensive error handling covering all major audio-related contingencies.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Innovative Features",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Dynamic difficulty adjustment based on reaction time, 2. Sound visualization for better accessibility, 3. Custom user sound uploads).Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Redundant Features",
+      "description": "Strictly check three types of redundancy: 1. Duplicate audio handling logic, 2. Unnecessary audio processing that impacts performance, 3. Over-complex audio features that don't contribute to the core reaction mechanics.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": "Code Engineering Quality",
+      "description": "Review modular design (separate audio engine/game logic/UI), audio resource management patterns, and code organization principles.Deduct 5 points if global audio state pollution is found; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no separation between audio logic and game mechanics. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Interface Design Standards",
+      "description": "Evaluate whether the overall design follows modern design principles: 1) Clear visual indicators for audio events, 2) Proper feedback animation for reactions, 3) Professional sound control UI (volume controls, mute options).Deduct 3 points for each unclear audio-related visual indicator, 5 points for confusing reaction feedback, and 5 points for missing essential audio controls. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Audio-Reaction Performance",
+      "description": "Judge the responsiveness and performance of the audio reaction system: 1) Audio-reaction latency ≤ 100ms, 2) Consistent frame rate during sound playback, 3) Efficient memory management for audio resources.Deduct 5 points for noticeable audio lag, 3 points for performance drops during intensive audio playback, and 5 points for memory leaks in audio handling. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Action/Rhythm",
+  "difficulty": "easy"
+}

package/library/game_development-action_rhythm/html-kpop-music-game-hit-keys-card-upgrade.json

@@ -0,0 +1,68 @@
+{
+  "index": 1309,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure to ensure that the code you generate is executable. Please provide an HTML format K-pop music game with hit keys, 3 levels, and a system where players clear levels by upgrading cards.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the basic K-pop music game core mechanics fully implemented?",
+      "description": "Review whether the code accurately implements key hit mechanics with timing detection (early/perfect/late hits), score calculation, and combo system. Check if the hit detection synchronizes properly with the music beats. Score 0 if core gameplay is missing, 5 if basic key hitting works without proper timing, and 10 if timing precision is properly implemented with visual feedback.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are the 3 difficulty levels properly implemented and balanced?",
+      "description": "Verify that 3 distinct difficulty levels exist with appropriate scaling of challenges (key hit frequency, pattern complexity, timing windows). Each level should have clear progression metrics and balance (not too easy/difficult). Deduct 3 points if levels aren't visually distinct, 5 points if difficulty scaling is poorly implemented, and 7 points if level progression system is broken or missing.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the card upgrade system functional and integrated with level progression?",
+      "description": "Check if the card collection and upgrade system is properly implemented, allowing players to gain upgrades through gameplay performance. Cards should have clear attributes affecting gameplay (score multipliers, timing windows, etc.). Deduct 5 points if the upgrade path is unclear, 7 points if card upgrades don't impact gameplay, and 10 points if the system is merely decorative.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the game include proper K-pop audio integration and music synchronization?",
+      "description": "Evaluate whether the game properly loads and synchronizes K-pop music tracks with the gameplay elements. Audio visualization should match the beat patterns, and hit markers should align with musical beats. Deduct 5 points for poor audio-visual synchronization, 3 points if music controls (pause/resume) aren't implemented, and 7 points if songs don't properly loop or transition between game states.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as audio loading failures, key input conflicts, browser incompatibilities, 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 backgrounds based on song mood 2. Leaderboard system with social sharing 3. Performance replays with highlights). 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 scoring systems operating simultaneously) 2. Function modules unrelated to K-pop rhythm gameplay (e.g., unrelated mini-games) 3. Fancy effects that affect performance (e.g., excessive particle effects causing 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/audio system/UI layers), code reusability, and asset loading 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 resource loading isn't optimized (preloading music files, image sprites). The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional K-pop game aesthetic standards?",
+      "description": "Evaluate whether the visual design captures K-pop aesthetics: 1) Vibrant color scheme appropriate to K-pop themes 2) Professional typography with readable scoring and feedback 3) Visual elements that reference K-pop culture and artists. Deduct 3 points for inconsistent visual theming, 5 points for poor readability during gameplay, and 5 points for generic designs that don't reflect K-pop styling. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and responsive to music?",
+      "description": "Judge whether the game provides satisfying feedback aligned with music: 1) Input lag under 50ms for key presses 2) Visual hit effects synchronized with audio cues 3) Smooth transitions between game states that don't interrupt the music flow. Deduct 5 points for noticeable input delay, 3 points for jerky animations during intense sections, and 5 points for audio-visual desynchronization during gameplay. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Action/Rhythm",
+  "difficulty": "hard"
+}