@getollie/cli 0.0.5 → 0.2.0

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

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

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

@@ -1,68 +0,0 @@
-{
-  "index": 1633,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be careful to ensure that the code you generate is executable. Create a web-based mini-game for the Chinese idiom solitaire game.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core idiom matching logic fully implemented?",
-      "description": "Review whether the code accurately implements the Chinese idiom solitaire matching rules (matching the last character of one idiom with the first character of the next). Check for proper validation of user inputs against a comprehensive idiom database. Score 0 if the core matching logic is missing, 5 if basic matching works but with limitations, and 10 if all rules including special cases (rare characters, homonyms) are handled properly.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the idiom database comprehensive and well-structured?",
-      "description": "Evaluate whether the code includes or connects to a substantial Chinese idiom database with at least 1000 common idioms. Check if the database structure efficiently enables first/last character lookups and prevents repetition in gameplay. Deduct 3 points if fewer than 500 idioms are included, 4 points if character-based indexing is inefficient, and 5 points if the database lacks meaning explanations for educational value. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the game progression and scoring system properly implemented?",
-      "description": "Check if the game has clear progression mechanics (increasing difficulty, time limits, or chain bonuses), proper scoring logic (points based on character complexity, idiom rarity, or response time), and game ending conditions. Deduct 5 points for missing progression, 3 points for simplistic scoring, and 3 points for poorly defined win/lose states. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are accessibility and learning features incorporated?",
-      "description": "Assess whether the game includes educational elements (idiom meanings, usage examples, historical context) and accessibility features (pinyin display, difficulty settings, hint systems). Deduct 3 points for each missing educational aspect and 4 points if accessibility considerations are absent. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid inputs, server failures, edge cases like no more matching idioms available, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Animated character calligraphy 2. Traditional Chinese background music 3. Challenge modes like limited time or category-specific idioms). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple ways to check idiom validity) 2. Function modules unrelated to the idiom game (e.g., unnecessary mini-games within the game) 3. Fancy effects that affect performance (e.g., excessive animations that slow down gameplay). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating game logic/view/data layers), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows traditional Chinese aesthetic principles while maintaining modern usability: 1) Traditional color palette appropriate for Chinese culture 2) Proper layout with adequate white space 3) Suitable typography using fonts that properly display Chinese characters. Deduct 3 points for cluttered visual elements, 5 points for culturally inappropriate visuals, and 5 points for poor readability of Chinese characters. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Immediate feedback when submitting idioms (≤ 100ms) 2) Smooth transitions when showing new idioms or game states 3) Clear visual indicators for valid/invalid submissions. Deduct 5 points for each operation without feedback, 3 points for laggy animations during gameplay, and 5 points for confusing user interface that doesn't clearly show game state. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Puzzle",
-  "difficulty": "hard"
-}

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

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

package/library/game_development-puzzle/wechat-mini-game-mahjong-tile-match.json

@@ -1,68 +0,0 @@
-{
-  "index": 1312,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and expert responses. Make sure the generated code is executable for demonstration. Please help me design a WeChat mini-game - Mahjong Tile Match. The development tool used is the WeChat Developer Tool.\n\nFor the game entrance, when users open the mini-game, they will first see a loading screen with a progress bar that updates according to resource loading progress, featuring a game background image, and a \"Start Game\" button on the page. After clicking the Start Game button, users enter the main game screen which has a large background image. Only write the relevant code and directory structure for what's described above.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the loading screen with progress bar fully implemented?",
-      "description": "Check whether the code properly implements a loading screen that accurately reflects resource loading progress. It should show a progress bar that updates dynamically, display a background image, and include a 'Start Game' button. The progress bar should not simply be animated but should reflect actual asset loading status. Score 0 if missing, 5 if only visually implemented without actual loading tracking, and 10 if fully functional with proper resource loading tracking.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the game entrance flow (loading to main game) implemented correctly?",
-      "description": "Evaluate the transition between loading screen and main game screen. The 'Start Game' button should be conditionally enabled only after resources are loaded. Check if there's proper event handling for the button click that transitions to the main game screen. Verify state management between screens. Deduct 5 points if button is active before loading completes, deduct 3 points if transition is abrupt without animations. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the WeChat Mini-Game API properly utilized?",
-      "description": "Review whether the code correctly uses WeChat Mini-Game APIs for resource loading, rendering, and user interactions. Score should reflect proper use of wx.createCanvas, wx.createImage and other WeChat-specific APIs instead of standard web APIs. Deduct 5 points if browser-only APIs are used, deduct 5 points if WeChat lifecycle events (onShow, onHide, etc.) are not properly handled. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the directory structure well-organized for a WeChat mini-game?",
-      "description": "Check if the project follows WeChat mini-game conventions with appropriate directory structure (e.g., separate folders for images, audio, js modules). Verify if game.js, game.json, project.config.json are properly configured. Deduct 5 points if assets are disorganized, deduct 3 points if configuration files are incorrect, deduct 5 points if the structure doesn't follow WeChat mini-game best practices. 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 resource loading failures, network issues, unexpected user 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 experience (e.g., 1. Animated loading screen elements 2. Interactive background elements 3. Subtle sound effects for button interactions). 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 implementations of similar functions (e.g., multiple loading mechanisms) 2. Function modules unrelated to game entrance (e.g., full game mechanics in the entrance screen) 3. Fancy effects that affect performance (e.g., excessive animations that slow down 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 core logic/rendering/resource management), 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 poor error handling or lack of 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 (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 transitions, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Puzzle",
-  "difficulty": "easy"
-}

package/library/game_development-puzzle/wechat-mini-program-match-3-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 1301,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate, professional responses. Make sure that the code you generate is executable. Write code for a WeChat Mini Program that is a match-3 game, where the image and audio resources do not exceed 200K.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the basic match-3 game mechanics fully implemented?",
-      "description": "Review whether the code accurately implements core match-3 mechanics including grid initialization, piece swapping, match detection, cascading effects, and score calculation. Score 0 if the core interaction logic is missing, 5 if only basic matching is implemented without cascades, and 10 if the full match-3 system with special combinations and cascading effects is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the WeChat Mini Program framework properly utilized?",
-      "description": "Evaluate proper use of the WXML/WXSS/JS architecture, lifecycle hooks (onLoad, onShow), and WeChat-specific APIs. Check for proper page navigation, event handling with bindtap, and appropriate use of component encapsulation. Deduct 5 points if custom components aren't used where appropriate, 3 points if lifecycle methods are misused, and 3 points if WeChat's storage APIs aren't utilized for game state.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the resource optimization requirement met?",
-      "description": "Verify that image and audio resources are properly optimized and do not exceed the 200K limit. Check for image compression techniques, sprite sheets usage, audio format optimization (preferring compressed formats like mp3), and lazy loading implementation. Deduct 10 points if resources exceed 200K, 5 points if no optimization techniques are applied, and 3 points if resource loading isn't handled efficiently.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the game progression system well-designed?",
-      "description": "Assess whether the game includes essential progression elements such as levels with increasing difficulty, goals/targets system, rewards mechanism, and player stats tracking. Deduct 5 points if level progression is missing, 3 points if there's no difficulty scaling, and 3 points if player achievements aren't tracked or displayed.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as touch events outside the grid, rapid consecutive taps, WeChat Mini Program lifecycle interruptions, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Special power-ups beyond basic matching 2. Social sharing features with custom images 3. Daily challenges/rewards system). 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 coexisting) 2. Function modules unrelated to match-3 gameplay (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 layers), use of design patterns appropriate for game development, and code maintainability. Deduct 5 points if global state is poorly managed; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no clear separation between UI and 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 mobile game 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, readable on small screens). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for poor adaptation to different WeChat device screens. 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) Touch feedback delay ≤ 100ms 2) Match animations duration controlled between 300-500ms 3) Clear visual feedback for successful/unsuccessful matches. Deduct 5 points for each operation without feedback, 3 points for laggy animations during cascades, and 5 points for unresponsive touch areas. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Puzzle",
-  "difficulty": "hard"
-}

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

@@ -1,68 +0,0 @@
-{
-  "index": 806,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable for demonstration. Create a WeChat mini-program for playing Tetris.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core Tetris game mechanics fully implemented?",
-      "description": "Review whether the code accurately implements the Tetris grid system, piece rotation, collision detection, line clearing, and scoring mechanisms. Score 0 if the core gameplay logic is incomplete, 5 if basic piece movement and rotation are implemented, and 10 if all standard Tetris rules (including wall kicks, lock delay, and next piece preview) are properly implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the WeChat mini-program structure properly set up?",
-      "description": "Check whether the project follows the standard WeChat mini-program structure with proper app.json, page configuration, and component organization. Verify that the code uses WXML, WXSS, and JS correctly according to WeChat platform guidelines. Deduct 5 points if the project structure is incomplete, 3 points if platform-specific APIs are misused. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Does the implementation handle touch/gesture controls effectively?",
-      "description": "Evaluate whether the game implements intuitive touch controls for the WeChat mini-program environment (swipe, tap, hold gestures) with proper sensitivity adjustment. Touch areas should be appropriately sized (at least 44x44px). Deduct 5 points for poor touch responsiveness, 3 points for unintuitive controls. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the WeChat mini-program lifecycle and state management properly handled?",
-      "description": "Check whether the code properly handles the mini-program lifecycle events (onLoad, onShow, onHide, etc.) and game state persistence. The game should be able to pause when switching to background and resume correctly. Deduct 5 points if game state is lost when switching between mini-program pages, and 3 points if the game doesn't handle system events properly. 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, 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. WeChat friend challenges 2. Custom themes or skins 3. Achievement system integrated with WeChat social features). 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 perform the same action) 2. Function modules unrelated to Tetris gameplay (e.g., unnecessary mini-games) 3. Fancy effects that affect performance (e.g., excessive animations that slow down gameplay). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating game logic/view/controller layers), proper use of WeChat framework features, and code maintainability. Deduct 5 points if global state pollution is found; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if WeChat mini-program best practices are not followed. 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 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, sufficient contrast against background). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for designs that don't conform to WeChat's visual language. 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) Game piece movement is smooth without frame drops 2) Touch response delay ≤ 100ms 3) Clear visual feedback for all user actions. Deduct 5 points for each operation without feedback, 3 points for laggy animations, and 5 points for unresponsive controls during gameplay. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Puzzle",
-  "difficulty": "medium"
-}

package/library/game_development-puzzle/wechat-mini-program-unique-elimination-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 1154,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code whenever possible. I want to create an elimination game for WeChat Mini Program that stands out compared to existing elimination games on the market. Please help me write the code and directly explain how to run it in the WeChat Mini Program.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core elimination gameplay mechanics fully implemented?",
-      "description": "Review whether the code implements a complete elimination logic including pattern matching algorithms, chain reaction handling, score calculation, and level progression. Check if the elimination rules are clearly defined (e.g., minimum match requirement, special combinations). Score 0 if core elimination logic is missing, 5 if basic matching is implemented but lacks special combinations, and 10 if it includes advanced features like cascading effects and combo systems.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the WeChat Mini Program integration properly implemented?",
-      "description": "Verify that the code follows WeChat Mini Program development specifications and utilizes appropriate APIs (wx.* namespace). Check if the project structure includes necessary app.js, app.json, and page files. Deduct 5 points if the configuration files are incomplete, 3 points if lifecycle hooks are improperly used, and 5 points if the app lacks proper navigation between screens. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Does the game have unique differentiating features compared to existing market offerings?",
-      "description": "Evaluate whether the game includes novel mechanics or features that distinguish it from typical elimination games (e.g., unique power-ups, interactive backgrounds, physics-based interactions, or meta-gameplay elements). Deduct 5 points if the game is merely a clone of existing games, 3 points if innovations are superficial. Give 10 points if truly innovative gameplay elements are present.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there a complete progression and reward system implemented?",
-      "description": "Check whether the code implements level progression, difficulty scaling, achievement tracking, and reward mechanisms. Verify if there's a persistence layer for saving player progress. Deduct 5 points if progression logic is missing, 3 points if difficulty doesn't scale appropriately, and 5 points if there's no reward/achievement system. 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. Social sharing with custom images 2. Daily challenges with unique rules 3. Mini-narratives between levels). 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 coexisting) 2. Function modules unrelated to the elimination game (e.g., excessive mini-games that distract from core gameplay) 3. Fancy effects that affect performance (e.g., excessive particles that cause lag on low-end devices). 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), unit test coverage, and WeChat Mini Program best practices. 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 project structure doesn't follow Mini Program conventions. 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 WeChat Mini Program 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 optimized for mobile?",
-      "description": "Judge whether the dynamic effects conform to mobile touch interaction standards: 1) Touch feedback delay ≤ 100ms 2) Animation performance optimized for WeChat's rendering engine 3) Touch targets at least 44x44px for comfortable tapping. Deduct 5 points for each operation without feedback, 3 points for frame drops during animations, and 5 points for touch targets that are too small or overlapping. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Puzzle",
-  "difficulty": "medium"
-}

package/library/game_development-puzzle/wechat-sokoban-game-development.json

@@ -1,68 +0,0 @@
-{
-  "index": 1399,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the generated code is executable for demonstration. Help me write a code for a Sokoban (box pushing) game that can run on WeChat.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core Sokoban gameplay mechanics fully implemented?",
-      "description": "Review whether the code accurately implements box movement logic, player control, collision detection (wall, box, target), and win condition validation. Score 0 if core mechanics are missing, 5 if basic movement works but with bugs, and 10 if the complete ruleset is properly implemented, including detecting when boxes are pushed onto target spots.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the WeChat Mini Program integration properly implemented?",
-      "description": "Evaluate if the code correctly uses WeChat Mini Program APIs and lifecycle functions (onLoad, onShow), follows WeChat development specifications, and implements page routing properly. Deduct 5 points if the code doesn't use wx.* APIs appropriately, 3 points if lifecycle methods are improperly handled. Check if the game adapts to different mobile screen sizes using rpx units or flex layouts.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Does the game include level design and progression mechanics?",
-      "description": "Check if multiple levels are included with proper difficulty progression, level selection interface, and level completion tracking. At minimum, the game should have 5+ distinct levels and save player progress. Deduct 5 points if only one level exists, 3 points if level progression isn't saved between sessions, and 2 points if difficulty curve is poorly designed.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are WeChat-specific features utilized for enhanced gameplay?",
-      "description": "Assess if the game leverages WeChat platform features such as cloud storage for saving progress, share functionality for level challenges, or user avatars integration. Give 3 points for each WeChat-specific feature properly implemented (maximum 10 points), with emphasis on features that enhance the social aspect of the game.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid moves, rapid taps, unexpected user input, or WeChat lifecycle interruptions) 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. Undo/redo functionality 2. Move counter and optimization hints 3. Custom character skins 4. Visual path indicators). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple movement control systems) 2. Function modules unrelated to the game (e.g., unnecessary social features) 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 maintainability, and adherence to WeChat Mini Program development best practices. Deduct 5 points if global state is mismanaged; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the project structure doesn't follow WeChat Mini Program conventions. 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) Touchscreen-optimized controls (sufficiently large tap targets ≥ 44px) 2) Proper layout spacing (elements not cluttered or too close to screen edges) 3) Professional visual language (consistent with WeChat design language). Deduct 3 points for each hard-to-use control element, 5 points for poor visual hierarchy, and 5 points for designs that clash with WeChat's aesthetic. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the game's performance and interactivity are optimized for mobile: 1) Movement response delay ≤ 100ms 2) Smooth animations at minimum 30fps 3) Touch gestures that feel natural and intuitive. Deduct 5 points for each laggy animation, 3 points for unresponsive controls, and 5 points for poor touch area design that causes misoperations. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Puzzle",
-  "difficulty": "hard"
-}