@getollie/cli 0.0.1

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

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

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

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

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

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

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

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

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

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

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

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