@getollie/cli 0.0.5 → 0.2.1

package/library/game_development-role-playing/sect-building-character-recruitment-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 1620,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Try to ensure that the generated code is executable for display. I want a game about building a sect, with a fictional background, avoiding fantasy, blood, horror, urgent choices, and focusing more on character development. I am the new sect master (16 years old, unmarried), with a family that includes my mother and a minor sibling (brother or sister). The game mainly focuses on recruiting disciples and expanding the sect storyline.\n\nResponse settings: For each round, update the time and character information in the main interface in real-time, wrap all information in separate pseudo code blocks, use asterisks for prompts, quotation marks for dialogues, add emoji expressions, use tree diagrams to show character relationship networks, and ensure code blocks fit mobile display dimensions. Reply \"next month\" to advance to the next month, reply \"restart\" to regenerate character information.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the sect building game foundation completely implemented?",
-      "description": "Check if the code implements the core game mechanics including time progression system, character attribute tracking, and sect management features. The implementation should handle the player as a 16-year-old sect master with family relationships (mother and sibling). Score 0 if core game loop is missing, 5 if basic mechanics exist but lack depth, 10 if comprehensive sect building mechanics are implemented with proper character relationships.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the disciple recruitment and character development system implemented?",
-      "description": "Evaluate the disciple recruitment mechanism, character attribute growth system, and relationship development features. Check if characters have unique personalities, backgrounds, and development paths. Disciples should have their own motivations and growth trajectories. Deduct 5 points if characters lack distinct personalities, 3 points if growth mechanics are simplistic or linear, and 5 points if there's no meaningful character interaction system.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the time progression and event system properly implemented?",
-      "description": "Review the 'next month' functionality that advances game time and triggers appropriate events. Check if the system includes random events, scheduled storylines, and consequences of previous choices. Event probability should be balanced, with event chains that build on previous player decisions. Deduct 5 points if time progression is buggy, 3 points if events are too repetitive or disconnect from context, and 5 points if there's no state persistence between time jumps.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the character relationship network visualization properly implemented?",
-      "description": "Assess the tree diagram implementation for character relationship networks. The visualization should be clear, interactive, and update dynamically as relationships evolve. Check if the relationships show hierarchy, loyalty, affection and other relevant metrics between sect master, family members, and disciples. Deduct 5 points if the visualization is static, 5 points if relationships aren't properly tracked in the data model, and 8 points if the tree diagram is unreadable or doesn't render properly on mobile.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid user inputs, edge cases in character interactions, corrupt game state) 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 story generation based on character traits 2. Procedurally generated sect challenges 3. Complex faction dynamics with rival sects). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple character creation systems) 2. Function modules unrelated to sect building (e.g., unnecessary mini-games) 3. Fancy effects that affect performance (e.g., excessive animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating game logic/view/data management layers), code organization, and maintainability. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no clear separation between presentation and game logic. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern 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 formatting of pseudo code blocks, asterisks for prompts, and quotation marks for dialogues. Deduct 3 points for each crowded visual element, 5 points for inconsistent emoji usage, and 5 points for poor mobile display optimization. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the storytelling and narrative design compelling and appropriate?",
-      "description": "Judge whether the narrative avoids fantasy, blood, horror, and urgent choices as specified, while focusing on character development. Evaluate if the storytelling provides meaningful choices, avoids clichés, and creates an engaging progression for the young sect master. Deduct 5 points for inappropriate content, 3 points for shallow character development, and 5 points for restrictive or railroaded storytelling without player agency. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Role-Playing",
-  "difficulty": "medium"
-}

package/library/game_development-role-playing/spirit-summoning-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 12,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Try to ensure that the generated code is executable for demonstration.\nPlease use HTML and JavaScript to implement a \"Spirit Summoning\" game.\n**Task**: Allow players to summon spirits or pets to assist in battles or puzzle-solving. Spirits can have different abilities and behavior patterns.\n**Hint**: You can set up a summoning system and design unique skills or characteristics for each spirit to help players complete tasks. Please think through and answer in detail, striving to implement a solution that is as complete as possible, meets the requirements, has a good game interface, and high playability. Note: The functionality should be implemented using HTML that can be executed directly in the frontend.\nPlease include comments in your code to help other developers understand your implementation process.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core spirit summoning mechanic fully implemented?",
-      "description": "Review whether the code accurately implements a spirit summoning system through HTML/JavaScript, including a clear summoning interface, selection mechanism, and successful/failed summoning feedback. Check if summoned spirits appear visually on screen with distinct appearances. Score 0 if summoning doesn't work, 5 if basic summoning exists but lacks variety, and 10 if there's a complete summoning system with multiple spirits and visual effects.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the spirits' unique abilities and behavior patterns well-designed?",
-      "description": "Evaluate whether each spirit has distinct abilities (attack patterns, special skills, passive effects) and behavior patterns (movement, AI decision-making). Check if spirits react differently to game situations and player commands. Deduct 3 points if spirits are merely cosmetic with no functional differences, 5 points if abilities exist but lack strategic depth, and 7 points if behavior patterns are static/predictable. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is there a meaningful battle or puzzle-solving system where spirits assist?",
-      "description": "Assess whether the game includes challenges (battles or puzzles) where spirits provide meaningful assistance. Check if different spirits offer strategic advantages in different scenarios. Deduct 5 points if challenges are trivial or spirits' contributions are negligible, and 3 points if the system lacks strategic depth. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there a progression or enhancement system for spirits?",
-      "description": "Check for implementation of growth mechanics such as leveling up spirits, unlocking new abilities, upgrading existing skills, or spirit evolution. Verify if player actions influence spirit development and if the system provides clear feedback on progression. Score 0 if no progression exists, 5 if basic progression with minimal impact on gameplay, and 10 if comprehensive progression with meaningful effects on gameplay.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid inputs, unexpected interactions, rapid clicking, 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 spirit fusion system 2. Environmental interaction between spirits 3. Spirit personality system affecting behaviors). 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 spirit selection methods that do the same thing) 2. Function modules unrelated to the core gameplay (e.g., unnecessary mini-games that distract from the main experience) 3. Fancy effects that affect performance (e.g., excessive particle effects 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 game logic/view/spirits behavior layers), code organization, quality of comments, and maintainability. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if comments are insufficient or misleading. 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 (thematic colors appropriate for a mystical/spiritual game) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Summoning feedback delay ≤ 100ms 2) Spirit animation transitions controlled between 300-500ms 3) Clear visual indication of spirit actions and abilities. Deduct 5 points for each operation without feedback, 3 points for choppy animations during spirit actions, and 5 points for unclear spirit status indicators. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Role-Playing",
-  "difficulty": "medium"
-}

package/library/game_development-role-playing/stress-relief-mini-game-equipment-level-progression.json

@@ -1,68 +0,0 @@
-{
-  "index": 704,
-  "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. Help me create a fun stress-relieving mini-game that includes equipment elements, level progression, free exploration features, and gradually increasing difficulty.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core game mechanics properly implemented?",
-      "description": "Review whether the code establishes a complete game loop with clear stress-relieving mechanisms. Check for well-defined player interactions, feedback systems, and measurable stress reduction elements. Score 0 if core mechanics are absent, 5 if basic interactions exist but lack engagement, and 10 if the game successfully implements scientifically-backed stress relief mechanisms (e.g., rhythmic interactions, progressive muscle relaxation, or mindfulness elements).",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the equipment system fully functional?",
-      "description": "Evaluate the implementation of equipment collection, management, and utilization. Check for item properties, inventory system, equipment effects on gameplay, and upgrade mechanisms. Deduct 5 points if equipment is purely cosmetic without gameplay impact, 3 points if balance issues exist between items, and 2 points if the equipment UI is unintuitive. Full score requires equipment that meaningfully impacts gameplay with clear progression paths.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the level progression system properly designed?",
-      "description": "Assess whether the code implements a structured level progression with increasing complexity, appropriate difficulty curves, and meaningful rewards. Check for score tracking, achievement systems, and player progress persistence. Deduct 5 points if levels are repetitive without new challenges, 3 points if difficulty spikes are too severe, and 3 points if progression metrics aren't clearly communicated to the player. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the free exploration feature effectively implemented?",
-      "description": "Review the implementation of non-linear exploration elements, such as discoverable areas, hidden content, or branching paths. Check for player agency in navigation, discovery mechanisms, and exploration rewards. Deduct 5 points if exploration areas are too restrictive, 3 points if discovered content lacks meaningful impact, and 3 points if navigation controls are unintuitive. Full implementation should balance guided experience with player freedom.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid inputs, browser compatibility issues, device orientation changes, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle edge cases without crashing, 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 stress-relief experience (e.g., 1. Personalized stress tracking 2. Dynamic difficulty adjustment based on performance 3. Mindfulness or breathing exercises integrated into gameplay). 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 mechanics (e.g., multiple progress tracking systems) 2. Function modules unrelated to stress relief or game progression 3. Excessive visual effects that may increase cognitive load rather than reduce stress. Deduct 3 points for each redundancy found, and directly deduct 10 points if core stress-relieving functions are compromised by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating game state/view/controller layers), reusability of components, and performance optimization. Deduct 5 points if global state is managed inefficiently; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the game performance degrades noticeably during extended play sessions. 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 stress relief (calming palette with no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each visually overwhelming element, 5 points for color combinations that induce anxiety, 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 and stress-relief goals: 1) Immediate feedback on player actions (≤ 100ms) 2) Soothing transition animations (300-500ms duration) 3) Clear visual hierarchy and intuitive controls. Deduct 5 points for each operation without feedback, 3 points for jarring or abrupt animations, and 5 points for confusion-inducing UI elements. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Role-Playing",
-  "difficulty": "medium"
-}

package/library/game_development-role-playing/text-based-character-homepage-attribute-panel-xiao-ke.json

@@ -1,68 +0,0 @@
-{
-  "index": 1269,
-  "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 display purposes. Create a text-based character homepage attribute panel for a character named Xiāo Kè.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the basic character attribute panel structure properly implemented?",
-      "description": "Check if the code implements the fundamental structure of a character attribute panel including name display (Xiāo Kè), basic attributes (e.g., strength, agility, intelligence), health/mana indicators, and level information. Score 0 if there is no clear panel structure, 5 if only basic name and limited attributes are shown, and 10 if a complete and well-organized attribute panel is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the text-based visualization properly executed?",
-      "description": "Evaluate whether the code effectively utilizes text characters (ASCII art, Unicode symbols, or other text elements) to create visual appeal without relying on images. Check for proper alignment, consistent spacing, and meaningful use of symbols to represent different attributes. Deduct 5 points if alignment is inconsistent, 3 points if spacing issues exist, and 5 points if the visualization is barely readable.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the character name 'Xiāo Kè' correctly displayed with proper formatting?",
-      "description": "Verify if the character name 'Xiāo Kè' is properly displayed with the correct diacritical marks and appropriate prominence in the panel. Check if the name is styled to stand out from other elements and whether proper character encoding is used for the special characters. Deduct 5 points if diacritical marks are missing or incorrect, 3 points if the name doesn't stand out visually.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the implementation include interactive elements for the attribute panel?",
-      "description": "Check if the code includes interactive features like hovering for additional information, expanding/collapsing attribute sections, ability to edit/update attributes, or keyboard navigation through the panel. Score 0 if no interaction is implemented, 5 if minimal interactions exist, and 10 if comprehensive interactive features are included.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as missing data, wrong input types, browser compatibility issues, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. ASCII art animations 2. Dynamic attribute changes based on time/actions 3. Terminal-like effects or typewriter animations). 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 display functions 2. Feature modules unrelated to character attributes 3. Fancy effects that affect readability or 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": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating data/view/controller layers), code organization, and maintainability. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the naming conventions are inconsistent or unclear. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the text-based design follows clear visual principles: 1) Consistent character usage for borders and separators 2) Logical grouping of related attributes 3) Proper use of whitespace and alignment principles. Deduct 3 points for inconsistent character usage, 5 points for illogical attribute grouping, and 5 points for poor spacing that affects readability. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects (if any) conform to human perception characteristics: 1) Immediate feedback for user interactions 2) Appropriate animation timing for text effects (150-300ms) 3) Clear focus states and navigation cues. Deduct 5 points for each operation without feedback, 3 points for overly long animations that delay information display, and 5 points for confusing navigation. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Role-Playing",
-  "difficulty": "easy"
-}

package/library/game_development-role-playing/text-based-immortality-pill-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 748,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable when presented. Help me write a text-based game about cultivating immortality and pill refining that can be used directly in WeChat Developer Tools without any errors.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core cultivation system properly implemented?",
-      "description": "Review whether the code accurately implements the cultivation levels, skill progression, and attribute system. Check if there are clear advancement mechanisms with distinct stages (e.g., Qi Condensation, Foundation Establishment, Core Formation). Score 0 if cultivation mechanics are absent, 5 if basic levels exist but lack depth, and 10 if there's a comprehensive system with meaningful progression choices.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the pill refining gameplay loop complete?",
-      "description": "Evaluate the implementation of the pill refining system, including ingredient collection, recipe discovery, refining process, and success/failure mechanics. Check for variables that affect outcomes (ingredient quality, player skill, equipment). Deduct 5 points if the refining process is overly simplistic, 3 points if ingredient variety is limited. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the game state management properly implemented?",
-      "description": "Check whether the code includes proper game state persistence using WeChat storage APIs (wx.setStorage/wx.getStorage). Verify save/load functionality works correctly and handles different game states appropriately. Deduct 5 points if state is lost between sessions, 3 points if critical game elements aren't preserved. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the WeChat Mini Program integration complete?",
-      "description": "Assess whether the code properly integrates with the WeChat Developer Tools environment, using appropriate WeChat APIs and following Mini Program best practices. Check for proper page structure, lifecycle hooks implementation, and adherence to WeChat's restrictions. Deduct 5 points for improper API usage, 5 points for incompatible code patterns. 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, unexpected user actions, 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 events based on real-world time 2. Random encounters with other cultivators 3. Special secret techniques discovery system). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple inventory systems coexisting) 2. Function modules unrelated to cultivation/refining (e.g., a built-in calculator) 3. Features that affect performance unnecessarily (e.g., excessive animations in a text-based game). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating game logic/view/data layers), code organization, and maintainability. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no clear structure for game components. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface text meet professional design standards?",
-      "description": "Evaluate whether the text presentation follows good design principles: 1) Consistent terminology for cultivation terms 2) Proper text spacing and formatting 3) Clear distinction between different information types (status, actions, narrative). Deduct 3 points for inconsistent terminology, 5 points for cluttered text presentation, and 5 points for confusing navigation instructions. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the game interaction intuitive and responsive?",
-      "description": "Judge whether the game controls and feedback conform to user expectations: 1) Clear command options 2) Immediate feedback after actions 3) Intuitive navigation between game sections. Deduct 5 points for confusing controls, 3 points for delayed feedback, and 5 points for hidden or difficult-to-access core functions. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Strategy",
-  "difficulty": "easy"
-}

package/library/game_development-role-playing/web-rpg-post-apocalyptic-combat-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 1079,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable when possible. Create a web-based RPG game featuring a lone warrior wandering through a post-apocalyptic world. The game mechanics should include real-time combat from a top-down perspective, with the character gaining experience and leveling up after defeating enemies. During their journey, the player will acquire numerous treasures. The art style should be realistic.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core RPG character system fully implemented?",
-      "description": "Review whether the code accurately implements the character attributes (health, experience, level, attack/defense stats), progression system, and realistic character rendering. Check if the level-up mechanics include stat improvements and provide visual feedback. Score 0 if the core character system is missing, 5 if only basic attributes are implemented, and 10 if the complete progression system with balanced difficulty curves is present.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the top-down real-time combat system properly implemented?",
-      "description": "Evaluate the combat system implementation including hitbox detection, damage calculation based on character stats, combat animations, and player control responsiveness. Check if the system includes attack cooldowns, dodge/block mechanics, and combat feedback effects. Deduct 5 points if hit detection is inaccurate, and 3 points if combat animations don't match actions. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the post-apocalyptic world environment well-designed?",
-      "description": "Assess whether the game includes a properly rendered post-apocalyptic environment with appropriate visual elements (ruins, wasteland, etc.), obstacle collision detection, and interactive objects. Check if the world has distinct areas/zones with varying challenges. Deduct 5 points if the environment lacks thematic consistency, and 3 points if collision detection is buggy. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the treasure and inventory system complete?",
-      "description": "Examine whether the code implements a functional inventory system with diverse treasures/items that have different effects, proper item categorization, and item usage mechanics. Check if treasures appear at appropriate intervals and if there's a balanced reward system. Deduct 5 points if the inventory UI is dysfunctional, and 3 points if item effects aren't implemented. 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 player inputs, asset loading failures, browser compatibility issues, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Dynamic weather system affecting gameplay 2. Moral choice system affecting story outcomes 3. Procedurally generated environments for replayability). 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 a post-apocalyptic RPG (e.g., a built-in social media feed) 3. Graphics effects that severely impact performance (e.g., excessive particle systems). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating game logic/view/input handling layers), asset loading optimization, and performance considerations for web environments. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no optimization for mobile/desktop differences. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the realistic art style meet professional standards?",
-      "description": "Evaluate whether the visuals achieve the required realistic style: 1) Consistent lighting and shadow effects 2) Appropriate texture resolution and detail 3) Cohesive post-apocalyptic aesthetic across all elements. Deduct 3 points for inconsistent art styles between characters and environment, 5 points for low-quality textures in prominent areas, and 5 points for animations that break immersion. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the game performance and responsiveness optimized?",
-      "description": "Judge whether the game runs smoothly in a browser environment: 1) Maintains consistent 30+ FPS during combat 2) Input response time under 100ms 3) Efficient asset loading with appropriate preloading strategy. Deduct 5 points for each noticeable frame rate drop during standard gameplay, 3 points for input lag over 200ms, and 5 points if the game causes browser crashes when testing on mid-range devices. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Role-Playing",
-  "difficulty": "hard"
-}

package/library/game_development-role-playing/ywt-adventure-pokemon-style-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 1662,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable for demonstration. Create an HTML game with the theme of \"YWT Adventure,\" using a style similar to Pokemon. Ideally the game interface should be 3D, with characters having health bars and being controllable.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the 3D game world and rendering system fully implemented?",
-      "description": "Review whether the code accurately implements 3D rendering using WebGL/Three.js or similar technologies, including proper 3D scene setup, camera controls, lighting systems, and terrain/environment models. Check if the 3D world has depth, proper perspective projection, and realistic spatial positioning. Score 0 if only 2D sprites are used, 5 if basic 3D elements exist but lack proper lighting/shadows, and 10 if a complete 3D environment with professional rendering quality is achieved.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the character system with health management properly designed?",
-      "description": "Evaluate whether characters have fully functional health bar systems, including real-time HP display, damage calculation, healing mechanisms, and visual feedback for health changes. Check if health bars are properly positioned above characters, have smooth animations for health changes, and include status effects visualization. Deduct 5 points if health bars are static or poorly positioned, 3 points if damage calculations are incorrect or missing. Full score requires Pokemon-style health management with smooth transitions and visual polish.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are the character controls responsive and adventure mechanics implemented?",
-      "description": "Check whether the character movement system includes smooth WASD/arrow key controls, collision detection with environment, interaction with NPCs/objects, and adventure progression mechanics. Evaluate if the controls feel responsive (input lag < 50ms), include animations for different movement states, and support exploration features like item collection, dialogue systems, or quest mechanics. Deduct 5 points if movement is choppy or unresponsive, 5 points if collision detection is missing or buggy.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the game capture the Pokemon-style adventure essence?",
-      "description": "Assess whether the game successfully implements Pokemon-inspired gameplay elements such as creature encounters, turn-based or real-time combat systems, character progression, inventory management, or exploration rewards. Check for thematic consistency in art style, UI design, and game mechanics that evoke the Pokemon adventure experience. Score 0 if no Pokemon-style elements exist, 5 if basic encounter/combat mechanics are present, and 10 if comprehensive adventure systems with proper game flow are implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust and handles edge cases properly?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid user inputs, browser compatibility issues, performance drops, collision edge cases, etc.) and provide friendly error handling or recovery mechanisms. Code with strong robustness should gracefully handle WebGL context loss, memory management, and various device capabilities. Give 10 points if fully robust, 5 points if basic error handling exists, and 0 points if no exception handling is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there innovative features that enhance the adventure experience?",
-      "description": "Check whether the code includes creative features that elevate the gaming experience (e.g., 1. Dynamic weather/day-night cycles 2. Procedural terrain generation 3. Advanced particle effects for abilities 4. Mini-map or compass navigation 5. Audio-reactive elements). Add 2-3 points for each well-implemented innovative feature that genuinely improves gameplay immersion (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant or performance-hindering features?",
-      "description": "Strictly identify three types of issues: 1. Redundant implementations of similar functionality (e.g., multiple rendering loops or duplicate input handlers) 2. Unnecessary features unrelated to the adventure game core (e.g., unrelated mini-games or excessive UI elements) 3. Performance-heavy effects that cause frame drops (e.g., excessive particle systems, unoptimized 3D models). Deduct 3 points for each redundancy found, and deduct 10 points if core gameplay is negatively affected.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code demonstrate proper engineering practices?",
-      "description": "Review modular architecture (separation of game logic/rendering/input systems), code organization, performance optimization techniques, and asset management. Check for proper use of design patterns, efficient memory usage, and clean code structure. Deduct 5 points for global variable pollution or lack of proper class/module structure; deduct 5 points if code duplication exceeds 30%; deduct 5 points for poor performance optimization (frame rate < 30fps on average hardware).",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the visual design meet professional game UI standards?",
-      "description": "Evaluate whether the game interface follows modern game UI principles: 1) Cohesive color palette suitable for adventure theme 2) Proper HUD layout with health bars, inventory, and controls clearly visible 3) Consistent visual hierarchy and readable typography (font size ≥ 12px for UI elements). Deduct 3 points for each cluttered UI element, 5 points for poor contrast or readability issues, and 5 points for inconsistent visual style that breaks immersion.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Are the game interactions fluid and provide proper feedback?",
-      "description": "Judge whether the interactive elements provide satisfying user feedback: 1) Character actions have immediate visual/audio response (≤ 100ms) 2) Smooth animation transitions for movements and UI changes (200-400ms duration) 3) Clear visual indicators for interactable objects and game state changes 4) Consistent 60fps performance during gameplay. Deduct 5 points for each unresponsive interaction, 3 points for choppy animations or frame drops, and 5 points for unclear interaction affordances that confuse players.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Role-Playing",
-  "difficulty": "hard"
-}

package/library/game_development-shooting/3d-shooting-game-html.json

@@ -1,68 +0,0 @@
-{
-  "index": 414,
-  "question": "You are a coding expert, please utilize your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable. Create a 3D shooting game similar to Game for Peace (PUBG Mobile) using HTML.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "3D Rendering Engine Implementation",
-      "description": "Check whether the code implements a functional 3D rendering engine using WebGL/Three.js or equivalent technology. Score 0 if no 3D rendering is implemented, 5 if basic 3D objects are displayed without proper lighting/shading, and 10 if the engine supports proper 3D terrain, dynamic lighting, shadows, and object rendering with appropriate performance optimization.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "First-Person Shooter Core Mechanics",
-      "description": "Evaluate the implementation of core FPS mechanics including character movement (WASD controls), aiming mechanism (mouse look), weapon system (multiple weapons with different characteristics), shooting mechanics with recoil and bullet physics, and hit detection. Deduct 2 points for each missing core mechanic. Score 10 if all core mechanics are implemented with realistic physics.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Battle Royale Game Loop",
-      "description": "Assess whether the code implements the complete battle royale game loop: player parachuting, shrinking play zone, looting system, and last-player-standing victory condition. Score 0 if the game loop is absent, 5 if only basic elements are implemented, and 10 if the full game cycle is present including shrinking zone damage, proper timing, and end-game scenarios.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "AI Bot Implementation",
-      "description": "Review whether the game includes AI opponents with appropriate behaviors: pathfinding, combat decision-making, looting, and using cover. Score 0 if no AI is implemented, 5 if bots only have basic movement and shooting, and 10 if bots demonstrate tactical behaviors including flanking, using cover, and adapting to player strategies.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Code Robustness",
-      "description": "Evaluate whether the code can handle common abnormal situations (browser compatibility issues, variable screen sizes, resource loading failures, unexpected user inputs). Code with strong robustness should handle these edge cases with graceful degradation and informative error messages, scoring 10 points. If robustness is average, give 5 points, and if no exception handling exists, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Innovative Features",
-      "description": "Check whether the code includes surprising features that enhance the experience (e.g., 1. Destructible environment 2. Weather effects affecting gameplay 3. Vehicle physics 4. Advanced hitbox system with damage zones). Add 2.5 points for each practical innovative feature implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Absence of Redundant Features",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple movement control systems) 2. Function modules unrelated to the core FPS experience 3. Excessive visual effects that severely impact performance. Deduct 3 points for each redundancy found, and directly deduct 10 points if core functions are compromised by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Engineering Quality",
-      "description": "Review modular design (separation of rendering engine, game logic, input handling, physics), asset loading optimization, and memory management. Deduct 3 points if global state pollution exists; deduct 3 points if framerate drops below 30fps on standard hardware; deduct 4 points if no asset preloading or progressive loading is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Visual Design and UI",
-      "description": "Evaluate whether the game interface follows professional gaming UI principles: 1) Minimalist HUD that doesn't obstruct gameplay 2) Clear visual indicators for health, ammo, and minimap 3) Proper scaling on different devices. Deduct 3 points for cluttered UI elements, 3 points for poor contrast making information hard to read, and 4 points for non-responsive design elements.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Game Feel and Responsiveness",
-      "description": "Judge whether the game controls and feedback create satisfying game feel: 1) Input lag under 50ms 2) Visual feedback for all player actions including hits, damage taken, and healing 3) Appropriate sound effects synchronized with actions. Deduct 3 points for sluggish controls, 3 points for missing feedback on critical actions, and 4 points if weapon handling lacks weight or impact.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Shooting",
-  "difficulty": "hard"
-}