@getollie/cli 0.0.4 → 0.2.0

package/library/game_development-adventure/ancient-ruins-adventure-game-html-js.json

@@ -1,68 +0,0 @@
-{
-  "index": 137,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable for demonstration purposes.\nPlease use HTML and JavaScript to implement an Ancient Ruins adventure game where players need to explore ruins and discover secrets. Tip: Implement exploration and decryption mechanisms.\nPlease include comments in your code to help other developers understand your implementation process.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Ancient Ruins exploration system fully implemented?",
-      "description": "Review whether the code implements a navigable ruins environment with interactive elements (rooms, corridors, landmarks) and clear spatial relationships. Check if the player can move between different areas of the ruins with appropriate transitions and if the environment provides adequate visual/textual feedback about the current location. Score 0 if there's no exploration functionality, 5 if basic movement between fixed locations exists, and 10 if a comprehensive ruins exploration system with multiple paths and areas is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are puzzle/decryption mechanisms properly integrated?",
-      "description": "Evaluate the implementation of puzzles or decryption challenges within the game. Check for variety (at least 3 different types), increasing difficulty progression, clear feedback on success/failure, and hint systems. Puzzles should be contextually appropriate for ancient ruins (hieroglyphics, symbol matching, sequence puzzles, etc.). Deduct 5 points if puzzles are too simplistic or illogical, 3 points if there's no difficulty curve, and 5 points if puzzle completion doesn't meaningfully advance gameplay.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is there a discovery/reward system for exploration?",
-      "description": "Check whether the game includes a system for discovering artifacts, treasures, or secrets that rewards player exploration. Evaluate if found items are tracked in an inventory, if discoveries reveal lore/story elements, and if there are hidden areas requiring specific actions to access. Deduct 3 points if discoveries are purely cosmetic with no gameplay effect, 5 points if there's no tracking system, and 5 points if discoveries aren't integrated into the overall game narrative.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the game state persistence implemented?",
-      "description": "Assess whether the game implements state management to save player progress, discovered items, and solved puzzles. Check for local storage implementation, save/load functionality, and whether the game state persists across browser sessions. Deduct 3 points if only partial game state is saved, 5 points if there's no auto-save feature, and 8 points if progress is completely lost on page refresh.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid player input, browser compatibility issues, resource loading failures) 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 lighting/shadow effects matching the ruins theme 2. Environmental sound effects triggered by player actions 3. Procedurally generated room layouts for replayability). 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 movement control systems) 2. Function modules unrelated to the ruins exploration theme (e.g., unnecessary mini-games) 3. Fancy effects that affect performance (e.g., excessive particle systems or animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating game logic/view/input handling), code organization, quality of comments, and reusability of components. 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 missing or unhelpful. 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 while maintaining an ancient ruins aesthetic: 1) Thematic color palette suitable for ruins (earthy tones, stone textures) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Atmospheric typography (readable yet thematic fonts). Deduct 3 points for inconsistent visual elements, 5 points for unreadable text or controls, and 5 points for visuals that break immersion. 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 animations between ruins areas feel natural (300-500ms) 3) Clear visual indicators for interactive elements. Deduct 5 points for each operation without feedback, 3 points for jarring transitions between scenes, and 5 points for interactive elements that aren't clearly distinguishable from decorative ones. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Adventure",
-  "difficulty": "medium"
-}

package/library/game_development-adventure/character-disappears-scene-appears-mouse-click.json

@@ -1,68 +0,0 @@
-{
-  "index": 928,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Ensure that the generated code is executable for demonstration. How would you create code for effects like in games where a character disappears and a scene appears after a mouse click?",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the character transition effect properly implemented?",
-      "description": "Review whether the code implements a smooth transition effect for the character's disappearance. Check for fade-out animations, opacity transitions, or other visual effects that make the character disappear naturally rather than abruptly. Score 0 if no transition effect is implemented, 5 if basic disappearance is achieved, and 10 if the transition includes polished animations like dissolve, particle effects, or custom easing functions.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the scene appearance transition properly implemented?",
-      "description": "Evaluate the scene appearance mechanism after the character disappears. Look for proper scene loading, fade-in effects, and smooth transitions. The code should demonstrate techniques like preloading, cross-fading between scenes, or progressive reveal. Deduct 5 points if the scene appears abruptly without animation, and 3 points if the transition is basic but lacks polish. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the click event handling properly implemented?",
-      "description": "Check if the click event is correctly captured and processed to trigger the transition. The implementation should include event listeners with proper scope, preventing event bubbling issues, and handling multiple clicks gracefully (preventing users from triggering the transition multiple times). Deduct 5 points if click handling is basic without safeguards, and 3 points if edge cases like rapid clicking aren't addressed. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is asset preloading/management handled effectively?",
-      "description": "Assess whether the code properly handles loading and management of visual assets required for both character and scene. Look for techniques like image preloading, texture atlases, or resource management systems. Code should avoid visible loading delays during the transition. Deduct 5 points if assets are loaded only when needed causing delays, and 3 points if loading indicators are missing. Give 10 points if asset management is comprehensive with loading optimization.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as missing assets, browser incompatibilities, performance issues on slower devices, 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 elements during the transition 2. Sound effects synchronized with visual changes 3. Responsive design adaptation for different screen sizes). 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 transition effects that overlap or conflict 2. Unnecessary DOM manipulations that could be handled more efficiently 3. Excessive animations that affect performance or distract from the main transition. 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 animation logic from event handling and scene management), potential for reusability, 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 the code lacks comments or documentation. 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) Visual consistency between character and scene elements 2) Proper use of visual hierarchy to guide attention 3) Appropriate use of color, contrast, and space to create mood and atmosphere. Deduct 3 points for each visual inconsistency, 5 points for clashing visual elements, and 5 points for poor composition that disrupts the transition effect. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Immediate visual feedback after click (≤ 100ms) 2) Natural-feeling transition timing (neither too fast nor too slow) 3) Proper use of easing functions for organic movement. Deduct 5 points for jerky animations, 3 points for frame rate drops during transitions, and 5 points for awkward timing that breaks immersion. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Adventure",
-  "difficulty": "easy"
-}

package/library/game_development-adventure/complete-text-adventure-game-code.json

@@ -1,68 +0,0 @@
-{
-  "index": 1441,
-  "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. Complete text adventure game code",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the text adventure game core engine fully implemented?",
-      "description": "Review whether the code accurately implements a complete game engine including room/location system, inventory management, command parsing, and game state persistence. Check if the parser can handle natural language commands (go north, take key, use item) and includes command aliases. Score 0 if basic navigation is missing, 5 if only simple move/look commands work, and 10 if complex multi-word commands and contextual responses are fully supported.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the interactive narrative system comprehensive?",
-      "description": "Evaluate whether the game includes a rich story framework with branching narratives, character dialogue systems, and quest/puzzle mechanics. Check for dynamic text generation, story progression tracking, and multiple endings based on player choices. Deduct 5 points if dialogue lacks depth or character development, 3 points if puzzles are too simplistic. Full score requires complex narrative branching with meaningful consequences.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the game world architecture well-designed and scalable?",
-      "description": "Assess whether the game world uses proper data structures for rooms, items, NPCs, and their relationships. Check for modular design allowing easy addition of new locations and content. Evaluate if the world state management supports complex interactions like item combinations, environmental changes, and persistent world modifications. Deduct 5 points if world data is hardcoded without extensibility, 3 points if object relationships are poorly structured.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the save/load and game progression system implemented?",
-      "description": "Check whether the code includes comprehensive save game functionality with multiple save slots, auto-save features, and game state serialization. Evaluate if the system can restore complex game states including inventory, world changes, story progress, and NPC states. Deduct 5 points if save system only covers basic variables, 3 points if no auto-save or crash recovery exists. Requires full state persistence for maximum score.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid commands, empty input, malformed save files, memory constraints, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should gracefully handle edge cases like circular command loops, null object references, and provide helpful hints for confused players. Give 10 points if fully robust, 5 points if average robustness, and 0 points if no exception handling exists.",
-      "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 gaming experience (e.g., 1. Dynamic ASCII art generation 2. Voice-to-text command input 3. Procedural content generation 4. Multi-language support 5. Achievement/statistics system 6. Interactive help system with contextual hints). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple command parsers coexisting) 2. Function modules unrelated to text adventure gaming (e.g., built-in calculator or unrelated mini-games) 3. Over-complicated features that detract from core gameplay (e.g., unnecessary graphics overlays in a text game). Deduct 3 points for each redundancy found, and directly deduct 10 points if core text adventure mechanics 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/parser/data layers), code documentation, and maintainability. Check for proper class/function organization, consistent naming conventions, and separation of concerns. Deduct 5 points if global state pollution is found or no design patterns are used; deduct 5 points if code duplication rate is too high (over 30%); deduct 5 points if code lacks comments or documentation. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the text interface design meet professional standards?",
-      "description": "Evaluate whether the text presentation follows good typography principles: 1) Consistent text formatting and spacing 2) Clear visual hierarchy for different types of content (descriptions, dialogue, system messages) 3) Readable font choices and appropriate line spacing 4) Proper use of colors/styling to distinguish content types. Deduct 3 points for inconsistent formatting, 5 points for poor readability or eye strain, and 5 points for confusing visual hierarchy. Screenshots should show clean, professional text layout.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the user interaction smooth and intuitive?",
-      "description": "Judge whether the command interface provides smooth user experience: 1) Command response time ≤ 200ms 2) Clear feedback for all player actions 3) Intuitive command structure that feels natural 4) Helpful error messages and suggestions for invalid commands 5) Consistent interaction patterns throughout the game. Deduct 5 points for each operation without clear feedback, 3 points for confusing command syntax, and 5 points for inconsistent interaction patterns. Screenshots should demonstrate responsive and user-friendly interface.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Adventure",
-  "difficulty": "easy"
-}

package/library/game_development-adventure/harry-potter-chamber-of-secrets-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 1440,
-  "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. Following the method you just provided, please give the complete code, including HTML, JS, and CSS. Also, enrich the game plot based on \"Harry Potter and the Chamber of Secrets\" to create multiple endings.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the game plot based on 'Harry Potter and the Chamber of Secrets' properly implemented?",
-      "description": "Evaluate whether the code successfully integrates storytelling elements from 'Harry Potter and the Chamber of Secrets' with multiple branching narratives leading to different endings. Check if key plot points (Basilisk, Tom Riddle's diary, etc.) are present. Score 0 if the Harry Potter theme is merely cosmetic, 5 if basic plot elements exist but without meaningful choices, and 10 if multiple coherent endings are implemented that reflect player decisions throughout the game.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are multiple endings properly implemented with different gameplay paths?",
-      "description": "Review whether the game provides genuinely different endings based on player choices rather than superficial text changes. Examine the code for branching logic structures, state tracking variables, and distinct story outcomes. Deduct 5 points if fewer than 3 meaningful endings exist, 3 points if the endings don't significantly differ in narrative consequences. The full score is 10 points if the game includes at least 4 distinct endings with appropriate build-up through gameplay.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the game state management system comprehensive?",
-      "description": "Check whether the code implements a robust state management system that tracks player progress, choices, inventory items, and storyline variables. The system should allow for saving/loading game state and persistently track critical narrative decisions. Deduct 5 points if state is tracked using only global variables without proper encapsulation, 3 points if there's no save/load functionality, and 3 points if the game state can easily become inconsistent. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the user interface thematically consistent with Harry Potter?",
-      "description": "Evaluate whether the UI elements (buttons, backgrounds, fonts, etc.) match the aesthetic of the wizarding world. Check for appropriate typography (gothic or serif fonts), color schemes (Hogwarts house colors), and thematic imagery (wands, magical elements). Deduct 5 points for generic UI with no Harry Potter theming, 3 points for inconsistent theming, and 2 points for overuse of copyrighted imagery. Full score is 10 points for an immersive, cohesive Harry Potter experience.",
-      "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, unexpected user behaviors) 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. Ambient magical sound effects that change with narrative 2. Wand-casting mechanics using mouse gestures 3. Interactive magical items with physics). 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 text display methods coexisting) 2. Function modules unrelated to the Harry Potter theme or storytelling (e.g., unnecessary mini-games) 3. Fancy effects that affect performance (e.g., excessive particle animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core narrative 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/story content layers), maintainability of narrative branching, 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 the story content is hardcoded throughout the JavaScript rather than stored in structured data. 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 scene transitions, and 5 points for hard-to-find key narrative choices or interaction elements. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Adventure",
-  "difficulty": "easy"
-}

package/library/game_development-adventure/html-javascript-level-switching-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 44,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable whenever possible.\nPlease implement a level switching game using HTML and JavaScript, where the character can enter the next level when reaching a certain position.\nInclude comments in your code to help other developers understand your implementation process.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core game movement system fully implemented?",
-      "description": "Review whether the code implements a complete character movement system with keyboard controls (WASD/arrow keys), collision detection, and proper physics (if applicable). Score 0 if movement is not implemented, 5 if only basic movement is present, and 10 if the movement includes acceleration/deceleration, proper collision handling, and feels responsive.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the level switching mechanism properly implemented?",
-      "description": "Check if the code includes a functional level transition system when the character reaches designated positions. Verify that level boundaries or exit points are clearly defined, the transition is triggered correctly, and the game state is properly preserved/reset between levels. Deduct 5 points if transitions are abrupt with no visual feedback, and 3 points if there are issues with game state persistence between levels.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are multiple game levels designed and implemented?",
-      "description": "Evaluate if the code includes at least 2-3 distinct levels with increasing difficulty or complexity. Each level should have unique layouts, obstacles, or objectives. Score 0 if only one level exists, 5 if multiple levels exist but are too similar, and 10 if levels show thoughtful progression in challenge and design.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the code well-commented with clear explanations?",
-      "description": "Assess if the code includes comprehensive comments explaining the implementation process, important functions, and game mechanics. Comments should cover architectural decisions, not just obvious code operations. Deduct 5 points if only basic/sparse comments exist, and give 0 points if crucial parts of the code remain unexplained.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid keypress combinations, rapid key presses, browser resizing, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should 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. Progressive difficulty adjustment 2. Character customization options 3. Interactive environmental elements 4. Scoring/achievement 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 functions (e.g., multiple movement control systems) 2. Function modules unrelated to level-based gameplay 3. Fancy effects that affect performance without adding to 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 logic/view/input handling), code reusability for level creation, and organization of assets. Deduct 5 points if global state pollution is found; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the game architecture makes adding new levels difficult. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the game UI follows modern design principles: 1) Consistent visual theme 2) Clear player character and level exit visibility 3) Proper contrast between gameplay elements and background 4) Appropriate feedback for player actions. Deduct 3 points for poor visual hierarchy, 5 points for confusing game elements, and 5 points for unclear objectives. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the game interactions conform to human perception characteristics: 1) Immediate response to player input (≤ 100ms) 2) Smooth animations for character movement and level transitions 3) Clear visual/audio feedback for significant events. Deduct 5 points for input lag, 3 points for choppy animations, and 5 points for confusing or missing feedback. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Adventure",
-  "difficulty": "easy"
-}

package/library/game_development-adventure/html-javascript-webvr-game-implementation.json

@@ -1,68 +0,0 @@
-{
-  "index": 114,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Please ensure the generated code is executable when possible.\n\nPlease use HTML and JavaScript to implement a Virtual Reality\n\n**Task**: Implement a simple virtual reality game that players can engage with through VR devices, providing an immersive experience.\n\n**Tip**: Use the WebVR API to implement VR support, and design game content suitable for VR.\n\ngame, and include comments in your code to help other developers understand your implementation process.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "WebVR/WebXR API Implementation",
-      "description": "Check whether the code correctly implements WebVR/WebXR API to support VR devices, including proper device detection, session establishment, and viewport rendering. The implementation should handle different VR headsets (Oculus, HTC Vive, etc.) and gracefully degrade when VR is not available.0 points if WebVR/WebXR API is not implemented at all, 5 points if basic implementation exists but lacks device compatibility, 10 points for complete implementation with proper device detection, session management, and fallback mechanisms.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "3D Environment and Scene Setup",
-      "description": "Evaluate the quality of the 3D environment setup using WebGL/Three.js/A-Frame. Check if the scene includes proper lighting, textures, skybox, and optimized 3D models with appropriate polygon counts for VR performance. Assess scene composition and spatial design for immersive quality.Deduct 3 points if the scene lacks depth or spatial awareness elements, 3 points if lighting is poorly implemented, 2 points if textures are low quality or missing. Full score for a complete, optimized 3D environment with proper VR spatial considerations.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "VR Interaction and Controls Implementation",
-      "description": "Check for implementation of VR-specific interaction methods: gaze-based selection, controller tracking, hand tracking, or gesture recognition. Verify that interactions feel natural in VR space with proper ray-casting for selection and manipulation of objects.0 points if no VR-specific interactions are implemented, 5 points for basic gaze or controller interactions, 10 points for comprehensive interaction system with multiple input methods and intuitive spatial feedback.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Game Mechanics and VR Experience Design",
-      "description": "Assess the game mechanics' suitability for VR: whether they leverage the unique aspects of VR (spatial awareness, presence, immersion) and avoid common VR pitfalls (motion sickness, disorientation). Check if the game provides clear objectives, feedback loops, and progression suitable for VR interaction.Deduct 5 points if game mechanics cause potential motion sickness, 3 points if spatial presence isn't leveraged, 5 points if core gameplay isn't adapted for VR's unique capabilities. Full score for VR-native gameplay that creates genuine immersion.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Code Robustness",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as VR device disconnection, browser compatibility issues, performance degradation) 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": "Innovative Features",
-      "description": "Check whether the code includes surprise features that enhance the VR experience (e.g., 1. Physics-based interactions 2. Spatial audio implementation 3. Multiplayer VR capability 4. Dynamic environment responses to user presence).Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Redundant Features",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions 2. Function modules unrelated to the core VR experience 3. Fancy effects that affect VR performance and might cause discomfort.Deduct 3 points for each redundancy found, and directly deduct 10 points if the core VR functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Engineering Quality",
-      "description": "Review modular design (separation of VR logic/rendering/game mechanics), performance optimization for VR (maintaining 90fps minimum), and code 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 no performance optimization techniques for VR are implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "User Interface in VR Space",
-      "description": "Evaluate whether UI elements follow VR best practices: 1) Depth-appropriate placement (0.5-3m from user) 2) Proper text size and legibility (minimum 1° visual angle) 3) Intuitive spatial arrangement 4) Non-intrusive HUD elements if present.Deduct 3 points for each UI element positioned too close/far or causing eye strain, 5 points for illegible text in VR, 5 points for UI elements that break immersion unnecessarily. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Performance and Comfort Optimization",
-      "description": "Judge whether the implementation prioritizes VR comfort and performance: 1) Consistent 90fps+ framerate 2) Proper locomotion methods to prevent motion sickness 3) Comfortable visual design (proper contrast, no flickering) 4) Balanced polygon count and texture resolution.Deduct 5 points for each implementation that could cause discomfort (jerky movements, strobing effects), 3 points for frame drops below 90fps, 5 points for lack of comfort options (teleportation, vignetting during movement). The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Adventure",
-  "difficulty": "hard"
-}

package/library/game_development-adventure/knight-77-rescues-prince-cloud-game.json

@@ -1,68 +0,0 @@
-{
-  "index": 1595,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable. Create a web mini-game with a story progression where the protagonist Knight 77 rescues Prince Cloud. The journey starts in England, passes through Thailand, and finally reaches Beijing to rescue Prince Cloud, with an iPhone 16 Pro as the final reward.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the story progression system fully implemented?",
-      "description": "Review whether the code accurately implements a three-stage story progression (England → Thailand → Beijing) with clear narrative transitions, character dialogue systems, and quest objectives for Knight 77's rescue mission. Check if each location has unique story elements, environmental descriptions, and progression triggers. Score 0 if no story structure exists, 5 if only basic location transitions are implemented, and 10 if complete narrative flow with dialogue, objectives, and story coherence is fully developed.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the game mechanics and player interactions properly designed?",
-      "description": "Evaluate whether the mini-game includes engaging gameplay mechanics such as puzzle-solving, combat systems, inventory management, or skill challenges appropriate for a rescue adventure. Check for player input handling, character movement controls, and interactive elements within each geographic location. Deduct 5 points if core gameplay mechanics are missing, 3 points if player controls are unresponsive or unclear. Full score requires intuitive and engaging game mechanics that support the rescue narrative.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the multi-location world design and progression system well-structured?",
-      "description": "Assess whether each location (England, Thailand, Beijing) has distinct visual themes, unique challenges, and appropriate cultural elements. Check if the progression system includes unlock mechanisms, save/load functionality, and clear advancement criteria between locations. Deduct 5 points if locations lack distinctiveness, 3 points if progression feels arbitrary or unclear. Require location-specific assets, challenges, and seamless transitions between stages.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the reward system and game completion mechanism properly implemented?",
-      "description": "Review whether the game includes a comprehensive reward system leading to the iPhone 16 Pro finale, with intermediate rewards, achievement tracking, and satisfying completion sequences. Check if Prince Cloud rescue sequence is properly scripted with appropriate celebration/completion animations. Deduct 5 points if reward system is incomplete, 3 points if final sequence lacks polish. Full score requires engaging reward progression and memorable completion experience.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid game states, save/load errors, asset loading failures, user input edge cases, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should effectively handle game state corruption, browser compatibility issues, and graceful degradation. Give 10 points if fully robust, 5 points if average robustness, and 0 points if no exception handling exists.",
-      "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 gaming experience (e.g., 1. Mini-map navigation system 2. Cultural Easter eggs in each location 3. Dynamic weather/time effects 4. Achievement badge system 5. Sound effects and background music). Add 3 points for each practical innovative feature implemented that adds genuine value to the gameplay experience (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 save systems coexisting) 2. Function modules unrelated to the rescue adventure theme (e.g., unrelated mini-games) 3. Excessive animations that impact performance (e.g., overuse of particle effects). Deduct 3 points for each redundancy found, and directly deduct 10 points if core game flow is 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/rendering/audio/state management layers), code organization, and maintainability. Deduct 5 points if global state pollution is found or proper architectural patterns aren't used; deduct 5 points if code duplication rate is too high (over 30%); deduct 5 points if assets aren't properly organized or optimized. Full score requires clean, modular, and maintainable code structure.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the game UI follows modern design principles: 1) Harmonious color palette reflecting each location's theme 2) Consistent UI element spacing and sizing 3) Readable typography with appropriate contrast 4) Cultural authenticity in visual representation of England/Thailand/Beijing. Deduct 3 points for each visually cluttered interface element, 5 points for poor color harmony that strains eyes, and 5 points for inconsistent or unprofessional visual styling. Full score requires polished, themed visual design.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the game interactions conform to user expectations: 1) Button/click feedback delay ≤ 100ms 2) Scene transition animations smooth and appropriately timed (300-500ms) 3) Clear visual feedback for all interactive elements 4) Smooth character movement and animation. Deduct 5 points for each unresponsive interaction, 3 points for jerky animations or transitions, and 5 points for unclear interactive affordances. Full score requires fluid, responsive, and intuitive interaction design.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Adventure",
-  "difficulty": "medium"
-}

package/library/game_development-adventure/narrative-game-song-dynasty-time-travel-cat.json

@@ -1,68 +0,0 @@
-{
-  "index": 723,
-  "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 for demonstration. Based on my design content, help me write a simple narrative game framework with a simple story. Since it will be presented through 3D web interaction, the game's interactive content includes the \"Four Elegances of the Song Dynasty\" (tea preparation, incense burning, flower arranging, and hanging paintings). These involve simple interactions. Please help me think about how to incorporate \"time travel\" into the painting. I've also designed an NPC cat.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the narrative game framework properly structured?",
-      "description": "Review whether the code establishes a complete narrative game framework with clear separation of story content, game state management, and player interaction handling. Check if the framework includes scene transitions, dialogue systems, and save/load functionality. Score 0 if the framework is missing, 5 if it's basic but functional, and 10 if it's comprehensive with proper encapsulation and extensibility.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the 'Four Elegances of the Song Dynasty' interactions fully implemented?",
-      "description": "Evaluate the implementation of all four activities (tea preparation, incense burning, flower arranging, and hanging paintings). Each activity should have unique interaction mechanics, clear success/failure states, and visual feedback. Deduct 2.5 points for each elegance that's missing or poorly implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the 'time travel' mechanic effectively integrated with the painting interaction?",
-      "description": "Assess whether the code implements a creative and functional time travel mechanic connected to the painting element. Check if it includes proper state management for different time periods, visual transitions between eras, and maintains narrative consistency. Score 0 if time travel is absent, 5 if it's basic, and 10 if it's well-integrated with both gameplay and storytelling.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the NPC cat properly implemented with meaningful interaction?",
-      "description": "Review the implementation of the NPC cat character. The cat should have a defined personality, dialogue system, animation states, and meaningful interactions with the player (e.g., providing hints, advancing the story). Deduct 5 points if the cat is static with minimal interaction, and 3 points if the cat lacks connection to the main narrative. 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 incorrect user inputs, resource loading failures, state inconsistencies) 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 environmental responses to player actions 2. Procedurally generated story variations 3. Accessibility options for different player needs). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple dialogue systems coexisting) 2. Function modules unrelated to the core narrative experience (e.g., an unnecessary mini-game) 3. Fancy effects that affect performance (e.g., excessive particle systems). 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 story logic/view/interaction layers), component reusability, 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 architecture for extending the game. 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 that evokes Song Dynasty aesthetics 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system appropriate for a narrative game (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for anachronistic visual styling, 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) Elegance interactions feel natural and responsive (≤ 100ms) 2) Transition animations between scenes/time periods controlled between 300-500ms 3) Clear visual guidance for interactive elements. Deduct 5 points for each interactive element without feedback, 3 points for jarring transitions between story segments, and 5 points for confusing navigation in the 3D environment. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Adventure",
-  "difficulty": "hard"
-}