@getollie/cli 0.0.5 → 0.2.1

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

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

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

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

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

package/library/web_applications-mapping_location_services/vue3-tianditu-address-search.json

@@ -1,68 +0,0 @@
-{
-  "index": 1290,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure any code you generate is executable when displayed. Write a Vue3 application for searching addresses using Tianditu (China's mapping service).",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Vue3 application correctly initialized with proper structure?",
-      "description": "Check if the application uses Vue3 composition API (with setup() or <script setup>), has appropriate component structure, and follows Vue best practices. Look for proper import statements, component registration, and directory organization. Score 0 if Vue3 is not used, 5 if basic Vue3 structure is implemented but lacking composition API, and 10 if fully structured according to Vue3 standards.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is Tianditu API integration properly implemented?",
-      "description": "Verify proper Tianditu API key authentication and initialization. The code should include robust error handling for API failures (timeouts, invalid keys, service unavailability). Examine if the necessary Tianditu map modules are imported correctly. Deduct 5 points if the API key is hardcoded without environment variable protection, 3 points if error handling is minimal. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the address search functionality complete and user-friendly?",
-      "description": "Evaluate the implementation of search input, processing, and results display. Check for features like autocomplete suggestions, search history, and clear search options. The search should handle different formats of Chinese addresses properly. Score 0 if search doesn't work, 5 if basic search works but lacks advanced features, and 10 if search is comprehensive with good UX features.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the map display and interaction properly implemented?",
-      "description": "Review map initialization, proper zoom levels, marker placement, and map interaction controls. Check for responsive map resizing based on viewport changes. Examine if search results are visually highlighted on the map and if interaction with map markers provides useful information. Deduct 3 points for missing map controls, 3 points for non-responsive map display, and 5 points if markers aren't interactive. 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, invalid search queries, API limitations, invalid addresses, 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. Route planning with multiple waypoints 2. Address favorites system 3. Street View integration 4. Geolocation features showing user's current location). 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 map instances or search methods) 2. Function modules unrelated to address searching (e.g., unnecessary social sharing features) 3. Fancy effects that affect performance (e.g., heavy animations that slow 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 API services/UI components/state management), unit test coverage, and build process configuration. Check for proper use of Vue3 reactivity system (ref, reactive, computed, watch). Deduct 5 points if global state pollution is found or Vuex/Pinia isn't used for complex state management; deduct 5 points if the component reusability is poor; deduct 5 points if the build process is not properly configured. 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) Search results appear within 300ms 2) Map zooming/panning animations are smooth 3) Clear visual focus and loading states during search. Deduct 5 points for operations without feedback, 3 points for laggy map interactions, and 5 points for confusing UI state transitions. Check specifically if search suggestions appear naturally and map markers have smooth entrance animations. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Mapping/Location Services",
-  "difficulty": "easy"
-}

package/library/web_applications-online_shopping/beauty-product-samples-app.json

@@ -1,68 +0,0 @@
-{
-  "index": 1147,
-  "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 when possible. Create an APP: \"All Samples\" The concept behind this APP is that contemporary beauty product prices are rising, and while we young people don't have income sources, we still want to use high-end brand cosmetics. This APP specifically sells product samples, allowing users to buy authentic products while saving money. The backend uses IDEA, the frontend uses HarmonyOS, and the database uses MySQL.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the sample product management system fully implemented?",
-      "description": "Review whether the code accurately implements sample product categorization, inventory management, and pricing logic through HarmonyOS frontend and IDEA backend. Check if it includes product authentication mechanisms, sample size specifications, and expiration date tracking. Score 0 if core product management is not implemented, 5 if only basic CRUD operations exist, and 10 if comprehensive sample-specific features (batch tracking, authenticity verification, size variants) are fully included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the user shopping and payment system properly integrated?",
-      "description": "Check whether the shopping cart, order processing, and payment gateway integration work seamlessly between HarmonyOS frontend and backend services. Verify if sample quantity limits, bulk purchase discounts, and secure payment processing are implemented. Deduct 5 points if payment security measures are missing, and 3 points if order state synchronization fails. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the MySQL database architecture optimized and backend API well-designed?",
-      "description": "Evaluate whether the database schema efficiently handles sample inventory, user orders, and product relationships with proper indexing and normalization. Check if the IDEA backend provides RESTful APIs with proper error handling and data validation. Deduct 5 points if database queries are not optimized, and 5 points if API responses exceed 500ms. Review connection pooling and transaction management implementation.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the HarmonyOS native user experience fully optimized?",
-      "description": "Check whether the app leverages HarmonyOS-specific features like distributed capabilities, service widgets, and atomic services. Verify if the UI follows HarmonyOS design guidelines and utilizes platform-specific animations and gestures. Deduct 5 points if generic mobile UI patterns are used instead of HarmonyOS native components, and 3 points if cross-device continuity features are missing. Give 10 points if fully optimized for the platform.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as network failures, payment timeouts, inventory shortages, invalid user inputs, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should effectively handle edge cases like concurrent inventory updates and payment processing failures, 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 sample shopping experience (e.g., 1. AR try-on for makeup samples 2. AI-powered shade matching recommendations 3. Social sharing of sample reviews with photos 4. Subscription boxes for curated samples). 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 product search mechanisms coexisting) 2. Function modules unrelated to sample commerce (e.g., built-in social media feeds) 3. Fancy effects that affect performance (e.g., excessive product image animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if core shopping 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 business logic/presentation/data layers), unit test coverage, and build process automation for both HarmonyOS frontend and IDEA backend. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if code duplication rate is too high (over 30%); deduct 5 points if CI/CD pipeline and automated testing are not implemented. 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 e-commerce and beauty industry design principles: 1) Harmonious color palette suitable for beauty products (no more than 3 primary colors) 2) Proper layout spacing following HarmonyOS design guidelines (element spacing follows 8dp grid system) 3) Professional typography system (body font size ≥ 14sp, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for unprofessional color combinations, and 5 points for chaotic product layout.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to HarmonyOS interaction patterns and human perception: 1) Touch feedback delay ≤ 100ms for product selection 2) Transition animations between screens controlled between 300-500ms 3) Clear visual focus guidance for shopping flow 4) Smooth product image loading and zooming. Deduct 5 points for each operation without proper feedback, 3 points for visual artifacts during scrolling, and 5 points if key shopping actions (add to cart, checkout) are hard to locate.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Online Shopping",
-  "difficulty": "hard"
-}

package/library/web_applications-online_shopping/bootstrap-product-store-display-format.json

@@ -1,68 +0,0 @@
-{
-  "index": 1683,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure the generated code is executable for display. Implement the format in the image using Bootstrap, where the three red boxes mark: first row is the product title, second row is the store information to which the product belongs, and the third is product information. Each page displays the corresponding number of store information, with the products of the current store shown below the store. Please provide code examples.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Bootstrap implementation correct?",
-      "description": "Verify that the code correctly implements Bootstrap framework with proper CDN links or imports. Check if Bootstrap grid system is used appropriately for responsive layout. Confirm Bootstrap classes are used consistently rather than custom CSS where possible. Score 0 if Bootstrap is not used at all, 5 if Bootstrap is implemented but with inconsistent usage, and 10 if Bootstrap is implemented correctly with proper responsive design principles.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the three-section layout implemented as shown in the image?",
-      "description": "Examine whether the code implements the three distinct sections as marked in the red boxes: product title section, store information section, and product information section. Check if these sections are visually separated and positioned in the correct vertical order. Deduct 5 points if any section is missing, 3 points if sections are not visually distinct, and 3 points if the layout order is incorrect. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the store-product relationship correctly implemented?",
-      "description": "Evaluate if the code properly groups products under their respective stores. Check if the relationship between stores and their products is clearly established in the DOM structure and data model. Verify that products are only displayed under their corresponding store. Deduct 5 points if products aren't properly grouped under stores, 5 points if the relationship isn't preserved in the data structure. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is pagination or dynamic loading for store information implemented?",
-      "description": "Assess whether the code implements pagination or dynamic loading to display \"the corresponding number of store information\" per page as specified. Check if navigation between pages is implemented and if the state is preserved when switching pages. Deduct 5 points if pagination/dynamic loading is missing, 3 points if it's implemented but with UI/UX issues, and 3 points if state isn't preserved between page transitions. 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 missing data, network errors, empty store/product lists, 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. Search/filter functionality for products 2. Store/product cards with hover effects 3. Responsive design for mobile devices 4. Product quick-view modal). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple ways to view product details) 2. Function modules unrelated to the store-product display (e.g., unnecessary animations) 3. Fancy effects that affect performance (e.g., heavy JavaScript 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 data/view/controller layers), code organization, and maintainability. Deduct 5 points if global variable pollution is found; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's poor separation of concerns. 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-Online Shopping",
-  "difficulty": "easy"
-}

package/library/web_applications-online_shopping/clothing-customization-mini-program.json

@@ -1,68 +0,0 @@
-{
-  "index": 756,
-  "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 whenever possible. I am a clothing maker who wants to design a mini program that allows customers to independently select the clothing styles and details they want.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is there a complete clothing style selection system?",
-      "description": "Evaluate whether the code implements a comprehensive clothing style selection system with clear categorization (tops, bottoms, dresses, etc.), filtering capabilities, and preview functionality. Score 0 if there's no selection system, 5 if only basic categories exist without filtering, and 10 if the system includes advanced filtering by material, occasion, season, etc.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the customization of clothing details fully implemented?",
-      "description": "Check if the code allows for detailed customization of elements such as collars, sleeves, buttons, pockets, hems, etc. Deduct 3 points if any major clothing component can't be customized, 5 points if the customization options are too limited (less than 3 options per component). The full score is 10 points for comprehensive customization options with at least 5 options per component.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is there a real-time visualization system for design changes?",
-      "description": "Examine if the implementation includes a real-time rendering system that updates as customers make selections (using SVG/Canvas/WebGL). Check for features like zoom functionality, 360-degree rotation, and accurate representation of fabric textures. Deduct 5 points if visualizations lag more than 300ms, 3 points if texture rendering is unrealistic, and 3 points if rotation controls are missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there a measurement and sizing system integration?",
-      "description": "Review whether the code includes functionality for users to input or select body measurements, automatically suggest sizes, or visualize fit on different body types. Score 0 if there's no sizing system, 5 if there's only basic size selection without visualization, and 10 if there's an advanced system with body type simulation and precise fit prediction.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as incomplete selections, missing measurements, unsupported browser features, 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. AR try-on capabilities 2. AI-based style recommendations 3. Share design with friends for feedback). 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 color pickers with different interfaces) 2. Function modules unrelated to clothing design (e.g., a built-in game while waiting) 3. Fancy effects that affect performance (e.g., unnecessary animations that slow down the design process). 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/business logic/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: 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 selection changes, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Online Shopping",
-  "difficulty": "medium"
-}