@getollie/cli 0.0.1

package/library/multimedia_editing-video_production/xiaohongshu-text-image-to-video-html.json

@@ -0,0 +1,68 @@
+{
+  "index": 309,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you provide is executable and can be demonstrated. Create a Xiaohongshu (Little Red Book) style text image, convert the image to video, add music, make it downloadable, and implement it using HTML.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Xiaohongshu-style text image generation fully implemented?",
+      "description": "Review whether the code accurately implements Xiaohongshu-style visual elements through HTML/CSS/JavaScript, including gradient backgrounds, emoji decorations, stylized fonts, and proper text layout. Check if it supports multi-line text input, automatic line wrapping, and character limits. Score 0 if basic text-to-image conversion is not implemented, 5 if only simple text overlay is achieved, and 10 if all authentic Xiaohongshu visual styles are replicated including shadows, borders, and brand-consistent aesthetics.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the image-to-video conversion mechanism properly implemented?",
+      "description": "Check whether the code uses Canvas API or WebGL to convert static images into video format (MP4/WebM). Evaluate if it includes proper frame rate control (minimum 24fps), duration settings, and transition effects. Verify if the video encoding uses efficient compression algorithms. Deduct 5 points if video quality is poor (resolution below 720p), and 3 points if frame rate is inconsistent. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the audio integration and synchronization system designed correctly?",
+      "description": "Evaluate whether the music integration uses Web Audio API for seamless audio-video synchronization. Check if it supports multiple audio formats (MP3/WAV/OGG), volume control, and fade-in/fade-out effects. Verify if background music loops properly and matches video duration. Deduct 5 points if audio-video sync drift exceeds 50ms, and 3 points if audio quality is compressed below 128kbps. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the download functionality complete with proper file handling?",
+      "description": "Check whether the code implements client-side file generation using Blob API and provides downloadable links for both image and video files. Evaluate if it includes proper filename generation, file size optimization, and format selection options. Verify cross-browser compatibility for download functionality. Deduct 5 points if download fails on major browsers, and 3 points if file naming is not user-friendly. Give 10 points if fully implemented with progress indicators.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as oversized text input, unsupported file formats, browser compatibility issues, memory limitations, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should effectively handle media processing failures, canvas rendering errors, and file system limitations, 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 text style preview 2. Multiple template themes selection 3. Custom font upload 4. Social sharing integration 5. Batch processing capabilities). 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 image rendering engines coexisting) 2. Function modules unrelated to text-image-video creation (e.g., built-in social media feeds) 3. Fancy effects that affect performance (e.g., excessive particle animations during processing). 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 text processing/image generation/video conversion/audio handling layers), error handling coverage, and performance optimization. Deduct 5 points if memory leaks are found during media processing 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 progress feedback for long-running operations. 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 and Xiaohongshu's aesthetic: 1) Harmonious color matching with brand-consistent pink/coral themes 2) Proper layout spacing following 8px grid system 3) Professional typography with readable fonts (≥14px, line height ≥1.5). Check if the text image output matches authentic Xiaohongshu post aesthetics. Deduct 3 points for each crowded visual element, 5 points for off-brand color schemes, and 5 points for poor text-image composition. 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) Real-time text preview updates ≤100ms 2) Image generation feedback with progress indicators 3) Video processing with loading states 4) Smooth transitions between editing and preview modes (300-500ms). Deduct 5 points for each operation without visual feedback, 3 points for laggy text input responses, and 5 points if users cannot track processing progress. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Multimedia Editing-Video Production",
+  "difficulty": "hard"
+}

package/library/other-astrology_divination_software/bazi-charting-software-four-pillars.json

@@ -0,0 +1,68 @@
+{
+  "index": 1501,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you provide is executable when possible. Write a Four Pillars (BaZi) charting software that only displays the Four Pillars and Decennial Cycles.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Four Pillars (BaZi) chart calculation correctly implemented?",
+      "description": "Check whether the code accurately calculates the Four Pillars (year, month, day, hour) based on date and time input. Verify that the Heavenly Stems and Earthly Branches are correctly assigned according to traditional Chinese calendar calculations. Score 0 if core calculation logic is missing, 5 if basic pillar formation exists with minor errors, and 10 if calculations fully comply with traditional BaZi principles including solar calendar adjustments.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are the Decennial Cycles (Luck Pillars) correctly calculated?",
+      "description": "Evaluate whether the code properly determines the Decennial Cycles (Da Yun) based on the Four Pillars chart. Check for accurate implementation of starting age calculation, cycle transitions, and proper sequencing of Heavenly Stems and Earthly Branches in the luck pillars. Deduct 5 points if the starting point of luck pillars is incorrect, 3 points if the cycle progression direction (forward/reverse based on gender) is wrong. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Does the software handle various calendar systems and time conversions properly?",
+      "description": "Verify that the software can convert between solar (Gregorian) and lunar calendars accurately, handling leap months and time zone differences correctly. Check if the software properly accounts for historical calendar changes and different date formats. Deduct 5 points if lunar-solar conversion has errors, 3 points if time zone handling is missing, and 2 points if historical dates (before 1900) are not supported. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the visual representation of the Four Pillars chart clear and traditional?",
+      "description": "Assess whether the chart follows traditional BaZi visualization standards with clear distinction between Heavenly Stems and Earthly Branches. Check if Chinese characters are properly displayed with their corresponding elements (Five Elements) appropriately color-coded. Deduct 3 points if elements aren't color-coded, 5 points if the traditional layout isn't followed, and 2 points if the relationship between pillars isn't visually clear. 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, future dates, dates before the supported calendar system, 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. Visual representation of the Five Elements balance 2. Interactive element clash/combination highlights 3. Simplified explanations of chart significance). 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. Features beyond the scope of Four Pillars and Decennial Cycles (e.g., detailed fortune interpretation) 2. Unnecessary calculation methods that complicate the codebase 3. Fancy effects that affect performance without adding value to the core functionality. 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 models), 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 while respecting traditional BaZi aesthetics: 1) Harmonious color matching (using traditional Five Elements colors appropriately) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (clear rendering of both Chinese characters and numerals). 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 when switching between chart views or date inputs. Deduct 5 points for each operation without feedback, 3 points for visual after-images during transitions, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Other-Astrology/Divination Software",
+  "difficulty": "hard"
+}

package/library/other-astrology_divination_software/bazi-fortune-telling-software-uni-app.json

@@ -0,0 +1,68 @@
+{
+  "index": 809,
+  "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. Develop an Eight-Characters (BaZi) fortune telling software using index.vue in uni-app with BuilderX that can calculate birth eight characters, major life cycles, yearly fortune and other information. Please provide me with the complete code. I am a beginner, so the process should be detailed.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Eight-Characters (BaZi) calculation core accurately implemented?",
+      "description": "Review whether the code implements accurate Chinese lunar calendar conversion, celestial stems and earthly branches calculation, and the Four Pillars formation (year, month, day, hour). Score 0 if core BaZi calculations are missing, 5 if basic calculations are implemented with minor inaccuracies, and 10 if the implementation includes all traditional calculation methods with leap month handling.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are the major life cycles (Da Yun) calculations properly implemented?",
+      "description": "Evaluate whether the code correctly calculates starting ages for major life cycles, properly implements the 10-year cycles based on gender differences, and accurately displays favorable/unfavorable periods. Deduct 5 points if gender-specific calculations are missing, and 3 points if cycle transitions are incorrectly handled. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the yearly fortune (Nian Yun) prediction system comprehensive?",
+      "description": "Check whether the code includes annual luck predictions with flowing stems and branches (Liu Nian), clash and combination relationships between elements, and specific life aspect predictions. Deduct 5 points if only basic yearly stems/branches are shown without interpretations, and 3 points if seasonal transitions are not considered. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the Five Elements analysis and interpretation complete?",
+      "description": "Assess whether the code provides accurate analysis of the user's Five Elements (Wu Xing) composition, identifies day master strength, favorable/unfavorable elements, and offers personalized recommendations. Score 0 if Five Elements analysis is missing, 5 if basic analysis is provided without personalization, and 10 if the implementation includes detailed interpretations with balancing suggestions.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid date inputs, future dates, edge case birth times, 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. Visual elemental charts 2. Compatibility analysis between two BaZi charts 3. Interactive explanations of terms). 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 2. Function modules unrelated to BaZi fortune telling (e.g., irrelevant horoscopes) 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 (such as separating calculation logic/view/data layers), appropriate use of uni-app components, and BuilderX integration. 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 BuilderX features are not properly utilized. 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 traditional Chinese aesthetics with modern UI principles: 1) Harmonious color matching reflecting Five Elements theory 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system with appropriate classical Chinese typography. 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 when switching between different fortune telling aspects. 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": "Game Development-Casual",
+  "difficulty": "hard"
+}

package/library/other-audio_player/html-music-player-with-interference-and-pause.json

@@ -0,0 +1,68 @@
+{
+  "index": 453,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Try to ensure that the generated code is executable. I need your help to write an HTML music player page. 1. It should be able to play 10 music tracks plus one interference audio. 2. After playing each music track, it will automatically play the interference audio once and then continue to the next music track, cycling through this pattern. 3. It also needs a pause button. When I press the pause button, the music won't stop immediately, but will pause after the current track finishes playing.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Music Player Core Functionality Implementation",
+      "description": "Evaluate whether the HTML/JavaScript code correctly implements the music player with 10 tracks and one interference audio. Check if the audio sources are properly defined and if the player initializes correctly.Score 0 if the player doesn't load any tracks, 5 if it loads but doesn't play properly, and 10 if all tracks are properly defined with appropriate metadata (artist, title, duration) and load correctly.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Automatic Play Sequence Logic",
+      "description": "Assess whether the code properly implements the required play sequence: a music track followed by the interference audio, then the next music track, in a continuous cycle.Deduct 5 points if the sequence logic is flawed (e.g., interference audio doesn't play after each track), deduct 3 points if the transition between tracks isn't smooth. Full score requires proper event listeners for the 'ended' event to trigger the correct sequence.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Deferred Pause Functionality",
+      "description": "Check if the pause button correctly implements the requirement to pause after the current track finishes playing rather than immediately.Deduct 10 points if pause occurs immediately. Deduct 5 points if the pause functionality works but doesn't resume from the correct position. The full score requires state management to remember the pause request and execute it only after the current track completes.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Playlist Management System",
+      "description": "Evaluate how well the code manages the playlist of 10 tracks plus the interference audio, including tracking the current position and handling the cycling behavior.Deduct 5 points if the playlist doesn't properly cycle back to the beginning after reaching the end. Deduct 3 points if the current track is not clearly indicated in the UI. Full score requires efficient playlist data structure with proper indexing.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Code Robustness",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as audio loading failures, user rapid clicking, browser compatibility issues) and provide friendly error prompts or recovery mechanisms.Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Innovative Features",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Visualizer for audio frequencies 2. Volume normalization between tracks and interference 3. Playlist reordering capabilities).Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Redundant Features",
+      "description": "Strictly check three types of redundancy: 1. Redundant audio handling logic 2. Function modules unrelated to the music player (e.g., unnecessary animations) 3. Fancy effects that affect performance (e.g., excessive DOM manipulations during playback).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": "Engineering Quality",
+      "description": "Review modular design (such as separating audio handling logic from UI components), code organization, and maintainability.Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no clear separation between audio handling and UI components. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Interface Design Quality",
+      "description": "Evaluate whether the music player interface follows modern design principles: 1) Intuitive controls with clear visual hierarchy 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional typography system (track titles clearly differentiated from artist names, timestamps in monospace font).Deduct 3 points for each confusing control element, 5 points for poor readability of track information, and 5 points for chaotic player layout. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Playback Experience Quality",
+      "description": "Judge whether the playback experience meets user expectations: 1) Visual indication of current playing track 2) Smooth transition between tracks and interference audio 3) Responsive controls with appropriate feedback.Deduct 5 points for missing visual indication of currently playing item, 3 points for audible gaps or pops between tracks, and 5 points for controls that don't provide visual feedback when activated. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Other-Audio Player",
+  "difficulty": "hard"
+}

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

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

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

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

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