@getollie/cli 0.0.1

package/library/game_development-role-playing/character-skill-upgrade-system-with-experience-points.json

@@ -0,0 +1,68 @@
+{
+  "index": 74,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure that the code you generate is executable.\n\nPlease use HTML and JavaScript to implement a character skill upgrade system.\n\n**Task**: Design a character skill upgrade system that allows players to enhance skill levels through experience points.\n\n**Hint**: You can set the required experience points for each skill upgrade, and display the skill tree and current levels.\n\nPlease include comments in your code to help other developers understand your implementation process.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the character skill system fully implemented?",
+      "description": "Review whether the code accurately implements a complete skill system with experience points allocation, level progression, and skill tree visualization. Score 0 if core skill upgrade functionality is missing, 5 if only basic level-up is implemented without dependencies, and 10 if a complete skill tree with prerequisites and branching paths is fully included.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the experience point calculation and distribution system properly designed?",
+      "description": "Evaluate whether the code includes a well-designed experience point calculation system with increasing difficulty curves for higher levels (e.g., exponential growth formula). Check if the system allows for partial XP allocation, saving unused points, and provides clear feedback on progress toward next level. Deduct 5 points if there's no formula for scaling difficulty, and 3 points if visual progress indicators are missing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Does the skill tree visualization meet industry standards?",
+      "description": "Check whether the skill tree is visually displayed with proper node connections (lines/arrows between related skills), clear indication of prerequisite relationships, and visual differentiation between locked, available, and maxed-out skills. Deduct 5 points if the tree structure is not visually apparent, and 3 points if skill dependencies are not clearly indicated. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the skill upgrade interaction intuitive and responsive?",
+      "description": "Assess the interaction flow for upgrading skills: clicking on skills should provide immediate visual feedback, show detailed information about the skill, confirm requirements before upgrading, and display success/failure states. Deduct 5 points if there's no confirmation dialog for point allocation, and 3 points if there's no immediate visual feedback. 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 insufficient experience points, attempting to upgrade locked skills, maxed-out skills, 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. Skill simulation preview before spending points 2. Automatic recommended skill paths based on play style 3. Visual skill animations on hover/selection). 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 calculation methods for the same skill level) 2. Function modules unrelated to skill upgrading (e.g., inventory management) 3. Fancy effects that affect performance (e.g., excessive particle animations on each skill hover). 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 skill logic/view/data layers), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern design principles: 1) 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) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast skill selection, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Role-Playing",
+  "difficulty": "easy"
+}

package/library/game_development-role-playing/cultivation-immortal-progression-game-mobile.json

@@ -0,0 +1,68 @@
+{
+  "index": 1101,
+  "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. Help me create a cultivation/immortal progression game that can run directly on a mobile device. Here are my ideas and requirements: At the start of the game, the main character's attribute values are randomly generated. The game should include a training system, equipment system, cultivation techniques and skills system, challenge/dungeon system, log functionality, leveling system, and some simple UI.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the character generation system properly implemented?",
+      "description": "Review whether the code correctly implements random attribute generation with balanced constraints. Check if attributes include at least 5 core stats (e.g., strength, spirit, agility) with proper min/max ranges and distribution curves. Score 0 if not implemented, 5 if basic randomization exists but lacks balance controls, and 10 if it includes attribute correlation rules and balanced generation algorithms that prevent overpowered initial characters.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the cultivation/training system comprehensive and engaging?",
+      "description": "Evaluate whether the cultivation system includes multiple cultivation paths with distinct progression mechanics. Check for meditation timers, resource consumption, breakthrough mechanics, and bottleneck challenges. Deduct 5 points if cultivation progression is linear without bottlenecks, deduct 3 points if it lacks resource management, and deduct 2 points if there's no visual feedback for cultivation progress. The full score is 10 points only if the system includes at least 3 distinct cultivation paths with unique mechanics.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are the equipment and inventory systems properly implemented?",
+      "description": "Check whether the equipment system includes different gear slots, item rarities, attribute bonuses, and set effects. Review inventory management including sorting, filtering, and item comparison. Score 0 if equipment is purely cosmetic, 5 if basic equipment affects stats but lacks variety, and 10 if the system includes crafting, upgrading, refinement mechanics, and special equipment with unique effects.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the skills and techniques system comprehensive?",
+      "description": "Assess the implementation of cultivation techniques and combat skills with proper cooldowns, resource costs, damage calculations, and skill trees. Examine whether techniques have different cultivation requirements and progression paths. Deduct 5 points if skills lack visual effects, deduct 3 points if skill progression is linear without choices, and deduct 2 points if there are fewer than 10 unique skills. 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 out-of-bounds input, network interruption, user operation errors, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Dynamic weather affecting cultivation 2. NPC relationship system with story consequences 3. Procedurally generated secret realms). 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 progression systems that function identically) 2. Function modules unrelated to cultivation gameplay (e.g., mini-games that don't contribute to progression) 3. Fancy effects that affect performance (e.g., excessive particle effects during cultivation). 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, and mobile optimization. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if mobile-specific optimizations are missing (touch controls, battery usage). 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 mobile game UI principles: 1) Harmonious color matching (no more than 3 primary colors with a consistent theme) 2) Proper layout spacing (element spacing follows the 8px multiple principle, touch targets ≥ 44px) 3) Professional font system (body font size ≥ 16px, readable on small screens). 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 mobile-friendly?",
+      "description": "Judge whether the dynamic effects conform to mobile interaction standards: 1) Touch feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) One-handed operation friendly layout. Deduct 5 points for each operation without feedback, 3 points for janky animations during state transitions, and 5 points if the game requires two hands for basic operations. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Role-Playing",
+  "difficulty": "hard"
+}

package/library/game_development-role-playing/cultivation-immortality-seeking-game.json

@@ -0,0 +1,68 @@
+{
+  "index": 1482,
+  "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 whenever possible. I'd like to create a text-based cultivation/immortality-seeking game. Please provide me with a framework and code for this.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core cultivation/immortality progression system implemented?",
+      "description": "Review whether the code implements a comprehensive cultivation system with different realms/stages (e.g., Qi Condensation, Foundation Establishment, Core Formation), cultivation resources, breakthrough mechanics, and bottlenecks. Score 0 if no progression system exists, 5 if only basic leveling is implemented, and 10 if the system includes varied cultivation techniques, resources management, and meaningful progression paths.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are character attributes and stats system properly designed?",
+      "description": "Check whether the character system includes both standard attributes (strength, intelligence, etc.) and cultivation-specific attributes (spiritual energy, comprehension, etc.). Evaluate if the stats affect gameplay meaningfully through formulas and checks. Deduct 3 points if attributes don't affect gameplay mechanics, 3 points if there's no clear growth curve, and 5 points if the system lacks cultivation-specific attributes. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is a robust text-based adventure/interaction system implemented?",
+      "description": "Assess if the code provides a text-based interface with clear navigation options, descriptive text output, and proper command parsing. Check for narrative text quality (descriptions of cultivation experiences, locations, NPCs). Score 0 if there's no interface, 5 if basic command input exists but lacks depth, and 10 if there's a rich interface with state tracking and dynamic text generation.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the game include world-building and environment elements?",
+      "description": "Evaluate the implementation of locations, sects/factions, special training areas, treasure hunting, and other world elements typical in cultivation novels. Check if different locations affect cultivation rates or provide unique events. Deduct 5 points if the world is static with no exploration options, and 3 points if areas don't affect gameplay mechanics. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid inputs, unexpected gameplay sequences, edge case character states) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Dynamic events based on character choices 2. Procedurally generated cultivation insights/epiphanies 3. Relationship systems with NPCs/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 ways to calculate the same stat) 2. Function modules unrelated to cultivation themes (e.g., modern-day elements that break immersion) 3. Overly complex systems that don't add to gameplay depth. 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/UI/data models), 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 game mechanics and presentation layer. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Is the text interface design clear and immersive?",
+      "description": "Evaluate whether the text display follows good principles: 1) Consistent formatting for different types of information 2) Clear distinction between narrative text, status information, and player options 3) Appropriate use of spacing and organization for readability. Deduct 3 points for confusing information layout, 5 points for inconsistent terminology that breaks immersion, and 5 points for text that's difficult to parse or follow. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the game state management and save system well-implemented?",
+      "description": "Judge whether the game properly handles state management, including: 1) Saving and loading game progress 2) Tracking player history and achievements 3) Persistent world changes based on player actions. Deduct 5 points for lack of save functionality, 3 points for incomplete state tracking that causes inconsistencies, and 5 points for not persisting important player choices. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Role-Playing",
+  "difficulty": "easy"
+}

package/library/game_development-role-playing/custom-character-creation-system.json

@@ -0,0 +1,68 @@
+{
+  "index": 52,
+  "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.\n\nPlease use HTML and JavaScript to implement a custom character system where players can choose and customize their character's appearance and attributes before starting the game.\n\n**Task**: Design a custom character system that allows players to select and customize their character's appearance and attributes before starting the game.\n\n**Hint**: You can provide different appearance options, equipment choices, and let players combine them according to their preferences.\n\nInclude comments in your code to help other developers understand your implementation process.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the character appearance customization system fully implemented?",
+      "description": "Review whether the code accurately implements various customization options (face, hair, body, skin tone, etc.) with real-time preview functionality. Score 0 if customization options are missing, 5 if only basic options are available, and 10 if a comprehensive set of appearance options with visual representation is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the character attribute allocation system properly implemented?",
+      "description": "Check whether the code implements a balanced attribute system (strength, agility, intelligence, etc.) with proper constraints (e.g., point allocation limits, minimum/maximum values). Verify if there's validation to prevent cheating. Score 0 if attribute customization is missing, 5 if basic attributes exist but lack validation, and 10 if a complete system with proper validation and visual feedback is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the equipment and accessory customization feature implemented?",
+      "description": "Evaluate whether players can select and preview different equipment items (weapons, armor, accessories) with visual representation. Check if equipment affects character attributes appropriately. Deduct 5 points if equipment doesn't visually appear on the character, 3 points if equipment doesn't affect attributes. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is there a character save/load mechanism implemented?",
+      "description": "Assess whether the code includes functionality to save customized characters (using localStorage or similar) and load them later. Check for export/import options and multiple character slot support. Deduct 5 points if only temporary session storage is used, and 3 points if there's no way to manage multiple character profiles. 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 input values, missing selections, 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. AI-assisted character recommendations 2. Character backstory generator 3. Social sharing of character designs). 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 modify the same attribute) 2. Function modules unrelated to character customization (e.g., a built-in minigame) 3. Fancy effects that affect performance (e.g., excessive particle effects or animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating UI/data/logic layers), code reusability, and proper documentation. 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 (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 visual feedback when changing character options 2) Smooth transitions when swapping between different character parts 3) Intuitive drag-and-drop or slider controls. Deduct 5 points for each operation without feedback, 3 points for jarring transitions between customization options, and 5 points for confusing navigation within the customization interface. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Role-Playing",
+  "difficulty": "medium"
+}

package/library/game_development-role-playing/dungeon-roguelike-game-generation.json

@@ -0,0 +1,68 @@
+{
+  "index": 390,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Ensure the generated code is executable when possible.\n\n## Generate a Dungeon Roguelike Game\n\n1. The main background should be a purple striped dungeon style\n2. The main interface should display \"Stinky Fish vs Rat Battle\" (as the main title) with a subtitle below showing \"🐭💗🐟\" and a \"Start Game\" button\n3. When clicking start, a caption appears introducing \"The stinky fish and rat fell into the sewer while fighting...\", with a \"Next\" button that transitions to the battle scene\n4. The battle scene is an adaptive rectangle frame with 2px distance from the screen edge, with rounded corners. Inside is an ocean scene composed of emoji 🌊\n5. The main characters are 🐟 and 🐭 at the bottom of the battle scene. Enemies appear at the top, represented by all possible monster/ugly animal emojis, with enemy types determined by available emojis\n6. There are 50 different battle cards with unique mechanisms. Each card can be upgraded to level 6. At level 6, fusion cards are unlocked. Max level cards can only be used for fusion and won't appear again. Fusion cards are only generated once, and won't appear again after selection\n7. A backpack button allows players to check their stats, selected cards and their levels\n8. A battle report box in the lower left corner, and a \"Challenge Next Level\" button appears after victory. Levels are endless. Every two levels, enemy stats increase by 10%. The protagonist recovers health after each level\n9. Clicking the protagonist 5 times activates God Mode, displaying a popup (God Backpack) with unlimited selectable cards (with a close button) and floating text \"The rat ate the stinky fish and evolved abilities\" that lasts for 3 seconds\n10. Base stats for both protagonist and enemies: Health 100, Attack 100, Defense 100, Critical Rate 5%, Critical Damage 50%, with 0 damage for each element (Wood, Fire, Water, Earth, Metal). Card skills can increase these stats\n11. For example, selecting a fire skill will display the corresponding attack effect\n12. All attacks, victories, and deaths have corresponding animations\n13. The UI is Instagram style with dungeon elements, cute enough that girls would like it\n14. Every 10 levels, a boss appears with stats 10% higher than the player but no skills. All player cards have skills, with attack power bonuses ranging from 100% to 150%. Examples include attacks that cost health, apply burning effects, or heal. Remember to maintain balance when designing these cards",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the main dungeon-style UI properly implemented?",
+      "description": "Check if the UI correctly implements the purple striped dungeon style with Instagram-inspired elements while maintaining cute aesthetics. The main title 'Stinky Fish vs Rat Battle' with the '🐭💗🐟' subtitle should be prominently displayed. UI elements should have consistent styling, proper spacing, and dungeon-themed decorative elements. Deduct 5 points if the purple striped background is missing, 3 points if the Instagram style is not evident, and 5 points if the UI lacks the cute aesthetics that would appeal to the target audience.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are the game flow transitions and narrative elements complete?",
+      "description": "Evaluate whether the code properly implements the starting sequence with the 'Start Game' button, the transition caption ('The stinky fish and rat fell into the sewer while fighting...'), and the 'Next' button that leads to the battle scene. Each transition should have appropriate animations. Check if the narrative elements are displayed with proper timing and if they can be skipped after being read. Deduct 5 points if any transition is missing, 3 points if animations are abrupt or missing, and 3 points if text appears/disappears without proper timing.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the battle scene correctly implemented with all required elements?",
+      "description": "Verify that the battle scene is an adaptive rectangle frame with exactly 2px distance from the screen edge, rounded corners, and contains an ocean scene composed of emoji 🌊. The main characters (🐟 and 🐭) should be positioned at the bottom, while enemies (various monster/ugly animal emojis) appear at the top. Check if the battle report box is present in the lower left corner and if the 'Challenge Next Level' button appears after victory. Deduct 5 points if the adaptive frame isn't properly implemented, 3 points if character positioning is incorrect, and 5 points if the ocean scene lacks visual coherence.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the card system fully implemented with progression mechanics?",
+      "description": "Assess if all 50 battle cards are implemented with unique mechanisms and proper upgrade paths (up to level 6). Check if fusion cards are unlocked at level 6, if max level cards are removed from selection, and if fusion cards only appear once. The backpack feature should allow players to check their stats and card collection/levels. Deduct 5 points if fewer than 50 distinct cards exist, 3 points if the fusion system doesn't work correctly, 5 points if card progression doesn't persist between battles, and 3 points if the backpack functionality is incomplete.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as rapid clicking, resizing the window, network interruption, 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. Additional visual effects for special attacks 2. Easter eggs beyond the God Mode 3. Dynamic difficulty adjustment based on player performance). 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 different healing mechanisms that functionally do the same thing) 2. Function modules unrelated to the game's core mechanics (e.g., unnecessary mini-games) 3. Fancy effects that affect performance (e.g., excessive particle effects that cause 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/controllers), state management patterns, 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 game assets are not properly managed or loaded efficiently. 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 (consistent with the purple dungeon theme without clashing 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 game balance and progression system well-designed?",
+      "description": "Analyze if the game provides a balanced experience with the specified stats system (Health, Attack, Defense, Critical Rate, Critical Damage, and elemental damages). Check if enemy progression (10% increase every two levels) creates an appropriate difficulty curve. Evaluate if the card skill power bonuses (100% to 150%) are balanced and if the God Mode feature doesn't completely break the game. Deduct 5 points if enemy scaling creates impossible situations, 3 points if card skills are poorly balanced, and 3 points if the progression system lacks meaningful choices. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Role-Playing",
+  "difficulty": "hard"
+}

package/library/game_development-role-playing/dynamic-npc-companion-system.json

@@ -0,0 +1,68 @@
+{
+  "index": 118,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate, expert responses. Make sure the code you generate is executable.\nPlease use HTML and JavaScript to implement a dynamic NPC companion system.\n\n**Task**: Implement a dynamic NPC companion system where players can command teammates in combat or puzzle-solving.\n\n**Hint**: You can set up a simple command system such as attack, follow, hold position, and have companions act according to the player's commands.\n\nPlease include some comments in your code so other developers can understand your implementation process.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the NPC companion command system fully implemented?",
+      "description": "Review whether the code accurately implements the core command system (attack, follow, hold position) through HTML/JavaScript, including command issuance, command visualization, and command execution by NPCs. Score 0 if no command system is implemented, 5 if only basic commands exist without proper execution logic, and 10 if a complete command system with visual feedback is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the NPC AI behavior system properly designed?",
+      "description": "Evaluate the AI decision-making logic for NPC companions. Check for state machines or behavior trees that govern NPC responses to commands and environmental conditions. Companion NPCs should exhibit appropriate autonomous behavior when not directly commanded. Deduct 3 points if NPCs lack situational awareness, 5 points if they don't have independent decision-making capabilities, and 3 points if path-finding is missing or broken. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are combat and puzzle-solving interactions implemented?",
+      "description": "Check whether the system includes both combat mechanics (such as targeting, attacking, damage calculation) and puzzle-solving capabilities (such as object interaction, position-based puzzles). NPCs should be able to assist in both contexts based on player commands. Deduct 5 points if either combat or puzzle systems are missing, and 3 points if the implemented systems lack depth or meaningful interaction. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is there a well-designed NPC status and feedback system?",
+      "description": "Assess whether the implementation includes visual indicators of NPC status (health, current command, action state) and provides feedback when commands are issued or completed. The system should communicate NPC states clearly to the player. Deduct 3 points if status indicators are missing, 4 points if command feedback is inadequate, and 3 points if there's no indication of task completion. 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 commands, NPCs being unable to reach targets, collision detection failures, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Adaptive NPC personalities 2. Dynamic dialogue system based on situation 3. Learning system where NPCs improve based on player actions). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple command handling systems) 2. Function modules unrelated to the NPC companion system (e.g., unrelated game mechanics) 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 NPC logic/command system/UI layers), code documentation quality, 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 for command UI and NPC indicators 2) Proper layout spacing for command buttons and status displays 3) Clear visual hierarchy between player and NPC elements. Deduct 3 points for each crowded visual element, 5 points for a confusing or inconsistent UI, and 5 points for poor command visibility during action sequences. 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) Command execution feedback delay ≤ 100ms 2) NPC animation transitions are smooth and natural 3) Clear visual indication when switching between command modes. Deduct 5 points for each command without feedback, 3 points for jerky NPC movements or animations, and 5 points for confusing command state visualization. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Role-Playing",
+  "difficulty": "medium"
+}

package/library/game_development-role-playing/family-generational-marriage-drama-game.json

@@ -0,0 +1,68 @@
+{
+  "index": 220,
+  "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 display. Create a family generational game with a fictional background that is comfortable and peaceful. Avoid fantasy, blood, horror, poisoning, birthmarks, metaphors, revenge, previous dynasties, urgent choices, and focus more on character development. I am the young lady of the family, with a mother and a random number of siblings. The game includes ancient professions like officials, scholars, warriors, doctors, merchants, farmers, etc., and differentiates between nobility and commoners. The game mainly focuses on marriage and family drama. The relationship development should progress naturally with reasonable scenarios and dialogues that match character personalities. In intimate scenes, use more casual and open language, and use parentheses to show physical actions or thoughts to create embarrassing, strong emotional experiences with colorful details of emotional reactions. No poison plots, scheming, or active seduction. I just want to have a romantic relationship with some spice.\n\nReply settings: Update the time and character information in the main interface for each round. Wrap all information in pseudo code blocks. Use asterisks for prompts, quotation marks for dialogues, and add emoji expressions. Use tree diagrams to show character relationship networks. The code blocks should fit mobile display dimensions. Reply \"next month\" to advance to the next month, or \"restart\" to regenerate character information.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core family simulation system implemented comprehensively?",
+      "description": "Review whether the code accurately implements a family generational simulator with proper character creation, attribute systems, and relationship tracking. Check for implementation of noble/commoner distinction, ancient profession system, and family hierarchy dynamics within the specified comfortable setting.Score 0 if core simulation is missing, 5 if basic family structure exists but lacks depth, 10 if the system fully models complex family relationships with appropriate attribute tracking and status changes based on interactions.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the character development and relationship progression logic properly implemented?",
+      "description": "Evaluate whether the code includes mechanisms for natural relationship development with context-appropriate dialogues and personality-driven interactions. Check if the system avoids prohibited themes (fantasy, horror, revenge plots) while still creating engaging relationship mechanics.Deduct 5 points if relationship progression is purely random without personality considerations. Deduct 3 points if dialogues don't reflect character personalities. The full score is 10 points for a robust character development system that progresses naturally with meaningful choice consequences.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are the game mechanics for time progression and event generation implemented?",
+      "description": "Check whether the code implements a functional month-by-month progression system with appropriate events, character aging, relationship changes, and new scenario generation. Verify that the \"next month\" command properly advances game state and updates all relevant variables.Award 0 points if time progression is missing, 5 points if basic monthly updates occur but lack event variety or consequence, and 10 points for a comprehensive system with appropriate life events, seasonal changes, and character development milestones.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the user interface implementation complete with all required display elements?",
+      "description": "Verify that the code properly implements all specified UI elements: code blocks for information, proper use of asterisks for prompts, quotation marks for dialogues, emojis for expressions, and relationship tree diagrams. Check if the display is optimized for mobile dimensions as requested.Deduct 2 points for each missing UI element (time/character updates, code blocks, asterisks for prompts, quotation marks for dialogues, emojis, relationship trees). Award 10 points only if all elements are properly implemented and responsive to game state changes.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid commands, unexpected input, state inconsistencies) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle edge cases.Give 10 points for comprehensive error handling and state validation, 5 points for average robustness with some edge case handling, and 0 points if no exceptions are handled.",
+      "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. Procedurally generated character backstories 2. Dynamic personality evolution based on life events 3. Seasonal festivals or special events 4. Family heirlooms or traditions that develop over time).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 generation systems) 2. Function modules unrelated to family simulation (e.g., unrelated mini-games) 3. Fancy effects that affect performance (e.g., excessive animations or graphics).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/state management layers), code organization, and maintainability. Check for proper encapsulation of game mechanics and state management.Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no clear separation between UI 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 for relationship trees and character information 3) Professional text formatting with consistent use of prompts, dialogue markers, and emojis.Deduct 3 points for each cluttered visual element, 5 points for inconsistent text formatting, and 5 points for poorly organized relationship trees. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the command processing and game state updates are responsive and intuitive: 1) Command feedback delay is minimal 2) State transitions are clear with appropriate feedback 3) Character and relationship updates are visually obvious after changes.Deduct 5 points for each operation without feedback, 3 points for confusing state transitions, and 5 points for difficulty in tracking relationship or character changes. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Role-Playing",
+  "difficulty": "easy"
+}

package/library/game_development-role-playing/game-backpack-item-management-system.json

@@ -0,0 +1,68 @@
+{
+  "index": 169,
+  "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 purposes.\nPlease use HTML and JavaScript to implement a Backpack and Item Management system.\n**Task**: Implement a backpack system that allows players to collect, view, and use different items.\n**Tip**: You can use a simple list to manage items and set different effects for each item.\ngame, and include some comments in the code so other developers can understand your implementation process.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the basic backpack UI structure properly implemented?",
+      "description": "Check if the HTML/CSS implementation creates a visually distinct backpack interface with appropriate grid or list layout. Verify that items are visually represented (with icons or images) and have clear boundaries. Score 3 if only basic HTML is used without styling, 7 if the backpack has basic styling but lacks visual hierarchy, and 10 if the implementation includes a polished interface with proper spacing, borders, and item slots.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the item management system functionality complete?",
+      "description": "Evaluate whether core backpack operations are implemented: adding items, removing items, and displaying item information. Check if items have properties (like name, description, type, quantity). Verify that the system manages item stacking or unique items appropriately. Score 3 if only basic item display is implemented, 7 if basic operations work but with limitations, and 10 if all core functionality is present including proper handling of edge cases (full inventory, duplicate items, etc.).",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are item interactions and usage mechanisms implemented?",
+      "description": "Assess if the code includes ways to use or interact with items (clicking/selecting to use, equipping, consuming). Verify that different item types have different usage effects. Score 3 if items can only be selected but not used, 5 if basic usage is implemented but all items behave the same way, and 10 if multiple interaction types are implemented with different effects based on item type.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is data persistence or state management implemented?",
+      "description": "Check if the backpack system maintains state between operations and if any form of data persistence is implemented (localStorage, sessionStorage, or simulated server-side storage). Verify if item quantities and states are properly tracked and updated. Score 3 if state is lost on page refresh, 7 if basic state management exists but has flaws, and 10 if robust state management with persistence is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as adding items to a full backpack, using items with insufficient quantity, invalid user inputs, 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. Drag-and-drop inventory management 2. Item categories with filtering 3. Item combination/crafting system 4. Visual effects when using items). 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 handle item addition) 2. Function modules unrelated to inventory management (e.g., embedded mini-games) 3. Fancy effects that affect performance (e.g., excessive animations for simple interactions). 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 model/view/controllers), code comments quality, and adherence to JavaScript best practices. 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 variable/function names are unclear or inconsistent. 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) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance. Deduct 5 points for each operation without feedback, 3 points for laggy animations during item management, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Role-Playing",
+  "difficulty": "easy"
+}