@getollie/cli 0.0.5 → 0.2.0

package/library/game_development-simulation_management/dynamic-weather-environmental-impact-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 119,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable and ready for display.\n\nPlease use HTML and JavaScript to implement a simulation game: Dynamic Weather and Environmental Impact\n**Task**: Implement a dynamic weather system where different weather conditions affect the game environment and player operations.\n**Hint**: You can adjust scene parameters to simulate how weather affects resource production or character behavior.\n\nCreate the game, and include comments in your code to help other developers understand your implementation process.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Weather System Implementation",
-      "description": "Evaluate whether the code implements a comprehensive and dynamic weather system with multiple weather states (rain, snow, sun, wind, etc.) and smooth transitions between them.Score 0 if weather system is absent, 5 if only basic weather states without transitions are implemented, 10 if the system includes at least 5 distinct weather conditions with smooth transition animations and appropriate visual/audio feedback.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Environmental Impact Mechanics",
-      "description": "Check if weather conditions meaningfully impact the game environment (vegetation growth, water levels, terrain conditions, etc.) with visible and logical consequences.Deduct 5 points if weather has no visible impact on environment. Deduct 3 points if the impacts are purely cosmetic without gameplay effects. Full score if at least 3 environmental elements dynamically respond to changing weather conditions.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Player Interaction With Weather",
-      "description": "Assess whether weather conditions affect player operations/actions in meaningful ways (movement speed, ability effectiveness, resource gathering rates, etc.).Score 0 if no player-weather interaction exists, 5 if only simple speed/visibility effects are implemented, 10 if weather creates strategic gameplay choices and adaptive player behaviors.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Weather Prediction and Control Mechanisms",
-      "description": "Evaluate whether the simulation includes weather forecasting, seasonal patterns, or player-influenced weather control mechanisms.Deduct 5 points if weather changes randomly without patterns. Deduct 3 points if no forecasting UI elements exist. Full score for implemented seasonal cycles with predictable patterns and optional player interaction to influence weather.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Code Robustness",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as rapid weather transitions, extreme conditions, 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": "Innovative Features",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Weather-based event triggers 2. Dynamic soundtrack that changes with weather 3. Weather history tracking and statistics).Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Redundant Features",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar weather effects 2. Function modules unrelated to weather/environment simulation 3. Fancy effects that affect performance without adding value to simulation.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": "Engineering Quality",
-      "description": "Review modular design (such as separating weather system/environment/UI layers), code organization, and implementation efficiency.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 no optimization for weather particle rendering is implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Visual Design Quality",
-      "description": "Evaluate whether the weather effects and environmental changes follow modern design principles: 1) Realistic visual representation 2) Proper use of animations and transitions 3) Clear visual distinction between weather states.Deduct 3 points for each unconvincing weather effect, 5 points for jarring transitions between weather states, and 5 points for unclear visual feedback of environmental impacts. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Performance and Optimization",
-      "description": "Judge whether the weather simulation performs efficiently: 1) Maintains 60 FPS during weather transitions 2) Optimizes particle systems and environmental effects 3) Implements appropriate level-of-detail for different device capabilities.Deduct 5 points for noticeable frame drops during weather changes, 3 points for inefficient rendering techniques, and 5 points for lack of optimization options for lower-end devices. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Simulation/Management",
-  "difficulty": "easy"
-}

package/library/game_development-simulation_management/dynastic-family-simulation-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 1176,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Coding Expert Character Generator\n\nYou 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. We need a dynastic family simulation game set in ancient times with a fictional background. Avoid fantasy superpowers, blood, horror, or overly dark themes. Don't include urgent choices, but focus on character development. I am the new family head (16 years old, unmarried), with a mother and underage sibling(s). The game includes ancient professions like officials, scholars, warriors, doctors, merchants, farmers, etc., with distinctions between nobility and commoners. The game primarily focuses on marriage and family drama.\n\nReply settings: Each round should update the time and character information in the main interface in real-time. All information should be wrapped in pseudo-code blocks. Use asterisks for prompts, quotation marks for dialogues, and emoticons for expressions. Display character relationships in a tree diagram. Code blocks should fit mobile display dimensions. Reply \"next month\" to advance to the next month, reply \"restart\" to regenerate character information.\nStarting as an aristocratic family.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the dynastic family simulation game structure fully implemented?",
-      "description": "Review whether the code accurately implements the core game structure with character generation, family relationships, and time progression mechanics. Check if it includes character attributes (age, marital status, profession), family hierarchy, and month-by-month progression as specified.Score 0 if core game structure is missing, 5 if basic character and time progression exists but lacks depth, 10 if it fully implements an interactive family simulation with rich character attributes and meaningful time progression.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the aristocratic family system properly designed?",
-      "description": "Evaluate whether the code implements a comprehensive aristocratic family system with appropriate hierarchies, titles, and social dynamics from ancient times. Check if it includes the 16-year-old unmarried family head, mother, and underage siblings as specified, with proper relationships between them.Deduct 5 points if family hierarchy is poorly implemented, 3 points if social status mechanics are missing, and 5 points if character relationships lack depth. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are the ancient professions and social class distinctions implemented?",
-      "description": "Check if the code includes diverse ancient professions (officials, scholars, warriors, doctors, merchants, farmers) with appropriate mechanics and distinctions between nobility and commoners. Verify that these professions influence gameplay and character interactions.Deduct 3 points for each major profession category missing, 5 points if nobility/commoner distinctions are absent, and 3 points if professions don't meaningfully impact gameplay. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the marriage and family drama system robust?",
-      "description": "Assess if the code implements compelling marriage mechanics and family drama scenarios that drive gameplay. Check if it includes courtship, marriage options, relationship dynamics, and realistic family conflicts appropriate for the ancient setting.Score 0 if marriage systems are absent, 5 if basic marriage options exist but lack depth, and 10 if a comprehensive system with meaningful choices and consequences is implemented. Deduct 5 points if family drama elements are missing.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid inputs, edge cases in character relationships, unexpected game states) 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 personality development system 2. Historical events integration 3. Family reputation mechanics 4. Detailed relationship visualization).Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple character status systems overlapping) 2. Function modules unrelated to dynastic simulation (e.g., unrelated mini-games) 3. Overly complex features that distract from the core experience.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 character logic/view/event systems), consistency in code structure, and maintainability for future extensions.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 organized structure. 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 the specified format requirements: 1) Proper use of pseudo-code blocks 2) Consistent use of asterisks for prompts, quotation marks for dialogues, and emoticons for expressions 3) Clear family relationship tree diagram 4) Mobile-friendly display dimensions.Deduct 3 points for each formatting requirement not met, 5 points for poor character relationship visualization, and 5 points for layouts that would break on mobile displays. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the interaction logic seamless and user-friendly?",
-      "description": "Judge whether the game provides clear interaction mechanisms: 1) Proper implementation of \"next month\" and \"restart\" commands 2) Real-time updating of time and character information 3) Clear presentation of choices and consequences 4) Logical progression of the family narrative.Deduct 5 points if command responses are not implemented correctly, 3 points for unclear information updates, and 5 points if the narrative progression lacks coherence or user agency. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Simulation/Management",
-  "difficulty": "medium"
-}

package/library/game_development-simulation_management/family-dynasty-simulation-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 1605,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and expert responses. Try to ensure that the code you generate is executable for demonstration. I want a family dynasty simulation game with a fictional background - no fantasy, gore, or horror elements, no urgent choices, and more focus on character development. I am the new family head (16 years old and unmarried), and the family includes my mother and underage sibling (brother or sister). The game includes ancient professions like officials, scholars, warriors, doctors, merchants, farmers, etc., and distinguishes between nobles and commoners. The game mainly focuses on marriage and household drama.\n\nReply settings: Each round should update the time and character information in a main interface, with all information enclosed in separate pseudo-code blocks. Use asterisks for prompts, quotation marks for dialogue, and add emoticons for expression. Use a tree diagram to show character relationships, and ensure code blocks fit mobile display dimensions. Reply 'next month' to advance to the next month, or 'restart' to regenerate character information.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the dynasty simulation core system fully implemented?",
-      "description": "Review if the code accurately implements the core dynasty simulation mechanics including time progression mechanism, character age tracking, family relationships management, and social class distinctions (nobles vs commoners). Score 0 if core simulation logic is missing, 5 if only basic time and character tracking exists, and 10 if the system fully models family dynamics, social status effects, and character development across time.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the character development systems properly implemented?",
-      "description": "Evaluate the implementation of character attributes, skills, and development paths related to the specified professions (officials, scholars, warriors, doctors, merchants, farmers). Check if characters have meaningful growth trajectories, realistic personality traits that affect decisions, and career progression mechanics. Deduct 5 points if profession mechanics are superficial, 3 points if character traits don't meaningfully impact gameplay. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the marriage and household drama system comprehensive?",
-      "description": "Assess whether the code implements comprehensive marriage mechanics (courtship, arrangement, compatibility, consequences) and household drama events (conflicts, alliances, betrayals). Check for realistic social dynamics between family members and marriage prospects. Deduct 5 points if marriage is merely cosmetic without gameplay impact, 3 points if household events lack variety. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the interface follow the specified display requirements?",
-      "description": "Verify that all the required interface elements are present: time display, character information in separate pseudo-code blocks, asterisks for prompts, quotation marks for dialogue, emoticons for expressions, and a tree diagram for character relationships. Check if all code blocks fit mobile display dimensions. Deduct 2 points for each missing element, with a minimum score of 0. 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 user inputs, missing character data, unexpected state transitions, 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 character personality evolution 2. Historical events integration 3. Family legacy achievements 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 ways to track the same character stats) 2. Function modules unrelated to dynasty simulation (e.g., mini-games that don't contribute to the narrative) 3. Excessive details that affect readability (e.g., overly complex attribute calculations). 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 character management/event system/display logic), maintainability, and reuse potential. 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 state management architecture. 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) Clear command feedback for 'next month' and 'restart' actions 2) Smooth transitions when updating character information and time progression 3) Readable and intuitive character relationship tree. Deduct 5 points for each operation without feedback, 3 points for cluttered information presentation, and 5 points for hard-to-follow narrative flow. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Simulation/Management",
-  "difficulty": "medium"
-}

package/library/game_development-simulation_management/homemade-3d-minecraft-like-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 814,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate, expert responses. Make sure any code you generate is executable for demonstration. Give me code for a homemade 3D game similar to Minecraft.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the 3D rendering system correctly implemented?",
-      "description": "Evaluate whether the code properly implements WebGL/Three.js for 3D rendering with proper perspective camera setup, viewport management, and frustum culling. Check if shaders are efficiently written for voxel rendering. Score 0 if no 3D rendering is implemented, 5 if basic rendering exists but with performance issues, and 10 if it implements efficient rendering with LOD (Level of Detail) systems.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is procedural terrain generation implemented?",
-      "description": "Assess whether the code implements noise algorithms (Perlin/Simplex) for terrain generation with proper biome differentiation. Check if chunk loading/unloading is implemented with efficient memory management. Deduct 5 points if terrain is static or pre-defined, 3 points if generation lacks variety, and 2 points if chunk boundaries are visible. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Does the game implement block interaction and physics?",
-      "description": "Review whether the code handles block placement, destruction, and interaction with realistic collision detection and response. Verify that ray casting for block selection works correctly. Check if physics simulation includes gravity, fluid dynamics, and entity collision. Score 0 if no interaction exists, 5 if basic interaction without physics, and 10 if full physics with realistic behaviors are implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is world persistence and save system properly designed?",
-      "description": "Evaluate whether the game implements world serialization, efficient storage of modified blocks, and chunk data compression. Check if the save/load system maintains world state including player position, inventory, and modified terrain. Deduct 5 points if saving is manual-only, 3 points if world state is partially lost, and 2 points if saving causes performance freezes. 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 asset loading failures, memory constraints, WebGL context loss, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Dynamic weather system 2. Advanced crafting mechanics 3. Custom shader effects for water/lighting). 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 inventory systems coexisting) 2. Function modules unrelated to the core gameplay (e.g., an overly complex menu system) 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 rendering/game logic/input handling), component architecture, and performant memory management. 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 no optimization techniques are implemented for the rendering pipeline. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional game design standards?",
-      "description": "Evaluate whether the UI design follows modern game principles: 1) Unobtrusive HUD elements 2) Clear inventory and crafting interfaces 3) Proper feedback for player actions (block selection highlighting, breaking animation). Deduct 3 points for each cluttered UI element, 5 points for inconsistent visual style, and 5 points for poor visibility of critical information. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the game maintains consistent FPS (ideally 60+) with smooth camera movement and block interaction. Check if the game implements: 1) Responsive controls (≤50ms input lag) 2) Smooth transitions when crossing chunk boundaries 3) Proper animation for block breaking/placing. Deduct 5 points for each noticeable stutter during gameplay, 3 points for delayed input response, and 5 points for jerky camera movement. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Simulation/Management",
-  "difficulty": "hard"
-}

package/library/game_development-simulation_management/html-qq-farm-simulation-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 1673,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable and can be displayed. Please help me create a simulation farm game similar to QQ Farm, using HTML.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the basic farm layout and grid system fully implemented?",
-      "description": "Review whether the code creates a proper HTML grid system for the farm plot layout. Check if the farm area has clearly defined planting grids, property boundaries, and proper DOM structure. Score 0 if there's no grid system, 5 if there's a basic layout without proper cell management, and 10 if the grid system supports proper plot state management with visual indicators.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the core farming mechanics implemented?",
-      "description": "Evaluate whether essential farming mechanics are present: planting seeds, watering, growth stages, harvesting crops, and storage system. Deduct 3 points if any of these core mechanics are missing. Deduct additional 2 points if the crop lifecycle is too simplified (less than 3 stages). Give full 10 points only if the system includes time-based growth with visual state changes.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is there a proper game economy system?",
-      "description": "Check if the game includes a functional economy with currency, purchasing seeds/items, selling harvested crops, and price variations. Deduct 3 points if there's no purchasing system, 3 points if selling harvested goods isn't implemented, and 4 points if there's no currency display or economic balance. Full score requires a complete economic loop with visual feedback.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there player progression and achievement system?",
-      "description": "Assess whether the game has player progression elements like leveling up, unlocking new crops/items, achievements, or farm expansion capabilities. Deduct 3 points for each missing progression component. The system should include visual indicators of progress and clear reward structures. Full score requires at least 3 different progression mechanics.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid actions, rapid clicking, out-of-sequence operations) and provides friendly error handling. Code with strong robustness should prevent crop state corruption and maintain game consistency. Give 10 points for comprehensive error handling, 5 points for basic validations, and 0 points if the game breaks easily.",
-      "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. Weather system affecting crops 2. Seasonal events/themes 3. Pest management system 4. Farm decoration options). 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 crop growth systems) 2. Function modules unrelated to farming (e.g., a built-in unrelated mini-game) 3. Fancy effects that affect performance (e.g., excessive animations slowing 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 (separation of game logic/view/data management), code organization, and maintainability. Deduct 5 points if global state pollution is found or proper 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 structure for adding new features. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the farm visualizations follow good design principles: 1) Consistent and theme-appropriate visual style 2) Clear visual distinction between interactive and decorative elements 3) Proper visual hierarchy with important game elements prominent. Deduct 3 points for inconsistent visual styles, 5 points for unclear interactive elements, and 5 points for cluttered or visually confusing layouts. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether interactions like planting, harvesting, and purchasing have appropriate feedback: 1) Visual/audio feedback for actions 2) Smooth transitions between game states 3) Intuitive controls with hover effects or tooltips. Deduct 5 points for actions without feedback, 3 points for jarring visual transitions, and 5 points for confusing or hidden controls. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Simulation/Management",
-  "difficulty": "medium"
-}

package/library/game_development-simulation_management/ice-snow-world-survival-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 32,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code when possible.\n\nPlease use HTML and JavaScript to implement an \"Ice and Snow World\" game.\n\nTask: Design an ice and snow world game where players need to survive in an extremely cold environment and complete missions.\n\nSuggestion: Implement ice and snow environment and survival mechanisms.\n\nPlease add comments in your code so other developers can understand your implementation process.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the ice and snow environment fully implemented?",
-      "description": "Review whether the code creates an immersive ice and snow environment through visual elements (snow textures, ice formations, cold-themed color palette) and environmental effects (falling snow, wind effects, fog). Score 0 if the environment is not distinguishable as an ice/snow setting, 5 if basic snow graphics are implemented, and 10 if the environment includes dynamic weather effects and interactive snow physics.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the survival mechanism properly implemented?",
-      "description": "Check whether the code implements core survival mechanics including temperature/cold resistance system, hunger/thirst indicators, energy management, and health tracking. Deduct 3 points if any core survival metric is missing, 5 points if there's no visual feedback on survival status, and 7 points if the survival mechanics don't meaningfully impact gameplay. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are the mission mechanics and progression system implemented?",
-      "description": "Evaluate whether the code includes a structured mission system with clear objectives, progress tracking, and rewards. Check for mission variety (gathering resources, building shelter, reaching locations) and difficulty progression. Deduct 5 points for lack of mission variety, 3 points for missing progress indicators, and 5 points if missions don't connect to a larger progression system. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the player movement and interaction with the environment implemented?",
-      "description": "Assess whether player movement feels responsive in the snow environment (including reduced speed in deep snow, slipping on ice) and if environment interaction is meaningful (gathering resources, building shelter, melting ice/snow). Score 0 if movement mechanics are generic with no snow-specific physics, 5 if basic snow movement is implemented, and 10 if the environment interaction is comprehensive and feels realistic.",
-      "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 temperature system affected by time of day and shelter 2. Realistic snow deformation and footprints 3. Interactive crafting system for survival tools). 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 ice/snow survival (e.g., tropical mini-games) 3. Fancy effects that affect performance (e.g., excessive particle effects that lag 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/environment physics 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) Cold-themed color palette appropriate for an ice world (blues, whites, with limited warm accents for UI elements) 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 inappropriate color combinations that break immersion, 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) Snow/ice movement animations feel natural and physics-based 3) Clear visual feedback for environmental dangers like hypothermia or frostbite. Deduct 5 points for each operation without feedback, 3 points for unnatural snow movement or accumulation, and 5 points for missing vital survival information indicators. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Simulation/Management",
-  "difficulty": "hard"
-}

package/library/game_development-simulation_management/in-game-economic-system-trading.json

@@ -1,68 +0,0 @@
-{
-  "index": 49,
-  "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.\n\nPlease use HTML and JavaScript to implement an in-game economic system.\n\n**Task**: Design an in-game economic system where players can acquire resources or items through trading.\n\n**Hint**: You can create a market interface that allows players to buy and sell items.\n\nPlease include comments in your code so other developers can understand your implementation process.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core economic system logic fully implemented?",
-      "description": "Review whether the code accurately implements the fundamental economic mechanics including resource generation, item creation, pricing algorithms, and supply-demand calculations through HTML/JavaScript. Check if it includes inventory management, transaction validation, and economic balance mechanisms (such as inflation control, market price fluctuation). Score 0 if the core economic logic is not implemented, 5 if only basic buy/sell functions are implemented, and 10 if a complete economic ecosystem with dynamic pricing is included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the market trading interface fully functional?",
-      "description": "Check whether the market interface implementation includes comprehensive trading features: real-time price updates, order book management, transaction history tracking, and search/filter capabilities. Evaluate if it supports different trading modes (instant buy/sell, auction, bidding). Deduct 5 points if transaction confirmation mechanisms are missing, and 3 points if market data visualization is inadequate. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the resource and inventory management system well-designed?",
-      "description": "Evaluate whether the system implements efficient resource tracking, item categorization, and inventory limitations. Check if it includes resource generation rates, item durability/expiration systems, and storage capacity management. Assess whether the data structure supports scalable item attributes and efficient querying. Deduct 5 points if inventory persistence is not implemented, and 3 points if resource calculation accuracy is compromised. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the economic balance and progression system constructed?",
-      "description": "Check whether the code includes sophisticated economic balance mechanisms such as dynamic pricing based on supply-demand, anti-inflation measures, player progression rewards, and market manipulation prevention. Evaluate if it supports different player economic levels and provides meaningful progression paths. Deduct 5 points if economic simulation lacks depth, and 3 points if progression rewards are not balanced. Give 10 points if a comprehensive economic ecosystem is fully implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid transactions, negative values, concurrent trading conflicts, data corruption, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should effectively handle edge cases like simultaneous purchases of limited items, network interruptions during transactions, and invalid user inputs, giving 10 points. If 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 economic experience (e.g., 1. Real-time market trend analytics and charts 2. AI-powered price prediction suggestions 3. Social trading features like guilds or marketplaces 4. Seasonal economic events or limited-time markets 5. Advanced trading tools like portfolio management). 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 economic functions (e.g., multiple pricing calculation methods coexisting) 2. Feature modules unrelated to the economic system (e.g., built-in mini-games) 3. Overly complex animations that affect trading performance (e.g., excessive particle effects on transactions). Deduct 3 points for each redundancy found, and directly deduct 10 points if core economic 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 economic logic/UI/data layers), code documentation quality, and maintainability standards. Evaluate if economic calculations are properly abstracted, if the codebase follows consistent patterns, and if comments adequately explain complex economic algorithms. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if code duplication rate is too high (over 30%); deduct 5 points if insufficient comments make the economic logic hard to understand. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the economic system UI follows modern design principles: 1) Clear data visualization with appropriate charts and graphs 2) Intuitive market interface layout with proper information hierarchy 3) Professional color coding for different economic states (profit/loss, buy/sell orders) 4) Consistent typography and spacing (element spacing follows 8px multiples, font sizes ≥ 14px). Deduct 3 points for each cluttered data display, 5 points for confusing color schemes that hinder economic decision-making, and 5 points for poor information architecture. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the economic system interactions conform to user expectations: 1) Transaction confirmations and price updates with delay ≤ 100ms 2) Smooth transitions between market views (300-500ms) 3) Clear visual feedback for successful/failed transactions 4) Intuitive drag-and-drop for item management 5) Real-time updates without jarring page refreshes. Deduct 5 points for each transaction without proper feedback, 3 points for laggy market data updates, and 5 points for non-intuitive trading interface elements. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Simulation/Management",
-  "difficulty": "medium"
-}

package/library/game_development-simulation_management/space-colony-game-with-resource-management.json

@@ -1,68 +0,0 @@
-{
-  "index": 136,
-  "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 purposes.\n\nPlease use HTML and JavaScript to implement a Space Colony game, where players need to establish colonies in space.\nHint: Implement space environment and resource management.\nInclude comments in the code so that other developers can understand your implementation process.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the space environment visualization properly implemented?",
-      "description": "Review whether the code creates a visually appealing space environment with appropriate celestial bodies, stars, or other space elements using HTML5 Canvas/SVG/WebGL. Check if the environment has depth perception and proper scaling. Score 0 if there's no visual environment, 5 if it's basic/static, and 10 if it has dynamic elements with proper physics representation.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the colony building system fully functional?",
-      "description": "Evaluate whether players can place, upgrade, and manage different types of colony structures. Check if there are different building categories (like habitats, resource extractors, energy generators) with unique functions. Deduct 5 points if buildings lack visual differentiation, 3 points if upgrade paths aren't implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the resource management system comprehensive?",
-      "description": "Check whether the game implements a complete resource economy (oxygen, water, minerals, energy, food) with meaningful collection, storage, consumption, and conversion mechanics. Verify if resource constraints create meaningful gameplay decisions. Deduct 3 points if resource visualization is missing, 5 points if the resource system lacks balance or complexity. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the gameplay loop well-designed with clear progression?",
-      "description": "Assess whether the code implements a satisfying gameplay loop with short-term goals and long-term colony development. Check if there are research systems, milestones or achievements to guide player progression. Deduct 5 points if there's no clear goal structure, 3 points if progression feels linear or lacks meaningful choices. 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, runtime errors, edge cases in game mechanics) 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 disasters like meteor showers or solar flares 2. Colonist needs and happiness systems 3. Procedural generation of space environments). 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 resource tracking systems) 2. Function modules unrelated to space colonization (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 mechanics/view/data management layers), code organization, and maintainability. Evaluate quality of comments as specified in the requirements. 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 comments are missing or unhelpful. 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 (space-appropriate palette with clear contrast) 2) Proper layout spacing (UI elements organized in logical groups with proper hierarchy) 3) Professional font system (readable fonts with good contrast against space backgrounds). Deduct 3 points for each crowded visual element, 5 points for poor color choices that harm readability, and 5 points for chaotic UI organization. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the game interactions feel responsive and intuitive: 1) Building placement and selection feels precise 2) Resource management interfaces update smoothly 3) Clear visual feedback for all player actions. Deduct 5 points for laggy animations, 3 points for confusing interaction models, and 5 points for missing feedback on important game events. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Simulation/Management",
-  "difficulty": "easy"
-}