@getollie/cli 0.0.1

package/library/game_development-role-playing/game-stat-allocation-simulator-web-wordpress.json

@@ -0,0 +1,68 @@
+{
+  "index": 379,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be careful to ensure that the code you generate is executable for demonstration. I want to create a game stat allocation simulator - a web version that can be embedded into WordPress. I will give you the rules below. Let's complete this step by step. I hope you will remember the code we create each time.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the stat allocation core system fully implemented?",
+      "description": "Review whether the code implements a complete stat allocation system that allows users to distribute points among different attributes. Check if it includes minimum/maximum constraints for each stat, total points limitation, and real-time validation. Score 0 if the core allocation logic is missing, 5 if basic allocation is implemented but lacks constraints, and 10 if the system fully handles allocation rules with proper validation.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the WordPress integration properly designed?",
+      "description": "Evaluate whether the code can be properly embedded into WordPress as required. Check for WordPress-compatible initialization (e.g., using wp_enqueue_script), proper namespacing to avoid conflicts, and responsive design that adapts to WordPress themes. Deduct 5 points if the code lacks WordPress hooks, 3 points if it doesn't handle theme compatibility, and 2 points if it doesn't use proper WordPress coding standards.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is there a save/load mechanism for stat configurations?",
+      "description": "Check if users can save their stat configurations and load them later. Examine whether the solution uses local storage appropriately, includes export/import functionality, and maintains data persistence. Deduct 5 points if saving is implemented but loading is unreliable, 3 points if there's no export/import feature, and give 0 points if no persistence mechanism exists.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is there visual feedback for stat effects?",
+      "description": "Assess whether the simulator provides visual representations of how stat changes affect character abilities or game parameters. Look for graphs, charts, derived stat calculations, or other visual aids. Give 10 points for comprehensive visual feedback with multiple representation options, 5 points for basic feedback, and 0 points if visual representation is absent.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid inputs, script loading errors, 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. Stat presets for different play styles 2. Comparison mode between configurations 3. Character preview based on stats). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple ways to reset stats) 2. Function modules unrelated to stat allocation (e.g., a built-in chat system) 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 UI/logic/data layers), use of appropriate design patterns, and maintainable structure. 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 there's no clear organization of components. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Immediate feedback when adjusting stats 2) Smooth transition animations for stat changes 3) Clear visual cues for available/unavailable actions. Deduct 5 points for each operation without feedback, 3 points for jerky animations during stat adjustments, and 5 points for confusing UI state representation. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Role-Playing",
+  "difficulty": "hard"
+}

package/library/game_development-role-playing/honkai-star-rail-critical-damage-attribute-multipliers.json

@@ -0,0 +1,68 @@
+{
+  "index": 1141,
+  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Pay attention to ensure that the generated code is executable for demonstration. Firstly, comment on each line. Secondly, look for examples from Honkai: Star Rail where critical damage is displayed as 200%, 150%, etc. Finally, for normal attacks, skills, etc., show what attribute multipliers are used without providing specific values.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the code provided with comprehensive line-by-line comments?",
+      "description": "Review whether each line of code includes meaningful comments that explain the purpose, logic, or functionality. Comments should be clear, concise, and add value beyond what is obvious from the code itself. Evaluate whether comments follow consistent formatting and explain complex algorithms or decision points. Score 0 if no comments are present, 5 if comments are sparse or superficial, and 10 if comments are comprehensive and insightful.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Does the code accurately implement critical damage visualization systems similar to Honkai: Star Rail?",
+      "description": "Check if the implementation correctly displays critical damage percentages (200%, 150%, etc.) in a visually distinct way. The visualization should include: 1) Different text color/size for critical hits 2) Animated effects that scale with critical damage multiplier 3) Appropriate timing for displaying the percentage. Deduct 3 points if critical values don't match the game reference, 5 points if animations are missing, and 3 points if critical hit indicators are not visually prominent. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the attribute multiplier system for different attack types properly implemented?",
+      "description": "Evaluate whether the code correctly implements different attribute multipliers for normal attacks, skills, and ultimates without hardcoding specific values. Check if the system: 1) Uses a flexible formula system that can draw from character stats 2) Separates base damage calculation from multiplier application 3) Handles special conditions like elemental weaknesses. Deduct 5 points if multipliers are hardcoded, 3 points if attack type differentiation is missing, and 5 points if the damage calculation pipeline is incomplete. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the implementation include a proper damage calculation system that integrates with the visualization?",
+      "description": "Assess whether the code connects the damage calculation system with the visualization components. Look for: 1) Event-based architecture for damage events 2) Proper separation between calculation logic and display logic 3) Performance optimization for multiple simultaneous damage numbers. Deduct 3 points if calculation and visualization are tightly coupled, 5 points if the system doesn't scale well with multiple damage instances, and 3 points if performance issues are evident. 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 null inputs, division by zero, unexpected data types, animation timing conflicts, etc.) and provide graceful fallbacks 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. Damage type-specific visual effects 2. Contextual damage indicators based on hit locations 3. Responsive audio cues for critical hits). 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 animation functions 2. Feature creep beyond damage calculation/visualization (e.g., unnecessary inventory systems) 3. Overly complex effects that affect performance without adding value. 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 damage calculation/visualization/animation layers), potential for unit testing, and maintainability. Deduct 5 points if global state pollution is found or proper design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the code isn't organized into logical classes or modules. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the visual design follows modern game UI principles: 1) Harmonious color matching for damage numbers (critical vs. normal) 2) Proper layout and positioning of damage indicators 3) Professional typography with appropriate size and readability. Deduct 3 points for each visual crowding issue, 5 points for poor color contrast or illegibility, and 5 points for inconsistent visual style compared to the reference game. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the animation effects conform to game feedback characteristics: 1) Damage number appearance timing is appropriate 2) Animation duration controlled for readability without blocking gameplay 3) Clear visual hierarchy between normal and critical damage. Deduct 5 points for jerky animations, 3 points for overlapping damage numbers that cause readability issues, and 5 points for animations that distract from core gameplay. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Role-Playing",
+  "difficulty": "hard"
+}

package/library/game_development-role-playing/html-three-kingdoms-role-playing-game.json

@@ -0,0 +1,68 @@
+{
+  "index": 841,
+  "question": "You are a coding expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you produce is executable and can be demonstrated. Create a Three Kingdoms role-playing game using HTML, featuring rich storylines and comprehensive gameplay mechanics.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Three Kingdoms setting authentically implemented?",
+      "description": "Check whether the code implements an immersive Three Kingdoms environment with historically accurate characters (e.g., Liu Bei, Guan Yu, Zhang Fei, Cao Cao, Sun Quan), events, and locations from the era. Score 0 if there are no authentic Three Kingdoms elements, 5 if only basic character references are included, and 10 if the game features rich historical context with accurate representation of major battles, alliances, and political dynamics.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the role-playing system comprehensively developed?",
+      "description": "Evaluate whether the code implements core RPG mechanics including character attributes (strength, intelligence, leadership, etc.), skill trees specific to different Three Kingdoms heroes, equipment systems, and character progression. Deduct 5 points if character attributes don't influence gameplay, 3 points if skill acquisition is linear rather than branching, and 2 points if equipment has no meaningful impact on gameplay. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the storyline rich and engaging with multiple paths?",
+      "description": "Check if the game offers branching storylines where player choices impact the narrative progression. Look for multiple story arcs (minimum 3 major storylines representing Wei, Shu, and Wu kingdoms), dialogue systems with meaningful choices, and consequences that alter the game world. Deduct 5 points if the story is completely linear, 3 points if choices don't meaningfully impact outcomes, and 2 points if historical events aren't incorporated into the narrative. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are the gameplay mechanics comprehensive and balanced?",
+      "description": "Assess whether the game includes strategic battles, resource management, diplomacy systems, and character relationships. Each system should be interconnected and balanced. Examine if battle mechanics include terrain effects, unit types, and tactical options. Score 0 if core gameplay mechanics are missing, 5 if mechanics exist but lack depth or balance, and 10 if all systems are fully implemented with proper balancing and strategic depth.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid inputs, resource 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 battles 2. Historical advisor system providing authentic context 3. Dynasty reputation mechanics influencing NPC interactions). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple inventory systems coexisting) 2. Function modules unrelated to the Three Kingdoms setting (e.g., anachronistic elements) 3. Fancy effects that affect performance (e.g., excessive particle effects during routine actions). 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 reusability for similar character abilities or battle mechanics, and asset management efficiency. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if assets aren't properly optimized for web performance. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the visual design authentically represents the Three Kingdoms era while following design principles: 1) Period-appropriate color palette and motifs 2) Consistent UI elements that don't break immersion 3) Proper typography that balances readability with thematic elements. Deduct 3 points for anachronistic visual elements, 5 points for inconsistent UI design, and 5 points for illegible text or overcrowded interfaces. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the game responds fluidly to player actions: 1) Battle animations that are visually distinct and provide clear feedback 2) Smooth transitions between game states (exploration, battle, dialogue) 3) Intuitive controls with appropriate visual and audio feedback. Deduct 5 points for laggy animations, 3 points for jarring transitions between game modes, and 5 points for unintuitive navigation that hinders gameplay. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Role-Playing",
+  "difficulty": "medium"
+}

package/library/game_development-role-playing/interactive-npc-system-html-javascript.json

@@ -0,0 +1,68 @@
+{
+  "index": 3,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable for demonstration purposes.\n\nPlease use HTML and JavaScript to implement an interactive NPC.\n\n**Task**: Implement an interactive NPC system where players can converse with NPCs, accept quests, or obtain clues.\n\n**Hint**: You can set different dialogue content and tasks for each NPC, and adjust the game progression based on player choices.\n\nInclude comments in your code to help other developers understand your implementation process.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the NPC dialogue system fully implemented?",
+      "description": "Review whether the code implements a complete dialogue system that includes multiple conversation paths, branching dialogue options, and persistent dialogue state tracking. Score 0 if basic dialogue display is missing, 5 if only linear conversations are supported, and 10 if the system handles complex branching dialogues with contextual responses based on previous player choices.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the quest/task system functional?",
+      "description": "Evaluate whether the code includes a quest management system that allows NPCs to offer quests, track quest progress, and provide appropriate rewards. Check if there are quest states (available, active, completed, failed). Deduct 5 points if quest tracking is absent, 3 points if quest state persistence is missing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the NPC state management implemented?",
+      "description": "Check if NPCs have different states and behaviors based on game progression, player actions, or time of day. NPCs should remember past interactions and adjust their dialogue/behavior accordingly. Deduct 5 points if NPCs have static behavior regardless of player actions, 3 points if state changes aren't persistent. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is there a clue/information system that affects gameplay?",
+      "description": "Assess whether information/clues provided by NPCs are tracked and have actual impact on gameplay mechanics or story progression. Check if the system includes hints, critical information, or red herrings that influence player decisions. Deduct 5 points if information has no gameplay impact, 3 points if the information system lacks variety. 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 undefined inputs, missing data, user operation errors, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. NPC mood/relationship system 2. Voice acting integration 3. Dynamic facial expressions/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 functions (e.g., multiple dialogue display systems) 2. Function modules unrelated to NPC interaction (e.g., a built-in inventory system not connected to dialogues) 3. Fancy effects that affect performance (e.g., unnecessary animations or transitions). 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 dialogue logic/view/data layers), code organization, and developer documentation through comments. 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 helpful comments are missing or inadequate. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the NPC interaction interface follows modern design principles: 1) Harmonious color matching for dialogue boxes and UI elements 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (dialogue text 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 NPC interaction experience conforms to human perception characteristics: 1) Dialogue response delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual indication of dialogue options and NPC status. Deduct 5 points for each interaction without feedback, 3 points for jarring transitions between dialogue states, and 5 points for confusing navigation in conversation trees. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Role-Playing",
+  "difficulty": "easy"
+}

package/library/game_development-role-playing/javascript-weekly-quest-system.json

@@ -0,0 +1,68 @@
+{
+  "index": 1511,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the code you generate is executable for display. Write a weekly quest system in JS where players can only claim a task once every seven days.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the weekly quest timing mechanism correctly implemented?",
+      "description": "Check if the code properly implements a 7-day cooldown period using Date objects and timestamp comparisons. Verify that the system prevents claiming the same quest before 7 days have elapsed. Score 0 if time tracking is missing, 5 if basic timestamp comparison exists but has edge cases (like timezone issues), 10 if the implementation is robust with proper date manipulation.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is quest state persistence implemented effectively?",
+      "description": "Review whether the code includes a proper persistence mechanism (localStorage, sessionStorage, cookies, or simulated database) to track claimed quests across browser sessions. Deduct 5 points if data is only stored in memory and lost on refresh, 3 points if persistence exists but without expiry management. Full points require proper data serialization and retrieval with error handling.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the quest data structure well-designed?",
+      "description": "Evaluate if the quest objects are properly structured with necessary properties (ID, title, description, rewards, cooldown period, completion criteria, etc.). Deduct 3 points for each missing essential property, 5 points if quests lack unique identifiers, and 5 points if the data structure doesn't support quest status tracking. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the user interface for the quest system complete and functional?",
+      "description": "Check if the code implements a proper UI for displaying available quests, claimed quests, cooldown timers, and reward information. Score 0 if no UI exists, 5 if a basic list is provided without visual cues for status, 10 if the interface clearly shows quest status with countdown timers and responsive design.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid dates, browser storage limitations, data corruption, 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. Visual countdown timers 2. Quest categories or difficulty levels 3. Progressive reward 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 functions (e.g., multiple timer implementations) 2. Function modules unrelated to quest system (e.g., unrelated game mechanics) 3. Fancy effects that affect performance (e.g., unnecessary 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 quest logic/view/data layers), function organization, and code reusability. 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 separation between UI rendering and business 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 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 quest claiming interaction conforms to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance for available vs. cooldown quests. Deduct 5 points for each operation without feedback, 3 points for jarring transitions when claiming quests, and 5 points for confusing status indicators. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Role-Playing",
+  "difficulty": "easy"
+}

package/library/game_development-role-playing/legends-condor-heroes-game.json

@@ -0,0 +1,68 @@
+{
+  "index": 843,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code for demonstration when possible. I want to create a \"Legends of the Condor Heroes\" game (based on Jin Yong's novels). Please list the detailed steps and provide the complete code.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core RPG game system fully implemented?",
+      "description": "Review whether the code accurately implements character attributes (internal energy, martial arts skills, reputation), combat mechanics (turn-based or real-time), skill progression system, and inventory management. Check if martial arts learning mechanics and internal energy cultivation are properly designed. Score 0 if core RPG mechanics are missing, 5 if only basic character stats are implemented, and 10 if complete RPG systems including martial arts mastery and character progression are fully functional.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the storyline and quest system properly structured?",
+      "description": "Evaluate whether the game includes a coherent narrative structure with branching storylines, character interactions, and quest mechanics that reflect the novel's plot elements. Check for dialogue systems, NPC interactions, and story progression triggers. Deduct 5 points if quest logic is incomplete, 3 points if character relationships are not tracked. Full score requires implemented story branching based on player choices with proper save/load functionality.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are the game world and map exploration mechanics implemented?",
+      "description": "Check whether the code includes a navigable game world with locations from the novel (such as Peach Blossom Island, Mount Hua), movement mechanics, and exploration features. Evaluate if the map system allows for fast travel, location discovery, and proper scene transitions. Deduct 5 points if world navigation is limited to static screens, 3 points if location-specific events are not implemented. Full score requires dynamic world exploration with interactive environments.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the martial arts combat system authentic and engaging?",
+      "description": "Assess whether the combat system captures the essence of wuxia martial arts with techniques like the Eighteen Dragon-Subduing Palms, Nine Yin Manual skills, and weapon-based combat. Check for combat animations, skill combinations, and strategic depth. Deduct 5 points if combat lacks martial arts authenticity, 3 points if special techniques are not differentiated. Full score requires implemented signature moves with visual effects and tactical combat mechanics.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid user input, save file corruption, memory leaks during long gameplay sessions, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should effectively handle edge cases, 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 enhance the gaming experience?",
+      "description": "Check whether the code includes creative features that elevate the game beyond basic RPG mechanics (e.g., 1. Dynamic weather affecting martial arts effectiveness 2. Relationship system with multiple romance options 3. Mini-games for internal energy cultivation 4. Achievement system for martial arts mastery). 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) 2. Features unrelated to wuxia/RPG gameplay (e.g., modern elements that break immersion) 3. Performance-heavy effects that don't add value (e.g., excessive particle systems during normal gameplay). Deduct 3 points for each redundancy found, and directly deduct 10 points if core game functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (separating game logic/rendering/audio/input systems), proper asset management, and scalable architecture. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if code duplication rate is too high (over 30%); deduct 5 points if the project structure is not organized for maintainability. Full score requires clean separation of concerns and professional code organization.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface design capture the wuxia aesthetic?",
+      "description": "Evaluate whether the visual design reflects ancient Chinese aesthetics appropriate for the setting: 1) Traditional color palette (earth tones, imperial colors) 2) Typography using appropriate fonts for the period 3) UI elements styled as scrolls, jade, or traditional materials 4) Consistent visual theme throughout. Deduct 3 points for each modern UI element that breaks immersion, 5 points for inappropriate color schemes, and 5 points for inconsistent visual style. Full score requires authentic period-appropriate design.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the game interaction smooth and intuitive?",
+      "description": "Judge whether the game controls and interactions feel natural for the RPG genre: 1) Responsive character movement and menu navigation 2) Intuitive combat controls with clear feedback 3) Smooth transitions between game states (exploration, combat, dialogue) 4) Clear visual indicators for interactive elements. Deduct 5 points for each unresponsive interaction, 3 points for confusing navigation, and 5 points for unclear game state feedback. Full score requires polished, intuitive gameplay experience.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Role-Playing",
+  "difficulty": "hard"
+}

package/library/game_development-role-playing/magic-academy-game-with-skills-and-exams.json

@@ -0,0 +1,68 @@
+{
+  "index": 20,
+  "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.\nPlease use HTML and JavaScript to implement a Magic Academy game where players need to learn magical skills and pass exams. Hint: Design magic courses and an examination system.\nInclude comments in your code so other developers can understand your implementation process.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Magic Academy core learning system fully implemented?",
+      "description": "Review whether the code accurately implements a learning progression system through HTML/JavaScript, with clearly defined magical skills, learning paths, and skill acquisition mechanics. Score 0 if the core learning mechanics are not implemented, 5 if only basic skill acquisition exists, and 10 if there's a comprehensive magical skill tree with prerequisites and advancement logic.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the examination system properly implemented?",
+      "description": "Evaluate whether the examination system includes different question types (multiple-choice, spell casting simulations, practical challenges), difficulty progression, and scoring mechanisms. The system should provide meaningful feedback on exam performance and track student progress. Deduct 5 points if exams are too simplistic, 3 points if feedback is limited to pass/fail without details. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are the magical courses and curriculum well-designed?",
+      "description": "Check if the game includes diverse magical disciplines (e.g., potions, spells, magical creatures), each with unique learning materials, interactive exercises, and thematic consistency. Each course should have clear objectives and learning outcomes. Deduct 3 points for each missing major discipline, and 5 points if courses lack progressive difficulty. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is there a player progression and achievement system?",
+      "description": "Assess whether the code implements character development features including experience points, level progression, skill mastery tracking, and achievements/badges. The system should show meaningful growth as players advance through the academy. Deduct 5 points if progression is linear without choices, and 3 points if achievements are too simplistic. 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 spell inputs, exam submission errors, interrupted learning sessions, 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. Interactive spell casting with mouse gestures 2. Dynamic potion brewing simulations 3. Magical dueling with other students). 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 separate spell casting systems) 2. Function modules unrelated to a magic academy (e.g., a complex inventory system with no educational purpose) 3. Fancy effects that affect performance (e.g., excessive particle effects). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating game mechanics/UI/data management), code documentation completeness, 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 comprehensive comments are missing as requested. 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 magical academy aesthetics with modern design principles: 1) Thematic color palette suitable for a magical setting 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Fantasy-appropriate typography (readable but thematic). Deduct 3 points for each cluttered UI section, 5 points for inconsistent visual themes, and 5 points for poor readability of critical information. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the magical interaction intuitive and engaging?",
+      "description": "Judge whether the magical interactions are intuitive and satisfying: 1) Clear visual feedback for spell casting ≤ 100ms 2) Satisfying animations for successful magical effects 3) Progressive difficulty in magical interactions. Deduct 5 points for each magical action without clear feedback, 3 points for confusing interaction patterns, and 5 points if key magical functions are difficult to discover. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Role-Playing",
+  "difficulty": "hard"
+}

package/library/game_development-role-playing/magic-learning-game-with-spells-and-effects.json

@@ -0,0 +1,68 @@
+{
+  "index": 88,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure the generated code is executable for demonstration.\n\nPlease use HTML and JavaScript to implement a Magic School.\nTask: Design a magic learning game where players complete tasks by learning spells and casting magic.\nHint: Implement a magic system that includes spell learning and effect display.\n\nPlease include comments in your code so other developers can understand your implementation process.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the magic spell learning system properly implemented?",
+      "description": "Review whether the code implements a comprehensive spell learning mechanism including spell collection, practice progression tracking, and mastery levels. Check if there's a structured spell database with properties like element type, difficulty, and effects. Score 0 if no learning system exists, 5 if only basic spell acquisition is present, and 10 if there's a complete progression system with feedback and skill advancement.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the magic casting mechanism interactive and engaging?",
+      "description": "Evaluate the implementation of spell casting interactions - whether they use keyboard combinations, mouse gestures, or other creative input methods. Check if the casting mechanism includes timing elements, accuracy requirements, or combination sequences that make spellcasting challenging and engaging. Deduct 5 points if casting is limited to simple button clicks, and 3 points if there's no visual feedback during casting. Full score requires multiple interaction patterns that increase in complexity with spell power.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are the magic effects visualized appropriately?",
+      "description": "Assess the visual representations of spells with animations, particle effects, or transformations. Each spell should have a distinctive visual signature that relates to its element or purpose. Deduct 5 points if effects are generic across different spells, 3 points if animations are static or jarring. Award full points only if the visualization includes smooth transitions, appropriate sound effects, and visual feedback proportional to spell power.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is there a task/quest system to drive player progression?",
+      "description": "Check if the code implements a structured task system with clear objectives, completion criteria, and rewards. Quests should progressively introduce more complex magic concepts and require mastery of previously learned spells. Score 0 if no quest system exists, 5 if only basic tasks are present without progression logic, and 10 if there's a complete branching quest system with difficulty scaling and narrative elements.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid spell inputs, rapid-fire casting attempts, or interrupted spell sequences) 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. Spell combinations creating new effects 2. Environmental interactions with spells 3. Spell customization or evolution 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 spell effects with different names 2. Function modules unrelated to magic learning (e.g., an overly complex character creator) 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 spell logic/visual effects/user interaction layers), commenting quality, and code organization. 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 are no meaningful comments explaining magic system components. 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 magical theme principles: 1) Thematic color matching appropriate for a magical setting 2) Proper layout spacing for spell books, casting areas, and feedback displays 3) Professional font system suitable for a magical academy aesthetic. Deduct 3 points for each crowded visual element, 5 points for inconsistent magical theming, 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 magical effects conform to expected fantasy aesthetics: 1) Spell casting feedback delay ≤ 100ms 2) Magic effect animations controlled between 300-1000ms based on power 3) Clear visual guidance for spell learning progression. Deduct 5 points for each spell without visual feedback, 3 points for choppy animations during complex spells, and 5 points for unintuitive spell learning interfaces. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Role-Playing",
+  "difficulty": "medium"
+}