@getollie/cli 0.0.5 → 0.2.0

package/library/game_development-puzzle/web-based-fruit-tetris-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 986,
-  "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. Hello, could you please help create a web-based Tetris game where the blocks are cartoon fruit shapes instead of traditional shapes?",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core Tetris game mechanics fully implemented?",
-      "description": "Review whether the code implements all standard Tetris mechanics including block rotation, movement, line clearing, scoring system, and increasing difficulty. Check if the game loop runs smoothly at 60fps. Score 0 if core mechanics are missing, 5 if basic movement works but some mechanics are incomplete, 10 if all standard Tetris mechanics are properly implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the cartoon fruit shapes properly designed and implemented?",
-      "description": "Evaluate whether the code replaces traditional Tetris blocks with distinct fruit shapes that maintain gameplay balance. Check if the fruits have clear visual designs with proper hitboxes that match their appearance. Examine if the rotation of fruit shapes feels natural and consistent. Score 0 if still using traditional shapes, 5 if fruits are implemented but have visual or functional issues, 10 if fruits are well-designed, visually appealing, and function correctly.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the collision detection and grid system properly implemented?",
-      "description": "Check if the collision detection works correctly with the irregular fruit shapes. Verify that fruits stack properly on the game grid without visual glitches or logical errors. Test edge cases like wall kicks and floor kicks. Deduct 5 points for collision bugs, 3 points for grid alignment issues, and 2 points if rotation near walls causes problems. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are game controls and user interactions well-implemented?",
-      "description": "Verify keyboard controls for movement (left/right/down), rotation, and hard drop. Check if mobile touch controls are implemented with swipe gestures and tap actions. Test responsiveness of controls (should be under 100ms). Evaluate if there's a pause function and game reset option. Deduct 3 points if mobile support is missing, 5 points if controls feel unresponsive, and 2 points if pause/reset functions are 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 rapid input, browser resize, focus loss, 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. Fruit juice splatter effects when lines clear 2. Combo animations with fruit themes 3. Fruit-matching bonus mechanics 4. Dynamic backgrounds based on fruit types). 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 fruit-themed Tetris (e.g., unnecessary social media features) 3. Fancy effects that affect performance (e.g., excessive particle effects that slow down gameplay). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating game logic/rendering/input handling), code organization, and performance optimization. Deduct 5 points if global state management is messy; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if no performance optimizations are implemented for rendering multiple fruit shapes. 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 palette appropriate for a fruit theme 2) Proper layout with clear game board and next-piece preview 3) Consistent art style for all fruit pieces and UI elements. Deduct 3 points for inconsistent fruit designs, 5 points for a cluttered game UI, and 5 points for poor contrast between fruits and background. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the fruit blocks move and rotate smoothly: 1) No frame drops during piece movement 2) Satisfying animations for line clearing (200-400ms) 3) Visual/audio feedback when pieces lock into place. Deduct 5 points for jerky animations, 3 points for missing feedback when lines clear, and 5 points for laggy rotation or movement. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Puzzle",
-  "difficulty": "medium"
-}

package/library/game_development-puzzle/web-based-match-three-puzzle-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 1544,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and expert responses. Take care to ensure that any code you generate is executable and ready to be displayed. Create a simple web-based match-three puzzle game.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core match-three game mechanics fully implemented?",
-      "description": "Review whether the code accurately implements the match detection algorithm, piece swapping mechanism, and board state management. Check if it handles special patterns like L-shapes and T-shapes. Score 0 if the core matching logic is missing, 5 if only basic three-in-a-row matching is implemented, and 10 if advanced patterns and cascading matches are fully supported.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the game board initialization and management properly implemented?",
-      "description": "Evaluate the board generation algorithm to ensure it creates valid starting positions without pre-existing matches. Verify that the board repopulates correctly after matches are cleared. Deduct 5 points if the initial board can contain pre-existing matches, 3 points if edge cases (like board deadlocks) aren't handled. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the scoring system and game progression logic implemented?",
-      "description": "Check whether the game includes a proper scoring mechanism, level progression, difficulty scaling, and win/lose conditions. Deduct 5 points if scoring is overly simplistic, 3 points if difficulty doesn't increase over time, and 5 points if there are no clear win/lose conditions. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the user interaction for selecting and swapping pieces intuitive?",
-      "description": "Assess if the drag-and-drop or click-based selection system works smoothly across devices. Check if invalid moves are properly rejected with feedback. Deduct 5 points if the selection mechanism is unintuitive, 3 points if there's no visual feedback for selections, and 5 points if touch/mobile support is missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid moves, rapid clicking, browser resizing, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Special power-ups or boosters 2. Unique game modes 3. Combo multipliers or special effects for impressive matches). 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 ways to check matches) 2. Function modules unrelated to the match-three gameplay (e.g., unnecessary mini-games) 3. Fancy effects that affect performance (e.g., excessive particle effects slowing down gameplay). 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), code organization, and maintainability. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no clear separation between game logic 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 design principles: 1) Harmonious color matching for game pieces and background 2) Clear visual distinction between different piece types 3) Proper layout with well-defined game boundaries and UI elements. Deduct 3 points for poor piece distinction, 5 points for cluttered UI elements, and 5 points for inconsistent visual styling. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the game animations conform to human perception characteristics: 1) Immediate response to player input (≤ 100ms) 2) Smooth matching/clearing animations (300-500ms) 3) Fluid piece-falling animations. Deduct 5 points for laggy animations, 3 points for jerky piece movements, and 5 points for missing visual/audio feedback for matches. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Puzzle",
-  "difficulty": "hard"
-}

package/library/game_development-puzzle/web-based-single-player-tetris-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 1541,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be careful to ensure that the generated code is executable for demonstration. Create a web-based single-player Tetris game.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core Tetris game mechanics fully implemented?",
-      "description": "Review whether the code accurately implements the standard Tetris mechanics including piece rotation, movement, collision detection, line clearing, and scoring. Score 0 if the basic game loop is not implemented, 5 if only basic movement is implemented without proper collision or line clearing, and 10 if all standard Tetris mechanics are fully included with proper game physics.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are all standard Tetris pieces (tetrominoes) correctly implemented?",
-      "description": "Check whether all seven standard Tetris pieces (I, O, T, S, Z, J, L) are correctly implemented with their proper shapes, colors, and rotation behaviors. Each piece should follow the official rotation system (preferably SRS - Super Rotation System). Deduct 2 points if a piece is missing, 3 points if rotation system is inconsistent, and 5 points if collision detection during rotation fails. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the game progression and difficulty system implemented?",
-      "description": "Evaluate whether the game includes proper level progression, increasing speed as the player advances, and appropriate scoring mechanisms (points for line clears, with bonuses for multiple lines). Check for implementation of special scoring for techniques like T-spins or back-to-back Tetrises. Deduct 5 points if speed progression is missing, 3 points if the scoring system is overly simplified. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the next piece preview and piece holding functionality implemented?",
-      "description": "Check whether the game includes standard modern Tetris features like displaying the next piece(s) in queue and the ability to hold a piece for later use. Evaluate the implementation of the piece swapping mechanism and whether it follows standard rules (can't swap twice in a row). Deduct 5 points if next piece preview is missing, and 5 points if hold functionality is not implemented or has incorrect rules. 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, browser resize events, focus/blur events when switching tabs, etc.) and provide friendly error handling or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Ghost piece showing where the tetromino will land 2. Game statistics tracking and visualization 3. Special visual/audio effects for combos or Tetris clears). 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 game loop implementations) 2. Function modules unrelated to Tetris (e.g., unnecessary social sharing features) 3. Fancy effects that affect performance (e.g., excessive particle animations that slow down gameplay). 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), code organization, and maintainability. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the code lacks comments or documentation. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching for the game board and pieces 2) Proper layout spacing with clear separation between game area and UI elements 3) Professional font system for score display and game information. 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 control scheme and game responsiveness optimized?",
-      "description": "Judge whether the game controls are intuitive and responsive: 1) Input response delay ≤ 50ms 2) Support for both keyboard and touch controls (for mobile devices) 3) Customizable controls or standard Tetris controls (arrow keys, spacebar for hard drop). Deduct 5 points for sluggish controls, 3 points for missing standard Tetris control options (like hard/soft drop), and 5 points for lack of mobile device support. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Puzzle",
-  "difficulty": "hard"
-}

package/library/game_development-puzzle/web-based-sokoban-box-pushing-mini-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 1182,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the code you generate is executable for demonstration. Create a web-based Sokoban (box pushing) mini-game.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core Sokoban game mechanics fully implemented?",
-      "description": "Review whether the code accurately implements the core Sokoban mechanics: player movement in four directions, box pushing rules (can push one box at a time, cannot push multiple boxes, cannot push through walls), win condition detection (all boxes on target spots). Score 0 if game mechanics are absent, 5 if basic movement works but with rule errors, and 10 if all standard Sokoban rules are correctly implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is level design and progression system implemented?",
-      "description": "Examine whether the game includes multiple well-designed levels with increasing difficulty, a level selection mechanism, and progression tracking. Check if levels are stored in a maintainable format (JSON/array structures) that allows easy modification. Deduct 5 points if only one level exists, 3 points if difficulty progression is illogical, and 2 points if there's no way to select levels. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are game controls and input handling properly implemented?",
-      "description": "Evaluate if the game responds correctly to keyboard inputs (arrow keys/WASD), includes touch/click controls for mobile devices, and provides visual feedback on input. Controls should feel responsive (≤100ms delay) and intuitive. Deduct 5 points if only keyboard OR touch controls exist (not both), and 5 points if there are noticeable input delays. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the game state management and undo/restart functionality implemented?",
-      "description": "Check for implementation of game state management including move history tracking, undo functionality (allowing players to undo mistakes), level restart, and automatic save/restore of game progress. Deduct 5 points if undo functionality is missing, 3 points if game progress is not persisted between sessions, and 2 points if restart requires page refresh. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid moves, rapid input sequences, browser refresh, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Move counter and efficiency rating 2. Visual path planning assistance 3. Level editor functionality 4. Custom animations for successful level completion). 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 move detection systems) 2. Function modules unrelated to Sokoban gameplay (e.g., unnecessary mini-games) 3. Fancy effects that affect performance (e.g., excessive animations that slow down gameplay). 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), code organization, and maintainability. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 3 points if variable and function names are not descriptive. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the game visuals follow modern design principles: 1) Consistent and clear visual language for walls, boxes, targets, and player character 2) Proper contrast between game elements and background 3) Responsive layout that works on different screen sizes. Deduct 3 points for each inconsistent game element, 5 points for poor contrast making gameplay difficult, and 5 points for layouts that break on mobile or smaller screens. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the game's interactive elements perform smoothly: 1) Character movement animations are fluid and immediate 2) Box pushing provides visual/audio feedback 3) Level completion and transitions are clearly indicated. Deduct 5 points for jerky or missing movement animations, 3 points for lack of feedback when pushing boxes or hitting walls, and 5 points if level completion is not clearly communicated to the player. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Puzzle",
-  "difficulty": "medium"
-}

package/library/game_development-puzzle/web-based-tetris-game-with-preview-panel.json

@@ -1,68 +0,0 @@
-{
-  "index": 1732,
-  "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 web-based Tetris game with arrow key controls and an information panel that displays block previews.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core Tetris game mechanics fully implemented?",
-      "description": "Review whether the code accurately implements the standard Tetris mechanics including block rotation (all 7 tetromino types), movement, collision detection, line clearing, and scoring. Score 0 if the core game logic is missing, 5 if only basic movements are implemented, and 10 if all standard Tetris rules (including wall kicks and hard/soft drops) are fully included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the information panel with block preview functionality implemented?",
-      "description": "Check whether the code includes an information panel that clearly displays the next block preview, current score, level, and lines cleared. Deduct 3 points if the preview is missing, 2 points if the score tracking is missing, and 2 points if level progression mechanics aren't implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are the arrow key controls properly implemented?",
-      "description": "Evaluate whether the keyboard event handling is properly implemented for arrow key controls (left, right, down for movement, up for rotation), along with other standard Tetris controls like space for hard drop. Check for responsiveness and whether key repeat rates are appropriate. Deduct 5 points if controls have noticeable lag, 3 points if key repeat handling is missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the game loop and animation properly managed?",
-      "description": "Check whether the code uses requestAnimationFrame or similar techniques for smooth gameplay, manages the game loop efficiently, and implements proper speed adjustment based on level progression. Deduct 5 points if frame timing is inconsistent, 3 points if level-based speed adjustment 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 rapid key presses, browser resizing, focus lost, 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. Ghost piece showing where the tetromino will land 2. Hold piece functionality 3. Interactive sound effects or music). 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 systems coexisting) 2. Function modules unrelated to Tetris (e.g., a built-in news feed) 3. Fancy effects that affect performance (e.g., excessive particle animations). 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), code organization, and maintainability. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no clear separation of concerns. 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) Classic Tetris color palette or harmonious color scheme 2) Proper layout spacing between game board and information panel 3) Professional font system with clear readability (score displays, level indicators). 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) Block movement responds within 100ms of key press 2) Line clearing animations are visually satisfying 3) Clear visual feedback for scoring and level changes. Deduct 5 points for each operation without feedback, 3 points for jerky animations during gameplay, and 5 points for poor visual feedback on important game events. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Puzzle",
-  "difficulty": "medium"
-}

package/library/game_development-puzzle/web-based-tetris-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 1725,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure that any code you generate is executable for demonstration purposes. Please help me write a web-based Tetris game.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core Tetris game mechanism fully implemented?",
-      "description": "Review whether the code accurately implements standard Tetris mechanics including piece rotation, movement, collision detection, and line clearing logic. Score 0 if the core interaction logic is not implemented, 5 if only basic piece movement is present, and 10 if all standard Tetris rules are fully included (including wall kicks, SRS rotation system, and proper piece spawning).",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are all seven Tetromino pieces correctly implemented?",
-      "description": "Check if all seven standard Tetromino pieces (I, J, L, O, S, T, Z) are properly implemented with correct shapes, colors, and rotation patterns. The game should use the standard piece spawning order and randomization system. Deduct 2 points for each missing piece or incorrect rotation behavior. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the scoring and level progression system properly implemented?",
-      "description": "Evaluate whether the scoring system follows standard Tetris rules (points for line clears with bonuses for multiple lines cleared simultaneously), and whether difficulty increases appropriately with level progression (faster falling speed). Deduct 3 points if scoring logic is incorrect, 3 points if level progression is absent, and 4 points if speed adjustment is not implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the game include preview functionality and proper game state management?",
-      "description": "Check whether the game includes a next piece preview, ability to pause/resume, game over detection, and game restart functionality. Deduct 2 points for each missing feature. Also verify that the game state is properly managed throughout the gameplay cycle. 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, browser resize, focus loss, 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. Ghost piece showing where the current piece will land 2. Hold piece functionality 3. Animated line clears 4. Sound effects or music). Add 2.5 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple game loop mechanisms coexisting) 2. Function modules unrelated to Tetris (e.g., unnecessary animations) 3. Fancy effects that affect performance (e.g., excessive particle effects). 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/controller layers), code reusability, and build process. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the code is monolithic with no separation of concerns. 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 responsive?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Input response delay ≤ 100ms 2) Smooth piece movement and rotation 3) Clear visual feedback for actions. Deduct 5 points for sluggish controls, 3 points for jerky animations, and 5 points for unclear or missing visual feedback. Check if the game runs at a consistent frame rate (≥ 30fps) even during intensive operations like clearing multiple lines. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Puzzle",
-  "difficulty": "easy"
-}

package/library/game_development-puzzle/web-based-tetris-mini-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 1714,
-  "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. Help me create a web-based Tetris mini-game.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core Tetris game mechanics fully implemented?",
-      "description": "Review whether the code accurately implements the standard Tetris mechanics including tetromino generation, rotation, movement, collision detection, line clearing, and scoring system. Score 0 if the core gameplay is not implemented, 5 if only basic movement is implemented, and 10 if all standard Tetris rules (wall kicks, hard/soft drop, ghost piece) are fully included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Does the game feature proper tetromino shapes and colors?",
-      "description": "Check if all 7 standard tetromino shapes (I, J, L, O, S, T, Z) are correctly implemented with proper colors following official Tetris guidelines. Verify that the rotation points are accurate and that the tetrominos display correctly on the grid. Deduct 2 points for each incorrect shape implementation and 3 points if the color scheme is inconsistent or clashes visually.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the game loop and state management properly implemented?",
-      "description": "Evaluate the implementation of the game loop, including speed progression as score increases, proper pausing/resuming functionality, game over detection, and state transitions. Check for consistent frame rate and smooth animations. Deduct 5 points if speed progression is missing, 3 points if pause functionality is broken, and 5 points if game over detection fails.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the game include a proper scoring system and level progression?",
-      "description": "Verify that the scoring system follows standard Tetris rules (points for line clears with bonuses for multiple lines), includes level progression that increases difficulty, and properly tracks and displays high scores. Deduct 3 points if scoring is inaccurate, 3 points if level progression is missing, and 4 points if there's no high score tracking.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as rapid key presses, browser resizing, focus loss, 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. Hold piece functionality 2. Next piece preview 3. Animated line clears 4. Sound effects/music 5. Custom themes). Add 2 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 handling systems) 2. Function modules unrelated to Tetris (e.g., unnecessary social media integration) 3. Fancy effects that affect performance (e.g., excessive particle effects). 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), code organization, and maintenance patterns. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no clear separation between game logic 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 design principles: 1) Harmonious color matching for the game elements and UI 2) Proper layout spacing and game board proportions 3) Professional font system for score/level display and menus (clear hierarchy, readable at all sizes). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for poor information hierarchy. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the control scheme and responsiveness appropriate?",
-      "description": "Judge whether the game controls are intuitive and responsive: 1) Input delay ≤ 100ms 2) Support for both keyboard and touch controls on mobile 3) Clear visual feedback for actions. Deduct 5 points for sluggish controls, 3 points for missing key bindings (e.g., no hard drop), and 5 points for lack of mobile support if applicable. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Puzzle",
-  "difficulty": "hard"
-}

package/library/game_development-puzzle/web-based-windows-minesweeper-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 1822,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure the code you provide is executable and ready for demonstration. Write code for a web-based Minesweeper game that resembles the style of Windows Minesweeper.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core Minesweeper game logic fully implemented?",
-      "description": "Check if the code correctly implements the essential Minesweeper mechanics: random mine placement, adjacent mine counting, cell revealing logic, and win/loss conditions. Score 0 if core game logic is missing, 5 points if basic functionality works but has flaws (e.g., incorrect adjacent mine counting), 10 points if all standard Minesweeper rules are properly implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Does the game match the Windows Minesweeper visual style?",
-      "description": "Evaluate how closely the implementation resembles the classic Windows Minesweeper aesthetic, including the iconic beveled button appearance, number coloring (1=blue, 2=green, etc.), mine and flag icons, and the classic smiley face status button. Deduct 2 points for each major visual element that doesn't match the Windows style. Award 10 points for a near-perfect match.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are all standard Minesweeper interactions implemented?",
-      "description": "Check for left-click to reveal cells, right-click to flag/mark cells, and chord clicking (pressing both buttons on a numbered cell to reveal adjacent cells). Also verify the first-click safety mechanism (first click should never be a mine). Deduct 3 points for each missing interaction. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the game customizable with different difficulty levels?",
-      "description": "Verify if the game offers standard difficulty options (Beginner: 9×9 grid with 10 mines, Intermediate: 16×16 grid with 40 mines, Expert: 30×16 grid with 99 mines) or a custom mode allowing players to set board dimensions and mine count. Deduct 5 points if only one difficulty is available, 3 points if some standard options are missing. Award full 10 points for comprehensive difficulty options.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code handles edge cases such as rapid clicking, invalid inputs, browser resizing, and prevents game state corruption. Code with strong robustness should effectively handle these scenarios and prevent crashes. Give 10 points if highly robust, 5 points if average, and 0 points if edge cases cause the game to break.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check for creative enhancements that improve upon the classic game (e.g., 1. Animation when revealing multiple cells 2. Game statistics tracking 3. Adaptive mobile/touch support 4. Dark/light theme options 5. Save game functionality). Add 2 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check for: 1. Unnecessary game mechanics not in original Minesweeper 2. Overly complex UI elements that distract from gameplay 3. Performance-heavy features (e.g., excessive animations) that impact responsiveness. Deduct 3 points for each redundancy found, and directly deduct 10 points if redundant code interferes with core gameplay.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review code architecture (separation of game logic/UI/event handling), maintainability, and performance optimization. Deduct 3 points if global variables are overused; deduct 3 points if there's significant code duplication; deduct 4 points if the application has noticeable performance issues with larger board sizes. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the UI follows consistent design principles: 1) Clean grid layout with appropriate cell sizing 2) Clear visual distinction between revealed/unrevealed cells 3) Proper spacing and alignment of all elements. Deduct 3 points for each inconsistent visual element, 5 points for poor readability of numbers or icons, and 5 points for improper scaling on different screen sizes. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and responsive?",
-      "description": "Judge whether the game provides appropriate feedback: 1) Immediate visual response to clicks (≤ 100ms) 2) Smooth transitions when revealing cells 3) Clear indicators for game state (playing/won/lost). Deduct 3 points for each click without proper feedback, 5 points for noticeable lag when revealing multiple cells, and 3 points for unclear game state indicators. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Puzzle",
-  "difficulty": "easy"
-}