@getollie/cli 0.0.1

package/library/game_development-puzzle/chinese-idiom-guessing-game-mobile.json

@@ -0,0 +1,68 @@
+{
+  "index": 1569,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code that can be displayed. Write code for a four-character Chinese idiom guessing game that can run on a local mobile phone.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core game logic for the Chinese idiom guessing mechanism fully implemented?",
+      "description": "Review whether the code implements the complete idiom guessing logic, including idiom database, correct character validation, and scoring system. Check if there's a function to match user input with the target idiom, character by character. Score 0 if there's no core logic, 5 if basic matching exists but without proper validation, and 10 if the complete guessing system with visual feedback for correct/incorrect characters is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Does the game include a comprehensive Chinese idiom database?",
+      "description": "Evaluate the quality and quantity of the idiom database. Check whether the idioms are correctly formatted with their meanings and possibly difficulty levels. A good implementation should have at least 100 idioms with proper pinyin and explanations. Deduct 5 points if fewer than 50 idioms are included, and 3 points if the idioms lack explanations. Give 10 points for a rich database with categorized idioms or difficulty levels.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is there a proper mobile-responsive UI designed specifically for touch screens?",
+      "description": "Check if the UI is designed with mobile constraints in mind - proper touch targets (at least 44×44px), responsive layout that works on different screen sizes, and appropriate keyboard implementation for character input. Verify if the game uses viewport meta tags and CSS media queries. Deduct 5 points for desktop-oriented design, 3 points for small touch targets, and 5 points for non-responsive layouts. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the game implement local storage for saving progress and game state?",
+      "description": "Review whether the code implements localStorage or IndexedDB to save game progress, high scores, and game state between sessions. Verify if the game can be resumed after closing the browser or app. Deduct 5 points if there's no persistence mechanism, 3 points if only basic settings are saved without game state. Full 10 points require complete state management including game progress, statistics, and settings.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid input, network issues when loading resources, browser compatibility issues, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Pronunciation guidance for idioms 2. Visual hints or animations for challenging idioms 3. Daily challenges with new idioms 4. Integration with Chinese language learning). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple scoring systems) 2. Function modules unrelated to idiom guessing (e.g., an unrelated mini-game) 3. Fancy effects that affect performance (e.g., unnecessary animations that slow down the app). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating game logic/view/data layers), code organization, and performance optimization for mobile devices. Deduct 5 points if global state pollution is found or if the code lacks organization; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there are no performance optimizations for mobile devices. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows mobile design principles: 1) Harmonious color matching that reflects Chinese cultural elements 2) Proper layout spacing (element spacing follows touch-friendly principles) 3) Appropriate font system (legible Chinese characters, proper contrast). Deduct 3 points for each crowded visual element, 5 points for illegible text, and 5 points for inconsistent design elements. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and optimized for mobile devices?",
+      "description": "Judge whether the touch interactions conform to mobile user expectations: 1) Touch response delay ≤ 100ms 2) Appropriate keyboard handling for Chinese character input 3) Gesture support if applicable. Deduct 5 points for sluggish response, 3 points for keyboard issues during character input, and 5 points for interaction patterns that don't follow mobile conventions. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Puzzle",
+  "difficulty": "easy"
+}

package/library/game_development-puzzle/collaborative-puzzle-solving-game.json

@@ -0,0 +1,68 @@
+{
+  "index": 37,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. You're a code expert. Please use your professional knowledge to generate accurate, professional responses. Ensure that the code you generate is executable.\n\nPlease use HTML and JavaScript to implement a collaborative puzzle-solving game.\n\n**Task**: Design a collaborative puzzle-solving mode where players need to cooperate with AI or another player to solve puzzles.\n\n**Tip**: You can set up puzzles that require multiple people to complete, such as pressing two switches simultaneously, passing props to each other, etc.\n\nPlease include comments in your code to help other developers understand your implementation process.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the puzzle-solving core game system fully implemented?",
+      "description": "Review whether the code accurately implements the puzzle game mechanics through HTML/JavaScript, including puzzle creation, manipulation, and completion detection logic. Evaluate the structure of the puzzle system and whether it allows for multiple players to interact with puzzle elements simultaneously. Score 0 if core puzzle mechanics are missing, 5 points if basic puzzle interaction is implemented but lacks collaborative features, and 10 points if a comprehensive puzzle system supporting collaborative actions is fully implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the collaborative interaction between players properly implemented?",
+      "description": "Check if the game includes mechanisms that genuinely require collaboration (e.g., simultaneous button presses, complementary abilities, or shared resource management). Evaluate the synchronization of player actions and their effect on the puzzle state. Award 10 points for well-designed collaborative mechanics with clear dependency between players; 5 points if collaboration exists but feels superficial; 0 points if players can effectively solve puzzles independently without collaboration.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the AI player implementation adequate (if applicable)?",
+      "description": "Assess the quality of the AI implementation for single-player mode. The AI should demonstrate intelligent behavior, respond to the player's actions, and provide meaningful assistance in solving puzzles. Examine decision-making algorithms, pathfinding capabilities, and ability to work cooperatively. Award 10 points for sophisticated AI that feels like a real partner; 5 points for functional but basic AI; 0 points if AI is missing or completely ineffective at puzzle solving.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the multiplayer synchronization mechanism properly designed?",
+      "description": "Evaluate whether the code includes proper state synchronization for multiplayer gameplay. Check for client-server communication or peer-to-peer mechanisms that maintain consistent game state across clients. Examine handling of latency, conflict resolution, and state reconciliation. Deduct 5 points if the synchronization mechanism lacks error handling or causes desynchronization issues. Deduct 3 points if there's no handling for network latency. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as out-of-bounds input, network interruption, user operation errors, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Dynamic puzzle difficulty adjustment based on player performance 2. Real-time visual feedback for collaborative actions 3. Voice or text chat integration for coordination). 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 handle the same puzzle interaction) 2. Function modules unrelated to puzzle solving (e.g., unnecessary game features that distract from the core experience) 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/network layers), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast sliding, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Puzzle",
+  "difficulty": "medium"
+}

package/library/game_development-puzzle/color-elimination-game-8x8-grid.json

@@ -0,0 +1,68 @@
+{
+  "index": 608,
+  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Try to ensure the generated code is executable for demonstration. ======== ROLE ========\nYou are an experienced code expert. I will provide you with a software development requirement description, and you are required to generate project code based on these requirements. Strictly follow the rules to help users generate complete project code that is fully commented in simple, easy-to-understand language, without outputting anything else.\n\n======== OUTPUT RULES ========\n1. Always generate complete, runnable project code, ensuring the project is fully executable\n2. Ensure all code files you output are complete, without omitting any code\n3. Carefully review and check all code before final output, evaluating its executability. If the code cannot be executed or contains errors, regenerate it\n4. If the requirements involve external API access or user data (images, videos, audio, etc.), please provide mock data\n\n======== PROJECT REQUIREMENTS ========\nCreate a color elimination game with an 8x8 grid of colored blocks as the interface. When three or more blocks of the same color form a straight line, they can be eliminated. After elimination, blocks from above will fall to fill the gaps. The game ends when no more blocks can be eliminated.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the 8x8 grid interface fully implemented?",
+      "description": "Check if the code correctly implements an 8x8 grid of colored blocks using HTML/CSS/JavaScript. Verify that the grid layout is properly structured with appropriate positioning and spacing. Each block should have a clear visual representation with distinct colors.Score 0 if the grid is not implemented, 5 if the grid is implemented but has layout issues (inconsistent sizing, alignment problems), 10 if the grid is properly implemented with appropriate styling and responsive design.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the core elimination logic correctly implemented?",
+      "description": "Assess if the code accurately implements the matching and elimination mechanism for three or more same-colored blocks in straight lines (horizontal or vertical). Check if the algorithm correctly identifies all valid matches on the board after each move and handles multiple eliminations in a single turn.Score 0 if elimination logic is missing, 5 if basic elimination works but with bugs (e.g., not detecting all valid matches, incorrect pattern detection), 10 if elimination logic works flawlessly including handling edge cases.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the gravity/falling mechanism properly implemented?",
+      "description": "Evaluate if blocks correctly fall to fill empty spaces after eliminations. Check if the animation is smooth and the logic ensures blocks fall directly downward to fill the lowest available empty space. Verify that the grid state is correctly updated after falling.Score 0 if falling mechanism is not implemented, 5 if blocks fall but with issues (stuck blocks, incorrect positioning), 10 if the falling mechanism works seamlessly with proper animations and state management.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the game end condition properly implemented?",
+      "description": "Check if the code correctly detects when no more possible eliminations are available and handles the game end appropriately. Verify that the game state is properly managed and the player is notified of the game end with appropriate UI feedback.Score 0 if end condition detection is missing, 5 if basic end detection exists but has flaws (false positives/negatives), 10 if the end condition is properly implemented with appropriate user feedback.",
+      "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 handling or recovery mechanisms. Check if the game state remains consistent during unexpected interactions.Score 0 if no exception handling exists, 5 if basic error handling is implemented but edge cases are not covered, 10 if comprehensive error handling is implemented with graceful recovery mechanisms.",
+      "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 for larger matches 2. Score multipliers or combos 3. Sound effects and visual feedback 4. Difficulty levels or time challenges).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 for matches) 2. Function modules unrelated to the elimination game (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/controller layers), code organization, naming conventions, and build process. Check for proper event handling and state management 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 separation between game logic and UI. 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 blocks and background 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Clear visual feedback for selections and eliminations 4) Readable score display and game information.Deduct 3 points for each crowded visual element, 5 points for clashing colors that affect gameplay, and 5 points for confusing visual feedback during matches. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the game interactions conform to human perception characteristics: 1) Block selection feedback ≤ 100ms 2) Elimination and falling animations between 300-500ms 3) Clear visual guidance for possible matches. Check if the game feels responsive and satisfying to play.Deduct 5 points for each interaction without feedback, 3 points for jerky or inconsistent animations, and 5 points for confusing or delayed response to user input. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Puzzle",
+  "difficulty": "easy"
+}

package/library/game_development-puzzle/cub-n-pup-drag-rotate-puzzle-game.json

@@ -0,0 +1,68 @@
+{
+  "index": 1,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Gameplay\n- **Drag and Rotate**: Manipulate blocks to form paths that guide Cub to the destination.\n- **Solve Puzzles**: Each level is designed with specific challenges and obstacles.\n\n# Game Features\n- **Intuitive Controls**: Control the game through simple drag and click operations.\n- **Creative Design**: Each level has a unique layout and solution.\n\n# Game Tips\n- **Strategic Planning**: Plan your moves and rotations in advance to optimize the path.\n- **Observation and Adaptation**: Pay attention to the characteristics and challenges of new levels, and adjust your strategy accordingly.\n\n# Summary\n\"Cub n Pup - Puzzle Game Demo\" is a grid-based, connection-element strategy puzzle game. Players need to drag and rotate blocks to ensure the puppy (Cub) can reach the Star's position. This game fully utilizes creative thinking and strategic planning, providing a challenging and entertaining puzzle-solving experience.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core puzzle gameplay mechanic fully implemented?",
+      "description": "Review whether the code accurately implements the block manipulation system through HTML/JavaScript, including drag functionality, rotation mechanics, and path validation for the puppy's movement. Score 0 if the core interaction logic is not implemented, 5 if only basic dragging is implemented without rotation, and 10 if both dragging and rotation mechanics work seamlessly with proper collision detection.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the level navigation and progression system implemented?",
+      "description": "Check whether the game includes a proper level selection interface, progress tracking, level completion validation, and the ability to advance to subsequent levels. Deduct 5 points if there's no level progression system, 3 points if progression exists but without state persistence between sessions. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are the path-finding and goal validation mechanics properly implemented?",
+      "description": "Evaluate whether the code correctly implements path validation to check if Cub can reach the Star destination, including handling of obstacles and ensuring continuous path connections. Deduct 5 points if path validation is simplistic (only checking start/end points), and 3 points if the validation doesn't account for all possible edge cases. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the block manipulation system intuitive and responsive?",
+      "description": "Assess whether the block dragging and rotation controls feel natural and responsive, with proper visual feedback during interaction. Check for snap-to-grid functionality, rotation pivot points, and ghost previews of potential placements. Deduct 5 points if dragging feels laggy, and 3 points if rotation lacks clear visual guidance. 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 clicking, dragging outside boundaries, 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. Visual path previews when hovering blocks 2. Undo/redo functionality 3. Hint system for stuck players). 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 dragging systems coexisting) 2. Function modules unrelated to the puzzle game (e.g., a built-in social media feed) 3. Fancy effects that affect performance (e.g., unnecessary particle systems). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating game logic/view/input handling layers), 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 game design standards?",
+      "description": "Evaluate whether the overall design follows modern game design principles: 1) Harmonious color matching with consistent theme 2) Proper layout spacing with clear grid visualization 3) Professional UI elements with clear affordances. Deduct 3 points for each inconsistent visual element, 5 points for clashing colors, and 5 points for unclear or confusing game state representation. 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 manipulation response delay ≤ 100ms 2) Path animation and level transitions between 300-500ms 3) Clear visual and audio feedback for successful/unsuccessful moves. Deduct 5 points for each operation without feedback, 3 points for jerky animations during block movement, and 5 points for confusing or missing feedback when reaching the goal. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Puzzle",
+  "difficulty": "hard"
+}

package/library/game_development-puzzle/english-card-flipping-memory-game.json

@@ -0,0 +1,68 @@
+{
+  "index": 1736,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be careful to ensure the code you generate is executable. As a programmer, please help me create a code for an English card-flipping memory game to learn weekly English vocabulary.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core memory game mechanism properly implemented?",
+      "description": "Review whether the code accurately implements the card-flipping mechanism with state management for each card (flipped/unflipped), pair matching logic, and score tracking. Score 0 if the core game logic is missing, 5 if only basic flipping is implemented without matching, and 10 if the complete memory game logic with pair validation is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the English vocabulary learning component effectively integrated?",
+      "description": "Check whether the code includes a system for presenting English vocabulary words with their meanings/definitions, proper word-pair associations, and methods to track vocabulary learning progress. Deduct 5 points if vocabulary is static without a learning component, 3 points if words are presented without meanings or context. The full score is 10 points for a comprehensive vocabulary learning system with spaced repetition concepts.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is there a proper weekly vocabulary management system?",
+      "description": "Evaluate whether the code organizes vocabulary into weekly sets, includes functionality to progress from one week to another, and maintains learning history. Deduct 5 points if there's no clear weekly structure, 3 points if the structure exists but without progress tracking. Give 10 points for a complete weekly vocabulary management system with progress visualization.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the game include appropriate learning reinforcement features?",
+      "description": "Assess whether the code implements features that reinforce vocabulary learning (such as pronunciation audio, example sentences, review mechanisms for previously learned words, difficulty progression). Deduct 3 points for each missing key learning reinforcement component. 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, missing vocabulary data, browser compatibility issues, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the learning experience (e.g., 1. Spaced repetition algorithm 2. Vocabulary pronunciation with text-to-speech 3. Progress statistics visualization 4. Personalized difficulty adjustment). 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 scoring systems) 2. Function modules unrelated to vocabulary learning (e.g., unnecessary mini-games) 3. Fancy effects that affect performance (e.g., excessive 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/data layers), code organization, and maintainability. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no clear file/component organization. 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 suitable for learning (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 16px for good readability, clear distinction between vocabulary and definitions). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for hard-to-read text. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and pedagogically sound?",
+      "description": "Judge whether the card-flipping and game interactions conform to educational design principles: 1) Immediate feedback on card matching attempts 2) Clear visual cues for matched/unmatched pairs 3) Appropriate animations that don't distract from learning 4) User-friendly controls for all age groups. Deduct 5 points for delayed feedback, 3 points for confusing visual cues, and 5 points for overly complex interaction patterns that detract from the learning focus. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Puzzle",
+  "difficulty": "medium"
+}

package/library/game_development-puzzle/english-word-elimination-game-for-children.json

@@ -0,0 +1,68 @@
+{
+  "index": 1680,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate, professional responses. Make sure the generated code is executable and demonstrable. Please write a code for an English word elimination game. I need to allow children to learn English words easily and happily through this game, and to discover patterns and fun in words during the gameplay.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core word elimination game mechanic fully implemented?",
+      "description": "Review whether the code implements a complete word elimination system including word selection, scoring, user input validation, and checking for correct word patterns. Score 0 if the core game logic is missing, 5 if only basic word matching is implemented, and 10 if it includes advanced features like difficulty levels and word pattern recognition.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Does the game incorporate educational elements for English learning?",
+      "description": "Evaluate whether the game effectively teaches English vocabulary through meaningful interactions. Check for age-appropriate word selection, pronunciation features, visual word-meaning associations, and progressive learning paths. Deduct 5 points if words are random without educational purpose, 3 points if difficulty progression is missing. Full score requires both engagement and pedagogical value.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the game designed to discover patterns in English words?",
+      "description": "Check if the game helps children recognize patterns in English words (like prefixes, suffixes, word families, etc.). Assess whether the game explicitly highlights these patterns or guides students to discover them. Deduct 5 points if pattern recognition is absent, and 3 points if patterns exist but aren't emphasized in gameplay. Full score requires interactive pattern discovery mechanisms.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the game engaging and enjoyable for children?",
+      "description": "Evaluate whether the game incorporates child-friendly elements like achievements, rewards, encouraging feedback, and age-appropriate challenges. Score 10 points for a fully engaging experience with visual/audio rewards and positive feedback mechanisms, 5 points for basic engagement elements, and 0 points if the game lacks child-appropriate motivation systems.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as incorrect input, empty submissions, rapid clicking, 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 characters that react to correct/incorrect answers 2. Word-to-picture associations 3. Voice recognition for pronunciation practice). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple scoring systems) 2. Function modules unrelated to word learning (e.g., unrelated mini-games) 3. Fancy effects that affect performance (e.g., excessive animations that slow loading). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating game logic/view/data layers), code structure, 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 are no comments or documentation. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet child-friendly design standards?",
+      "description": "Evaluate whether the design follows child-friendly design principles: 1) Bright, contrasting but harmonious colors 2) Large, readable text (minimum 16px for body text) 3) Intuitive iconography with clear visual cues. Deduct 3 points for each confusing UI element, 5 points for text that's too small or difficult to read, and 5 points for cluttered or overwhelming visuals. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and appropriate for children?",
+      "description": "Judge whether the interactions are suitable for children's motor skills and attention spans: 1) Large clickable areas (minimum 44x44px) 2) Immediate visual/audio feedback for actions 3) Forgiving input mechanisms that account for developing motor skills. Deduct 5 points for small, difficult-to-click elements, 3 points for delayed or missing feedback, and 5 points for complex interactions requiring precise movements. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Puzzle",
+  "difficulty": "easy"
+}

package/library/game_development-puzzle/fifth-grade-science-textbook-outline-game.json

@@ -0,0 +1,68 @@
+{
+  "index": 255,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Fifth Grade Science Textbook Knowledge Outline - Second Semester\n\n## Unit 1: Heart and Brain\n### Lesson 1: Our Brain\n1. The brain is the \"command center\" of the human body, directing human actions, generating thoughts and emotions, and carrying out cognition and decision-making. The brain controls human behavior and emotions.\n2. The brain is divided into three parts: the cerebrum, cerebellum, and brainstem. The cerebrum is divided into left and right hemispheres. Different areas have different functions.\n3. Our brain has sensory centers, auditory centers, motor centers, and visual centers.\n4. We can think, make judgments, and experience emotions like happiness, anger, sadness, and joy. This is the brain at work.\n\n### Lesson 2: The Nervous System\n1. The nervous system includes the brain, peripheral nerves, and spinal cord.\n2. Nerves are the body's \"telephone lines,\" capable of promptly reporting information obtained from various parts of the body to the brain, and transmitting commands from the brain to different parts of the body.\n3. After a starting gun fires, an athlete's ears receive the sound stimulus, the auditory nerve transmits the signal to the brain, the brain identifies it as the starting signal, and sends commands through nerves to the muscles, causing the athlete to begin running.\n4. If a finger is suddenly pricked by a sharp object, we withdraw our hand first, then feel the pain.\n\n### Lesson 3: Protecting the Brain\n1. The brain is an important organ of the human body.\n2. How does the human body protect the brain?\n   Answer: ① The skull, similar to a walnut shell, protects the brain. ② There are membranes between the skull and brain tissue that protect and support brain tissue. ③ Yawning is a brief self-protective measure that increases the brain's oxygen content.\n3. How can we protect our brain?\n   Answer: ① Adequate sleep; ② Alternating between different subjects when studying; ③ Appropriate physical exercise; ④ Not smoking or drinking excessively; ⑤ Wearing helmets when cycling.\n\n### Lesson 4: Heart and Blood Vessels\n1. People of different ages have different heart rates. Under normal circumstances, children and adolescents have 60 to 100 heartbeats per minute.\n2. Heart rate refers to the number of times the heart beats per minute. Pulse rate refers to the number of times arteries pulsate per minute. Under normal circumstances, a person's pulse rate matches their heart rate.\n3. The heart is located on the left side of the chest cavity, shaped like an inverted pear, larger at the top and smaller at the bottom, about the size of one's fist. The heart has four chambers: left atrium, right atrium, left ventricle, and right ventricle.\n4. Blood vessels are categorized as arteries, veins, and capillaries.\n5. With each contraction and relaxation of the heart, we feel one heartbeat. Generally, the heart pumps about 70ml of blood with each beat.\n6. How do we protect our heart and blood vessels?\n   Answer: ① Daily outdoor exercise; ② Maintaining a calm, optimistic attitude; ③ Balanced diet and moderate eating habits.\n\n### Lesson 5: Our Health Records\n1. Establishing health records helps us understand our physical health condition and prevent diseases in a timely manner.\n2. The WHO has proposed that a healthy person exhibits:\n   (1) Abundant energy, handling daily life and work with composure.\n   (2) Positive attitude, optimism, willingness to take responsibility, and not being picky.\n   (3) Good at resting with quality sleep.\n   (4) Strong adaptability to various environmental changes.\n   (5) Certain resistance to common colds and infectious diseases.\n   (6) Appropriate weight and balanced physique.\n   (7) Bright eyes, quick reactions, and no eyelid inflammation.\n   (8) Clean, undamaged teeth with gums that don't bleed.\n   (9) Lustrous hair without dandruff.\n   (10) Glowing skin with elasticity, walking with ease and vitality.\n\nBased on the above text, please generate an offline game code containing 50 checkpoint questions that can help fifth-grade students better master the knowledge points through gameplay.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the educational game fundamentally aligned with the fifth-grade science curriculum?",
+      "description": "Examine whether the game accurately covers the 5 key lessons from the Unit 1 'Heart and Brain' curriculum. The game should balance content from all sections (brain, nervous system, brain protection, heart and blood vessels, health records). Score 0 if major curriculum areas are missing, 5 if coverage is uneven, and 10 if all curriculum areas are thoroughly represented with accurate scientific information.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are the 50 checkpoint questions pedagogically sound and age-appropriate?",
+      "description": "Evaluate if the questions follow educational best practices: appropriate difficulty for 5th graders, varied question types (multiple choice, matching, fill-in-blank, etc.), and clear educational objectives per question. Deduct 5 points if questions are too advanced/simple for the age group, 3 points if question types are monotonous, and 3 points if questions don't align with learning objectives. Excellent questions should require critical thinking rather than mere memorization. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the game mechanic engaging and supportive of the learning process?",
+      "description": "Assess whether the game mechanics (e.g., points system, progression, feedback loops) support learning rather than distract from it. Check if the game includes scaffolded difficulty, immediate feedback on answers, and learning reinforcement techniques. Deduct 5 points if gameplay interferes with learning objectives, 3 points if there's no adaptive difficulty, and 5 points if feedback on wrong answers lacks educational explanation. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the game maintain offline functionality with appropriate data management?",
+      "description": "Verify that the game works completely offline as specified, with local storage for saving progress, question randomization that works without server connection, and efficient client-side performance. Examine code handling for saving/loading game state. Deduct 5 points if offline mode has significant limitations, 3 points if progress saving is unreliable, and 5 points if performance issues would affect classroom use on typical school devices. 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, browser compatibility issues, unexpected user behavior) and provide friendly error handling or recovery mechanisms. Code with strong robustness should effectively handle edge cases like rapid clicking, browser refreshes during gameplay, or corrupted saved data. Give 10 points if fully robust, 5 points if average robustness, and 0 points if no exception handling exists.",
+      "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 learning experience (e.g., 1. Interactive anatomical models of brain/heart, 2. Visual progress tracking tied to health metrics, 3. Virtual lab experiments, 4. Knowledge application scenarios). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple scoring systems that overlap), 2. Function modules unrelated to the science curriculum (e.g., unnecessary mini-games without educational value), 3. Fancy effects that affect performance on school computers (e.g., excessive animations that slow down older devices). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core educational 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/question database), code organization, and maintainability for teacher customization. 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 cannot be easily modified by teachers to update questions or content. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards for educational software?",
+      "description": "Evaluate whether the design follows child-friendly educational design principles: 1) Age-appropriate color scheme that maintains focus, 2) Clear information hierarchy with important elements emphasized, 3) Legible typography (min 16px font size, 1.5 line height, high contrast for readability). Deduct 3 points for cluttered screens, 5 points for distracting visual elements that compete with educational content, and 5 points for poor accessibility considerations (e.g., color-only indicators without text labels). The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction suitable for classroom use?",
+      "description": "Judge whether the game's interactivity is appropriate for classroom settings: 1) Game sessions can be completed within typical class periods (30-45 minutes), 2) Progress can be saved/resumed between sessions, 3) Interactions are intuitive for the target age group with minimal instruction needed. Deduct 5 points if game length is impractical for classroom use, 3 points if save/resume functionality is unreliable, and 5 points if the interface requires extensive explanation from teachers. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Puzzle",
+  "difficulty": "easy"
+}

package/library/game_development-puzzle/front-end-program-tetris-mini-game.json

@@ -0,0 +1,68 @@
+{
+  "index": 261,
+  "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. Write a front-end program for a Tetris mini-game.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core Tetris game mechanics fully implemented?",
+      "description": "Verify if the code implements all essential Tetris mechanics: piece rotation, movement, collision detection, line clearing, scoring, and level progression. The implementation must handle all 7 standard tetromino shapes correctly. Score 0 if core mechanics are missing, 5 if basic movement is implemented but with flaws, and 10 if all standard Tetris rules are correctly implemented including wall kicks and rotation systems.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the game loop and rendering system properly implemented?",
+      "description": "Examine the game loop implementation for proper timing control, consistent frame rates (target 60fps), and smooth animation. Check if the rendering system (Canvas API or DOM) efficiently updates only changed elements. Deduct 5 points if there's visible stuttering at higher levels, 3 points if the implementation uses inefficient full-screen redraws, and 2 points if there's no frame rate control. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are game controls responsive and customizable?",
+      "description": "Evaluate keyboard handling for responsiveness (<50ms delay), proper event handling (keydown/keyup distinction), and support for both arrow keys and WASD. Check if there's support for control customization, mobile touch controls, or gamepad integration. Deduct 5 points if controls feel sluggish, 3 points if there's no key repeat handling for continuous movement, and 3 points if mobile support is missing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is there a complete game state management system?",
+      "description": "Check if the code includes proper game state management: start/pause/game over states, score tracking, level progression, speed increases, and next piece preview. Verify if the game can be saved/resumed and if high scores are persisted in localStorage. Deduct 5 points if pause functionality is missing, 3 points if there's no game over detection, and 3 points if state transitions aren't smooth. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as browser focus loss, rapid input sequences, window 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. Ghost piece showing where blocks will land 2. Hold piece functionality 3. Special effects for Tetris clears 4. Customizable themes). 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 Tetris (e.g., a built-in calculator) 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/view/input handling), clear function naming, code comments, and potential for extension. Deduct 5 points if global variables are excessively used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no 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 that enhances block visibility 2) Proper layout with clear game board borders and appropriate grid cells 3) Clean and readable UI elements for score, level, and next piece display. Deduct 3 points for each cluttered visual element, 5 points for poor color contrast that makes pieces hard to distinguish, and 5 points for chaotic UI layout. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the piece movements and animations conform to human perception characteristics: 1) Immediate response to player input (≤ 100ms) 2) Smooth piece landing and line clearing animations (300-500ms) 3) Clear visual and audio feedback for actions. Deduct 5 points for each operation without feedback, 3 points for jerky animations, and 5 points for confusing visual effects during gameplay. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Puzzle",
+  "difficulty": "hard"
+}