@getollie/cli 0.0.5 → 0.2.1

package/library/other-code_generation/html5-javascript-code-generation-expert-responses.json

@@ -1,68 +0,0 @@
-{
-  "index": 1316,
-  "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. The code should be implemented using HTML5 and JavaScript, with the time period from March 10, 2025 to June 14, 2025.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the date range implementation correctly handling the specified time period?",
-      "description": "Review whether the code accurately implements the date range from March 10, 2025 to June 14, 2025. Check if date validation is properly implemented, preventing out-of-range selections. Score 0 if dates are hardcoded without validation, 5 if basic range implementation exists but with edge case issues, and 10 if full date range management with proper validation and error handling is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the calendar visualization properly implemented?",
-      "description": "Evaluate the visual representation of the calendar. Check if it shows all days within the specified period (March 10, 2025 to June 14, 2025) correctly, with appropriate month transitions. Verify that weekdays and weekends are visually distinguishable. Deduct 3 points if month transitions are incorrect, 3 points if the day labeling is inaccurate, and 4 points if the calendar doesn't reflect the exact specified date range.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are date selection and manipulation features implemented?",
-      "description": "Check for functionality to select, highlight, or interact with dates in the specified range. Score 0 if no selection mechanism exists, 5 if basic date selection is implemented but lacks feedback or validation, and 10 if comprehensive date selection with visual feedback, range selection capabilities, and proper validation against the specified time period are all properly implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the date format handling flexible and internationalized?",
-      "description": "Assess whether the code handles different date formats and localization. Check if it provides options for different date display formats (MM/DD/YYYY, DD/MM/YYYY, etc.) and supports different locales for day/month names. Deduct 3 points if only one date format is supported, 3 points if no localization options exist, and 4 points if the implementation doesn't handle timezone considerations.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid date inputs, browser compatibility issues, leap year considerations, 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 date range visualization 2. Event marking/annotation capabilities 3. Animated transitions between months). 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 date handling functions 2. Function modules unrelated to the calendar/date requirement 3. Fancy effects that affect performance (e.g., excessive animations when changing months). 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 date logic/view layers), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast sliding, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Other-Code Generation",
-  "difficulty": "hard"
-}

package/library/other-code_generation/static-code-generation-no-environment.json

@@ -1,68 +0,0 @@
-{
-  "index": 1135,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be careful to ensure the code you generate is executable for demonstration. First, I don't want to install any environments - if I were to install environments, I wouldn't need XML files - so I'll still implement this using a purely static approach.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the code expert clearly establishing what type of code demonstration is being requested?",
-      "description": "Evaluate whether the response properly acknowledges the absence of a specific request and provides appropriate guidance. The response should include a clear statement about what kind of demonstration is being offered and why. Deduct 5 points if the response immediately jumps into a random code example without context, deduct 10 points if it assumes a specific task without clarification. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is there a proper explanation of static implementation approaches?",
-      "description": "Check if the response includes a comprehensive explanation of static implementation options (HTML/CSS/JavaScript without server dependencies) that align with the requirement of not installing environments. The explanation should cover browser-based execution options and limitations. Award 10 points for thorough coverage with examples, 5 points for basic explanation, 0 points if missing entirely.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is there a self-contained HTML/JS demonstration?",
-      "description": "Assess whether the response includes at least one complete, executable HTML file with embedded JavaScript that demonstrates a concept without requiring any installation or server. The code must be fully functional when copied to a text file and opened in a browser. Award 10 points for a working demonstration with clear purpose, 5 points if it has minor issues but shows the concept, 0 points if it requires installation or server-side components.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there an explanation of alternatives to XML for static implementations?",
-      "description": "Evaluate whether the response provides alternatives to XML for data representation in static environments (e.g., JSON objects, data attributes, JavaScript literals). The alternatives should be accompanied by practical code examples showing how they can be used. Award 10 points for comprehensive coverage with examples, 5 points for limited coverage, 0 points if not addressed.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as missing data, browser compatibility issues, user operation errors, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Interactive visualizations 2. Progressive enhancement techniques 3. Creative use of modern browser APIs without external dependencies). 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 2. Function modules unrelated to the core demonstration 3. Fancy effects that affect performance. 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, code organization, and best practices. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the code is not properly commented or lacks clear structure. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast sliding, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Other-Code Generation",
-  "difficulty": "hard"
-}

package/library/other-development_configuration/tailwind-css-4-electron-vite-no-react.json

@@ -1,68 +0,0 @@
-{
-  "index": 230,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and expert responses. Be sure to make the code you generate executable for demonstration. How to use Tailwind CSS 4 in Electron.js with Vite, without using other frameworks such as React.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Electron.js + Vite integration properly configured?",
-      "description": "Check if the code includes proper configuration for Electron.js with Vite, including correct entry points, build scripts, and development server setup. Verify that main and renderer processes are correctly separated and communicate properly. Score 0 if basic integration is missing, 5 if it works but with suboptimal configuration, and 10 if fully optimized with proper HMR support.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is Tailwind CSS 4 correctly installed and configured?",
-      "description": "Evaluate if Tailwind CSS 4 is correctly installed with proper postcss configuration. Check for presence of tailwind.config.js with appropriate content paths targeting Electron's renderer process files. Verify that the Tailwind directives (@tailwind base, components, utilities) are properly included. Deduct 5 points if configuration is incomplete, 3 points if customization options are missing, and 3 points if purging/content configuration is incorrect. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the build process properly set up without framework dependencies?",
-      "description": "Check if the build process avoids React, Vue, or other frameworks as specified. Verify that the solution uses vanilla JS or minimal libraries that don't qualify as frameworks. Ensure build scripts in package.json correctly handle both development and production builds for Electron without framework-specific configurations. Deduct 10 points if any framework is used, 5 points if build process doesn't handle both dev and prod environments.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there a working demonstration of Tailwind CSS usage in the Electron app?",
-      "description": "Review whether the code includes practical examples of Tailwind CSS classes being used in HTML elements within the Electron renderer process. Check for demonstration of responsive design, dark mode support, and at least one custom component using Tailwind's @apply directive. Score 0 if no examples provided, 5 if basic examples only, 10 if comprehensive examples showing Tailwind CSS 4's new features.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as missing files, CSS parsing errors, electron process crashes, 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. Hot reload with CSS changes preservation 2. Custom Tailwind plugins specific for desktop apps 3. Native OS integration with Tailwind-styled components). 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 configuration files or duplicate Tailwind setups 2. Unnecessary dependencies that could bloat the Electron app 3. Overly complex build steps that could be simplified. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functionality is interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating main/renderer processes, CSS modules, and utility functions), file organization, and build process automation. 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 build process is not automated. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast sliding, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Other-Development Configuration",
-  "difficulty": "medium"
-}

package/library/other-development_framework_setup/spfx-vue-project-generation.json

@@ -1,68 +0,0 @@
-{
-  "index": 440,
-  "question": "You are a code expert. Please utilize your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable when possible. Generate an SPFx+Vue project.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the SPFx project foundation correctly established?",
-      "description": "Review if the code sets up a proper SPFx project structure with the required configurations (package-solution.json, config folder, etc.). Check if the proper SPFx version is specified and if the gulpfile.js includes all necessary build tasks. Score 0 if no SPFx structure exists, 5 if basic structure exists but with configuration errors, and 10 if a complete and valid SPFx project foundation is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is Vue properly integrated into the SPFx framework?",
-      "description": "Evaluate whether the Vue integration follows best practices: 1) Proper webpack configuration for Vue SFC support 2) Vue component registration within SPFx web parts 3) Lifecycle management between SPFx and Vue instances. Deduct 5 points if Vue is loaded as an external script instead of webpack integration, 3 points if prop passing between SPFx and Vue is improperly handled, and 5 points if Vue devtools integration is missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the SPFx web part configuration properly implemented?",
-      "description": "Check whether the web part implements property panes correctly, including property types, validation, groups, and custom controls. Verify the manifest.json file properly defines the web part capabilities and permissions. Deduct 3 points for missing localization, 5 points for incorrect property persistence, and 5 points if SharePoint context is not properly utilized. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the project demonstrate proper Vue component architecture?",
-      "description": "Assess whether the Vue components follow the single responsibility principle, implement proper parent-child communication (props down, events up), and utilize Vue features appropriately (Vuex for state management, Vue Router if needed, computed properties, watchers, etc.). Deduct 5 points for monolithic components, 3 points for prop drilling beyond 3 levels, and 5 points if component reusability is poor. 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 network errors when fetching data from SharePoint, permission issues, browser compatibility problems, 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. Integration with Microsoft Graph API 2. Responsive design for mobile SharePoint 3. Performance optimizations like code-splitting or lazy loading). 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 dependencies not utilized in the project 2. Bloated node_modules with unnecessary packages 3. Inclusion of both Vue 2 and Vue 3 artifacts or multiple state management solutions. 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 services/components/models), TypeScript usage (instead of plain JavaScript), and deployment pipeline setup. Deduct 5 points if 'any' type is overused; deduct 5 points if no unit tests are present; deduct 5 points if SharePoint-specific best practices are ignored (like proper API versioning). The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the design follows SharePoint/Fluent UI design principles: 1) Consistent use of Office UI Fabric/Fluent UI components 2) Proper theme token usage for colors/spacing 3) Responsive design for different screen sizes. Deduct 3 points for each instance of custom styles contradicting Fluent UI guidelines, 5 points for not respecting user's SharePoint theme settings, and 5 points for accessibility issues (contrast, keyboard navigation). 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 SharePoint UX patterns: 1) Loading states for async operations 2) Proper transitions between views/states 3) Optimistic UI updates where appropriate. Deduct 5 points for each operation without loading indicators, 3 points for jarring/abrupt transitions, and 5 points for UI elements that don't react to user interaction within 200ms. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Other-Development Framework Setup",
-  "difficulty": "hard"
-}

package/library/other-divination/generate-detailed-hexagram-interpretations.json

@@ -1,68 +0,0 @@
-{
-  "index": 1327,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable for demonstration purposes. The generated hexagrams should include all 64 hexagrams, not just the eight basic ones. Each hexagram should have detailed explanatory texts and interpretations. The analysis needs to be more comprehensive, addressing the specific question being asked, providing detailed insights and definitive answers based on my requirements. Please regenerate the code accordingly.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Are all 64 I Ching hexagrams properly implemented and displayed?",
-      "description": "Check if the implementation includes all 64 hexagrams with their proper binary representation, traditional names and numbers. Each hexagram should be visually distinct with clear representation of broken and unbroken lines. Deduct 10 points if fewer than 64 hexagrams are implemented, 5 points if the visual representation is unclear or inaccurate.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the hexagram generation algorithm correctly implemented?",
-      "description": "Evaluate whether the algorithm for generating hexagrams follows traditional I Ching principles (either yarrow stalk or coin toss methods). The algorithm should account for changing lines and properly transform between hexagrams. Deduct 5 points if only one method is implemented, 10 points if the transformation logic contains errors in calculating changing lines.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Does each hexagram include comprehensive interpretation texts?",
-      "description": "Verify that each hexagram has detailed textual interpretations including: overall judgment, image text, line-by-line interpretations, and changing line meanings. The texts should be accurate to traditional I Ching sources. Give 0 points if interpretations are missing, 5 points if only basic interpretations are provided, and 10 points for comprehensive texts that include all traditional elements.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there a question analysis mechanism that correlates hexagrams with user queries?",
-      "description": "Check if the code includes functionality to analyze specific user questions and provide relevant interpretations based on the generated hexagram. The system should establish meaningful connections between the question context and the hexagram's symbolic meaning. Deduct 5 points if the system only provides generic readings without relating to specific questions, and 10 points if there's no question analysis at all.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code handles edge cases such as invalid inputs, unexpected user interactions, and provides appropriate error handling. Test with boundary inputs like empty questions or special characters. Code with strong robustness should gracefully handle these 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. Visual animations for coin/yarrow casting 2. Historical context for each hexagram 3. Related hexagrams visualization). 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 divination methods 2. Function modules unrelated to I Ching divination 3. Excessive visualizations that distract from the core readings. 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 hexagram generation/interpretation/display logic), reusable components, 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 there's no clear organization of hexagram data and interpretation texts. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the visual design follows traditional Chinese aesthetics while maintaining modern usability: 1) Appropriate use of traditional colors and symbols 2) Clear visual hierarchy for hexagram display 3) Professional typography with readable Chinese characters when applicable. Deduct 3 points for each cluttered visual element, 5 points for inappropriate color schemes that don't respect the I Ching tradition, and 5 points for poor typography making interpretations difficult to read. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and intuitive?",
-      "description": "Judge whether the interaction design follows natural divination processes: 1) Clear visualization of the divination process 2) Intuitive transition from question to hexagram generation to interpretation 3) Accessible navigation between different parts of the reading. Deduct 5 points if the divination process isn't visually represented, 3 points for confusing transitions between steps, and 5 points if interpretations are difficult to navigate or understand. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Casual",
-  "difficulty": "hard"
-}

package/library/other-divination/heavenly-stems-earthly-branches-i-ching-auspicious-times.json

@@ -1,68 +0,0 @@
-{
-  "index": 1249,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the generated code is executable for demonstration purposes. Create a small program code that combines Heavenly Stems and Earthly Branches, the Chinese Zodiac, and the 64 hexagrams of I Ching for auspicious time analysis.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Heavenly Stems and Earthly Branches calculation system accurately implemented?",
-      "description": "Review whether the code correctly implements the 60-year cycle calculation system (天干地支) with accurate mapping of the 10 Heavenly Stems and 12 Earthly Branches. Check if the conversion from Gregorian calendar to traditional Chinese calendar includes proper leap year handling and solar term calculations. Score 0 if basic stem-branch pairing is wrong, 5 if only basic conversion is implemented without solar terms, and 10 if complete with accurate astronomical calculations.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the Chinese Zodiac integration and compatibility analysis properly implemented?",
-      "description": "Evaluate whether the 12 zodiac animals (生肖) are correctly mapped to birth years and integrated with compatibility analysis (相冲相合). Check if the code includes zodiac personality traits, lucky elements (五行), and inter-zodiac relationship calculations. Deduct 5 points if zodiac-year mapping is incorrect, 3 points if compatibility logic is missing. Full score requires complete zodiac interaction matrix with Five Elements theory integration.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are the 64 I Ching hexagrams correctly implemented with divination logic?",
-      "description": "Check whether all 64 hexagrams (六十四卦) are accurately represented with correct trigram combinations, names, and interpretations. Evaluate if the divination algorithm includes proper randomization methods (coin toss, yarrow stalk simulation) and hexagram transformation logic. Deduct 5 points if hexagram structures are wrong, 5 points if divination randomization is pseudo or biased. Requires complete hexagram database with changing lines functionality.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the auspicious time analysis algorithm comprehensive and culturally accurate?",
-      "description": "Assess whether the time analysis combines all three systems (stems-branches, zodiac, I Ching) into coherent auspicious timing recommendations. Check if the algorithm considers traditional factors like conflict avoidance (冲煞), favorable directions (吉方), and time-specific activities. Deduct 5 points if integration logic is superficial, 3 points if cultural context is inaccurate. Full score requires sophisticated multi-factor analysis with seasonal adjustments.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle edge cases such as invalid dates, leap years, timezone conversions, and boundary conditions in calendar calculations. Code should gracefully handle user input errors and provide meaningful error messages for invalid queries. Give 10 points for comprehensive error handling, 5 points for basic exception management, and 0 points if crashes occur with invalid inputs.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that enhance cultural authenticity?",
-      "description": "Check for creative features that add cultural depth such as: 1) Interactive hexagram casting animations 2) Personalized zodiac compatibility reports 3) Historical event correlation with stem-branch cycles 4) Multi-language support for traditional terms. Add 3 points for each well-implemented cultural feature (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly examine three types of redundancy: 1) Duplicate calendar conversion functions 2) Unrelated fortune-telling elements (Western astrology, tarot) 3) Excessive decorative animations that obscure cultural content. Deduct 3 points for each redundancy found, and directly deduct 10 points if core traditional systems are compromised by irrelevant features.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular separation of calendar systems, zodiac logic, and I Ching components. Check for proper data structures, algorithm efficiency, and maintainable code organization. Deduct 5 points for monolithic code structure; deduct 5 points if calculation algorithms are inefficient; deduct 5 points if no input validation exists. Full score requires clean architecture with separated concerns.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface design respect traditional Chinese aesthetics?",
-      "description": "Evaluate whether the visual design incorporates traditional Chinese design elements appropriately: 1) Color harmony using traditional palettes (red, gold, jade green) 2) Typography respecting Chinese character spacing and hierarchy 3) Layout following traditional symmetry principles. Deduct 3 points for culturally inappropriate color choices, 5 points for poor Chinese text rendering, and 5 points for layout that conflicts with traditional aesthetics. Full score requires authentic cultural visual representation.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the user interaction intuitive and culturally contextual?",
-      "description": "Judge whether interactions follow cultural expectations: 1) Intuitive date selection with lunar calendar support 2) Clear hexagram casting process with appropriate ritual feel 3) Results presentation that respects traditional consultation format. Deduct 5 points for confusing navigation between different systems, 3 points for rushed transitions that break cultural immersion, and 5 points for results that lack traditional interpretive context. Full score requires seamless cultural user experience.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Other-Divination",
-  "difficulty": "hard"
-}

package/library/other-divination/html-64-hexagrams-divination-app.json

@@ -1,68 +0,0 @@
-{
-  "index": 1093,
-  "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. Write a 64 hexagrams divination application in pure HTML, with two buttons on the interface: \"Start Shaking\" and \"Stop\". When \"Start Shaking\" is pressed, the names of the 64 hexagrams will start scrolling. When the \"Stop\" button is pressed, it will randomly display one hexagram name and show its corresponding divination text.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the 64 hexagrams system completely and accurately implemented?",
-      "description": "Review whether all 64 hexagrams from the I Ching are correctly included with accurate names and corresponding divination texts. Check if hexagram data structure includes proper Chinese names, pinyin, and authentic interpretations. Score 0 if less than 50 hexagrams are included, 5 points if hexagrams are complete but texts are inaccurate or overly simplified, and 10 points if all 64 hexagrams with authentic divination content are fully implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the hexagram scrolling animation mechanism properly implemented?",
-      "description": "Evaluate whether the 'Start Shaking' function creates a smooth, continuous scrolling effect that cycles through hexagram names at an appropriate speed (recommended 50-100ms intervals). Check if the animation uses requestAnimationFrame or setInterval effectively, and whether the scrolling creates a realistic divination atmosphere. Deduct 5 points if scrolling is choppy or too fast/slow, 3 points if animation doesn't loop properly. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the random selection algorithm fair and the stop mechanism responsive?",
-      "description": "Check whether the 'Stop' button immediately halts scrolling and uses a proper random number generator (Math.random()) to ensure each hexagram has equal probability of selection. Verify that the stopping mechanism is instantaneous without delay and that the final result appears to be truly random across multiple tests. Deduct 5 points if randomization is biased, 3 points if stop response is delayed. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the divination result display comprehensive and well-formatted?",
-      "description": "Assess whether the selected hexagram displays complete information including hexagram name, traditional symbol representation, and detailed divination interpretation text. Check if the result presentation is clear, readable, and maintains cultural authenticity. Deduct 5 points if only hexagram name is shown without interpretation, 3 points if formatting is poor or text is truncated. Give 10 points if comprehensive hexagram information is elegantly presented.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as rapid button clicking, browser compatibility issues, missing hexagram data, etc.) and provide stable performance. Code with strong robustness should prevent double-clicking issues, handle edge cases gracefully, and maintain consistent behavior across different browsers. Give 10 points for excellent robustness, 5 points for average handling, and 0 points if no exception handling exists.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that enhance the divination experience?",
-      "description": "Check whether the code includes thoughtful features that improve user engagement (e.g., 1. Traditional I Ching hexagram symbols display 2. Sound effects for authentic divination atmosphere 3. Divination history tracking 4. Hexagram interpretation with classical references). 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 random generators) 2. Function modules unrelated to I Ching divination (e.g., unrelated games or calculators) 3. Excessive animations that distract from the spiritual nature of divination. Deduct 3 points for each redundancy found, and directly deduct 10 points if core divination functions are interfered with by unnecessary code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review code organization (separation of hexagram data, UI logic, and animation control), maintainability, and clean structure. Deduct 5 points if global variables are overused or code structure is chaotic; deduct 5 points if code duplication rate is too high (over 30%); deduct 5 points if hexagram data is hardcoded without proper data structure. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface design reflect appropriate cultural aesthetics and professional standards?",
-      "description": "Evaluate whether the design respects traditional Chinese aesthetics while maintaining modern usability: 1) Color scheme appropriate for spiritual/cultural context (earth tones, traditional colors) 2) Typography that honors the cultural significance (proper font choices for Chinese characters) 3) Layout that creates a contemplative atmosphere. Deduct 5 points for inappropriate modern flashy colors, 3 points for poor Chinese character rendering, and 5 points for cluttered layout that disrupts the meditative experience. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the user interaction intuitive and the divination flow seamless?",
-      "description": "Judge whether the divination process feels natural and engaging: 1) Button states clearly indicate when shaking is active 2) Scrolling speed creates anticipation without being tedious 3) Result presentation feels ceremonial and significant 4) Clear visual feedback for all user actions. Deduct 5 points for confusing button states, 3 points for poor timing in the divination sequence, and 5 points for anticlimactic result presentation. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Casual",
-  "difficulty": "easy"
-}

package/library/other-divination_system/javascript-qi-men-dun-jia-divination-chart.json

@@ -1,68 +0,0 @@
-{
-  "index": 1699,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate, professional responses. Be sure to ensure the generated code is executable for demonstration. Generate JavaScript code for the Qi Men Dun Jia divination chart system.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core Qi Men Dun Jia calculation system accurately implemented?",
-      "description": "Check whether the code correctly implements the fundamental calculations for Qi Men Dun Jia, including the 9 Stars (九星), 8 Gates (八門), 8 Gods (八神), Heavenly Stems (天干), Earthly Branches (地支), and their relationships. Verify if the code handles solar terms (節氣) and time divisions correctly. Score 0 if core calculations are incorrect, 5 if basic calculations are implemented but with minor errors, and 10 if all traditional Qi Men Dun Jia rules are accurately implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Does the code correctly implement the temporal logic for chart generation?",
-      "description": "Evaluate whether the system can generate charts based on different time systems (solar/lunar calendar) and calculate charts for different periods (hour/day/month charts). Check if the code manages the transitions between different Yuan (元) periods and handles the conversion between solar and lunar calendars correctly. Deduct 5 points if the temporal calculations are inconsistent with traditional methods, and 3 points if only basic timing systems are implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the spatial arrangement of the Qi Men Dun Jia chart properly visualized?",
-      "description": "Verify if the code generates a visually accurate representation of the Qi Men chart with its characteristic 3x3 palace structure. Check for correct placement of elements (Stems, Branches, Stars, Gates, Gods) within the palaces according to traditional rules. Examine if the chart changes dynamically based on input time parameters. Deduct 5 points if the spatial arrangement is incorrect, and 3 points if the visual representation lacks clarity. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the system include interpretation capabilities for divination purposes?",
-      "description": "Review whether the code provides analytical functions to interpret the generated chart for divination purposes. Check if it can identify important patterns like Du Mu He (遇墓解), Tian Yi He Jin (天乙合金), or San Qi Ju (三奇聚). Evaluate if the system offers interpretations for common divination questions (career, relationships, etc.). Deduct 5 points if interpretation functions are missing, and 3 points if they lack depth or cultural accuracy. 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 dates, out-of-range inputs, or missing data) and provide friendly error prompts or recovery mechanisms. Check if the code validates Chinese calendar edge cases (e.g., leap months). 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 visual animations for chart transitions 2. AI-assisted interpretation recommendations 3. Historical data correlation for validation 4. Integration with other divination systems like I-Ching). 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 calculation methods (e.g., multiple ways to calculate the same stem-branch combination) 2. Function modules unrelated to Qi Men Dun Jia (e.g., unrelated fortune-telling systems) 3. Fancy effects that affect performance (e.g., unnecessary animations that slow down chart generation). 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 calculation logic/view/data layers), unit test coverage for calendar calculations, and appropriate use of design patterns. Check if the code follows clear naming conventions that reflect traditional Qi Men Dun Jia terminology. 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 there's no separation between calculation logic 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 chart visualization follows both traditional aesthetics and modern design principles: 1) Culturally appropriate color schemes (traditional five-element colors) 2) Clear hierarchy in displaying chart elements (palaces, stems, branches, stars, gates, gods) 3) Professional typography (appropriate use of Chinese characters and their spacing). Deduct 3 points for visually confusing element placement, 5 points for inappropriate color symbolism, and 5 points for illegible character display. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and informative?",
-      "description": "Judge whether the interactive elements enhance understanding of this complex divination system: 1) Clear highlighting of relationships between elements when selecting components 2) Informative tooltips explaining traditional meanings 3) Smooth transitions when changing chart parameters. Deduct 5 points for each interaction without explanatory feedback, 3 points for confusing navigation between chart sections, and 5 points for important elements being difficult to select or identify. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Other-Divination System",
-  "difficulty": "hard"
-}