@getollie/cli 0.0.5 → 0.2.1

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

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

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

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

package/library/game_development-puzzle/fruit-matching-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 256,
-  "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 design a fruit matching game using HTML code. Please provide me with a complete code.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core fruit matching mechanic fully implemented?",
-      "description": "Review whether the code accurately implements the matching logic, including detection of adjacent fruits, pattern recognition (minimum 3 matching fruits), and handling of cascading matches when new fruits fall. Score 0 if matching logic is missing, 5 if only basic matching is implemented, and 10 if advanced matching patterns and cascading effects are included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the game board generation and fruit distribution implemented properly?",
-      "description": "Check whether the code includes dynamic board generation with appropriately sized grid cells, random but balanced fruit distribution (avoiding pre-matched patterns), and proper visual representation of different fruit types. Deduct 5 points if the board is static/hardcoded, 3 points if fruit distribution lacks variety. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is there a scoring system and game progression mechanism?",
-      "description": "Evaluate whether the game includes a proper scoring system (points for matches, bonuses for combos/larger matches), level progression, and increasing difficulty (time limits, target scores, etc.). Give 0 points if scoring is missing, 5 points if basic scoring exists, and 10 points if a complete progression system is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are animations and transitions implemented for game events?",
-      "description": "Check whether the code implements smooth animations for fruit swapping, matching/disappearing, new fruits falling, and special effects for combos/achievements. Deduct 5 points if animations are missing entirely, and 3 points if they look choppy or incomplete. 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, invalid moves, browser resizing, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Special power-up fruits 2. Unique visual/sound effects for combos 3. Personalized themes or customization). 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 fruit matching (e.g., unnecessary mini-games) 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), code readability, 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 code documentation or comments. 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 (fruit colors contrast nicely with background) 2) Proper layout spacing (game board centered, UI elements properly aligned) 3) Professional font system (readable score display, clear instructions). 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 game interactions conform to human perception characteristics: 1) Fruit selection/swapping responds within 100ms 2) Smooth transitions when fruits disappear/fall 3) Clear visual feedback for valid/invalid moves. Deduct 5 points for each operation without feedback, 3 points for jerky animations, and 5 points for confusing/unintuitive controls. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Puzzle",
-  "difficulty": "medium"
-}

package/library/game_development-puzzle/gravity-control-html-javascript-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 142,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable for demonstration.\nPlease implement a gravity control feature using HTML and JavaScript. \n\n**Task**: Implement a gravity control feature that allows players to temporarily change the direction of gravity in the level to solve puzzles.\n\n**Hint**: You can control the gravity direction through keyboard inputs, and design levels that require specific gravity states to pass through.\n\nPlease include comments in your code to help other developers understand your implementation process.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the gravity control mechanism fully implemented?",
-      "description": "Review whether the code accurately implements gravity physics simulation using JavaScript, including proper acceleration, terminal velocity, and collision response. Check if the gravity direction can be changed via keyboard inputs as specified in the requirements. Score 0 if gravity simulation is missing, 5 if only basic gravity is implemented in one direction, and 10 if directional gravity control (up, down, left, right) with proper physics is fully implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are interactive puzzle elements designed that utilize the gravity mechanics?",
-      "description": "Evaluate whether the code includes interactive elements (movable objects, platforms, obstacles) that respond to gravity changes. Score 5 if basic objects that respond to gravity are implemented, and 10 if there are multiple interactive elements designed specifically to create meaningful puzzle scenarios with the gravity control mechanics.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is there level design that requires specific gravity states to complete?",
-      "description": "Check if at least one complete level is implemented that requires changing gravity direction to solve. Evaluate whether the level design challenges players to use the gravity mechanism strategically. Score 3 if a basic level exists, 7 if the level has interesting challenges, and 10 if multiple levels with escalating complexity in gravity usage are implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is proper visual feedback provided for gravity changes?",
-      "description": "Assess whether the code provides clear visual indicators when gravity direction changes (such as UI indicators, environment shifts, or particle effects). Score 0 if no visual feedback exists, 5 if basic indicators are implemented, and 10 if comprehensive, intuitive visual feedback is provided that clearly communicates the current gravity state to the player.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as rapid gravity switching, edge cases in physics calculations, object intersections) and provide 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. Time-limited gravity shifts 2. Gravity strength adjustment 3. Special objects that have their own gravity fields). 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 physics functions 2. Function modules unrelated to the gravity puzzle (e.g., unnecessary gameplay elements) 3. Fancy effects that affect performance (e.g., excessive 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 physics engine/game logic/rendering), code comments as required in the task, and overall structure. 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 comprehensive comments explaining the implementation process are missing. 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) Clear distinction between game elements and UI elements. Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for confusing game vs UI elements. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the gravity transition animation smooth and intuitive?",
-      "description": "Judge whether the gravity transition effects conform to human perception characteristics: 1) Visual indication begins ≤ 100ms after input 2) Transition animation duration controlled between 200-400ms 3) Objects respond naturally to gravity changes with appropriate acceleration curves. Deduct 5 points for abrupt gravity transitions, 3 points for unrealistic object movement during transitions, and 5 points for lack of directional indicators for current gravity state. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Puzzle",
-  "difficulty": "medium"
-}

package/library/game_development-puzzle/how-to-design-implement-tetris-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 1175,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure that the code you generate is executable. How would you design and implement code for a Tetris game?",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core Tetris game mechanics fully implemented?",
-      "description": "Review whether the code accurately implements the standard Tetris mechanics including piece rotation, movement, dropping, line clearing, and scoring. Check if the 7 standard Tetrimino shapes are correctly defined and if their rotation points follow official Tetris guidelines. Score 0 if core game logic is missing, 5 if basic movement is implemented but with flaws, and 10 if all standard Tetris mechanics are correctly implemented including wall kicks and SRS rotation system.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the game board properly implemented?",
-      "description": "Evaluate the implementation of the standard 10x20 game board (or 10x22 with hidden rows), boundary detection, collision detection, and grid system. Check if the board state is properly managed and updated. Deduct 5 points if the board dimensions are incorrect, 3 points if collision detection has bugs, and 2 points if the board state management is inefficient. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are the game controls and user input handling implemented correctly?",
-      "description": "Check if the code handles keyboard/touch inputs properly with support for standard controls (left, right, rotate, hard drop, soft drop). Assess if the code implements DAS (Delayed Auto Shift) and ARR (Auto-Repeat Rate) for smooth piece movement. Deduct 3 points if key bindings cannot be customized, 3 points if there's significant input lag, and 5 points if critical controls are missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the game progression system properly implemented?",
-      "description": "Review the implementation of level progression, speed increases, scoring system, and next piece preview. Check if the game follows the standard Tetris scoring system with bonuses for T-spins, combos, and perfect clears. Deduct 3 points if level progression is missing, 3 points if the scoring system is incomplete, and 5 points if there's no next piece preview or hold feature. 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 unexpected inputs, game state inconsistencies, browser compatibility issues) 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. Battle mode features 4. Dynamic difficulty adjustment). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple game loop mechanisms) 2. Function modules unrelated to Tetris (e.g., unrelated mini-games) 3. Fancy effects that affect performance (e.g., excessive animations that cause lag). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating game logic/view/controller layers), code readability, proper commenting, and efficient algorithms. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 3 points if the code duplication rate is too high (over 30%); deduct 3 points if the game loop implementation is inefficient. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the game UI follows modern design principles: 1) Clear block visibility and distinction 2) Readable score/level display 3) Proper layout with next piece preview and hold piece areas 4) Consistent color scheme following Tetris standards. Deduct 3 points for poor block visibility, 3 points for cluttered UI elements, 5 points for illegible text information. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the game runs at a consistent frame rate (60 FPS recommended), whether piece movements are smooth, and if animations (line clearing, game over) are visually appealing without disrupting gameplay. Deduct 5 points for frame rate drops during gameplay, 3 points for jerky piece movement, and 5 points for animations that interrupt the game flow. Check if the game timing system uses requestAnimationFrame or similar for smooth rendering. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Puzzle",
-  "difficulty": "medium"
-}

package/library/game_development-puzzle/html-6x6-klotski-sliding-block-puzzle.json

@@ -1,68 +0,0 @@
-{
-  "index": 1793,
-  "question": "You are a code expert. Please utilize your professional knowledge to generate accurate and professional responses. Be sure to make the generated code executable for demonstration. Create a 6x6 Klotski (sliding block puzzle) game using HTML.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core Klotski puzzle mechanism implemented correctly?",
-      "description": "Evaluate whether the code accurately implements the 6x6 grid system with movable blocks, proper collision detection, and valid move validation. Check if blocks can only slide horizontally or vertically into empty spaces without jumping over other blocks. Score 0 if core sliding mechanism is missing, 5 if basic movement works but has bugs, and 10 if the sliding mechanism is flawless with smooth transitions.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is there a complete puzzle initialization and win-condition system?",
-      "description": "Check if the code includes proper puzzle initialization with blocks of different sizes positioned correctly on the 6x6 grid, a clear objective (typically moving a specific block to a target position), and win-condition detection. Deduct 3 points if initial state is hardcoded without variety, 3 points if win conditions are unclear, and 5 points if there's no win detection implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Does the game include a move counter and history tracking?",
-      "description": "Assess whether the implementation tracks the number of moves made, provides an undo/redo functionality, and maintains a move history that can be reviewed. Deduct 3 points if only basic move counting exists, 5 points if no undo functionality is provided, and 7 points if there's no history tracking at all. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there a puzzle reset and level selection system?",
-      "description": "Evaluate if the game allows players to reset the current puzzle to its initial state and provides multiple puzzle configurations or difficulty levels to choose from. Deduct 3 points if only reset functionality exists without level selection, 5 points if neither feature is implemented properly. Give 10 points if both reset and level selection are fully functional with at least 3 different puzzle configurations.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as rapid clicking, invalid moves, browser resize, etc.) and provide friendly error handling or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Animation effects when sliding blocks 2. Hint system for next optimal move 3. Timer/leaderboard functionality 4. Puzzle solving visualization). 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 reset the game) 2. Function modules unrelated to Klotski (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, and maintainability. Deduct 5 points if global state pollution is found or proper encapsulation is missing; 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 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) Clear visual distinction between blocks of different types and the game board. Deduct 3 points for poor block differentiation, 5 points for unclear or inconsistent visual hierarchy, and 5 points for confusing or cluttered UI. 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) Immediate visual feedback on block selection and movement 2) Smooth transitions when blocks slide (150-300ms animation) 3) Clear indication of legal vs. illegal moves. Deduct 5 points if blocks move without animation, 3 points for laggy or jerky movements, and 5 points if there's no clear indication when attempting illegal moves. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Puzzle",
-  "difficulty": "hard"
-}

package/library/game_development-puzzle/html-javascript-environmental-interaction-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 11,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable.\n\nPlease use HTML and JavaScript to implement environmental interaction.\n**Task**: Add environmental interaction functionality that allows characters to interact with objects in the scene, such as pushing boxes, pulling levers, etc.\n**Tip**: You can use a simple physics engine to implement object movement and design puzzle elements for levels. Please think through and answer in detail, aiming to implement a solution that is as complete as possible, meets the requirements, has a good game interface, and high playability. Note: Use HTML to implement the above functionality, ensuring it can be directly executed in the frontend.\n\nPlease include comments in your code to help other developers understand your implementation process.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the character-object interaction system fully implemented?",
-      "description": "Evaluate whether the code accurately implements core interactions like pushing boxes and pulling levers with proper collision detection and physics calculations. Score 0 if interactions are absent, 5 if only basic interactions work, and 10 if multiple interactions are implemented with physical properties (mass, friction, momentum).",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the physics engine properly implemented?",
-      "description": "Check if the code includes essential physics calculations (collision detection, object momentum, velocity) and handles edge cases like stacking objects or preventing objects from passing through walls. Score 0 for no physics implementation, 5 for basic physics without edge cases, and 10 for robust physics handling all scenarios.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are the interactive puzzle elements well-designed?",
-      "description": "Review whether the solution includes actual puzzle scenarios using the environmental interactions (e.g., box-pushing puzzles, lever-activated doors, pressure plates). Deduct 5 points if puzzle logic is inconsistent, 3 points if puzzle difficulty is poorly balanced. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the level design system implemented?",
-      "description": "Evaluate whether the code includes a level structure with progressive challenges, objectives, and states (solved/unsolved). Check for level progression logic and state management. Deduct 5 points if level state persistence is missing, 3 points if level transitions are abrupt. 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, out-of-bounds movement, object stacking, wall clipping, etc.) and provide friendly error handling or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Physics-based chain reactions 2. Interactive tutorial system 3. Multiple solution paths for puzzles). 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 environmental interaction (e.g., unnecessary scoring system) 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 physics/game logic/input handling/rendering layers), code organization, and implementation of design 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 are insufficient comments explaining complex physics calculations or game logic. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern game UI principles: 1) Clear visual distinction between interactive and non-interactive elements 2) Intuitive feedback when interacting with objects 3) Visual cues for physics interactions (shadows, movement indicators). Deduct 3 points for each confusing interactive element, 5 points for unclear visual feedback, and 5 points for misleading physics representations. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the movement and physics interactions feel natural: 1) Character movement response ≤ 50ms 2) Physics calculations maintain 60fps even with multiple objects 3) Smooth transitions during object interactions. Deduct 5 points for each laggy interaction, 3 points for physics glitches during complex interactions, and 5 points for jerky animation during object movement. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Puzzle",
-  "difficulty": "medium"
-}