@getollie/cli 0.0.1

package/library/web_applications-entertainment/genshin-impact-gacha-simulation.json

@@ -0,0 +1,68 @@
+{
+  "index": 824,
+  "question": "You are a coding expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable and demonstrable. Create a web application code that simulates Genshin Impact's gacha system, resembling the in-game wishing interface, complete with animations and character images.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the gacha core mechanism accurately implemented?",
+      "description": "Review whether the code correctly implements the gacha probability system with proper rarity distribution (5-star ~0.6%, 4-star ~5.1%, 3-star ~94.3%), pity system (hard pity at 90 pulls for 5-star, 10 pulls for 4-star), and soft pity mechanism (increased rates after 74 pulls). Score 0 if basic probability is missing, 5 if only simple random is implemented, and 10 if all gacha mechanics including guaranteed systems are fully accurate.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the wishing interface animation system complete?",
+      "description": "Check whether the implementation includes authentic gacha animations: shooting star effects, character reveal animations, rarity-based lighting effects (golden for 5-star, purple for 4-star), and smooth transition sequences. Evaluate if the animation timing matches the original game experience (3-5 seconds per pull). Deduct 5 points if animations are choppy or missing, 3 points if color schemes don't match rarity standards. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the character/weapon database and display system properly designed?",
+      "description": "Evaluate whether the system includes a comprehensive database of characters and weapons with proper categorization, rarity classification, and detailed information display. Check if character portraits, weapon images, and descriptions are properly integrated. Deduct 5 points if image loading is slow or broken, 3 points if character information is incomplete or inaccurate. Full score requires proper data structure and seamless asset management.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the banner system and wish history tracking implemented?",
+      "description": "Check whether the code includes multiple banner types (character event, weapon event, standard), proper banner rotation mechanism, and comprehensive wish history tracking with detailed statistics. Evaluate if pity counters are accurately maintained across different banner types. Deduct 5 points if banner switching is not functional, 3 points if history data is not persistent. Full score requires complete banner management system.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as network failures, invalid user inputs, animation interruptions, data corruption, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should gracefully handle edge cases like rapid clicking during animations or browser refresh during pulls, 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 gacha experience (e.g., 1. Constellation/refinement tracking system 2. Pull prediction and statistics dashboard 3. Custom banner creation tools 4. Social sharing of rare pulls 5. Achievement system for milestones). 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 number generators) 2. Function modules unrelated to gacha simulation (e.g., built-in chat system) 3. Excessive visual effects that impact performance (e.g., overly complex particle systems). Deduct 3 points for each redundancy found, and directly deduct 10 points if core gacha 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 gacha logic/UI components/data management), proper state management, and code organization. Deduct 5 points if global state pollution is found or no design patterns are used; deduct 5 points if code duplication rate is too high (over 30%); deduct 3 points if asset loading is not optimized. 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 Genshin Impact's visual style: 1) Authentic color palette matching the game's theme 2) Proper spacing and layout following game UI conventions 3) Appropriate typography and iconography 4) Consistent visual hierarchy. Deduct 3 points for each element that breaks visual consistency, 5 points for poor color harmony that doesn't match the game aesthetic, and 5 points for cluttered layout. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the gacha interactions feel authentic and responsive: 1) Wish button response time ≤ 100ms 2) Animation sequences flow naturally without stuttering 3) Smooth transitions between different UI states 4) Proper audio-visual feedback synchronization 5) Intuitive navigation and controls. Deduct 5 points for each laggy animation, 3 points for missing interaction feedback, and 5 points for confusing user flow. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Game Development-Casual",
+  "difficulty": "hard"
+}

package/library/web_applications-entertainment/music-player-app-with-online-playback-and-api.json

@@ -0,0 +1,68 @@
+{
+  "index": 575,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable when possible. Create a music player application where users can search for songs, create playlists, play, pause, and switch between songs. Song data should be retrieved through a music API, and the application should support online playback and display song covers, artist information, etc. The playback progress should update in real-time.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the music API integration and data management fully implemented?",
+      "description": "Review whether the code properly integrates with music APIs (such as Spotify, Apple Music, or similar services) with proper authentication handling, rate limiting, and error responses. Check if song metadata (title, artist, album, duration, cover art) is correctly parsed and cached. Evaluate data structure design for efficient storage and retrieval of track information. Score 0 if API integration is missing, 5 if basic search is implemented but lacks metadata handling, and 10 if comprehensive API integration with proper error handling and caching is present.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the playlist management system comprehensively designed?",
+      "description": "Check whether the code implements complete playlist functionality including creation, deletion, modification, and persistence of playlists. Evaluate if drag-and-drop reordering, duplicate detection, and playlist sharing capabilities are included. Review local storage or database integration for playlist persistence across sessions. Deduct 3 points if playlist operations lack undo functionality, 5 points if persistence is not implemented, and 2 points if drag-and-drop interactions are missing. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the audio playback engine robust and feature-complete?",
+      "description": "Evaluate whether the audio playback system supports seamless transitions between tracks, proper buffering strategies, and crossfade capabilities. Check if the player handles various audio formats, implements proper preloading for next tracks, and manages memory efficiently during long listening sessions. Review real-time progress updates with millisecond precision and seek functionality. Deduct 5 points if buffering causes frequent interruptions, 3 points if seek operations are imprecise, and 5 points if memory leaks occur during extended playback. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the search and discovery functionality intelligent and responsive?",
+      "description": "Check whether the search implementation includes autocomplete, search history, advanced filtering (by artist, album, genre, year), and fuzzy matching capabilities. Evaluate if search results are paginated efficiently and include relevant metadata. Review if the system implements search result caching and provides search suggestions. Give 10 points if all features are implemented with sub-200ms response times, 5 points if basic search works but lacks advanced features, and 0 points if search functionality is non-functional or extremely slow.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as network failures during streaming, invalid API responses, corrupted audio files, browser compatibility issues, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should gracefully handle API rate limits, network timeouts, and audio loading failures. Give 10 points if comprehensive error handling is present, 5 points if basic error handling exists, and 0 points if no exception handling is implemented.",
+      "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 music experience (e.g., 1. Real-time audio visualization/spectrum analyzer 2. Lyrics synchronization with playback 3. Smart playlist generation based on listening history 4. Social sharing of currently playing tracks 5. Equalizer with custom presets 6. Sleep timer and alarm integration). Add 2-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 audio context instances, duplicate playlist logic) 2. Function modules unrelated to music playback (e.g., built-in games, unrelated social features) 3. Performance-heavy effects that don't enhance user experience (e.g., excessive visual effects during playback). Deduct 3 points for each redundancy found, and directly deduct 10 points if core music 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 audio engine/UI components/API services), proper state management, and build process automation. Check for proper TypeScript usage, component reusability, and performance optimization. Deduct 5 points if global audio state pollution is found or audio context is not properly managed; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process lacks optimization for audio assets. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional music app design standards?",
+      "description": "Evaluate whether the overall design follows modern music app design principles: 1) Harmonious color scheme that complements album artwork 2) Proper visual hierarchy with clear focus on currently playing track 3) Professional typography system with readable artist/track information 4) Consistent iconography for playback controls. Deduct 3 points for each cluttered interface element, 5 points for poor contrast affecting readability, and 5 points if the design doesn't adapt well to different album artwork colors. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and intuitive for music playback?",
+      "description": "Judge whether the interactive elements conform to music app standards: 1) Playback control responsiveness ≤ 50ms 2) Smooth progress bar scrubbing with real-time preview 3) Intuitive gesture controls (swipe for next/previous track) 4) Visual feedback for all user actions 5) Smooth transitions between different app states (search, playlist, now playing). Deduct 5 points for each unresponsive control, 3 points for jerky progress bar animations, and 5 points if key music controls are hard to access during playback. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Multimedia Editing-Audio Editing",
+  "difficulty": "hard"
+}

package/library/web_applications-entertainment/vue-3-local-music-card-layout-modern-ui.json

@@ -0,0 +1,68 @@
+{
+  "index": 1113,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable when possible. Please help me design a local music page using Vue 3, with a card-based layout and modern, minimalist, and aesthetically pleasing UI. Also explain what features it includes.\n\n```vue\n<template>\n  <div>\n    <h1>Local Music</h1>\n  </div>\n</template>\n\n<script setup lang=\"ts\">\n\n</script>\n\n<style scoped>\n\n</style>",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the card-based layout fully implemented?",
+      "description": "Evaluate whether the code implements a proper card-based layout for displaying music items with appropriate spacing, shadows, and responsive design. Check if the cards have proper hover effects, click interactions, and consistent sizing. Score 0 if there's no card implementation at all, 5 if basic card structure exists but lacks visual refinement, and 10 if a complete, polished card system is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are music playback controls implemented?",
+      "description": "Review the implementation of essential music player controls (play, pause, skip, volume, progress bar). Check if the audio is managed properly with Vue refs and if the UI state reflects playback status accurately. Deduct 3 points if progress tracking is missing, 3 points if volume control is absent, and 4 points if play/pause functionality is not implemented. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is local file access and handling implemented?",
+      "description": "Assess how the application handles local file access, including file selection, metadata extraction (artist, album, duration), and storage of user preferences. Check for file type validation and error handling when dealing with unsupported formats. Award 10 points for complete implementation with proper error handling, 5 points if basic file selection works but lacks metadata extraction, 0 points if local file access is not implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the music library management system implemented?",
+      "description": "Evaluate whether the code includes features for organizing music (playlists, favorites, sorting, filtering, search). Check if state management is properly implemented using Vue's reactivity system. Deduct 3 points if sorting/filtering is missing, 3 points if search functionality is absent, and 4 points if there's no playlist management. 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 corrupted audio files, browser storage limitations, 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. Audio visualization 2. Lyrics synchronization 3. Audio equalizer 4. Sleep timer). 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 volume control mechanisms) 2. Function modules unrelated to music playback (e.g., unnecessary social sharing features) 3. Fancy effects that affect performance (e.g., excessive animations that impact 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": "Does the code have engineering quality?",
+      "description": "Review Vue 3 Composition API usage, component structure, TypeScript type safety, and proper event handling. Check for proper separation of concerns and reusable components. Deduct 5 points if prop drilling is used instead of provide/inject or proper state management; deduct 3 points if TypeScript types are missing or incorrect; deduct 2 points if component cohesion is poor. 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, minimalist UI 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 for currently playing tracks. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast scrolling, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Entertainment",
+  "difficulty": "medium"
+}

package/library/web_applications-entertainment/web-based-intelligent-music-player-with-scheduled-playlists.json

@@ -0,0 +1,68 @@
+{
+  "index": 1285,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable and displayable. Create a web-based intelligent music player that can automatically add playlists for different times and play the scheduled music when the time arrives. Please provide detailed implementation process and complete code.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core music playback system fully implemented?",
+      "description": "Review whether the code accurately implements HTML5 Audio API or Web Audio API for music playback, including play/pause, volume control, progress tracking, and playlist management. Check if it supports multiple audio formats (MP3, WAV, OGG) and includes proper audio loading states. Score 0 if basic playback is not functional, 5 if only simple play/pause works, and 10 if all core audio features including seamless track transitions are implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the intelligent scheduling system properly designed?",
+      "description": "Evaluate whether the time-based scheduling mechanism uses accurate timing APIs (setInterval/setTimeout or Web Workers for precision). Check if it includes timezone handling, schedule conflict resolution, and persistent storage of scheduled playlists. Deduct 5 points if scheduling accuracy exceeds ±30 seconds, 3 points if timezone issues aren't handled, and 5 points if schedules don't persist after browser refresh. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the automatic playlist generation algorithm effective?",
+      "description": "Check whether the system implements intelligent playlist creation based on time context (morning, afternoon, evening, night) with appropriate music categorization logic. Evaluate if it includes music metadata analysis, mood-based selection, or learning from user preferences. Deduct 5 points if playlists are randomly generated without context awareness, 3 points if music categorization is overly simplistic. Full score requires sophisticated algorithmic playlist generation.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the complete music library management system constructed?",
+      "description": "Review whether the code includes comprehensive music library features: file upload/import, metadata editing, search/filter functionality, and playlist organization. Check for drag-and-drop support, bulk operations, and music file validation. Deduct 5 points if file management is basic, 3 points if search functionality is missing, and 5 points if no bulk operations are supported. Give 10 points if fully implemented with advanced library management.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as corrupted audio files, network interruption, invalid time inputs, browser compatibility 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. Audio visualization/spectrum analyzer 2. Smart crossfade between tracks 3. Voice control integration 4. Sleep timer with fade-out 5. Social sharing of playlists). 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 audio players coexisting) 2. Function modules unrelated to music playing (e.g., built-in games or social media feeds) 3. Fancy effects that affect audio performance (e.g., heavy visual effects during playback). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core music 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 audio engine/UI/scheduling/storage 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 music player design principles: 1) Harmonious color matching with proper contrast for readability 2) Intuitive music controls layout (standard play/pause/skip positioning) 3) Professional typography for song titles and metadata (body font size ≥ 14px, line height over 1.5 times) 4) Proper album artwork display. Deduct 3 points for each crowded visual element, 5 points for poor color contrast affecting usability, and 5 points for chaotic music information 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 music player UX standards: 1) Audio control feedback delay ≤ 100ms 2) Progress bar scrubbing is responsive and accurate 3) Volume slider transitions are smooth 4) Track switching animations are seamless 5) Schedule notifications are non-intrusive. Deduct 5 points for each laggy audio control response, 3 points for jerky progress bar interactions, and 5 points for disruptive notification behavior. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Entertainment",
+  "difficulty": "hard"
+}

package/library/web_applications-entertainment/web-based-music-synthesizer-with-modules-and-export.json

@@ -0,0 +1,68 @@
+{
+  "index": 639,
+  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable when possible. Implement a web-based music synthesizer that offers various synthesizer modules (such as oscillators, filters, envelope generators), allowing users to create custom sounds by dragging and connecting modules, with capabilities for real-time playback and audio export.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core synthesizer architecture properly implemented?",
+      "description": "Review whether the code correctly implements the Web Audio API with proper audio nodes (OscillatorNode, BiquadFilterNode, GainNode, etc.) and connects them in a functional audio graph. Check if the system handles audio context initialization, sample rate management, and buffer processing correctly. Score 0 if audio synthesis is not implemented, 5 if basic oscillators are present but lacking modulation capabilities, and 10 if a complete modular synthesis system is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are essential synthesizer modules implemented and functional?",
+      "description": "Evaluate the range of synthesizer modules offered: oscillators (sine, square, sawtooth, triangle, noise), filters (lowpass, highpass, bandpass), envelope generators (ADSR), LFOs, and effects (reverb, delay, distortion). Each module should be properly parameterized. Deduct 1 point for each essential module missing, with a minimum score of 0. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the drag-and-drop connection system properly implemented?",
+      "description": "Check whether the interface allows intuitive dragging of modules onto a workspace and creating connections between them. Examine if the connection system validates compatible inputs/outputs, prevents audio feedback loops, and handles signal flow visualization. Deduct 5 points if connections aren't visually represented, 5 points if invalid connections aren't prevented, and 3 points if reconnection/disconnection isn't supported. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the system handle real-time control and audio export functions?",
+      "description": "Verify that real-time parameter adjustment is possible while audio is playing, with minimal latency (<50ms). Check if the system supports exporting audio as WAV or MP3 files with proper encoding, metadata handling, and download functionality. Deduct 5 points if real-time control introduces audible glitches, and 5 points if export functionality is missing or produces corrupted files. 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 audio context suspended states, browser audio restrictions, memory management for long audio processes, 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. Preset library with shareable configurations 2. Spectral visualization of output audio 3. MIDI device support for external control). 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 audio processing functions 2. Function modules unrelated to audio synthesis (e.g., built-in video player) 3. Fancy effects that consume excessive CPU and affect audio 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 audio engine/UI/persistence layers), unit test coverage, and web audio performance 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 audio performance is not optimized (e.g., unnecessary resampling or inefficient audio processing). 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 DAW/synthesizer design principles: 1) Consistent control appearance (knobs, sliders, buttons share visual language) 2) Proper layout spacing with logical signal flow (typically left-to-right) 3) Professional color coding of different module types and connection paths. Deduct 3 points for confusing module appearances, 5 points for unintuitive control layouts, and 5 points for unclear signal flow visualization. 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 musical instrument interaction standards: 1) Parameter changes reflect in audio with <10ms latency 2) Smooth animations for control adjustments without audio artifacts 3) Clear visual feedback when making connections. Deduct 5 points for audible glitches during control changes, 3 points for laggy UI responses during audio processing, and 5 points for connection feedback that doesn't clearly indicate signal flow. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Multimedia Editing-Audio Editing",
+  "difficulty": "hard"
+}

package/library/web_applications-entertainment_platform/movie-website-login-registration-homepage.json

@@ -0,0 +1,68 @@
+{
+  "index": 792,
+  "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. Create a movie project in my \"E:\\graduation project\\movie website system\" folder, first implementing login, registration, and homepage functionality. We'll handle the data later. I need a very complete process.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the project structure properly set up?",
+      "description": "Check if the project follows a standard structure with clear separation of concerns (frontend/backend directories, assets, components, etc.). The structure should be located in 'E:\\graduation project\\movie website system'. Verify if appropriate build tools or frameworks are initialized (like React, Vue, Angular for frontend; Node.js, Spring, Django for backend). Score 0 if there is no clear structure, 5 if basic structure exists but lacks organization, and 10 for a comprehensive, industry-standard architecture.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the authentication system fully implemented?",
+      "description": "Evaluate the implementation of login and registration functionality. Check for proper form validation (email format, password strength, required fields), secure password handling (hashing, not storing plaintext), session/token management, and user feedback mechanisms. Deduct 3 points if form validation is missing, 4 points if password security is inadequate, and 3 points if user feedback is poor. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the homepage design comprehensive and functional?",
+      "description": "Assess whether the homepage includes essential movie website elements: featured movies carousel, categorized movie listings, search functionality, and navigation to other sections. Check if data placeholders are properly implemented for future integration. Deduct 3 points if the layout is incomplete, 4 points if navigation is missing or broken, and 3 points if there are no data placeholders. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the front-end responsive and mobile-friendly?",
+      "description": "Verify if the application uses responsive design principles for different screen sizes (desktop, tablet, mobile). Check if media queries are properly implemented, if flexible grid systems are used, and if touch interfaces are considered. Score 0 if not responsive at all, 5 if partially responsive with issues, and 10 if fully responsive across devices.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid form inputs, authentication failures, network 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. Dark/light mode toggle 2. Animated transitions between pages 3. Personalized user greetings 4. Remember-me functionality). 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 authentication methods without clear purpose) 2. Function modules unrelated to the movie website (e.g., unnecessary social media features) 3. Fancy effects that affect performance (e.g., excessive animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating UI/logic/data layers), code reusability, naming conventions, and build process setup. 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": "Web Applications-Entertainment Platform",
+  "difficulty": "easy"
+}

package/library/web_applications-entertainment_platform/webpage-code-for-xian-cuisine.json

@@ -0,0 +1,68 @@
+{
+  "index": 1761,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code in your demonstration. Design a webpage code for Xi'an cuisine.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Xi'an cuisine webpage layout properly structured?",
+      "description": "Evaluate if the webpage has a clear HTML5 semantic structure with proper header, navigation, main content sections, and footer. Check if the layout adapts to different screen sizes (responsive design) with media queries. Give 10 points for perfect structure with semantic HTML5 elements, 5 points for basic structure without responsiveness, 0 points if critical structural elements are missing.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are Xi'an cuisine dishes comprehensively presented?",
+      "description": "Review whether the code includes presentation of at least 5 signature Xi'an dishes (e.g., Biang Biang noodles, Roujiamo, Liangpi, Paomo, etc.) with accurate descriptions, images, and cultural context. Each dish should have proper categorization, ingredient information, and preparation methods. Give 10 points for comprehensive coverage, 5 points if only basic information is provided, 0 points if fewer than 3 signature dishes are included.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is there interactive functionality for user engagement?",
+      "description": "Check if the code implements interactive elements such as dish filtering/sorting, image galleries/carousels, recipe expansion/collapse, interactive maps of Xi'an food streets, or user rating systems. Award 10 points for 3+ well-implemented interactive features, 5 points for basic interactivity, 0 points if no JavaScript interaction is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the webpage incorporate cultural elements of Xi'an?",
+      "description": "Evaluate if the website design integrates cultural elements specific to Xi'an (Terracotta Army, city wall, Muslim Quarter, etc.) through visual design elements, typography, color schemes, or background patterns. Check for historical context about Xi'an's culinary traditions. Give 10 points for deep cultural integration, 5 points for superficial references, 0 points if cultural context is absent.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as image loading failures, form validation, browser compatibility 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. Interactive cooking process animations 2. Virtual tour of Xi'an food streets 3. Audio pronunciations of dish names in local dialect). 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 gallery implementations) 2. Function modules unrelated to Xi'an cuisine (e.g., non-food related content) 3. Fancy effects that affect performance (e.g., excessive animations that slow page loading). 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 HTML structure, CSS styling, and JavaScript functionality), code organization, and maintainability. Deduct 5 points if inline styles are extensively used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if JavaScript is not properly organized or lacks comments. 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 reflecting Xi'an's cultural palette (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 when navigating through dishes or categories. 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": "Web Applications-Education/Learning",
+  "difficulty": "easy"
+}

package/library/web_applications-mapping_location_services/mapbox-kml-viewer-with-tools.json

@@ -0,0 +1,68 @@
+{
+  "index": 258,
+  "question": "You are a code expert. Please utilize your professional knowledge to generate accurate and professional responses. Be careful to ensure the generated code is executable for demonstration. Create an HTML using Mapbox that can import KML files, with map switching functionality to toggle between satellite imagery, road networks, etc. Add annotation capabilities and measurement functions for distance and area.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Mapbox integration properly implemented?",
+      "description": "Check whether the Mapbox API is correctly initialized with proper authentication, fallback handling for API limits, and error management. The map container should be responsive with proper viewport settings. Score 0 if Mapbox is not properly initialized, 5 if basic integration exists but lacks error handling, and 10 if fully implemented with proper error handling and responsive design.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Does the KML file import functionality work correctly?",
+      "description": "Evaluate the KML parsing and rendering implementation. Check for proper file validation, error handling during parsing, and efficient rendering of complex KML structures (including multigeometry, extended data, and styles). Test with different KML file sizes and complexities. Deduct 5 points if only simple KML elements are supported, 3 points if parsing errors aren't handled properly. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the map layer switching function complete?",
+      "description": "Verify that the implementation includes multiple map styles (satellite, streets, terrain, etc.) with smooth transitions between them. The UI should clearly indicate the current map style. Check that custom layers persist across style changes, and the system handles style loading failures gracefully. Deduct 5 points if transitions are jarring, 3 points if fewer than 3 map styles are available. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are the annotation and measurement tools fully functional?",
+      "description": "Examine whether the implementation includes both distance and area measurement tools with clear UI controls. Check for proper unit display (meters/kilometers, square meters/hectares), interactive editing capabilities, and persistence of measurements. Annotations should support multiple geometry types (points, lines, polygons) with customizable styles. Deduct 5 points if either measurement type is missing, 3 points if unit conversion is absent. 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 KML files, API errors, browser compatibility 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. KML data statistics visualization 2. Automated geolocation clustering 3. 3D terrain visualization integration). 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 conversion utilities for the same purpose) 2. Function modules unrelated to mapping (e.g., unnecessary social sharing features) 3. Fancy effects that affect performance (e.g., excessive animations that slow down map rendering). 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 map rendering/data handling/UI components), event handling patterns, and code organization. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no clear separation between data and presentation layers. 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 UI controls that obstruct map visibility. 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) Map interaction responsiveness ≤ 100ms 2) Smooth zoom and pan operations without jankiness 3) Clear visual feedback for tool selection and operation. Deduct 5 points for jerky map movements, 3 points for delayed feedback when drawing measurements, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Utility Tools-Calculation Tools",
+  "difficulty": "medium"
+}