@getollie/cli 0.0.1

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

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

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

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

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

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

package/library/game_development-simulation_management/star-maker-entertainment-agency-simulation.json

@@ -0,0 +1,68 @@
+{
+  "index": 385,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Star-Maker: The Entertainment Agency Simulation\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. This is a game about cultivating stars, set in a fictional modern background that is peaceful and comfortable. No fantasy, gore, horror, poisoning, birthmarks, metaphors, revenge plots, previous dynasties, or urgent choices. Focus on development/growth aspects.\n\nI am a talent manager at a small entertainment company who also mentors the rookie Pei Yu (male, 24 years old, single, attracted to men, submissive). In the game, you can develop yourself or recruit artists, book gigs for them, and gradually develop them into singers, actors, idols, etc. in this management-style game. The game features other modern professions with a storyline background that doesn't exceed current technological capabilities. The game primarily focuses on management and character development plotlines.\n\nRelationship developments should progress naturally, with realistic scenarios and dialogue matching character personalities. In intimate scenes, use more casual, explicit language. You can use parentheses to show physical actions or thoughts, creating embarrassing, intense emotional experiences with detailed physiological reactions. Avoid using poison plots, scheming, memory fragments, or active seduction.\n\nCharacter information should include personality, preferences, and descriptions of facial features and physical characteristics. Reply settings: Each round should include real-time updates of time, company status, and character information on the main interface. All information should be wrapped in pseudo-code blocks. Use asterisks for prompts, quotation marks for dialogue, and add emojis for expression. Use tree diagrams to show character relationship networks. Code blocks should fit mobile display dimensions.\n\nReply \"Continue\" to advance to the next week, reply \"Restart\" to regenerate character information.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the entertainment agency simulation system fully implemented?",
+      "description": "Review whether the code accurately implements the core management mechanics through HTML/JavaScript, including talent recruitment, booking gigs, and artist development systems. Check if character progression paths (singers, actors, idols) are clearly defined with distinct attributes and career trajectories.Score 0 if the core management system is not implemented, 5 if only basic talent management exists, and 10 if the complete ecosystem with different career paths, attribute progression, and gig booking mechanics are fully included.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the character development and relationship system implemented?",
+      "description": "Evaluate the code implementation of character relationships, personality traits, and natural progression of relationships. Check if the system tracks and updates relationship values, displays character information (personality, preferences, physical characteristics), and implements realistic dialogue matching character personalities.Deduct 5 points if character attributes don't influence interactions, 3 points if relationship progression lacks depth or variety. The full score is 10 points if the system has multi-dimensional relationship tracking with context-sensitive interactions.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the time management and company status tracking system implemented?",
+      "description": "Check if the code includes a comprehensive time management system (weeks/months progression), company status tracking (finances, reputation, resources), and how these elements affect gameplay. Verify if the interface displays real-time updates of time and company status.Deduct 5 points if time progression doesn't meaningfully impact gameplay, 3 points if company metrics are static or don't influence decision-making. Give 10 points if time and company management create dynamic gameplay with clear consequences and strategic depth.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the user interface/experience appropriate for the game concept?",
+      "description": "Assess if the interface follows the requirements: displays character information, company status, and time on the main interface; uses asterisks for prompts, quotation marks for dialogue, and emojis for expressions; implements tree diagrams for character relationship networks; and ensures code blocks fit mobile display dimensions.Deduct 2 points for each missing UI element (relationship trees, status display, etc.), 5 points if mobile optimization is absent. Give 10 points if all required elements are present and the UI enhances the management simulation experience.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common edge cases and user inputs (invalid commands, unexpected interactions, etc.) and provide friendly error prompts or recovery mechanisms. The code should gracefully handle state transitions and prevent game-breaking bugs.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 market trends affecting artist popularity 2. Special events or scandals that require management decisions 3. Detailed artist development skill trees 4. Fan base management systems).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 management functions 2. Function modules unrelated to entertainment agency simulation (e.g., unrelated mini-games) 3. Fancy effects that affect performance without enhancing 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 models), code organization, and maintainability. Check if the code follows object-oriented principles appropriate for a simulation game with complex state 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 the code lacks clear documentation or 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 modern design principles: 1) Harmonious color matching appropriate for an entertainment agency theme 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) 4) Clear information hierarchy for management interfaces.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 for management actions 4) Appropriate feedback when booking gigs or developing artists.Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast interaction, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Simulation/Management",
+  "difficulty": "hard"
+}

package/library/game_development-simulation_management/traffic-light-game.json

@@ -0,0 +1,68 @@
+{
+  "index": 879,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be careful to ensure the code you generate is executable for demonstration. Help me create a traffic light game using web technologies. When opened, it shows an interface where clicking the plus button allows you to create new traffic lights, including pedestrian signals, road traffic lights, and various arrow-style traffic lights, etc. Please develop this into a playable game.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the traffic light creation system fully implemented?",
+      "description": "Review whether the code implements a flexible traffic light creation system. Check if users can add different types of traffic lights (standard road lights, pedestrian signals, arrow lights) through the plus button interface. Score 0 if creation functionality is missing, 5 if only one type of traffic light can be created, and 10 if multiple customizable traffic light types are implemented with proper visual differentiation.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the traffic light state management system properly implemented?",
+      "description": "Evaluate whether the code includes a proper state management system for traffic lights (red-yellow-green cycles, pedestrian wait-walk states, arrow signals). Check for timing mechanisms, state transitions, and realistic traffic light behavior. Deduct 5 points if lights don't follow real-world timing patterns, 3 points if state transitions lack animations. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the game component implemented with proper interaction logic?",
+      "description": "Check if the implementation includes actual game mechanics (such as scoring, challenges, timing constraints or traffic management scenarios). Verify if win/loss conditions exist and whether player actions have meaningful consequences. Score 0 if no game elements exist, 5 if basic interactivity without objectives is present, 10 if complete game mechanics with clear objectives are implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the traffic coordination system implemented?",
+      "description": "Assess whether multiple traffic lights can coordinate with each other (e.g., intersection management, sequential timing, conflicting traffic prevention). Check if the game implements realistic traffic flow patterns. Deduct 5 points if lights operate independently without coordination, 3 points if coordination exists but with unrealistic patterns. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as rapid clicking, adding too many lights, improper user interactions) 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. Day-night cycle affecting visibility 2. Weather conditions impacting traffic 3. Vehicle/pedestrian animations responding to signals). 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 traffic light controls 2. Function modules unrelated to traffic management 3. Fancy effects that affect performance (e.g., unnecessary particle effects or animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating traffic light logic/view/controller layers), object-oriented principles for traffic light entities, and code 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 event handling is poorly implemented. 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) Realistic traffic light rendering with proper proportions and colors 2) Proper layout spacing for controls and game elements 3) Professional UI for game controls and feedback. Deduct 3 points for each visually inaccurate traffic light element, 5 points for poor control placement, and 5 points for chaotic visual hierarchy. 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) Traffic light transitions occur with appropriate timing and animations 2) Light state changes are clearly visible with proper visual feedback 3) UI controls respond promptly to user input. Deduct 5 points for abrupt light transitions without animations, 3 points for delayed response to user clicks, and 5 points for confusing or inconsistent traffic light behavior. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Simulation/Management",
+  "difficulty": "medium"
+}

package/library/game_development-simulation_management/weather-effects-dynamic-environment-system.json

@@ -0,0 +1,68 @@
+{
+  "index": 127,
+  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Try to ensure the generated code is executable for demonstration.\n\nPlease use HTML and JavaScript to implement a Weather Effects and Dynamic Environment system.\n\n**Task**: Implement a weather effects system where different weather conditions (such as storms, dense fog) will affect character movement, vision, or abilities.\n\n**Hint**: You can simulate the impact of weather on the game by changing scene lighting, wind speed, slippery surfaces, etc.\n\nPlease include comments in your code so other developers can understand your implementation process.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core weather effect system fully implemented?",
+      "description": "Review whether the code accurately creates different weather conditions (rain, snow, fog, etc.) using HTML5 Canvas or WebGL. Check if each weather type has unique visual representations. Score 0 if no weather effects are implemented, 5 if only basic effects (like simple rain) exist, and 10 if there are at least 4 distinct weather types with proper particle systems and physics.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the dynamic environment interaction implemented?",
+      "description": "Evaluate whether weather effects actually impact the environment/character in meaningful ways (slippery surfaces during rain, reduced visibility in fog, slowed movement in snow, etc.). Check if these interactions are properly calculated and applied to movement mechanics. Score 0 if no interaction exists, 5 if basic interactions are present but inconsistent, and 10 if weather comprehensively affects multiple game aspects with appropriate physics.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the weather transition system implemented?",
+      "description": "Assess whether the code implements smooth transitions between different weather states rather than abrupt changes. Check for gradual parameter modifications (opacity, intensity, particle count) and appropriate easing functions. Deduct 5 points if transitions are absent, 3 points if transitions exist but are visually jarring. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are the environmental elements responsive to weather?",
+      "description": "Examine if the implementation includes responsive environmental elements (trees swaying in wind, puddles forming in rain, fog affecting light sources). Check for physics-based responses and not just visual overlays. Score 0 if environment is static regardless of weather, 5 if simple responses exist, and 10 if the environment has complex, physically-accurate reactions to weather conditions.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as rapid weather changes, extreme parameter values, browser compatibility issues, etc.) and provide fallback mechanisms. Code with strong robustness should maintain performance under stress and gracefully degrade on weaker devices, 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 sound effects that change with weather intensity 2. Weather affecting lighting and shadows realistically 3. Interactive elements like user-controlled weather manipulation). 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 effects (e.g., multiple rain systems running simultaneously) 2. Function modules unrelated to weather effects (e.g., unnecessary game mechanics) 3. Excessive effects that affect performance (e.g., too many particles causing lag). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating weather systems, environmental responses, and rendering), code reusability, and performance optimization. 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 no performance considerations are implemented (like particle pooling or LOD). The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the visual effects follow modern graphics principles: 1) Appropriate particle density and distribution 2) Realistic color grading for different weather conditions 3) Proper depth and parallax effects. Deduct 3 points for unrealistic weather visualization, 5 points for poor particle system implementation (uniform/unnatural distribution), and 5 points for inconsistent lighting across weather types. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the weather effects maintain consistent framerates (minimum 30fps): 1) No stuttering during weather transitions 2) Efficient particle management 3) Proper use of hardware acceleration. Deduct 5 points for noticeable fps drops during heavy effects, 3 points for delayed environmental responses to weather changes, and 5 points for particle systems that don't scale based on device capabilities. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Simulation/Management",
+  "difficulty": "easy"
+}