@getollie/cli 0.0.5 → 0.2.0

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

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

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

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

package/library/game_development-action_rhythm/html5-game-virtual-joystick-npc-combat-vehicles-missions-map.json

@@ -1,68 +0,0 @@
-{
-  "index": 423,
-  "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 a complete HTML5 game code that includes virtual joystick controls, mobile system, NPC combat, vehicle driving and mission systems, with some NPCs owning vehicles that we can steal, and featuring a large map.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the virtual joystick control system properly implemented?",
-      "description": "Examine whether the virtual joystick provides smooth, responsive touch controls with proper event handling, tactile feedback, and customizable sensitivity. Check if it handles multi-touch events, provides visual feedback, and adapts to different screen sizes. Score 0 if joystick controls are missing, 5 if basic implementation exists but lacks responsiveness or visual feedback, and 10 if fully implemented with configurable deadzones and multi-directional input support.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the mobile-friendly architecture properly designed and implemented?",
-      "description": "Evaluate if the code uses responsive design principles, optimizes for mobile performance (e.g., texture compression, asset loading strategies), implements proper touch events handling, and includes mobile-specific features like device orientation controls. Deduct 5 points if mobile detection and adaptation are missing, and 3 points if performance optimizations for mobile devices are inadequate. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the NPC combat system fully functional?",
-      "description": "Analyze if NPCs have proper AI behaviors (pathfinding, aggression ranges, combat tactics), health/damage systems, and provide appropriate challenge levels. Check for combat mechanics like hitboxes, weapon systems, and damage indicators. Deduct 5 points if NPCs lack basic AI behaviors, 3 points if combat interactions are buggy or incomplete. Give 10 points for a complete system with varied NPC types and combat behaviors.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the vehicle system and theft mechanic completely implemented?",
-      "description": "Check if vehicles have realistic physics (acceleration, braking, steering), collision detection, enter/exit animations, and if NPCs can own and drive vehicles. Validate if the player can approach NPC vehicles, steal them through appropriate mechanics, and if NPCs respond accordingly. Deduct 5 points if vehicle physics are unrealistic, and 5 points if the stealing mechanic is missing or poorly implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as touch event errors, device orientation issues, resource loading failures, 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. Weather systems affecting gameplay 2. In-game economy with shops/upgrades 3. Day/night cycle with different NPC behaviors). 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 that conflict) 2. Function modules unrelated to the core gameplay (e.g., unnecessary mini-games) 3. Fancy effects that affect performance (e.g., excessive particle effects that slow down mobile devices). 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 systems), proper use of design patterns, code organization, and asset management. Deduct 5 points if global state pollution is found; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if proper asset preloading and caching strategies are missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional game design standards?",
-      "description": "Evaluate whether the UI follows modern game design principles: 1) Clear, non-intrusive HUD elements 2) Proper scaling across different device sizes 3) Consistent visual language and readable text (minimum 16px on mobile). Deduct 3 points for cluttered UI elements, 5 points for poor visibility during gameplay, and 5 points for inconsistent UI styling. 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 performance: 1) Minimum 30 FPS during gameplay 2) Loading times under 5 seconds for scene transitions 3) Responsive controls with input lag under 100ms. Deduct 5 points for frequent frame drops, 3 points for janky animations, and 5 points for unresponsive controls during intense gameplay. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Action/Rhythm",
-  "difficulty": "hard"
-}

package/library/game_development-action_rhythm/mario-style-game-html.json

@@ -1,68 +0,0 @@
-{
-  "index": 425,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure any code you generate is executable for demonstration. Create a Mario-style game using HTML.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core Mario game mechanics fully implemented?",
-      "description": "Review whether the code accurately implements fundamental mechanics like character movement (left/right running, jumping), gravity physics, collision detection with platforms/blocks, and enemy interactions. Score 0 if core mechanics are missing, 5 points if only basic movement is implemented, and 10 points if all classic Mario mechanics (including jumping on enemies, breaking blocks, collecting coins) are properly implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the level design system properly constructed?",
-      "description": "Check whether the code provides a flexible system for defining game levels, including platform placement, enemy positioning, item distribution, and scrolling functionality. Evaluate if the level structure supports horizontal scrolling as Mario moves. Deduct 5 points if scrolling is missing, 3 points if collision detection with level elements is inconsistent. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are classic Mario game elements included?",
-      "description": "Evaluate whether the implementation includes recognizable Mario elements like coins, mushrooms for power-ups, question blocks, pipes, different enemy types, and end-level flags. Deduct 2 points for each missing classic element that affects the authentic Mario experience. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the game state and scoring system properly implemented?",
-      "description": "Check whether the code includes game state management (lives system, level progression, score tracking), power-up status effects, and proper restart/game over conditions. Deduct 3 points if the scoring system is missing, 3 points if power-up effects don't change gameplay, and 4 points if level progression or game over handling is absent. 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, performance issues on different devices) 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. Custom level editor 2. Modern visual effects while maintaining retro style 3. Mobile-friendly touch controls 4. Local multiplayer). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple movement control systems) 2. Function modules unrelated to the Mario game (e.g., unrelated 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 engine/rendering/input handling), code reusability, and maintainability. Evaluate whether the game loop uses requestAnimationFrame properly and maintains consistent FPS. Deduct 5 points if global state pollution is found; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the game performance degrades significantly during play. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the visual design balances retro Mario aesthetics with modern web standards: 1) Consistent pixel art style that respects the original design 2) Proper UI scaling for different screen sizes 3) Clean HUD layout showing score, lives, and level information. Deduct 3 points for inconsistent visual style, 5 points for unreadable UI elements, and 5 points for poor responsive design. 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 animations feel responsive and natural: 1) Input response delay ≤ 50ms 2) Smooth character animations for running, jumping, and state changes 3) Consistent frame rate without stuttering. Deduct 5 points for input lag, 3 points for choppy animations, and 5 points for unresponsive controls during complex actions. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Action/Rhythm",
-  "difficulty": "hard"
-}

package/library/game_development-action_rhythm/monkey-king-havoc-in-heaven-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 1729,
-  "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. Create a game about Monkey King's Havoc in Heaven and generate the code for it.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core gameplay mechanic of Monkey King's Havoc in Heaven properly implemented?",
-      "description": "Review whether the code accurately implements the core gameplay elements of Monkey King fighting against heavenly forces. Check for proper character movement controls, combat mechanics (attacks, special abilities like cloud-riding, somersaults, staff transformation), and enemy AI behaviors. Score 0 if core gameplay is missing, 5 if basic movement and combat exist, and 10 if the gameplay includes signature Monkey King abilities from the classic story.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the game progression system well-designed?",
-      "description": "Evaluate whether the game includes level progression that follows the narrative of Monkey King's journey (Havoc in Heaven storyline with recognizable scenes like the celestial palace, Dragon King's underwater palace, etc.). Check if there are boss battles with known characters from the story (Jade Emperor, Erlang Shen, Nezha). Deduct 5 points if the game lacks progression logic, and 3 points if the progression doesn't follow the traditional narrative. Give 10 points for a comprehensive story-based level system.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are the key character abilities and transformations of Monkey King implemented?",
-      "description": "Check whether the code implements Monkey King's signature abilities: 1) Staff transformation (extending/shrinking), 2) 72 transformations or shapeshifting, 3) Cloud-somersault travel, 4) Hair magic tricks. Deduct 3 points for each missing signature ability. The full score is 10 points for including all or most iconic abilities with proper visual feedback.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the game's visual style consistent with Chinese mythological aesthetics?",
-      "description": "Assess whether the visual elements (character designs, environments, animations) reflect traditional Chinese art styles appropriate for the Journey to the West theme. Check for proper use of colors symbolic in Chinese culture, traditional architectural elements, and authentic character designs. Deduct 5 points if the visuals are generic without Chinese cultural elements, and 3 points if the style is inconsistent. 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 out-of-bounds input, resource loading failures, user operation errors, 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 systems affecting gameplay 2. Procedurally generated heavenly palaces 3. Interactive storytelling with famous scenes from Journey to the West). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple movement control systems) 2. Function modules unrelated to the Monkey King theme (e.g., unrelated 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/view/physics/input layers), resource management efficiency, and performance optimization. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no optimization for asset loading and rendering. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern game UI principles: 1) Harmonious color matching reflecting Chinese cultural aesthetics 2) Proper layout spacing for game HUD elements 3) Professional font system with legible text that fits the theme (possibly stylized Chinese-inspired fonts). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic UI 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) Responsive controls with input lag ≤ 100ms 2) Smooth animations for Monkey King's movements and transformations 3) Clear visual feedback for player actions and game events. Deduct 5 points for each operation without feedback, 3 points for choppy animations during fast movements, and 5 points for unclear combat hit detection or feedback. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Action/Rhythm",
-  "difficulty": "medium"
-}

package/library/game_development-action_rhythm/music-rhythm-training-application.json

@@ -1,68 +0,0 @@
-{
-  "index": 645,
-  "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. Design a music rhythm training application where users listen to beats at different speeds and then practice by clicking a beat button within a specified time period. The system compares the user's clicking rhythm with the standard rhythm to calculate a score, displaying the user's rhythm accuracy.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the audio playback system properly implemented?",
-      "description": "Review whether the code accurately implements audio playback functionality using Web Audio API or similar technology, with proper handling of timing precision. Check if it includes adjustable tempo controls (BPM range at least 40-240), metronome sounds with appropriate attack and decay, and the ability to schedule beats with millisecond precision. Score 0 if core audio playback is not implemented, 5 if basic playback without precise timing is implemented, and 10 if the system has precise timing and all required controls.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the rhythm detection and scoring mechanism accurate?",
-      "description": "Evaluate whether the application correctly measures the time difference between user clicks and expected beats. The scoring system should account for human reaction time (typically 150-250ms) and have a graded scoring scale based on timing accuracy. Check for proper handling of early/late clicks with visualization of deviations. Deduct 5 points if the scoring doesn't account for human reaction time, and 3 points if the scoring lacks granularity (e.g., just right/wrong). The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the training progression system comprehensive?",
-      "description": "Check whether the application provides a structured learning approach with increasing difficulty levels (e.g., starting with simple quarter notes and progressing to complex polyrhythms). Verify if it includes exercises with varying time signatures (3/4, 4/4, 5/8, etc.) and rhythm patterns. Evaluate if there's a clear progression path with unlockable levels based on performance. Deduct 5 points if progression is linear without adaptivity, and 3 points if variety in rhythm patterns is limited. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is performance analysis and feedback implemented?",
-      "description": "Assess whether the application provides detailed performance metrics and visual feedback. Look for features like historical performance tracking, visualization of timing errors (e.g., waveform or graph showing deviations), and actionable improvement suggestions. The system should store and display progress over time. Deduct 5 points if only basic scoring is provided without visual representation, and 3 points if historical tracking is missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as audio context initialization failures, timing drift, browser compatibility issues, etc.) and provide friendly error prompts or recovery mechanisms. Check for proper cleanup of audio resources and event listeners. 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. Visualization of rhythm patterns with animations 2. AI-assisted rhythm correction 3. Social features for comparing scores with friends 4. Exportable practice recordings). 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 timing systems coexisting) 2. Function modules unrelated to rhythm training (e.g., a built-in music player without training purpose) 3. Fancy effects that affect performance (e.g., excessive animations that impact timing accuracy). 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 engine/UI/scoring logic), unit test coverage for timing-critical components, 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). Check if visual cues for rhythm are intuitive and clear. 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 latency ≤ 50ms (critical for rhythm applications) 2) Visual feedback synchronized with audio events 3) Clear visual indication of successful/missed beats. Check if the application feels responsive during interaction. Deduct 5 points for perceptible input lag, 3 points for audio-visual synchronization issues, and 5 points for confusing feedback during rhythm exercises. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Action/Rhythm",
-  "difficulty": "hard"
-}

package/library/game_development-action_rhythm/musical-rhythm-key-response-action-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 38,
-  "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 display.\n\nPlease use HTML and JavaScript to implement an action game - rhythm game: Musical rhythm and key response\n\n**Task**: Design a rhythm game system where players need to press corresponding keys according to the music rhythm to score points.\n\n**Hint**: You can use audio analysis or time nodes to synchronize key inputs with music rhythm.\n\nPlease create the game and add some comments in the code so other developers can understand your implementation process.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the rhythm game core mechanics fully implemented?",
-      "description": "Review whether the code accurately implements the key note system through HTML/JavaScript, including note generation, timing detection, and scoring calculation. Check if there's proper synchronization between the music and falling notes. Score 0 if the core mechanics are missing, 5 if basic note detection works but with timing issues, and 10 if the system has precise timing windows with appropriate visual feedback.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the audio synchronization mechanism properly designed?",
-      "description": "Evaluate whether the game implements proper audio synchronization using either audio analysis (frequency/beat detection) or predefined time nodes. Check for audio calibration options to handle different devices/browsers. Deduct 5 points if there's noticeable lag between audio and visuals, 3 points if there's no calibration system, and 2 points if the synchronization degrades over time. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is a comprehensive scoring system implemented?",
-      "description": "Check whether the code includes a multi-tier scoring system (Perfect/Great/Good/Miss) with appropriate timing windows, combo multipliers, and visual/audio feedback for each tier. Evaluate if the scoring algorithm rewards consistency and includes features like combo breaks and recovery. Deduct 5 points if only binary hit/miss detection exists, and 3 points if combo tracking is missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there a complete song/level management system?",
-      "description": "Review if the code includes functionality for multiple songs/difficulty levels with different note patterns. Check if there's a difficulty rating system, song selection interface, and progression tracking (high scores, grade rankings). Deduct 5 points if only a single song is supported, 3 points if difficulty options are missing, and 2 points if there's no score persistence. 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 audio loading failures, browser audio API limitations, irregular key presses, 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. Custom beatmap creator 3. Visual effects synchronized with music 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 input detection logic (e.g., multiple keyboard event listeners with overlapping functionality) 2. Function modules unrelated to rhythm gameplay (e.g., unnecessary mini-games) 3. Excessive visual effects that cause performance issues on regular devices. 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 handling, note generation, input detection, and rendering), code readability (including the requested developer comments), and performance optimization. Deduct 5 points if global variable abuse is found; deduct 5 points if the code lacks meaningful comments as requested; deduct 5 points if there are performance bottlenecks causing frame drops. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern game UI principles: 1) Clear note highway with distinct lane separation 2) High contrast between notes and background for visibility 3) Coherent color scheme that matches the musical theme. Deduct 3 points for each hard-to-see element, 5 points for cluttered UI that obscures gameplay, and 5 points for inconsistent visual style. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the game's response and animations conform to rhythm game standards: 1) Input lag ≤ 50ms for responsive feel 2) Smooth note movement at minimum 60fps 3) Clear hit/miss feedback with appropriate duration. Deduct 5 points for each noticeable input delay, 3 points for jerky note movement, and 5 points for confusing or missing hit feedback. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Action/Rhythm",
-  "difficulty": "hard"
-}