@getollie/cli 0.0.5 → 0.2.0

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

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

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

@@ -1,68 +0,0 @@
-{
-  "index": 20,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable for demonstration.\nPlease use HTML and JavaScript to implement a Magic Academy game where players need to learn magical skills and pass exams. Hint: Design magic courses and an examination system.\nInclude comments in your code so other developers can understand your implementation process.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Magic Academy core learning system fully implemented?",
-      "description": "Review whether the code accurately implements a learning progression system through HTML/JavaScript, with clearly defined magical skills, learning paths, and skill acquisition mechanics. Score 0 if the core learning mechanics are not implemented, 5 if only basic skill acquisition exists, and 10 if there's a comprehensive magical skill tree with prerequisites and advancement logic.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the examination system properly implemented?",
-      "description": "Evaluate whether the examination system includes different question types (multiple-choice, spell casting simulations, practical challenges), difficulty progression, and scoring mechanisms. The system should provide meaningful feedback on exam performance and track student progress. Deduct 5 points if exams are too simplistic, 3 points if feedback is limited to pass/fail without details. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are the magical courses and curriculum well-designed?",
-      "description": "Check if the game includes diverse magical disciplines (e.g., potions, spells, magical creatures), each with unique learning materials, interactive exercises, and thematic consistency. Each course should have clear objectives and learning outcomes. Deduct 3 points for each missing major discipline, and 5 points if courses lack progressive difficulty. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there a player progression and achievement system?",
-      "description": "Assess whether the code implements character development features including experience points, level progression, skill mastery tracking, and achievements/badges. The system should show meaningful growth as players advance through the academy. Deduct 5 points if progression is linear without choices, and 3 points if achievements are too simplistic. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid spell inputs, exam submission errors, interrupted learning sessions, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Interactive spell casting with mouse gestures 2. Dynamic potion brewing simulations 3. Magical dueling with other students). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple separate spell casting systems) 2. Function modules unrelated to a magic academy (e.g., a complex inventory system with no educational purpose) 3. Fancy effects that affect performance (e.g., excessive particle effects). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating game mechanics/UI/data management), code documentation completeness, and maintainability. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if comprehensive comments are missing as requested. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows magical academy aesthetics with modern design principles: 1) Thematic color palette suitable for a magical setting 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Fantasy-appropriate typography (readable but thematic). Deduct 3 points for each cluttered UI section, 5 points for inconsistent visual themes, and 5 points for poor readability of critical information. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the magical interaction intuitive and engaging?",
-      "description": "Judge whether the magical interactions are intuitive and satisfying: 1) Clear visual feedback for spell casting ≤ 100ms 2) Satisfying animations for successful magical effects 3) Progressive difficulty in magical interactions. Deduct 5 points for each magical action without clear feedback, 3 points for confusing interaction patterns, and 5 points if key magical functions are difficult to discover. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Role-Playing",
-  "difficulty": "hard"
-}

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

@@ -1,68 +0,0 @@
-{
-  "index": 88,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure the generated code is executable for demonstration.\n\nPlease use HTML and JavaScript to implement a Magic School.\nTask: Design a magic learning game where players complete tasks by learning spells and casting magic.\nHint: Implement a magic system that includes spell learning and effect display.\n\nPlease include comments in your code so other developers can understand your implementation process.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the magic spell learning system properly implemented?",
-      "description": "Review whether the code implements a comprehensive spell learning mechanism including spell collection, practice progression tracking, and mastery levels. Check if there's a structured spell database with properties like element type, difficulty, and effects. Score 0 if no learning system exists, 5 if only basic spell acquisition is present, and 10 if there's a complete progression system with feedback and skill advancement.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the magic casting mechanism interactive and engaging?",
-      "description": "Evaluate the implementation of spell casting interactions - whether they use keyboard combinations, mouse gestures, or other creative input methods. Check if the casting mechanism includes timing elements, accuracy requirements, or combination sequences that make spellcasting challenging and engaging. Deduct 5 points if casting is limited to simple button clicks, and 3 points if there's no visual feedback during casting. Full score requires multiple interaction patterns that increase in complexity with spell power.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are the magic effects visualized appropriately?",
-      "description": "Assess the visual representations of spells with animations, particle effects, or transformations. Each spell should have a distinctive visual signature that relates to its element or purpose. Deduct 5 points if effects are generic across different spells, 3 points if animations are static or jarring. Award full points only if the visualization includes smooth transitions, appropriate sound effects, and visual feedback proportional to spell power.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there a task/quest system to drive player progression?",
-      "description": "Check if the code implements a structured task system with clear objectives, completion criteria, and rewards. Quests should progressively introduce more complex magic concepts and require mastery of previously learned spells. Score 0 if no quest system exists, 5 if only basic tasks are present without progression logic, and 10 if there's a complete branching quest system with difficulty scaling and narrative elements.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid spell inputs, rapid-fire casting attempts, or interrupted spell sequences) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Spell combinations creating new effects 2. Environmental interactions with spells 3. Spell customization or evolution system). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar spell effects with different names 2. Function modules unrelated to magic learning (e.g., an overly complex character creator) 3. Fancy effects that affect performance without enhancing gameplay. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating spell logic/visual effects/user interaction layers), commenting quality, and code organization. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there are no meaningful comments explaining magic system components. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows magical theme principles: 1) Thematic color matching appropriate for a magical setting 2) Proper layout spacing for spell books, casting areas, and feedback displays 3) Professional font system suitable for a magical academy aesthetic. Deduct 3 points for each crowded visual element, 5 points for inconsistent magical theming, and 5 points for chaotic text-image layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the magical effects conform to expected fantasy aesthetics: 1) Spell casting feedback delay ≤ 100ms 2) Magic effect animations controlled between 300-1000ms based on power 3) Clear visual guidance for spell learning progression. Deduct 5 points for each spell without visual feedback, 3 points for choppy animations during complex spells, and 5 points for unintuitive spell learning interfaces. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Role-Playing",
-  "difficulty": "medium"
-}

package/library/game_development-role-playing/monster-slaying-leveling-game-web-browser.json

@@ -1,68 +0,0 @@
-{
-  "index": 1225,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the code you generate is executable for demonstration. Help me create a small monster-slaying leveling game that can be played directly in a web browser.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core monster-slaying combat system fully implemented?",
-      "description": "Review whether the code accurately implements the combat mechanics through HTML/JavaScript, including player attack/defense calculations, monster AI behavior, hit point calculations, and damage formulas. Score 0 if basic combat logic is missing, 5 if only simple attack mechanics exist, and 10 if comprehensive combat system with skills, critical hits, and status effects are fully implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the character leveling and progression system complete?",
-      "description": "Check whether the experience point system, level progression, attribute enhancement (HP/MP/Attack/Defense), skill tree unlocking, and equipment upgrade mechanisms are properly implemented. Deduct 5 points if stat scaling is unbalanced, 3 points if skill progression lacks depth. Full score requires exponential XP curves and meaningful character growth.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the monster variety and AI behavior well-designed?",
-      "description": "Evaluate whether multiple monster types exist with distinct behaviors, attack patterns, and difficulty scaling. Check if monsters have appropriate AI logic, spawn mechanics, and boss encounters. Deduct 5 points if all monsters behave identically, 3 points if difficulty progression is poorly balanced. Full score requires diverse enemy types with unique mechanics.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the game state management and save system implemented?",
-      "description": "Check whether the code includes persistent game state using localStorage/sessionStorage, ability to save/load progress, inventory management, and quest/achievement tracking. Deduct 5 points if progress cannot be saved, 3 points if state management is inconsistent. Give 10 points if complete persistence with data validation is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid user input, NaN calculations, negative stats, boundary conditions, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should effectively handle edge cases and prevent game-breaking bugs, giving 10 points. If robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes engaging features that enhance gameplay experience (e.g., 1. Dynamic loot generation system 2. Mini-map or exploration mechanics 3. Achievement system with rewards 4. Sound effects and particle effects 5. Story/quest narrative elements). Add 2 points for each well-implemented innovative feature (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple inventory systems) 2. Function modules unrelated to monster-slaying gameplay (e.g., built-in calculator) 3. Performance-heavy effects that cause lag (e.g., excessive particle systems). Deduct 3 points for each redundancy found, and directly deduct 10 points if core gameplay is interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (separating game logic/rendering/data layers), code organization, maintainability, and performance optimization. Deduct 5 points if global state pollution is found or no clear architecture; deduct 5 points if code duplication rate exceeds 30%; deduct 3 points if performance is poor (frame drops, memory leaks). Full score requires clean, well-structured code.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface design meet professional gaming standards?",
-      "description": "Evaluate whether the UI follows game design principles: 1) Clear HUD displaying health/mana/XP bars 2) Intuitive inventory and character panels 3) Readable fonts and appropriate contrast 4) Consistent visual theme and color scheme. Deduct 3 points for cluttered interface elements, 5 points for poor readability, and 5 points for inconsistent visual design. Full score requires polished, cohesive game UI.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the gameplay interaction smooth and responsive?",
-      "description": "Judge whether game interactions feel responsive and engaging: 1) Combat actions have immediate visual feedback 2) Smooth animations for attacks/movement 3) Clear indication of player actions and results 4) Intuitive controls and button placement. Deduct 5 points for unresponsive controls, 3 points for choppy animations, and 5 points for unclear feedback mechanisms. Full score requires fluid, satisfying gameplay interactions.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Role-Playing",
-  "difficulty": "medium"
-}

package/library/game_development-role-playing/multiple-choice-character-life-simulation-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 953,
-  "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 and ready for demonstration. Design a small, immediately playable game consisting of multiple-choice questions, similar to a character development/life simulation game.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the multiple-choice question system properly implemented?",
-      "description": "Evaluate whether the code implements a robust question system with clear data structure for questions, options, and results. Check for features like question randomization, answer tracking, and proper state management. Score 0 if no functional question system exists, 5 if basic functionality is present but lacks variety, 10 if the system is comprehensive with validation and variety.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the character development/life simulation aspect implemented?",
-      "description": "Check if the code includes character state variables (e.g., personality traits, skills, relationships) that evolve based on player choices. Verify the presence of a cause-effect system where choices influence character development. Score 0 if there's no character development, 5 if basic stat tracking exists, 10 if comprehensive character evolution with meaningful impacts is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the game flow and progression logic fully functional?",
-      "description": "Analyze whether the code manages game stages, progression, and events properly. Look for features like branching storylines, milestone events based on character development, and proper game ending conditions. Deduct 5 points if progression is linear without branches, 3 points if there's no clear ending. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the game immediately playable with minimal setup?",
-      "description": "Verify that the code can run directly in a browser without complicated setup steps. Check if it includes all necessary resources bundled together, proper initialization, and clear instructions for players. Deduct 5 points if external dependencies aren't properly managed, 5 points if initialization requires manual steps. 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 user input, browser compatibility issues, or unexpected game 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 character portraits that change with development 2. Animated transitions between questions 3. Background music/sound effects tied to character mood). 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 scoring systems coexisting) 2. Function modules unrelated to the character simulation (e.g., unnecessary mini-games) 3. Fancy effects that affect performance (e.g., excessive animations slowing gameplay). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating game data/logic/view layers), maintainability, and code organization. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no clear separation of concerns. 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 transitions, 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/post-apocalyptic-game-vue3-typescript.json

@@ -1,68 +0,0 @@
-{
-  "index": 396,
-  "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. Develop a post-apocalyptic game using Vue3 and TypeScript with main gameplay elements including survival, searching/scavenging, combat, base building, quests, and companions.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core survival game system fully implemented?",
-      "description": "Review whether the code accurately implements essential survival mechanics using Vue3 and TypeScript (hunger/thirst/health stats, day-night cycle, environmental hazards). Score 0 if core survival mechanics are missing, 5 if basic stats are implemented but lack dynamic environmental interactions, and 10 if the survival system is comprehensive with meaningful player choices and consequences.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the scavenging and inventory management system properly designed?",
-      "description": "Check if the code includes a robust inventory system with TypeScript interfaces for items, weight/space constraints, and procedurally generated loot tables. Examine whether scavenging locations are diverse with risk-reward mechanics. Deduct 5 points if items lack properties or categorization, 3 points if inventory UI is unintuitive, and 3 points if the scavenging system lacks variety or challenge. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the combat system engaging and balanced?",
-      "description": "Evaluate whether the combat system uses TypeScript classes for weapons with distinct properties, includes both melee and ranged options, and features enemy AI with varying difficulty. Check for Vue reactive health/damage systems and visual combat feedback. Score 3 points for basic attack implementation, 7 points for a complete combat system with multiple weapons, and 10 points for a polished system with strategic depth and balanced progression.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the base building functionality interactive and meaningful?",
-      "description": "Assess whether the Vue components for base building include placement validation, resource requirements, functional buildings that affect gameplay, and upgrade paths. Check if TypeScript interfaces enforce building prerequisites and constraints. Deduct 5 points if building placement is buggy, 5 points if buildings don't meaningfully impact gameplay, and 3 points if there's no defensive value to constructions. 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, async operation failures, state inconsistencies, etc.) and provide friendly error prompts or recovery mechanisms. Check for proper TypeScript typing, null checks, and Vue error boundaries. 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 gameplay 2. Faction system with reputation mechanics 3. Procedurally generated storylines). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple inventory systems coexisting) 2. Function modules unrelated to post-apocalyptic survival (e.g., a built-in mini-game that breaks immersion) 3. Overengineered components that affect performance (e.g., unnecessary re-renders in Vue components). 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 Vue3 composition API usage, TypeScript typing strictness, state management practices, and component reusability. Check for proper separation of concerns between game logic and UI. Deduct 5 points if global state is handled poorly outside a proper store; deduct 5 points if TypeScript types are missing or incorrect; deduct 5 points if Vue components are overly coupled. 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 post-apocalyptic aesthetics while maintaining usability: 1) Thematic color palette that conveys the setting 2) Proper HUD layout with critical survival information easily visible 3) Clear visual hierarchy distinguishing interactive elements from decorative ones. Deduct 3 points for each cluttered UI section, 5 points for inconsistent visual language, and 5 points for poor readability of critical information. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the game's Vue transitions and animations enhance the experience: 1) Immediate feedback for player actions (≤100ms) 2) Smooth transitions between game states 3) Proper loading indicators for longer operations. Deduct 5 points for each interaction without feedback, 3 points for jarring transitions between game screens, and 5 points for performance issues during complex interactions (like combat or base building). The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Strategy",
-  "difficulty": "hard"
-}

package/library/game_development-role-playing/rpg-equipment-attribute-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 68,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable and displayable.\n\nPlease use HTML and JavaScript to implement a Role-Playing Game (RPG): Equipment and Attribute System.\n\n**Task**: Design an equipment system where players can change equipment, with different equipment affecting character attributes and abilities.\n\n**Hint**: You can create an attribute system and adjust attribute values based on equipment.\n\nFor the game, include comments in your code to help other developers understand your implementation process.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the equipment system fully implemented?",
-      "description": "Review whether the code implements a complete equipment system including equipment slots (weapons, armor, accessories, etc.), equipment properties (stats, effects), and the ability to equip/unequip items. Score 0 if there is no equipment system, 5 if only basic equipment slots are implemented, and 10 if there's a complete system with diverse equipment types and properties.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the attribute system properly implemented and integrated with equipment?",
-      "description": "Check if the code creates a robust character attribute system (strength, agility, intelligence, etc.) and properly calculates how equipment modifies these attributes. Deduct 5 points if equipment doesn't affect attributes, 3 points if attribute calculations contain errors, and 2 points if attribute updates don't trigger visual feedback. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Does the implementation include equipment comparison and inventory management?",
-      "description": "Evaluate whether players can compare equipment stats before equipping and if there's an inventory system to manage unequipped items. Score 3 points for basic item comparison, 4 points for visual comparison indicators, and 3 points for a functional inventory with sorting/filtering. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there a visual representation of equipped items on the character?",
-      "description": "Assess whether equipped items are visually represented on the character model or through icons/indicators. Award 5 points for basic visual indicators showing equipped gear, 3 additional points if equipment changes character appearance, and 2 more points if there are equip/unequip animations. 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 equipping incompatible items, inventory management edge cases, invalid attribute values, 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. Equipment set bonuses 2. Equipment durability/repair system 3. Equipment enhancement/upgrading). 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 equipment/attributes (e.g., an unrelated mini-game) 3. Fancy effects that affect performance (e.g., unnecessary particle effects when equipping items). 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 equipment logic/attribute calculation/UI layers), code organization, and commenting quality as requested in the task. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if comprehensive comments are missing. 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 feedback when equipping/unequipping items or when attributes change. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast interactions, 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/rpg-leveling-monster-fighting-text-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 1764,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to generate executable code for display whenever possible. Create a text-based game for me, specifically an RPG-style leveling and monster-fighting text game, implemented in HTML.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core RPG combat system fully implemented?",
-      "description": "Review whether the code accurately implements essential RPG combat mechanics through HTML/JavaScript, including player attributes (HP, MP, strength, etc.), enemy encounters, turn-based combat, and damage calculation. Score 0 if core combat mechanics are missing, 5 if basic combat is implemented but lacks depth, and 10 if the system includes critical hits, special attacks, and varied enemy behaviors.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the character progression system properly designed?",
-      "description": "Evaluate the implementation of leveling mechanics, experience point accumulation, skill progression, and statistical growth. Check if the code includes level-up events with meaningful attribute increases, unlockable abilities, and balanced progression curves. Deduct 5 points if the leveling system is too simplistic (just number increases), and 3 points if there's no meaningful progression impact on gameplay. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the game economy and inventory system functional?",
-      "description": "Assess whether the code implements a proper inventory system with items, equipment management, currency, and potentially crafting mechanics. Check for item differentiation (weapons, armor, consumables), equipment effects on character stats, and economic balance. Deduct 5 points if inventory management is missing, and 3 points if item effects aren't properly implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there a proper game state management and storyline progression?",
-      "description": "Review the implementation of game state persistence, save/load functionality, quest/mission tracking, and narrative elements. Check if the code manages different game states (exploration, combat, inventory) and transitions between them smoothly. Deduct 5 points if there's no game state persistence, and 3 points if the narrative elements are completely missing. 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 user actions, state inconsistencies, 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 storytelling that adapts to player choices 2. Procedurally generated monsters or dungeons 3. Special events or mini-games within the main game). 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 heal the character) 2. Function modules unrelated to the RPG experience (e.g., a built-in calculator) 3. Fancy effects that affect performance or readability. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating game logic/view/data layers), code organization, and maintainability. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no clear separation between game mechanics and presentation. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the text-based UI follows good design principles: 1) Clear information hierarchy (important stats easily visible) 2) Proper layout and spacing (organized sections with adequate whitespace) 3) Consistent styling (uniform text formatting, colors, and visual elements). Deduct 3 points for cluttered information display, 5 points for inconsistent styling, and 5 points for poor readability. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the user interaction intuitive and responsive?",
-      "description": "Judge whether the game controls and feedback conform to user expectations: 1) Clear action buttons or commands 2) Immediate feedback for player actions 3) Helpful instructions or UI guidance. Deduct 5 points for confusing controls, 3 points for delayed or missing feedback, and 5 points for lack of instructions on how to play. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Role-Playing",
-  "difficulty": "easy"
-}