@getollie/cli 0.0.1

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

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

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

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

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

package/library/web_applications-online_shopping/college-second-hand-trading-platform.json

@@ -0,0 +1,68 @@
+{
+  "index": 1472,
+  "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. Help me write a mini program similar to the Xianyu platform, called \"Heavy Industry Second-hand Trading Platform,\" targeted for college students' use. It should be written in HTML and run in a browser. Please provide the complete code.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core marketplace functionality fully implemented?",
+      "description": "Evaluate if the code implements essential e-commerce functions: product listing, search functionality, product detail pages, and category filtering. Score 0 if these core features are missing, 5 if only basic listing is implemented, and 10 if all marketplace functionalities work properly with appropriate data handling.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the user authentication and profile management implemented?",
+      "description": "Check if the code includes complete user registration, login/logout functionality, and profile management (including editing personal information, viewing transaction history). Deduct 5 points if authentication is missing security measures (like password hashing), and 3 points if profile editing is incomplete. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the product listing and management system properly developed?",
+      "description": "Assess whether users can post new items with images, descriptions, and pricing. Check if the system includes editing/deleting listings and proper validation for required fields. Deduct 5 points if image handling is not implemented, and 3 points if form validation is missing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the message/chat system for buyer-seller communication implemented?",
+      "description": "Evaluate whether the platform includes a messaging system allowing potential buyers to communicate with sellers. Check if the system supports message history, notifications, and real-time updates. Deduct 5 points if there's no messaging functionality at all, 3 points if it's incomplete. 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 form submission errors, image loading failures, network interruptions, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Real-time price tracking 2. Campus location-based filtering 3. Student verification system). 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 listing creation forms) 2. Function modules unrelated to second-hand trading (e.g., a built-in game) 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 components, data models, and controllers), code reusability, and 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 project structure. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast scrolling, and 5 points if key functions (like 'post item' or 'contact seller') are difficult to find. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Online Shopping",
+  "difficulty": "medium"
+}

package/library/web_applications-online_shopping/create-localized-jd-website-framework.json

@@ -0,0 +1,68 @@
+{
+  "index": 1251,
+  "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 for demonstration purposes. I need to complete an e-commerce website design assignment: How can I create a localized version of JD.com? I don't need JD's data, just the website framework that looks exactly the same.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core e-commerce homepage structure fully implemented?",
+      "description": "Review whether the code accurately implements the key structural components of JD.com's homepage, including the primary navigation bar, promotional banner carousel, product grid display, and category sidebar. Score 0 if the basic structure is missing, 5 if only partial components are implemented, and 10 if the complete JD.com layout structure is replicated with proper responsive design principles.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the product listing and category navigation system properly implemented?",
+      "description": "Evaluate whether the code includes JD's multi-level category navigation system, product listing pages with filtering options, and sorting mechanisms. Check if the implementation includes breadcrumb navigation, proper grid/list view options, and pagination functionality. Deduct 5 points if the category system is oversimplified, 3 points if filtering options are missing, and 2 points if pagination is not implemented. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the product detail page complete with all necessary components?",
+      "description": "Check whether the product detail page includes all critical components: image gallery with zoom functionality, product description tabs, specifications table, price display with discount calculations, buying options (quantity, variants), and the 'add to cart' functionality. Deduct 3 points for each missing major component. Award full 10 points only if the layout perfectly mirrors JD's product detail page structure.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the shopping cart and checkout process flow correctly implemented?",
+      "description": "Assess whether the implementation includes JD's shopping cart preview, full cart page, address selection, payment method selection, and order confirmation screens. The code should handle cart item management (add, remove, update quantity) and preserve cart data across sessions. Deduct 5 points if the cart functionality is basic without session persistence, and 5 points if the checkout flow is incomplete. 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 API request failures, invalid inputs, empty search results, out-of-stock products, etc.) and provide friendly error prompts or fallback mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Real-time price comparison 2. Personalized recommendation engine 3. Voice search capability 4. AR product visualization). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple cart management systems) 2. Function modules unrelated to e-commerce (e.g., a built-in game center not present in JD) 3. Fancy effects that affect performance (e.g., excessive animations causing lag). 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 components, business logic, and data services), component reusability, code organization, and build process automation. Deduct 5 points if global state management is poorly implemented; 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 JD.com's design standards?",
+      "description": "Evaluate whether the design accurately replicates JD.com's: 1) Exact color scheme (including the characteristic red accent color) 2) Proper layout spacing and proportions 3) Typography system and icon set. Deduct 3 points for each visual element that doesn't match JD's style, 5 points for incorrect color palette usage, and 5 points for significant layout differences from the original site. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the dynamic effects match JD.com's interaction patterns: 1) Hover effects on navigation menus 2) Smooth transitions between pages 3) Lazy loading of product images 4) Responsive feedback on buttons and interactive elements. Deduct 5 points for each key interaction pattern that differs from JD's implementation, 3 points for sluggish animations, and 5 points for missing hover states and visual feedback. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Online Shopping",
+  "difficulty": "hard"
+}

package/library/web_applications-online_shopping/doce-5-in-1-payment-system-template.json

@@ -0,0 +1,68 @@
+{
+  "index": 710,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure that the code you generate is functional and can be executed. Build a 5-in-1 payment system frontend template in doce language for: 1. Meituan / 2. JD / 3. Pinduoduo / 4. DiDi / 5. Ctrip, each template should have its own dedicated title name.\n\nThis system is based on a semi-finished product that has been further developed and fixed. Many versions in the market have detail issues, but I have fixed many of these details. Mine is the only version on the market with these fixes. If anyone disagrees, they can compare their site with mine - I can definitely identify many problems!\n\n|  Payment Status | Order Cancellation | Order Delivery |\n| Order Expiration | Payment Success | Jump to Official Page |",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Are all 5 payment templates properly implemented with accurate branding?",
+      "description": "Verify if each template (Meituan, JD, Pinduoduo, DiDi, Ctrip) is implemented with correct brand-specific color schemes, logos, and styling. Each template should have its own dedicated title name clearly indicated. Deduct 5 points for each missing platform, 3 points for incorrect brand styling on any platform, and 2 points for missing or incorrect title names. The full score is 20 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Does the code implement all the required payment status features?",
+      "description": "Check whether the code includes proper implementation of all required payment statuses: Payment Status display, Order Cancellation, Order Delivery, Order Expiration, Payment Success, and Jump to Official Page functionality. Each feature should have corresponding UI elements and event handlers. Deduct 3 points for each missing feature, and 2 points for partially implemented features. The full score is 20 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are the payment status transitions properly handled?",
+      "description": "Evaluate how the system handles state transitions between different payment statuses. Check if there's a clear state management system, proper event listeners for status changes, and smooth visual transitions between states. Look for appropriate loading indicators, success/failure animations, and confirmation dialogs. Deduct 5 points if state management is missing, 3 points if transitions are abrupt or unclear, and 3 points if user feedback on state changes is insufficient. The full score is 15 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the code include the claimed fixes for common issues?",
+      "description": "Analyze whether the code includes specific fixes that address common problems in other implementations. Look for comments or implementation details that demonstrate deliberate improvements over standard templates, such as enhanced error handling, better responsiveness, optimization for edge cases, or improved security measures. At least 5 distinct fixes should be identifiable. Deduct 2 points for each missing fix. The full score is 15 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as network errors, payment failures, timeout scenarios, invalid inputs) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Animated payment success/failure indicators 2. Smart order status tracking 3. Customizable payment preferences). 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 payment confirmation dialogs) 2. Function modules unrelated to payment (e.g., a built-in game while waiting) 3. Fancy effects that affect performance (e.g., excessive animations during payment processing). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating payment logic/view/network layers), code organization, and maintainability. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no clear separation between UI components and business logic. 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 that matches brand guidelines 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 during payment flow. Deduct 5 points for each operation without feedback, 3 points for visual after-images during transitions, and 5 points for hard-to-find key payment buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Online Shopping",
+  "difficulty": "hard"
+}

package/library/web_applications-online_shopping/donation-webpage-creation.json

@@ -0,0 +1,68 @@
+{
+  "index": 1790,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate, professional responses. Be sure to provide executable code when possible. Create a donation webpage.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core donation form functionality implemented correctly?",
+      "description": "Review whether the form includes all essential donation fields (amount, name, email, payment method) with proper input validation. Form submission should handle data safely with CSRF protection and show clear confirmation messages. Score 0 if the form is missing, 5 if basic fields exist but lack validation, 10 if fully implemented with secure submission handling.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the payment processing integration complete and secure?",
+      "description": "Check whether the code implements integration with payment gateways (like Stripe/PayPal) following their security best practices. Look for PCI compliance considerations, proper API key management, and server-side verification. Deduct 5 points if integration uses client-side processing only, and 3 points if error handling for failed transactions is missing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are donation transparency features implemented?",
+      "description": "Evaluate if the page shows donation progress (e.g., progress bars, goals reached, recent donors list) and provides transparency about fund usage. Check for real-time updates with proper state management. Deduct 5 points if there's no visual representation of donation progress, and 3 points if data visualization lacks interactivity. Give 10 points if fully implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is donor engagement and community building functionality present?",
+      "description": "Check whether the code includes features for donor acknowledgment (thank-you emails, donor walls, social sharing options) and recurring donation options. Assess if the implementation encourages community participation. Deduct 5 points if automated acknowledgments are missing and 3 points if there's no social integration. 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 incomplete form submissions, payment failures, network interruptions, 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 impact visualization showing what each donation amount achieves 2. Personalized donor stories/journeys 3. Gamification elements like donation challenges or badges). 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 payment processing systems duplicating code) 2. Function modules unrelated to donations (e.g., unrelated content sections) 3. Fancy effects that affect performance (e.g., excessive animations that slow loading). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core donation 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 payment logic/UI components/API services), 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 on donation calls-to-action. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast sliding, and 5 points for hard-to-find donation buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Online Shopping",
+  "difficulty": "medium"
+}