@getollie/cli 0.0.1

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

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

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

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

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

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

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

@@ -0,0 +1,68 @@
+{
+  "index": 1397,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Ensure that the code you generate can be executed and displayed. Please help me write code for a Tetris game that can be played on a web browser.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core Tetris game mechanics properly implemented?",
+      "description": "Review whether the code accurately implements standard Tetris mechanics including piece rotation, movement, collision detection, and line clearing. Score 0 if core mechanics are missing, 5 if basic movement and collision are implemented but with flaws, and 10 if all standard Tetris rules (including wall kicks, SRS rotation system, and proper piece spawning) are correctly implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the game board rendering and piece visualization complete?",
+      "description": "Evaluate whether the game board is properly rendered with a clear grid system, displaying current and next pieces correctly. Check if piece colors follow the standard Tetris color scheme and if the ghost piece feature (showing where the piece will land) is implemented. Deduct 3 points if the grid system is unclear, 3 points if next piece preview is missing, and 5 points if ghost piece feature is absent. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are all standard Tetris game features implemented?",
+      "description": "Verify implementation of scoring system, level progression with increasing speed, next piece preview, held piece functionality, and game over detection. Deduct 2 points for each missing feature. Check if the scoring follows standard Tetris rules (single line: 100, double: 300, triple: 500, tetris: 800 points). The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the control system responsive and user-friendly?",
+      "description": "Check if keyboard controls are properly implemented (arrow keys/WASD for movement, space for hard drop, shift/C for hold), and if controls are customizable or if touch controls are available for mobile devices. Evaluate input responsiveness (key repeat rates for continuous movement). Deduct 5 points if basic controls are missing, 3 points if there's noticeable input lag, and 5 points if mobile compatibility 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, focus loss during gameplay, 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. Battle mode or multiplayer options 2. Customizable themes or tetromino skins 3. Replay system or high score tracking). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple collision detection algorithms) 2. Function modules unrelated to Tetris (e.g., unnecessary animations or effects) 3. Fancy effects that affect performance (e.g., excessive particle effects that cause frame rate drops). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating game logic/view/input handling layers), code organization, 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 the game loop is inefficient (causing frame skips or performance issues). 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 besides tetromino colors) 2) Proper layout spacing (clear separation between game board, score/level display, and next/hold piece areas) 3) Professional font system (readable score and level indicators, consistent style). Deduct 3 points for each cluttered UI element, 5 points for illegible text or confusing color schemes, and 5 points for poor organization of game elements. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the game animations and interactions conform to human perception characteristics: 1) Piece movement and rotation feels responsive (≤ 100ms) 2) Line clearing animations are satisfying but not too lengthy (300-500ms) 3) Game over and level up transitions are clear. Deduct 5 points for stuttering animations, 3 points for inconsistent frame rates during intensive actions (like tetris clears), and 5 points for jarring transitions between game states. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Puzzle",
+  "difficulty": "hard"
+}

package/library/game_development-puzzle/web-chinese-idiom-solitaire-game.json

@@ -0,0 +1,68 @@
+{
+  "index": 1633,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be careful to ensure that the code you generate is executable. Create a web-based mini-game for the Chinese idiom solitaire game.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core idiom matching logic fully implemented?",
+      "description": "Review whether the code accurately implements the Chinese idiom solitaire matching rules (matching the last character of one idiom with the first character of the next). Check for proper validation of user inputs against a comprehensive idiom database. Score 0 if the core matching logic is missing, 5 if basic matching works but with limitations, and 10 if all rules including special cases (rare characters, homonyms) are handled properly.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the idiom database comprehensive and well-structured?",
+      "description": "Evaluate whether the code includes or connects to a substantial Chinese idiom database with at least 1000 common idioms. Check if the database structure efficiently enables first/last character lookups and prevents repetition in gameplay. Deduct 3 points if fewer than 500 idioms are included, 4 points if character-based indexing is inefficient, and 5 points if the database lacks meaning explanations for educational value. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the game progression and scoring system properly implemented?",
+      "description": "Check if the game has clear progression mechanics (increasing difficulty, time limits, or chain bonuses), proper scoring logic (points based on character complexity, idiom rarity, or response time), and game ending conditions. Deduct 5 points for missing progression, 3 points for simplistic scoring, and 3 points for poorly defined win/lose states. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are accessibility and learning features incorporated?",
+      "description": "Assess whether the game includes educational elements (idiom meanings, usage examples, historical context) and accessibility features (pinyin display, difficulty settings, hint systems). Deduct 3 points for each missing educational aspect and 4 points if accessibility considerations are 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 invalid inputs, server failures, edge cases like no more matching idioms available, 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. Animated character calligraphy 2. Traditional Chinese background music 3. Challenge modes like limited time or category-specific idioms). 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 idiom validity) 2. Function modules unrelated to the idiom game (e.g., unnecessary mini-games within the game) 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/data layers), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows traditional Chinese aesthetic principles while maintaining modern usability: 1) Traditional color palette appropriate for Chinese culture 2) Proper layout with adequate white space 3) Suitable typography using fonts that properly display Chinese characters. Deduct 3 points for cluttered visual elements, 5 points for culturally inappropriate visuals, and 5 points for poor readability of Chinese characters. 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) Immediate feedback when submitting idioms (≤ 100ms) 2) Smooth transitions when showing new idioms or game states 3) Clear visual indicators for valid/invalid submissions. Deduct 5 points for each operation without feedback, 3 points for laggy animations during gameplay, and 5 points for confusing user interface that doesn't clearly show game state. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Puzzle",
+  "difficulty": "hard"
+}

package/library/game_development-puzzle/web-match-3-game-with-translations.json

@@ -0,0 +1,68 @@
+{
+  "index": 1813,
+  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Make sure that the generated code is executable for demonstration. Please help me create a web-based match-3 game that includes input with English and Chinese translations.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core match-3 game logic fully implemented?",
+      "description": "Review whether the code accurately implements the match-3 mechanics including tile swapping, pattern detection (horizontal and vertical matches of 3+ same tiles), and cascading effects when matches are removed. Score 0 if the core matching logic is missing, 5 if only basic matching works, and 10 if advanced mechanics like special tile creation after 4+ matches and cascading matches are implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are the game board generation and randomization properly implemented?",
+      "description": "Check whether the code implements a balanced board generation algorithm that ensures the initial board has no pre-existing matches and guarantees solvable states throughout gameplay. Deduct 5 points if the board generation doesn't prevent initial matches, and 5 points if the algorithm doesn't ensure solvable states after matches. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the bilingual (English-Chinese) translation system fully integrated?",
+      "description": "Evaluate whether the code implements a complete language switching system between English and Chinese that covers all UI elements, game instructions, and in-game messages. Check if proper localization techniques (like language resource files or objects) are used rather than hardcoded strings. Deduct 5 points if only partial content is translated, and 3 points if the translation implementation is inefficient. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the game scoring and progression system properly designed?",
+      "description": "Review whether the game includes a well-designed scoring system (with multipliers for combos/cascades), level progression with increasing difficulty, and persistent state management. Deduct 3 points if combo scoring is missing, 4 points if difficulty progression isn't implemented, and 3 points if there's no game state 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 invalid moves, edge cases in pattern detection, rapid user inputs, browser compatibility issues) and provide friendly error handling. Code with strong robustness should prevent board deadlocks and handle window resizing. Give 10 points for comprehensive exception handling, 5 points for average robustness, and 0 points if no exceptions are handled.",
+      "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-up tiles with unique animations 2. Themed visual/audio effects based on matched item types 3. Daily challenges or puzzle modes). 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 event handlers or duplicate game state tracking 2. Excessive animations or effects that don't contribute to core gameplay 3. Unnecessary complexity in the language switching system. 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 (separation of game logic from UI rendering, language handling in a separate module), naming conventions consistency, and code reusability. Deduct 5 points for global variable abuse; deduct 3 points for inconsistent coding style between game modules and language handling; deduct 2 points if the code lacks comments for complex algorithms. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the match-3 grid has clear visual distinction between tile types, proper spacing, and aesthetically pleasing animations. Check if the bilingual UI accommodates both language character sets without layout breaking. Deduct 3 points for poor tile visibility, 4 points for cramped or inconsistent layout between languages, and 3 points for jarring color schemes. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the game has responsive controls (≤100ms feedback for tile selections), smooth animations for tile swapping/matching/falling (300-500ms duration), and clear visual/audio feedback for matches and language switching. Deduct 4 points for laggy animations, 3 points for missing feedback on successful/unsuccessful moves, and 3 points for abrupt or jarring language transitions. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Puzzle",
+  "difficulty": "hard"
+}