@getollie/cli 0.0.5 → 0.2.0

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

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

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

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

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

package/library/web_applications-online_shopping/dynamic-clothing-purchases-webpage.json

@@ -1,68 +0,0 @@
-{
-  "index": 1564,
-  "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 for demonstration. Write a webpage for dynamic clothing purchases.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the dynamic clothing display system fully implemented?",
-      "description": "Review whether the code implements a responsive clothing display system that shows products dynamically, with proper filtering, sorting, and search capabilities. Score 0 if the core display logic is missing, 5 if only basic display is implemented, and 10 if the system includes advanced features like dynamic filtering, sorting options, and search functionality with autocomplete.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the product interaction and customization functionality complete?",
-      "description": "Evaluate whether users can interact with clothing items (like zoom, rotate, color selection, size selection) and if the system provides visual feedback. Deduct 5 points if interactive elements are missing, 3 points if color/size selection doesn't visually update the product, and 2 points if zoom/detailed view options are absent. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the shopping cart system properly implemented?",
-      "description": "Check whether the shopping cart functionality includes adding/removing items, quantity adjustments, persistent storage (localStorage/sessionStorage), and dynamic cart summary updates. Deduct 3 points if cart persistence is missing, 3 points if quantity modification doesn't update totals in real-time, and 4 points if there's no cart summary display. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the checkout process well-designed and user-friendly?",
-      "description": "Assess if the checkout flow includes form validation, multiple payment options, shipping address management, and order summary before confirmation. Deduct 3 points for missing form validation, 3 points for inadequate payment options, 2 points for no shipping calculation, and 2 points for absence of order confirmation. 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 failures during checkout, invalid user inputs, image loading failures, 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 shopping experience (e.g., 1. Virtual fitting room 2. Outfit combination suggestions 3. Social sharing integration 4. Size recommendation based on user measurements). 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 storage mechanisms) 2. Function modules unrelated to clothing purchase (e.g., unnecessary games or distracting elements) 3. Fancy effects that affect performance (e.g., excessive animations that slow down browsing). 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 product display/cart logic/checkout processes), responsiveness for different devices, code maintainability, and 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 the website doesn't adapt to mobile devices. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional e-commerce design standards?",
-      "description": "Evaluate whether the design follows e-commerce best practices: 1) Clear product presentation with high-quality images 2) Consistent branding and color scheme (no more than 3 primary colors) 3) Professional typography hierarchy (product names, prices, descriptions properly distinguished) 4) Intuitive navigation and categorization. Deduct 3 points for cluttered product displays, 3 points for inconsistent styling, 2 points for poor typography, and 2 points for confusing navigation. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and responsive?",
-      "description": "Judge whether the shopping experience feels fluid and responsive: 1) Product filtering/sorting updates in under 500ms 2) Add-to-cart feedback within 100ms 3) Smooth transitions between pages or states 4) Clear loading indicators for async operations. Deduct 3 points for sluggish filtering/sorting, 3 points for delayed cart updates, 2 points for jarring page transitions, and 2 points for missing loading states during API calls. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Online Shopping",
-  "difficulty": "medium"
-}

package/library/web_applications-online_shopping/e-commerce-flash-sale-interface-frontend.json

@@ -1,68 +0,0 @@
-{
-  "index": 702,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code if possible. Please provide frontend code for a flash sale interface of an e-commerce system.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the flash sale countdown timer functionality fully implemented?",
-      "description": "Review whether the code accurately implements a countdown timer showing hours, minutes, and seconds until the flash sale starts/ends. Check if it handles time zones correctly, updates in real-time (not just on page load), and has visual cues when time is running low. Score 0 if no timer exists, 5 if basic functionality exists but has timezone issues, and 10 if fully implemented with edge cases handled.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the product inventory management system properly implemented?",
-      "description": "Evaluate whether the code includes real-time inventory tracking, stock reservation during checkout, and clear visual indicators when products are running low or sold out. Check for race condition handling and inventory locks. Deduct 5 points if no real-time stock updates are implemented, and 3 points if there's no visual feedback for low stock. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the high-concurrency user experience optimized?",
-      "description": "Check whether the interface implements queuing systems, throttling mechanisms, or other techniques to handle high traffic. Look for loading states, disabled buttons during processing, and clear feedback on user position in queue. Deduct 5 points if the UI freezes during operations, 5 points if no concurrent access handling exists. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the mobile responsiveness and cross-device compatibility implemented?",
-      "description": "Evaluate whether the flash sale interface adapts properly to different screen sizes using responsive design techniques. Check if touch interactions are properly handled for mobile users, and if critical elements (add to cart, buy now) are easily accessible on small screens. Deduct 5 points for each major breakpoint (mobile, tablet, desktop) that doesn't display properly. 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 delays, failed API calls, partial data loading, etc.) and provide friendly error prompts or recovery mechanisms. Look for error boundaries, fallback UI components, and proper loading states. 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. Live purchase counter showing real-time popularity 2. Social sharing with dynamic discount incentives 3. Interactive product image zoom/360° view). 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 add-to-cart mechanisms) 2. Function modules unrelated to flash sales (e.g., excessive product comparison tools) 3. Fancy effects that affect performance (e.g., heavy 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 component modularization (such as separating UI components, state management, and API services), code reusability, and performance optimizations. Deduct 5 points if global state management is chaotic or prop drilling is excessive; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if no performance optimizations (lazy loading, memoization, etc.) are implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional e-commerce design standards?",
-      "description": "Evaluate whether the overall design follows e-commerce best practices: 1) Clear product highlight and discount visualization (original vs. sale price) 2) Proper hierarchy with primary CTAs standing out 3) Professional typography system that emphasizes key information (price, discount, time remaining). Deduct 3 points for each confusing product card layout, 5 points for unclear price/discount display, and 5 points for hard-to-find purchase buttons. 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 user expectations in e-commerce: 1) Add-to-cart feedback delay ≤ 100ms 2) Smooth transitions when products sell out or prices update 3) Clear loading states during operations. Deduct 5 points for each operation without feedback, 3 points for jarring UI updates when inventory changes, and 5 points for confusing checkout flow. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Online Shopping",
-  "difficulty": "medium"
-}

package/library/web_applications-online_shopping/e-commerce-mini-program-homepage-info-profile.json

@@ -1,68 +0,0 @@
-{
-  "index": 1515,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the code you generate is executable for demonstration. I want to develop a complete e-commerce mini program consisting of a home page, information page, and personal profile page. Please help me create a plan and write out the complete structure.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the complete e-commerce mini program structure implemented?",
-      "description": "Check if the code provides a comprehensive structure with all three required pages (home page, information page, personal profile page) and proper navigation between them. Score 0 if any of the three main pages are missing, 5 if basic pages are implemented but lack proper navigation, and 10 if all pages are fully structured with seamless navigation implementation.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the home page functionality fully implemented?",
-      "description": "Evaluate if the home page includes essential e-commerce features: product listing with thumbnails, search functionality, category filtering, banners/promotions, and product sorting options. Deduct 2 points for each missing core feature. The home page should load efficiently with lazy loading or pagination for product listings. Score 10 points for complete implementation with optimized loading.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are the product information page features properly implemented?",
-      "description": "Check if the product information page includes detailed product descriptions, multiple images, price information, stock status, variant selection (size/color), related products, reviews system, and 'add to cart' functionality. Deduct 1 point for each missing component. Score 10 points for a comprehensive implementation that includes all these elements with smooth interaction.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the personal profile page complete with user management features?",
-      "description": "Assess whether the personal profile page includes user authentication, order history, saved items/wishlists, shipping addresses, payment methods, profile editing, and notifications settings. Deduct 2 points for each missing key function. Verify if secure authentication is properly implemented. Score 10 points for a fully functional profile system with secure user data handling.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as network errors, empty data states, form validation, image loading failures, authentication expiration) 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 product visualization 2. Voice search functionality 3. Personalized recommendation engine 4. Social sharing 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 user authentication systems coexisting) 2. Function modules unrelated to e-commerce (e.g., a built-in game) 3. Fancy effects that affect performance (e.g., excessive animations slowing down product browsing). 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/state management/API services), reusable components for product cards and forms, proper state management, and build process optimization. Deduct 5 points if global state pollution is found; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if no performance optimization is implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the design follows e-commerce best practices: 1) Consistent branding and color scheme (primary, secondary, and accent colors) 2) Clear product presentation with appropriate white space 3) Professional typography hierarchy (headings vs body text) 4) Mobile-responsive design with touch-friendly elements. Deduct 3 points for inconsistent UI elements, 5 points for poor readability, and 5 points for non-responsive designs. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the interactions follow e-commerce UX principles: 1) Quick product loading times (≤2 seconds) 2) Smooth transitions between pages 3) Clear feedback for add-to-cart actions (≤100ms) 4) Intuitive navigation patterns. Deduct 5 points for slow-loading product pages, 3 points for jarring page transitions, and 5 points for confusing checkout processes. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Online Shopping",
-  "difficulty": "medium"
-}

package/library/web_applications-online_shopping/e-commerce-product-detail-page.json

@@ -1,68 +0,0 @@
-{
-  "index": 1007,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure that the generated code is executable for demonstration. E-commerce product detail page HTML5 dynamic template.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the product display system fully implemented?",
-      "description": "Review whether the code accurately implements product image gallery with zoom functionality, product information display, variant selection (size/color), and price calculation through HTML/JavaScript. Check if it includes image lazy loading, thumbnail navigation, and 360-degree view support. Score 0 if core product display is missing, 5 if only basic image display is implemented, and 10 if all e-commerce product features are fully included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the shopping cart and purchase flow implemented?",
-      "description": "Check whether the implementation includes add-to-cart functionality, quantity adjustment, cart persistence (localStorage/sessionStorage), and checkout process simulation. Verify if inventory validation, price calculation with discounts, and shipping cost calculation are handled. Deduct 5 points if cart state management is missing, and 3 points if quantity validation is not implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the dynamic content loading and template system designed?",
-      "description": "Evaluate whether the template system supports dynamic product data injection, variant switching without page reload, and asynchronous content loading. Check if it includes template inheritance, component reusability, and data binding mechanisms. Deduct 5 points if template rendering causes layout shifts, and 3 points if dynamic updates are not smooth. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the complete e-commerce interaction lifecycle constructed?",
-      "description": "Check whether the code includes complete user interaction flows: product browsing, variant selection, reviews display, related products recommendation, and wishlist functionality. Verify if breadcrumb navigation, product comparison, and social sharing features are implemented. Deduct 5 points if user session management is missing, and 3 points if accessibility features are not included. Give 10 points if fully implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as missing product images, invalid variant selections, network failures, malformed data, etc.) and provide friendly error prompts or fallback mechanisms. Code with strong robustness should gracefully handle API failures, image loading errors, and invalid user inputs, 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 shopping experience (e.g., 1. AR/VR product preview 2. Real-time stock countdown 3. Interactive size guide 4. Voice search capability 5. Smart product recommendations). 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 e-commerce (e.g., built-in games or unnecessary animations) 3. Excessive decorative effects that impact performance (e.g., heavy particle effects or auto-playing videos). 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 product data/UI components/business logic), code organization with proper file structure, and reusable component architecture. Deduct 5 points if global state pollution is found or component coupling is too tight; deduct 5 points if code duplication rate is too high (over 30%); deduct 5 points if no build optimization or minification is considered. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional e-commerce design standards?",
-      "description": "Evaluate whether the overall design follows modern e-commerce principles: 1) Professional color scheme with proper brand consistency 2) Clear visual hierarchy with proper spacing (8px grid system) 3) Readable typography (body text ≥ 14px, proper contrast ratios) 4) Consistent button styles and hover states. Deduct 3 points for each cluttered section, 5 points for poor color choices that affect readability, and 5 points for inconsistent design patterns. 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 e-commerce user expectations: 1) Image transitions and zoom effects ≤ 300ms 2) Cart updates with immediate visual feedback 3) Smooth variant switching without layout jumps 4) Loading states for all async operations 5) Touch-friendly interactions for mobile. Deduct 5 points for each interaction without proper feedback, 3 points for janky animations or layout shifts, and 5 points for poor mobile responsiveness. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Online Shopping",
-  "difficulty": "hard"
-}