@getollie/cli 0.0.4 → 0.2.0

package/library/game_development-role-playing/character-customization-game-html-javascript.json

@@ -1,68 +0,0 @@
-{
-  "index": 48,
-  "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 whenever possible.\n\nPlease use HTML and JavaScript to implement a character customization game that allows players to customize their character's appearance and abilities. You should provide a user interface that allows players to select different skins, colors, and ability configurations.\n\nInclude comments in your code so other developers can understand your implementation process.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the character customization interface fully implemented?",
-      "description": "Review whether the code accurately implements all core customization elements including skin selection, color customization, and ability configuration through HTML/JavaScript. Score 0 if the core interface elements are missing, 5 if only partial customization options are available, and 10 if the interface provides comprehensive character customization with visual previews.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the appearance customization system comprehensive?",
-      "description": "Evaluate the range and depth of appearance customization options. Check for variety in character elements (face, hair, body, clothing, accessories), color selection mechanisms (RGB/HSL pickers, preset palettes), and whether changes are immediately reflected in a preview. Deduct 3 points if fewer than 3 customizable appearance elements are available, 3 points if color customization is limited, and 2 points if there's no real-time preview. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the ability configuration system balanced and interactive?",
-      "description": "Check whether the ability configuration system includes a balanced point allocation mechanism (e.g., limited total points, trade-offs between different abilities), visual representation of character stats, and effect demonstration. Deduct 5 points if there are no constraints on ability allocation, 3 points if visual feedback on abilities is missing, and 2 points if there's no effect preview or explanation. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is persistence and state management properly implemented?",
-      "description": "Evaluate whether the code includes state management to persist customization choices (localStorage/sessionStorage), undo/redo functionality, save/load character presets, and clean state transitions. Deduct 5 points if no persistence mechanism exists, 3 points if state history management is absent, and 2 points if there are no preset management features. 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, browser compatibility issues, performance under heavy customization, 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. Randomize character feature 2. Social sharing of character designs 3. Animation of character based on ability scores 4. AR/camera integration for custom faces). 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 color pickers with the same functionality) 2. Function modules unrelated to character customization (e.g., an unnecessary minigame) 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 UI/logic/data layers), code comments as requested, consistency in naming conventions, and overall architecture. 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 code 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) Changes to character appearance are instantly reflected (≤ 100ms) 2) Transition animations when switching between customization sections (300-500ms) 3) Clear visual feedback when selecting options. Deduct 5 points for each operation without feedback, 3 points for lagging character preview updates, and 5 points for unintuitive navigation between customization sections. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Role-Playing",
-  "difficulty": "medium"
-}

package/library/game_development-role-playing/character-dialogue-system-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 162,
-  "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 character dialogue system game where players can interact with NPCs, obtain information or quests. Set up dialogue boxes and conversation options, and trigger different dialogue content based on the player's choices.\n\nInclude comments in your code so other developers can understand your implementation process.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the dialogue system core functionality fully implemented?",
-      "description": "Review whether the code accurately implements a dialogue box system with NPC conversations and player response options. Check if the dialogue content changes based on player choices and if the dialogue flow is properly managed. Score 0 if the core dialogue interaction is not implemented, 5 if only basic dialogue display is implemented without branching, and 10 if the system includes conditional dialogue paths, dialogue history, and proper state management.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the NPC interaction system properly designed?",
-      "description": "Evaluate if the code includes a well-structured NPC system with unique characters having different dialogue options. Check if NPCs can store state (like remembering previous conversations) and if their dialogue changes based on player history or game state. Deduct 5 points if NPCs are just static dialogue dispensers without memory, 3 points if there's no variety in NPC personalities or dialogue styles. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is a quest/information system integrated with the dialogue?",
-      "description": "Check if the system allows NPCs to provide quests or important information through dialogue, with proper tracking mechanisms. Verify if quests can be accepted, tracked, completed, and rewarded through the dialogue system. Deduct 5 points if there's no actual quest functionality tied to dialogue, 3 points if quest states aren't properly tracked or don't affect subsequent dialogue. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the dialogue UI design user-friendly and well-implemented?",
-      "description": "Assess if the dialogue UI is well-designed with clear indication of who's speaking, readable text presentation, obvious player choices, and smooth transitions between dialogue states. Check if the UI adapts to different text lengths and number of options. Deduct 5 points for poor text presentation (too small, bad contrast), 3 points for confusing option selection mechanisms, and 3 points for jarring transitions. 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 unexpected user input, clicking rapidly through dialogue, or skipping conversations) and provide friendly error handling. Code with strong robustness should prevent dialogue state corruption and handle edge cases gracefully, 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. Character portraits that change with emotions 2. Voice/sound effects for dialogue 3. Typewriter text effect 4. Dialogue history/log system 5. Keyword highlighting in important dialogue). Add 2 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 dialogue functions (e.g., multiple text display mechanisms) 2. Function modules unrelated to dialogue (e.g., complex combat systems) 3. Fancy effects that affect readability or usability of dialogue. 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 data/logic/UI layers), code organization, and proper commenting as specified in the requirements. Deduct 5 points if global state pollution is found or dialogue data is hardcoded throughout; deduct 3 points if the code lacks the requested comments; deduct 5 points if the code duplication rate is too high (over 30%). The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the dialogue UI follows modern design principles: 1) Harmonious color matching for dialogue boxes and character identification 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional typography (body font size ≥ 14px, line height over 1.5 times, proper contrast). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for poor text readability. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects in dialogue conform to human perception characteristics: 1) Response delay when selecting options ≤ 100ms 2) Smooth transitions between dialogue segments 3) Clear visual feedback when making choices. Deduct 5 points for each interaction without feedback, 3 points for jarring transitions between dialogue states, and 5 points for confusing navigation through dialogue options. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Role-Playing",
-  "difficulty": "easy"
-}

package/library/game_development-role-playing/character-leveling-skill-tree-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 2,
-  "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 character leveling up and skill tree system.\n\n**Task**: Implement a character leveling system where characters can level up by collecting experience points, unlock new skills or enhance attributes.\n\n**Hint**: You can use a simple experience point system and skill tree structure to manage upgrades and skill unlocking.\n\nGame, and add some comments to your code so other developers can understand your implementation process.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the character leveling system implemented correctly?",
-      "description": "Review whether the code accurately implements an experience point tracking system, level calculation, and level-up events. Check if the experience requirements for each level follow a logical progression (e.g., logarithmic or exponential growth). Verify if the code handles edge cases like max level cap and experience overflow. Score 0 if the core level system is missing, 5 if only basic leveling is implemented, and 10 if it includes animations, sound effects, and visual feedback for level-up events.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "How well is the skill tree structure designed?",
-      "description": "Evaluate if the skill tree has a logical hierarchical structure with clear dependencies between skills. Check if there are multiple branching paths, prerequisites for skill unlocks, and proper visualization of connections between related skills. Verify if skill nodes store proper metadata (cost, effects, requirements). Deduct 5 points if skills aren't organized in a tree/graph structure, 3 points if there are no skill dependencies/prerequisites, and 2 points if the tree doesn't visually represent relationships between skills. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the skill unlocking mechanism properly implemented?",
-      "description": "Check if the code validates all conditions before unlocking skills (level requirements, skill points, prerequisites). Verify if the system prevents invalid operations like unlocking unavailable skills or spending more points than available. Examine if there's proper state management for locked/unlocked skills and visual indication of available/unavailable skills. Deduct 5 points if prerequisite validation is missing and 5 points if there's no proper error handling for invalid unlock attempts. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are character attributes and their enhancement implemented?",
-      "description": "Assess if the system includes character attributes (like strength, intelligence, etc.) that can be enhanced through leveling or skill points. Check if attribute changes affect character capabilities in meaningful ways. Verify if there are attribute caps or diminishing returns implemented. Deduct 3 points if attributes don't impact gameplay/visuals, 4 points if there's no way to customize attribute distribution, and 3 points if attribute scaling is unbalanced. 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, skill point misallocation, attribute reset requests, 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 preview animations 2. Respec/reset mechanisms with appropriate costs 3. Skill combos for special effects when certain combinations are unlocked). 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 attribute bonus) 2. Function modules unrelated to the skill tree system (e.g., an unnecessary inventory system) 3. Fancy effects that affect performance (e.g., excessive particle effects on every 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 character data/skill tree logic/UI layers), code organization, and maintainability. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the code lacks proper comments as requested in the requirements. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the skill tree UI 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 when allocating points or unlocking skills 2) Transition animations when unlocking skills or leveling up controlled between 300-500ms 3) Clear visual focus guidance highlighting available skills or next level milestone. Deduct 5 points for each operation without feedback, 3 points for sluggish animations during skill tree navigation, and 5 points for hard-to-find important UI elements like available skill points or level progress. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Role-Playing",
-  "difficulty": "easy"
-}

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

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

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

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

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

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