@getollie/cli 0.0.4 → 0.2.0

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

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

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

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

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

@@ -1,68 +0,0 @@
-{
-  "index": 1609,
-  "question": "You are a coding expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you provide is executable when possible. I want to develop a game similar to Minecraft, but simpler. Please help me develop it with the following requirements: 1. The game should be a web-based 3D game; 2. In this game, players can freely build things using cubes similar to those in Minecraft; 3. Players should be able to select colors for the cubes.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "3D World Rendering Implementation",
-      "description": "Evaluate whether the code properly implements a 3D environment using WebGL/Three.js or similar technology with proper perspective, lighting, and scene management.Score 0 if there's no 3D environment, 5 if there's basic rendering without proper lighting/shadowing, and 10 if the 3D world is fully implemented with proper depth perception, lighting effects, and optimization for web performance.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Cube Creation & Manipulation System",
-      "description": "Check if the code enables players to add, remove, and manipulate cubes in 3D space with appropriate collision detection.Score 0 if cube placement is not implemented, 5 if basic cube adding/removing is available but lacks precision controls, and 10 if the system provides intuitive placement with snapping, rotation options, and collision prevention.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Color Selection & Customization",
-      "description": "Evaluate the implementation of color selection for cubes, including the UI for color picking and application to cubes.Score 0 if color selection is missing, 5 if only basic predefined colors are available, and 10 if there's a full color picker with RGB/HSL controls, color history, and the ability to save favorite colors.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Player Movement & Camera Controls",
-      "description": "Assess the implementation of player movement in the 3D environment and camera controls for different perspectives.Deduct 3 points if WASD/arrow key navigation is missing, 3 points if camera rotation is not smooth, 5 points if first-person and third-person views aren't toggleable. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Code Robustness",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as browser compatibility issues, WebGL support detection, input validation, 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. Texture system for cubes 2. Save/load functionality 3. Physics interactions between cubes).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 functions 2. Function modules unrelated to the building game 3. Fancy effects that affect performance.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 game logic/rendering/UI layers), code organization, and performance optimization.Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if no performance optimizations are implemented for 3D rendering. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Interface Design",
-      "description": "Evaluate whether the UI follows modern design principles: 1) Harmonious color matching 2) Proper layout spacing 3) Unobtrusive controls that don't block the 3D view.Deduct 3 points for each crowded UI element, 5 points for controls that obstruct gameplay, and 5 points for chaotic HUD layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Performance & Optimization",
-      "description": "Judge whether the game runs smoothly with increasing numbers of cubes: 1) Maintains 30+ FPS with 1000+ cubes 2) Implements LOD (Level of Detail) for distant objects 3) Uses efficient data structures for cube storage.Deduct 5 points if FPS drops below 30 with moderate cube count, 3 points if there's no chunk-based rendering for large worlds, and 5 points if memory usage grows linearly with world size without optimization. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Simulation/Management",
-  "difficulty": "medium"
-}

package/library/game_development-simulation_management/web-based-farm-game-html-js-css.json

@@ -1,68 +0,0 @@
-{
-  "index": 1491,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and expert responses. Be careful to ensure that the code you generate is executable and can be displayed. Create a web-based farm game using HTML+JS+CSS.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core farm game system fully implemented?",
-      "description": "Review whether the code accurately implements the farm simulation mechanics through HTML/JavaScript, including crop planting/growing/harvesting cycles, resource management (seeds, water, tools), and economic system (buying/selling). Score 0 if core farming mechanics are missing, 5 if only basic planting is implemented, and 10 if a complete farming ecosystem with growth stages, seasonal effects, and crop varieties is included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the interactive game world properly constructed?",
-      "description": "Check whether the farm environment includes a functional grid-based field system, interactive buildings (barn, shop, house), and inventory management. Evaluate if click/drag interactions for planting and harvesting are smooth and intuitive. Deduct 5 points if the field system lacks proper coordinate mapping, and 3 points if building interactions are non-functional. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the game progression and time management system designed effectively?",
-      "description": "Evaluate whether the game implements a realistic time progression system with day/night cycles, seasonal changes affecting crop growth, and save/load functionality for game state persistence. Check if growth timers work accurately and if the game state can be properly serialized. Deduct 5 points if time progression is unrealistic or inconsistent, and 3 points if save/load functionality is buggy. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the complete game economy and achievement system constructed?",
-      "description": "Check whether the code includes a balanced economic system with currency management, market price fluctuations, and progression rewards. Evaluate if there are achievement milestones, level progression, and unlockable content. Deduct 5 points if the economy is unbalanced or currency system is broken, and 3 points if progression feels unrewarding or unclear. Give 10 points if fully implemented with engaging progression mechanics.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid user inputs, rapid clicking, browser refresh, localStorage errors, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should effectively handle edge cases like negative currency, invalid crop placement, or corrupted save data, 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 gaming experience (e.g., 1. Weather system affecting crop growth 2. Animal husbandry with breeding mechanics 3. Seasonal festivals with special events 4. Crop mutation system 5. Market trading with price predictions). 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 farming (e.g., built-in calculator or unrelated mini-games) 3. Excessive visual effects that impact performance (e.g., constant particle systems or heavy animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if core farming 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/rendering/data persistence layers), code organization, and maintainability. Deduct 5 points if global state pollution is found or no clear separation of concerns; deduct 5 points if code duplication rate is too high (over 30%); deduct 3 points if variable naming is unclear or functions are overly complex. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern game UI principles: 1) Harmonious color palette suitable for farming theme (earth tones, natural colors) 2) Proper spacing and grid alignment for farm elements 3) Readable typography (UI text ≥ 14px, proper contrast) 4) Consistent iconography for tools and crops. Deduct 3 points for each cluttered UI element, 5 points for jarring color combinations, and 5 points for poor visual hierarchy. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the game interactions conform to user expectations: 1) Click feedback delay ≤ 100ms for planting/harvesting 2) Smooth animations for crop growth and UI transitions (200-400ms) 3) Clear visual feedback for all user actions 4) Intuitive drag-and-drop mechanics. Deduct 5 points for each unresponsive interaction, 3 points for jarring or missing animations, and 5 points for confusing user interface elements. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Simulation/Management",
-  "difficulty": "medium"
-}

package/library/game_development-simulation_management/web-based-single-player-cooking-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 1354,
-  "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 when possible. Help me create a web-based single-player cooking game.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the cooking game mechanics fully implemented?",
-      "description": "Review whether the code accurately implements core cooking mechanics through HTML/JavaScript, including ingredient preparation, cooking processes (chopping, frying, boiling, etc.), timing systems, and recipe completion validation. Score 0 if core cooking interactions are not implemented, 5 if only basic ingredient handling is present, and 10 if comprehensive cooking mechanics with multiple recipes and cooking methods are fully included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the game progression and level system implemented?",
-      "description": "Check whether the game includes a structured progression system with multiple levels, difficulty scaling, recipe unlocking mechanisms, and player skill advancement. Evaluate if scoring/rating systems are present for completed dishes. Deduct 5 points if no progression tracking exists, and 3 points if level transitions are abrupt without proper difficulty curves. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the real-time cooking simulation and timing system designed properly?",
-      "description": "Evaluate whether the cooking simulation includes realistic timing mechanisms for different cooking processes, ingredient state changes (raw to cooked), temperature management, and multi-tasking capabilities. Check if players can manage multiple cooking processes simultaneously. Deduct 5 points if timing is unrealistic or inconsistent, and 3 points if no visual feedback is provided for cooking states. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is complete game state management and save functionality constructed?",
-      "description": "Check whether the code includes comprehensive game state management, including progress saving, recipe collection tracking, high score persistence, and game pause/resume functionality. Deduct 5 points if local storage is not implemented for game progress, and 3 points if the game cannot properly resume after interruption. Give 10 points if fully implemented with robust state persistence.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid user inputs, timer conflicts, resource loading failures, 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 cooking game experience (e.g., 1. Recipe suggestion system based on available ingredients 2. Cooking tutorial with interactive guidance 3. Customizable kitchen layouts 4. Sound effects that match cooking actions). 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 timer systems coexisting) 2. Function modules unrelated to cooking games (e.g., built-in social media features) 3. Overly complex animations that affect gameplay performance (e.g., excessive particle effects during cooking). Deduct 3 points for each redundancy found, and directly deduct 10 points if core cooking 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/rendering/input handling), code organization, and maintainability. Deduct 5 points if global state pollution is found or proper architecture patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 3 points if functions are not properly documented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional game design standards?",
-      "description": "Evaluate whether the visual design follows modern game UI principles: 1) Cohesive color scheme that fits cooking theme (warm, appetizing colors) 2) Proper visual hierarchy with clear ingredient/tool identification 3) Consistent iconography and typography (readable fonts ≥ 14px). Deduct 3 points for each cluttered interface element, 5 points for poor color choices that hinder gameplay, and 5 points for confusing visual layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the interactive gameplay smooth and engaging?",
-      "description": "Judge whether the game interactions provide satisfying feedback: 1) Immediate response to player actions (≤ 100ms) 2) Smooth drag-and-drop for ingredients with proper visual feedback 3) Clear audio-visual cues for cooking progress and completion 4) Intuitive controls that don't require extensive learning. Deduct 5 points for each unresponsive interaction, 3 points for confusing control schemes, and 5 points for lack of satisfying feedback mechanisms. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Simulation/Management",
-  "difficulty": "hard"
-}

package/library/game_development-simulation_management/web-electronic-pet-raising-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 1180,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code where possible. Design a web-based mini-game, an electronic pet raising game.\n\nPlayers can choose pets shaped like kittens, puppies, ponies, etc. Once a pet is selected, players cannot choose another one.\n\nThe pet can run, jump, lie down, and sleep on the screen.\n\nThe pet has a hunger bar with 100 points, which decreases by 1 point every half hour. The bar has different colors for each 30% segment.\n\nWhen the hunger bar is completely depleted, the pet will die and cannot be revived.\n\nProvide three types of food for players to feed their pets, which can increase the hunger bar by 5%, 10%, and 15% respectively.\n\nProvide three types of toys for players to interact with their pets. Each toy can decrease the pet's hunger bar by 5%, 10%, and 15% respectively.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the pet creation and selection system fully implemented?",
-      "description": "Check if the code allows players to select from different pet types (kittens, puppies, ponies) with distinct visual representations. Verify that once a pet is selected, the selection cannot be changed. Evaluate if pet selection is properly persisted in local storage or a database, and if the UI clearly indicates the selection is permanent.10 points maximum. Deduct 5 points if pet selection isn't permanent. Deduct 3 points if fewer than 3 pet types are implemented. Deduct 2 points if pet selection isn't visually intuitive or lacks confirmation dialog. Score 0 if pet selection system is missing entirely.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are all pet animations and behaviors correctly implemented?",
-      "description": "Evaluate whether the required pet behaviors (running, jumping, lying down, sleeping) are implemented with smooth animations and clear visual distinction. Check if animations transition naturally between states and if they respond to player interactions or environmental changes appropriately.15 points maximum. Award 3-4 points for each well-implemented animation (running, jumping, lying down, sleeping). Deduct 3 points if animations are jerky or unnatural. Deduct 5 points if animations don't properly represent the intended behavior. Score 0 if animations are missing entirely.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the hunger system properly implemented with visual indicators?",
-      "description": "Check if the hunger bar starts at 100 points, decreases at the specified rate (1 point every half hour), and changes colors for each 30% segment. Verify that the game correctly detects when hunger reaches zero and implements the death state properly. Validate that hunger persists between sessions.15 points maximum. Deduct 5 points if hunger doesn't decrease at the specified rate. Deduct 3 points if color segments aren't implemented. Deduct 5 points if death state isn't properly handled. Deduct 3 points if hunger doesn't persist between sessions.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are the feeding and toy interaction systems complete?",
-      "description": "Evaluate whether the three types of food and three types of toys are visually distinct and whether they affect the hunger bar by the specified percentages. Check if the feeding/play animations are satisfying and if there are appropriate cooldown mechanisms to prevent spam.10 points maximum. Deduct 2 points for each missing food or toy type. Deduct 3 points if hunger effects don't match specifications. Deduct 2 points if feeding/playing lacks appropriate animations or feedback. Score 0 if systems are completely missing.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as browser refreshes, interruptions, inconsistent timing intervals, etc.) and provide friendly error prompts or recovery mechanisms. Verify that game state is properly saved and restored.10 points maximum. If the robustness is strong with proper error handling and state management, give 10 points. If the robustness is average with some error handling, give 5 points. 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. Weather effects influencing pet behavior 2. Day/night cycle affecting sleep patterns 3. Pet personality traits that evolve over time 4. Social sharing features).10 points maximum. 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 hunger tracking mechanisms) 2. Function modules unrelated to pet raising (e.g., a built-in calculator) 3. Fancy effects that affect performance (e.g., unnecessary 3D renders or particle effects).10 points maximum. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating game logic/view layers), unit test coverage, and build process automation. Check for proper use of design patterns, code organization, and maintainability.10 points maximum. 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.",
-      "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) 4) Appropriate pet design that feels cohesive with the UI.10 points maximum. Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. Deduct 3 points if the pet designs clash with the UI style.",
-      "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 4) Pet responds naturally to interactions.10 points maximum. Deduct 5 points for each operation without feedback, 3 points for visual after-images during animations, and 5 points for hard-to-find key function buttons. Deduct 3 points if pet interactions feel delayed or unnatural.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Simulation/Management",
-  "difficulty": "medium"
-}

package/library/game_development-sports/3d-first-person-racing-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 1495,
-  "question": "You are a coding expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the generated code is executable for demonstration. Create a racing game with a first-person driver's perspective, allowing for left and right turns, acceleration and deceleration based on the track. The track should resemble a realistic three-dimensional racing circuit.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the first-person 3D racing view accurately implemented?",
-      "description": "Review whether the code correctly implements a first-person perspective camera system using WebGL/Three.js or Canvas 3D, including proper field of view (FOV 60-90°), camera positioning inside the cockpit, and realistic depth perception. The view should include dashboard elements and steering wheel. Score 0 if only 2D top-down view is provided, 5 if basic 3D view without cockpit details, and 10 if full immersive first-person racing experience with proper perspective projection.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the vehicle physics and control mechanics realistic?",
-      "description": "Check whether the implementation includes proper physics simulation for acceleration, deceleration, steering dynamics, and momentum conservation. Vehicle should have inertia, drift mechanics, speed-dependent turning radius, and realistic braking distance. Keyboard/gamepad controls should be responsive with proper input mapping (WASD/Arrow keys for steering, acceleration/braking). Deduct 5 points if physics feel arcade-like without momentum, 3 points if steering lacks progressive response. Full score requires realistic vehicle dynamics.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the 3D racing track properly designed and rendered?",
-      "description": "Evaluate whether the track features realistic 3D geometry with proper banking, elevation changes, curves of varying difficulty, and track boundaries. Track should include visual elements like barriers, grass/gravel run-off areas, start/finish line, and lap markers. Texture mapping and lighting should create depth and realism. Deduct 5 points if track is flat without elevation, 3 points if missing proper track boundaries or visual landmarks. Full score requires professional circuit-like design.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the complete racing game loop implemented?",
-      "description": "Check whether the code includes essential racing features: lap counting system, timing/speed display, race start countdown, finish line detection, and basic HUD (speedometer, lap counter, position). Should handle race completion, lap records, and restart functionality. Deduct 5 points if lap detection is inaccurate, 3 points if missing essential HUD elements, 2 points if no timing system. Give 10 points if all core racing mechanics are properly implemented with accurate tracking.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as collision detection edge cases, frame rate drops, browser compatibility issues, memory leaks in 3D rendering, invalid input states) and provide appropriate fallbacks or error handling. Code should gracefully handle WebGL context loss and provide meaningful error messages. Give 10 points for comprehensive error handling, 5 points for basic exception management, and 0 points if no error handling is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that enhance the racing experience?",
-      "description": "Check whether the code includes engaging features that elevate the gameplay (e.g., 1. Realistic engine sound effects with Doppler effect 2. Dynamic weather/lighting conditions 3. Multiple camera angles 4. Ghost car for lap comparison 5. Particle effects for tire smoke/sparks). Add 3 points for each well-implemented innovative feature that adds value to the racing experience (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant rendering pipelines or duplicate 3D model loading 2. Unnecessary non-racing features (e.g., built-in chat system, unrelated mini-games) 3. Performance-heavy visual effects that don't enhance racing (e.g., excessive particle systems, overly complex shaders). Deduct 3 points for each redundancy found, and directly deduct 10 points if core racing performance is significantly impacted by bloated features.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular architecture separating rendering engine, physics simulation, input handling, and game state management. Check for proper asset loading optimization, frame rate management (targeting 60fps), and memory usage patterns. Deduct 5 points if global state pollution or poor separation of concerns; deduct 5 points if code duplication rate exceeds 30% or lacks consistent coding patterns; deduct 5 points if no performance optimization considerations for 3D rendering. Full score requires clean, maintainable architecture.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional racing game standards?",
-      "description": "Evaluate whether the visual design follows modern racing game UI principles: 1) High contrast HUD elements clearly visible against track background 2) Realistic color palette with appropriate track surface textures 3) Professional typography for racing data (lap times, speed) with adequate sizing (≥16px for critical info). Deduct 3 points for each cluttered HUD element, 5 points for poor contrast affecting readability, and 5 points for unrealistic or distracting visual styling that breaks immersion.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the racing performance smooth and responsive?",
-      "description": "Judge whether the game performance meets racing standards: 1) Consistent frame rate ≥30fps (preferably 60fps) during gameplay 2) Input lag ≤50ms for steering responsiveness 3) Smooth camera movement without stuttering during high-speed sections 4) Proper LOD (Level of Detail) management for distant track elements. Deduct 5 points for each noticeable frame drop during normal racing, 3 points for input delay affecting control precision, and 5 points for camera jitter or motion sickness-inducing movement.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Sports",
-  "difficulty": "hard"
-}