@getollie/cli 0.0.1

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

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

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

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

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

package/library/other-document_editor/vue-microsoft-word-like-editor.json

@@ -0,0 +1,68 @@
+{
+  "index": 1630,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the code you generate is executable for demonstration purposes. Implement an editor similar to Microsoft Word in Vue.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core text editing functionality fully implemented?",
+      "description": "Review whether the code implements essential text editing features using Vue: text input/deletion, cursor positioning, selection, copy/paste, and undo/redo. Check if contentEditable is properly utilized or if a custom implementation handles key events. Score 0 if basic text editing is missing, 5 if only simple text entry works, and 10 if all standard editing operations are fully implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are the formatting capabilities comprehensive?",
+      "description": "Evaluate the text formatting features: font styles (bold, italic, underline), font family/size selection, text alignment, paragraph spacing, bullet/numbered lists, and indentation. Verify that formatting is preserved when copying or saving content. Deduct 2 points for each missing core formatting feature. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is document structure management properly implemented?",
+      "description": "Check if the editor supports document structure features like headings, sections, page breaks, headers/footers, and tables. Assess whether the document model maintains a proper hierarchical structure rather than just styling text. Deduct 3 points if headings/sections are missing, 3 points if page management is absent, and 4 points if table support is not implemented. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are file operations and document state management properly handled?",
+      "description": "Review implementation of new document creation, opening existing documents, saving (with appropriate formats like .docx or HTML), auto-save functionality, and document state tracking. Check if the editor prompts users about unsaved changes. Deduct 3 points if save/load is missing, 3 points without auto-save, and 4 points without document state management. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code handles common edge cases (large documents, special characters, pasting from external sources, browser compatibility issues). Test if the editor prevents data loss during unexpected operations or crashes. Code with strong robustness should effectively handle these scenarios, giving 10 points. If robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Real-time collaboration 2. AI-powered writing suggestions 3. Voice-to-text input 4. Advanced find/replace with regex 5. Accessibility features like screen reader support). Add 2 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functionality (e.g., multiple text selection mechanisms) 2. Function modules unrelated to word processing (e.g., built-in games or unrelated tools) 3. Fancy effects that affect performance (excessive animations or transitions). 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 Vue component architecture (proper use of props/events/slots), state management approach, code reusability, and build process. Check for adherence to Vue best practices and performance optimization techniques. Deduct 3 points for improper component design, 3 points for inefficient state management, and 4 points if the code has poor maintainability. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the UI follows Microsoft Word-like design principles: 1) Clean, organized toolbar/ribbon interface 2) Proper use of icons and tooltips 3) Consistent spacing and alignment 4) Professional color scheme similar to Microsoft Office. Deduct 3 points for cluttered toolbars, 3 points for inconsistent visual language, and 4 points for poor overall layout resemblance to a professional word processor. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the editor provides smooth interactions: 1) Responsive typing with no perceptible lag 2) Smooth cursor movement and selection 3) Immediate visual feedback for formatting changes 4) Clean transitions between different view modes. Deduct 3 points for typing lag, 2 points for jerky scrolling/selection, 3 points for delayed formatting feedback, and 2 points for abrupt view transitions. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Other-Document Editor",
+  "difficulty": "medium"
+}

package/library/other-educational/five-elements-generation-destruction-e-language.json

@@ -0,0 +1,68 @@
+{
+  "index": 245,
+  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Try to ensure the generated code is executable. You are an experienced Chinese programming E-language (yiyu) developer. Below are the generation and destruction relationships of the Five Elements: \"Five Elements Generation: Wood generates Fire, Fire generates Earth, Earth generates Metal, Metal generates Water, Water generates Wood. Five Elements Destruction: Wood overcomes Earth, Earth overcomes Water, Water overcomes Fire, Fire overcomes Metal, Metal overcomes Wood.\" Please implement the Five Elements generation and destruction relationships in a Windows window program using E-language.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Five Elements core theory fully implemented?",
+      "description": "Review whether the code accurately implements both the Generation and Destruction relationships of the Five Elements (Wood, Fire, Earth, Metal, Water). Each element should have proper directional relationships with others. Score 0 if the core theory is missing, 5 if only one relationship type is implemented, and 10 if both Generation and Destruction relationships are fully represented with correct directional connections.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the Windows GUI implementation complete?",
+      "description": "Check whether the E-language code properly creates a Windows window with appropriate controls (buttons, labels, graphics) to display and interact with the Five Elements system. The window should have proper title, size, position, and event handling. Deduct 3 points if the window lacks basic properties, 5 points if controls are poorly organized, and 7 points if the GUI doesn't display at all. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the Five Elements visualization properly designed?",
+      "description": "Evaluate whether the Five Elements are visualized clearly with appropriate symbols/images and connection lines showing their relationships. The Generation and Destruction paths should be visually distinct (different colors, line styles, or arrows). Deduct 5 points if elements lack visual distinction, 3 points if relationship lines are confusing, and 5 points if the visualization is static with no interactive component. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is there an interactive demonstration of the relationships?",
+      "description": "Assess whether the program allows users to interact with the Five Elements system (e.g., clicking on elements to show their Generation and Destruction relationships, animated demonstrations, or interactive simulations). Deduct 5 points if interaction is limited to static display, 3 points if only one relationship type can be demonstrated, and 5 points if there's no visual feedback during interaction. 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 resource loading failures, unexpected user inputs, window resizing issues, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Animated transitions between elements 2. Sound effects for generation/destruction interactions 3. Traditional Chinese styling or themes). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple ways to demonstrate the same relationship) 2. Function modules unrelated to the Five Elements theory (e.g., unnecessary game features) 3. Fancy effects that affect performance (e.g., excessive animations that slow down the program). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating UI logic/Five Elements logic/event handling), code structure, and E-language best practices. Deduct 5 points if global variable pollution is found or functions are not properly organized; deduct 5 points if the code duplicates logic unnecessarily; 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) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows consistent principles) 3) Professional font system (appropriate text size and readability). 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 lag during animations, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Other-Educational",
+  "difficulty": "easy"
+}

package/library/other-financial_platform/mobile-h5-digital-currency-llm-data.json

@@ -0,0 +1,68 @@
+{
+  "index": 1281,
+  "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 display. Help me create an H5 page similar to Tencent's \"Yuanbao\" (digital currency) using a mobile development framework that can support rendering data returned from large language models.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the mobile H5 framework integration complete and optimized?",
+      "description": "Review whether the code properly integrates mobile-first frameworks (Vue3/React with mobile UI libraries like Vant/Ant Design Mobile), includes viewport meta configuration, touch event handling, and mobile-specific optimizations. Score 0 if basic mobile framework is missing, 5 if only basic responsive layout is implemented, and 10 if comprehensive mobile optimization including gesture handling, scroll optimization, and performance tuning is fully implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the large language model data rendering system robust and efficient?",
+      "description": "Check whether the implementation includes streaming data parsing, markdown/rich text rendering capabilities, code syntax highlighting, and real-time content updates. Must support incremental rendering for long responses and handle various LLM output formats (text, code blocks, lists, tables). Deduct 5 points if streaming rendering is missing, 3 points if content formatting is poor, and 3 points if loading states are not handled properly. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Does the digital currency UI accurately replicate Tencent Yuanbao's design system?",
+      "description": "Evaluate whether the interface closely matches Tencent Yuanbao's visual hierarchy, including proper card layouts, currency display formats, transaction lists, and interactive elements. Must include authentic color schemes, typography, and component styling that reflects professional fintech design standards. Deduct 5 points if visual consistency is poor, 3 points if layout proportions are incorrect, and 5 points if key UI components are missing or poorly implemented. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the chat/conversation interface optimized for LLM interactions?",
+      "description": "Check whether the code implements a conversation interface with proper message bubbles, typing indicators, auto-scroll behavior, and conversation history management. Must support various message types (text, images, files) and include features like message copying, regeneration, and conversation clearing. Deduct 5 points if conversation flow is awkward, 3 points if message display is inconsistent, and 3 points if interaction feedback is missing. 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 API failures, network interruption, malformed LLM responses, touch gesture conflicts, 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. Voice input/output for LLM interactions 2. Smart content summarization and extraction 3. Multi-modal input support with image/document upload 4. Personalized conversation themes). 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 message rendering systems coexisting) 2. Function modules unrelated to digital currency/LLM interaction (e.g., built-in games or irrelevant widgets) 3. Heavy animations that affect mobile performance (e.g., complex particle effects or excessive transitions). Deduct 3 points for each redundancy found, and directly deduct 10 points if 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 API layer/UI components/state management), TypeScript usage, component reusability, and build optimization for mobile. Deduct 5 points if global state pollution is found or proper state management is not used; deduct 5 points if component coupling is too high; deduct 5 points if mobile build optimization (code splitting, lazy loading) is missing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional fintech design standards?",
+      "description": "Evaluate whether the overall design follows modern fintech app principles: 1) Professional color scheme matching Tencent's brand guidelines 2) Proper mobile layout spacing (following 4px/8px grid system) 3) Clear information hierarchy with appropriate font sizes (≥16px for mobile readability, line height ≥1.4). Deduct 3 points for each cramped mobile layout element, 5 points for unprofessional color combinations, and 5 points for poor content readability on mobile devices. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the mobile interaction smooth and touch-optimized?",
+      "description": "Judge whether the mobile interactions conform to touch interface standards: 1) Touch feedback delay ≤ 100ms with proper haptic responses 2) Smooth scrolling and gesture recognition 3) Proper touch target sizes (≥44px) and spacing 4) Optimized for various screen sizes and orientations. Deduct 5 points for each unresponsive touch interaction, 3 points for scroll lag or gesture conflicts, and 5 points for poor accessibility on different mobile devices. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Other-Financial Platform",
+  "difficulty": "hard"
+}

package/library/other-frontend_development_tools/ai-frontend-development-scaffolding-tools.json

@@ -0,0 +1,68 @@
+{
+  "index": 272,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code examples whenever possible. I am referring to AI-integrated frontend development scaffolding tools like Vue and React.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the AI integration framework clearly defined and properly implemented?",
+      "description": "Check if the code defines a clear integration pattern for AI services with frontend frameworks. Score 0 if no integration architecture is defined, 5 if basic API calls are implemented without proper state management, and 10 if a comprehensive pattern (e.g., middleware, hooks, composables) is established that handles API calls, response processing, error states and loading indicators. The integration should follow the idiomatic patterns of the chosen framework (Vue/React).",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are the AI service connections properly abstracted and reusable?",
+      "description": "Evaluate if the code properly abstracts AI service connections through service layers or custom hooks/composables. The abstraction should handle authentication, rate limiting, request formatting, and response normalization. Deduct 3 points if authentication is hardcoded, 3 points if there's no error handling strategy, and 2 points if response parsing is inconsistent. The implementation should enable reusability across components. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Does the scaffolding include proper state management for AI operations?",
+      "description": "Review the state management implementation for AI operations, checking for proper handling of loading states, error states, partial results, and caching strategies. For Vue, look for Pinia/Vuex integration or composable patterns; for React, check for Context API, Redux, or custom hooks. Deduct 3 points if loading states are missing, 3 points for inadequate error handling, and 4 points if no caching/memoization strategy exists. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is there a comprehensive set of AI-enhanced UI components?",
+      "description": "Assess the implementation of AI-enhanced UI components such as predictive inputs, content generation tools, recommendation systems, or intelligent forms. Score 0 if no AI-enhanced components exist, 5 if basic components are implemented but lack customization options, and 10 if the code includes a diverse set of polished, reusable AI components with proper documentation and examples. Components should follow the design system of the chosen framework.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as API failures, rate limiting, token expiration, malformed AI responses, 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. Real-time feedback during AI generation 2. Explainable AI visualizations 3. Progressive AI enhancement based on user interaction patterns). 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 AI integrations (e.g., multiple implementations of the same capability) 2. Function modules unrelated to the core AI integration (e.g., unnecessary analytics) 3. Heavyweight dependencies that could affect performance (e.g., including full ML libraries in the frontend). 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 AI service/UI components/application logic), unit test coverage for AI integrations, and build process optimization. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process doesn't handle AI service environment variables securely. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the AI-integrated components follow modern design principles: 1) Consistent visual language with the rest of the application 2) Clear indication of AI-generated vs. user content 3) Professional loading and error states for AI operations. Deduct 3 points for inconsistent AI component styling, 5 points for confusing AI-generated content presentation, and 5 points for jarring transitions between AI and non-AI elements. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction with AI features smooth and seamless?",
+      "description": "Judge whether the AI interaction patterns conform to human perception characteristics: 1) Progressive feedback during long-running AI operations 2) Appropriate throttling/debouncing of AI requests 3) Clear visual indication of when AI is processing input. Deduct 5 points for each AI operation without feedback, 3 points for jarring UI updates when AI responses arrive, and 5 points for AI features that block the UI thread. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Other-Frontend Development Tools",
+  "difficulty": "hard"
+}