@getollie/cli 0.0.4 → 0.2.0

package/library/game_development-puzzle/asia-climate-puzzle-game-for-students.json

@@ -1,68 +0,0 @@
-{
-  "index": 891,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Ensure that the generated code is executable for demonstration. I am a middle school geography teacher and want to help students master the climate types of Asia through a puzzle game. (Temperate monsoon climate-Beijing, Subtropical monsoon climate-Shanghai, Tropical monsoon climate-Mumbai, Tropical rainforest climate-Indonesia, Tropical desert climate-Saudi Arabia, Mediterranean climate-Italy, Temperate continental climate-Xinjiang, Plateau mountain climate-Tibet, Arctic climate-North Pole) Please generate online puzzle game code.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core geography puzzle game mechanic implemented?",
-      "description": "Evaluate whether the code implements the matching mechanism between climate types and their respective geographic locations (Beijing, Shanghai, Mumbai, etc.). Check if all 9 climate types mentioned are included with accurate associations. Score 0 if the core puzzle logic is missing, 5 if basic matching exists but with inaccurate geography information, and 10 if all climate types and locations are correctly implemented with educational validity.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the interactive learning mechanism effectively designed?",
-      "description": "Assess whether the game includes educational components that help students learn while playing. Check for explanatory text about each climate type, feedback mechanisms that explain why matches are correct/incorrect, and progressive difficulty levels. Deduct 3 points if climate descriptions are missing, 4 points if no educational feedback exists, and 3 points if the learning curve is inappropriate for middle school students. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the geographic visualization component properly implemented?",
-      "description": "Review the implementation of geographic visualization (map of Asia, climate zone indicators, location markers). Check if the map accurately represents Asian geography with proper country boundaries and if the climate zones are visually distinguishable. Score 0 if no map visualization exists, 5 if basic visualization exists but with geographic inaccuracies, and 10 if visualization is geographically accurate and educationally valuable.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the game state management and scoring system implemented?",
-      "description": "Evaluate the implementation of game progression tracking, scoring system, and completion metrics. Check for features like progress saving, performance metrics (time taken, accuracy rate), and level progression. Deduct 3 points if no scoring mechanism exists, 4 points if game state isn't preserved between sessions, and 3 points if performance tracking is inadequate for educational assessment. 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 incorrect user inputs, browser compatibility issues, touch vs. mouse interactions, 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. Climate animation showing seasonal changes 2. Real climate data visualization 3. Interactive quizzes based on puzzle completion 4. Climate comparison tool). 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 drag-and-drop systems) 2. Function modules unrelated to geography learning (e.g., unrelated mini-games) 3. Fancy effects that affect performance (e.g., excessive animations that distract from learning). 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/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 the code lacks comments or documentation for educational content. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet educational design standards?",
-      "description": "Evaluate whether the overall design follows educational design principles: 1) Age-appropriate visuals for middle school students 2) Clear information hierarchy with educational content prominently displayed 3) Proper contrast and readability for geographic labels and climate information. Deduct 3 points for cluttered educational content, 5 points for poor readability of critical geography information, and 5 points for visuals that misrepresent climate characteristics. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and suitable for classroom use?",
-      "description": "Judge whether the interaction design is appropriate for educational settings: 1) Simple enough for classroom use without extensive training 2) Works on school computers/tablets with potential hardware limitations 3) Provides clear visual and textual feedback for learning reinforcement. Deduct 5 points if interactions are too complex for classroom use, 3 points if performance issues would disrupt learning, and 5 points if educational feedback is delayed or unclear. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Puzzle",
-  "difficulty": "hard"
-}

package/library/game_development-puzzle/candy-crush-wechat-mini-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 1283,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Pay attention to ensuring that the code you generate is executable for demonstration. Write code for a Candy Crush-style WeChat Mini Program game, with as much detail as possible, that can be played directly.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core game mechanics properly implemented?",
-      "description": "Review whether the code accurately implements the basic Candy Crush mechanics including: 1) Grid generation with randomized candies 2) Swap detection with validation of legal moves 3) Match-3 or more pattern recognition 4) Cascading effect when candies are removed. Score 0 if core mechanics are missing, 5 if basic swapping and matching are implemented, and 10 if all mechanics including cascades and special candy creation are fully implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the WeChat Mini Program structure correctly set up?",
-      "description": "Check whether the code follows WeChat Mini Program development standards with proper page structure (WXML/WXSS/JS), correct use of Mini Program APIs, project configuration files (app.json, project.config.json), and lifecycle events handling. Deduct 5 points if the basic structure is incorrect, 3 points if certain important Mini Program APIs are missing, and 5 points if configuration files are not provided or incomplete. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are the game scoring and level progression systems implemented?",
-      "description": "Evaluate whether the game includes a complete scoring mechanism (points for matches, combos, special candies), level progression (increasing difficulty, targets/goals), and achievement tracking. Deduct 3 points if the scoring is simplistic, 5 points if level progression is missing, and 5 points if there's no win/lose condition. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the game state management and data persistence implemented?",
-      "description": "Check whether the code implements proper game state management (using Mini Program storage APIs), including saving/loading games, tracking player progress, and handling app lifecycle events (background/foreground transitions). Deduct 5 points if state management is rudimentary, 5 points if persistence is missing, and 3 points if app lifecycle isn't properly handled. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid moves, edge cases in the matching algorithm, touchscreen gesture 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. Special candy combinations with unique effects 2. Social features like sharing scores with friends 3. Daily rewards or 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 scoring systems) 2. Function modules unrelated to the candy crush game (e.g., a built-in calculator) 3. Fancy effects that affect performance (e.g., excessive animations that slow down the game). 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/UI/state management), component reusability, and build process optimization. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if performance optimization for WeChat Mini Program is not considered. 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 mobile game design principles: 1) Vibrant but harmonious color palette suitable for a candy-themed game 2) Proper layout with touch-friendly element sizing (buttons at least 44x44px) 3) Professional typography system with clear instructions and scoring display. Deduct 3 points for each crowded visual element, 5 points for a confusing game board layout, and 5 points for inconsistent visual style. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception and mobile game standards: 1) Touch response delay ≤ 100ms 2) Candy swap/match animations between 300-500ms 3) Clear visual and audio feedback for matches and special effects. Deduct 5 points for each interaction without feedback, 3 points for jerky animations during cascades, and 5 points if the game feels sluggish on typical mobile devices. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Puzzle",
-  "difficulty": "hard"
-}

package/library/game_development-puzzle/chinese-english-word-matching-game-html.json

@@ -1,68 +0,0 @@
-{
-  "index": 1735,
-  "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. Please help me create a word matching game that focuses on memory and learning, with Chinese on one side and English on the other, in HTML code for sixth grade first semester.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core word matching game mechanism fully implemented?",
-      "description": "Review whether the code implements a proper card-flipping mechanism for word matching, with random distribution of Chinese-English pairs, correct match detection, and score tracking. Score 0 if the core matching logic is not implemented, 5 if only basic flipping is implemented without proper matching validation, and 10 if it includes proper matching validation with appropriate feedback.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the Chinese-English vocabulary content appropriate for sixth grade first semester?",
-      "description": "Evaluate whether the vocabulary selection matches the sixth grade first semester curriculum standards, with age-appropriate difficulty levels (roughly 300-500 common words). Deduct 5 points if the vocabulary is too advanced or too elementary, 3 points if there aren't enough word pairs (at least 15-20 pairs minimum), and 5 points if the Chinese-English translations are incorrect. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Does the game implement learning reinforcement features?",
-      "description": "Check for features that reinforce vocabulary memorization, such as spaced repetition, hint systems, pronunciation aids, or review modes for previously matched words. Deduct 5 points if no learning reinforcement features exist, 3 points if only basic review is available. Give full points if comprehensive learning tools are implemented including audio pronunciation, repetition of difficult words, or progress tracking.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there a clear game progression system?",
-      "description": "Assess whether the game includes levels of increasing difficulty, achievement tracking, or a scoring system that encourages continued play and learning. Deduct 5 points if there's no progression system, 3 points if progression exists but without difficulty adjustment. Full points if the system includes multiple levels, performance metrics, and adaptive difficulty based on player performance.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code handles common abnormal situations (such as invalid inputs, browser compatibility issues, or unexpected user actions) and provides friendly error handling or recovery mechanisms. Code with strong robustness should effectively handle 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. Audio pronunciation of words 2. Visual memory aids like pictures 3. Animated feedback for correct/incorrect matches). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple ways to restart a game) 2. Function modules unrelated to word matching (e.g., an unrelated mini-game) 3. Fancy effects that affect performance (e.g., excessive animations that slow down card flipping). 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 layers), code organization, and maintainability. Deduct 5 points if global state pollution is found or if code organization is poor; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the code lacks comments or documentation. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet educational design standards?",
-      "description": "Evaluate whether the overall design follows child-friendly educational design principles: 1) Age-appropriate color scheme (bright but not distracting) 2) Clear and readable typography (font size ≥ 16px, simple fonts) 3) Intuitive layout with proper spacing between elements. Deduct 3 points for visual clutter, 5 points for text that's difficult to read, and 5 points for confusing navigation. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction suitable for children?",
-      "description": "Judge whether the interactive elements are appropriate for sixth-grade students: 1) Simple and obvious clickable elements 2) Clear feedback for actions 3) Forgiving interaction design that prevents frustration. Deduct 5 points for confusing interactions, 3 points for insufficient feedback, and 5 points for interactions requiring fine motor skills beyond a typical sixth-grader's ability. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Puzzle",
-  "difficulty": "easy"
-}

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

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

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

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

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

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