@getollie/cli 0.0.5 → 0.2.0

package/library/web_applications-online_shopping/online-shopping-website-with-recommendations.json

@@ -1,68 +0,0 @@
-{
-  "index": 522,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable when possible. Develop an online shopping website with a homepage that displays recommendations based on users' browsing history. The product details page should include a live streaming feature for product introductions. The shopping cart page needs to support price protection (such as automatic refunds if prices drop). After placing an order, provide an after-sales service portal (for returns, exchanges, repairs, etc.).",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the homepage recommendation system fully implemented?",
-      "description": "Review whether the code accurately implements a user browsing history-based recommendation system, including data collection, processing algorithms, and rendering mechanisms. Check if it includes user behavior tracking, recommendation algorithm implementation (collaborative filtering, content-based, or hybrid approach), and personalization features. Score 0 if recommendation logic is not implemented, 5 if only basic static recommendations exist, and 10 if a complete dynamic recommendation system with user history integration is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the product details page with live streaming feature properly implemented?",
-      "description": "Evaluate the implementation of the live streaming feature on the product details page. Check for WebRTC or similar technology implementation, stream quality controls, chat functionality alongside the stream, and recording/playback capabilities. Deduct 3 points if the streaming lacks real-time interaction features, 3 points if there's no chat functionality, and 4 points if there are no stream quality controls or the implementation is purely simulated without actual streaming capability. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the shopping cart price protection mechanism implemented?",
-      "description": "Check whether the code includes a robust price protection system that monitors price changes and automatically processes refunds. Verify if the implementation includes price history tracking, threshold-based triggers, notification system for users, and automated refund processing. Deduct 3 points if only price monitoring exists without automatic refunds, 4 points if there's no verification mechanism to prevent abuse, and 3 points if there's no user interface to track price protection status. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the after-sales service portal comprehensive and functional?",
-      "description": "Assess if the after-sales portal supports all specified functionalities (returns, exchanges, repairs) with proper workflow management. Check for ticket creation, status tracking, communication tools between users and support staff, and integration with order management. Deduct 3 points for each missing key function (returns process, exchange workflow, repair request system), and 5 points if there's no status tracking system. Award full 10 points only if all features are implemented with intuitive user flow.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid inputs, network failures, server errors, concurrent user actions, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should implement proper error boundaries, form validation, API error handling, and transactional operations for critical functions. Give 10 points for comprehensive error handling throughout the application, 5 points if only critical paths are protected, and 0 points if exceptions are largely unhandled.",
-      "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 product visualization 2. Voice-based shopping assistant 3. Social sharing with integrated reviews 4. AI-powered outfit recommendations). Add 3 points for each practical innovative feature implemented that genuinely improves user experience rather than serving as a gimmick (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Duplicate implementation of similar functions (e.g., multiple cart systems working in parallel) 2. Function modules unrelated to e-commerce (e.g., news feeds not tied to shopping) 3. Performance-heavy effects that impact page load time (e.g., excessive animations or auto-playing videos). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core shopping functions are negatively affected by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review the architecture (separation of concerns, state management), code organization (component reusability, service abstraction), testing strategy, and build process. Deduct 3 points if there's no clear separation between data and presentation layers; deduct 3 points if the code has high duplication rates (>20%); deduct 2 points if responsive design principles aren't followed; deduct 2 points if there's no automated build or deployment process. 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 design principles: 1) Consistent product card design with clear pricing and action buttons 2) Logical information hierarchy with proper whitespace 3) Responsive layouts that adapt to different devices 4) Clear visual distinction between interactive and static elements. Deduct 3 points for inconsistent product displays, 3 points for cluttered layouts, and 4 points for poor mobile adaptability. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the shopping interactions meet user expectations: 1) Add-to-cart confirmation within 200ms 2) Smooth transitions between product listings and details 3) Real-time cart updates without page reloads 4) Intuitive form progression during checkout. Deduct 3 points for each interaction that causes visible lag, 2 points for each abrupt transition between states, and 5 points if the checkout flow has confusing navigation or unexpected steps. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Online Shopping",
-  "difficulty": "hard"
-}

package/library/web_applications-online_shopping/pet-store-login-registration-frontend.json

@@ -1,68 +0,0 @@
-{
-  "index": 1785,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate, professional responses. Be sure to ensure that the code you generate is executable for demonstration. Write me frontend code for a pet store login and registration page.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the login functionality fully implemented?",
-      "description": "Review whether the code implements complete login functionality including form validation (email format checking, password strength validation), error handling for invalid credentials, and session management. Score 0 if login logic is missing, 5 if basic validation exists but lacks comprehensive error handling, and 10 if it includes all validation rules, proper error messages, and secure session handling.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the registration functionality properly implemented?",
-      "description": "Evaluate whether the registration system includes comprehensive form validation (unique username/email checking, password complexity requirements, confirmation password matching), user data persistence strategy, and success/error feedback. Deduct 5 points if backend validation hooks are missing, 3 points if password strength indicators are absent. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is there appropriate form validation and user feedback?",
-      "description": "Check if real-time client-side validation is implemented with clear visual indicators (highlighting invalid fields, showing specific error messages), and whether validation occurs both during typing and on submission. Proper feedback should be provided for all user actions. Deduct 5 points for delayed feedback, 3 points for generic error messages, and 5 points if validation is only performed on submission. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the responsive design properly implemented for multi-device usage?",
-      "description": "Verify whether the code implements responsive design principles that adapt to various screen sizes (desktop, tablet, mobile) using media queries, flexible grid layouts, and appropriately sized touch targets. Deduct 5 points if the layout breaks on mobile screens, 3 points for fixed-width elements, and 5 points if input fields are not optimized for touch interfaces. 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 form submission, browser compatibility issues, input with special characters, 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. Social media login integration 2. Password strength meter with visual feedback 3. Remember me functionality 4. Auto-saving form inputs). 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 validation logic (e.g., multiple validation systems running in parallel) 2. Function modules unrelated to authentication (e.g., full product catalog in login page) 3. Fancy effects that affect performance (e.g., excessive animations or transitions). 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/validation logic/API calls), code reusability, and maintainability. Deduct 5 points if global variables are excessively used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there are no comments or documentation for complex 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 (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) Form submission feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance for tab navigation. Deduct 5 points for each operation without feedback, 3 points for jarring transitions between form states, and 5 points for accessibility issues (like missing ARIA attributes or keyboard navigation). The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Online Shopping",
-  "difficulty": "easy"
-}

package/library/web_applications-online_shopping/product-bundling-feature.json

@@ -1,68 +0,0 @@
-{
-  "index": 482,
-  "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. Build a product bundling feature for an online shopping mall, where when users purchase a certain item, they can see \"Bundle Offers,\" and by clicking on them, related products are automatically added to the shopping cart, and the total amount is updated.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the product bundling feature fully implemented?",
-      "description": "Review whether the code accurately implements the core bundling functionality, including displaying bundle offers, adding bundled products to cart, and updating the total amount. Score 0 if the core functionality is missing, 5 if only basic bundling without proper UI integration is implemented, and 10 if the feature is fully functional with clear visual representation and intuitive user interaction.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the shopping cart system properly implemented?",
-      "description": "Evaluate whether the shopping cart functionality is complete, with features like adding/removing items, quantity adjustment, price calculation, and persistent state management. Check for real-time updates when items are added/removed and proper handling of cart operations. Deduct 3 points if quantity adjustment is missing, 3 points if price calculation has errors, and 4 points if cart state isn't properly maintained across user sessions. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are bundle offers properly displayed and integrated?",
-      "description": "Check how bundle offers are presented to users. Bundle offers should be clearly visible, show cost savings, include relevant product information, and be contextually displayed next to the main product. Deduct 3 points if savings aren't highlighted, 3 points if bundle offers lack visual distinction from regular products, and 4 points if the offers aren't contextually relevant to the main product. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the price calculation logic accurate and transparent?",
-      "description": "Review whether the price calculation system correctly handles individual products, bundles, potential discounts, taxes, and shipping costs. The calculations must be accurate and transparent to users. Deduct 3 points for calculation errors, 4 points if bundle discounts aren't clearly shown, and 3 points if the breakdown of costs isn't visible to users. 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, out-of-stock items, price changes during shopping, 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. Bundle recommendation based on browsing history 2. Dynamic bundle pricing based on selected options 3. Visual comparison of buying individually vs. bundled). 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 update mechanisms) 2. Function modules unrelated to shopping (e.g., unnecessary social sharing features) 3. Fancy effects that affect performance (e.g., excessive animations when adding items to cart). 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/cart/pricing logic), 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 e-commerce 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 e-commerce UX best practices: 1) Cart update feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual cues when bundle items are added to cart. Deduct 5 points for each operation without feedback, 3 points for jarring animations during bundle addition, and 5 points for confusing UI states after user interactions. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Online Shopping",
-  "difficulty": "medium"
-}

package/library/web_applications-online_shopping/product-reviews-dianping-imitation.json

@@ -1,68 +0,0 @@
-{
-  "index": 1565,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Please ensure that the code you generate is executable for demonstration purposes. {__ob__: Observer}\n\nlist:\nArray(5)\n0:\navatar: \"https://lutuyiyi.xyz/uploads/20250309/6973bf0c46fb7b55077020e478ad431c.jpeg\"\ncontent: \"ssssssssss\"\ncreatetime: 1742028195\nid: 5\nimages: \"\"\nnickname: \"Jingcang\"\nstar: 1\nuser_id: 3\n__ob__: Observer {value: {…}, dep: Dep, vmCount: 0}\n\n<view class=\"plr30\">\n    <view class=\"fs34 col10 fwb pb20\">Product Reviews</view>\nComplete the frontend code, imitating Dianping (Chinese Yelp)",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the product review listing functionality properly implemented?",
-      "description": "Evaluate whether the code correctly renders the review list data with proper structuring. Check if avatar, nickname, content, rating (star), and timestamp are displayed properly. Deduct 5 points if data binding is incorrect, 3 points if the list doesn't handle empty states, and 3 points if pagination isn't implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the review image gallery functionality implemented?",
-      "description": "Check if the implementation handles review images correctly, including displaying multiple images, handling empty image arrays, and providing image preview functionality. Score 0 if images are not handled at all, 5 if basic image display is implemented, and 10 if the implementation includes a full image gallery with preview and zoom capabilities.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the timestamp formatting implemented correctly?",
-      "description": "Verify whether the timestamp (createtime in Unix format) is properly converted to a human-readable format. Check if the implementation uses relative time (e.g., '2 hours ago') or absolute time with proper localization. Score 0 if timestamps are displayed as raw Unix timestamps, 5 if basic formatting is applied, and 10 if the implementation handles various time formats with proper localization.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the reactive data binding with Vue Observer correctly utilized?",
-      "description": "Evaluate whether the code properly utilizes Vue's reactivity system (noted by __ob__: Observer in the data). Check if changes to the list are properly reflected in the UI, whether computed properties and watchers are used appropriately. Score 0 if reactive binding is broken, 5 if basic reactivity works but has edge case bugs, and 10 if the implementation fully leverages Vue's reactivity system.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as missing data fields, network errors when fetching reviews, display issues with unusually long content, etc.) and provide friendly error handling or fallbacks. 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. Review sorting/filtering options 2. Interactive ratings with animations 3. User interaction features like helpful/unhelpful buttons). 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 display the same data) 2. Function modules unrelated to reviews (e.g., unnecessary user profile sections) 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 component structure (such as separating review items into components), code reusability, and maintainability. 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 appropriate CSS methodologies (like BEM or scoped CSS) aren't used. 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 mobile app standards: 1) Smooth scrolling without jank 2) Transition animations for expanding reviews or loading images 3) Clear visual feedback for user interactions like tapping stars. Deduct 5 points for each operation without feedback, 3 points for performance issues during scrolling, and 5 points for hard-to-tap interaction targets. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Online Shopping",
-  "difficulty": "easy"
-}

package/library/web_applications-online_shopping/react-retail-receipt-printing.json

@@ -1,68 +0,0 @@
-{
-  "index": 1265,
-  "question": "You are a coding expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you provide is executable and demonstrable. Implement seamless printing of retail receipts in a React frontend.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the receipt printing functionality fully implemented?",
-      "description": "Review whether the code correctly implements receipt generation and printing in React, including handling of line items, price calculations, taxes, and discounts. Score 0 if core printing logic is missing, 5 if basic printing is implemented but lacks formatting options, and 10 if the solution offers complete receipt formatting with configurable templates.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the printing method compatible with different browsers and devices?",
-      "description": "Evaluate whether the implementation uses cross-browser compatible APIs (like window.print()) or specialized libraries (like react-to-print) properly. Check if it handles different browser environments and printer configurations. Deduct 5 points if mobile printing is not supported, 3 points if print previews aren't available. Full score requires graceful fallbacks for environments without direct printing access.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is there appropriate printer communication and error handling?",
-      "description": "Check if the code handles printer connection issues, print job failures, and provides user feedback. Assess whether it implements polling for printer status or alternative delivery methods (email/PDF) when printing fails. Deduct 5 points if no error handling exists, 3 points if feedback is inadequate. Full score requires complete error recovery with actionable user guidance.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the receipt design handle various retail scenarios?",
-      "description": "Evaluate if the implementation supports different receipt types (returns, exchanges, gift receipts), variable-length item lists, and special retail elements (loyalty points, coupons, QR codes). Deduct 3 points for each missing retail-specific feature. Give 10 points if the solution comprehensively addresses diverse retail scenarios.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as printer disconnection, malformed data, network issues) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Digital receipt copies to customer emails 2. Integration with customer loyalty systems 3. Thermal printer-optimized graphics). 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 implementations of similar printing functions 2. Function modules unrelated to receipt printing (e.g., unnecessary analytics) 3. Heavy UI elements that could slow down the printing 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 receipt data model/view/printing logic), unit test coverage for printing functions, and React best practices. Deduct 5 points if global state management is poorly implemented; deduct 5 points if there's excessive prop drilling or component coupling; deduct 5 points if there are no tests for critical printing functions. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the receipt layout meet professional design standards?",
-      "description": "Evaluate whether the receipt design follows retail standards: 1) Clear visual hierarchy with proper spacing 2) Appropriate font choices and sizing (readable on thermal paper) 3) Professional alignment of price columns and totals. Deduct 3 points for each layout inconsistency, 5 points for poor information hierarchy, and 5 points for layouts that would be illegible when printed. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the printing process user-friendly?",
-      "description": "Judge whether the printing workflow is intuitive: 1) Clear print button placement 2) Appropriate user feedback during printing process 3) Print preview capabilities before committing to paper. Deduct 5 points if the user has no indication of printing progress, 3 points for unnecessary confirmation steps, and 5 points for unintuitive placement of printing controls. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Online Shopping",
-  "difficulty": "medium"
-}

package/library/web_applications-online_shopping/second-hand-trading-app-page.json

@@ -1,68 +0,0 @@
-{
-  "index": 1798,
-  "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 display. Create a second-hand trading app page.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core product listing functionality implemented?",
-      "description": "Evaluate whether the code properly implements product listings with image thumbnails, price display, and basic product information. Check if products can be sorted or filtered. Score 0 if the listing functionality is missing, 5 if basic listings are implemented but lack sorting/filtering, and 10 if comprehensive product display with filtering options is included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the product detail view fully implemented?",
-      "description": "Check if the product detail page includes high-resolution images with zoom functionality, complete product descriptions, seller information, and contact options. Verify if there are multiple product images with a gallery/carousel view. Deduct 3 points if image zoom is missing, 3 points if seller details are incomplete, and 3 points if product specifications are insufficient. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the user interaction for buying/selling implemented?",
-      "description": "Review if the code includes functionality for listing a new item (with image upload, form validation), making offers, messaging between buyers and sellers, and a checkout process. Deduct 3 points if image upload is missing, 3 points for incomplete form validation, and 4 points if the messaging system is not implemented. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there a user profile and authentication system?",
-      "description": "Verify if the app includes user registration, login functionality, profile management (viewing/editing user details, managing listings, tracking purchases/sales), and logout features. Deduct 3 points for missing authentication, 3 points for incomplete profile management, and 4 points if there's no transaction history feature. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code handles common abnormal situations (such as form validation errors, image loading failures, network errors, etc.) and provides friendly error prompts or recovery mechanisms. Check for input sanitization to prevent XSS attacks and form validation before submission. Code with strong robustness should effectively handle these edge cases, 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 user experience (e.g., 1. In-app chat with real-time notifications 2. AR view of products in your space 3. Price history graph/trend analysis 4. Condition scoring system with visual indicators). 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 uploaders) 2. Function modules unrelated to second-hand trading (e.g., a built-in game) 3. Fancy effects that affect performance (e.g., unnecessary animations or heavy background 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 UI components/business logic/API services), code reusability, state management implementation, and responsive design principles. Deduct 3 points if global state pollution is found; deduct 3 points if the code duplication rate is too high (over 30%); deduct 4 points if the layout breaks on different screen sizes. 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) 4) Consistent design language across all screens. 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 4) Intuitive gestures for mobile interaction. Deduct 3 points for each operation without feedback, 3 points for visual after-images during fast scrolling, and 4 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/shopping-app-price-aggregator-purchasing-channels.json

@@ -1,68 +0,0 @@
-{
-  "index": 1166,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code in your demonstrations whenever possible. How can one create a shopping app in a short time that aggregates prices and size information from major shopping websites to help users find the best purchasing channels?",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the price aggregation system properly implemented?",
-      "description": "Review whether the code implements efficient web scraping or API integration for major shopping websites. Check for proper handling of different website structures, rate limiting, and data normalization. Score 0 if no aggregation functionality exists, 5 if only basic scraping is implemented without error handling, and 10 if a comprehensive solution with multiple source support is provided.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the size information collection and standardization implemented correctly?",
-      "description": "Evaluate how the code extracts and normalizes size information across different retailers (e.g., converting between US/EU/UK size systems). Check for a comprehensive size mapping database and conversion logic. Deduct 5 points if size standardization is missing, 3 points if the system only handles a limited set of size formats. Full score requires handling of apparel, footwear, and other product category size variations.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the product comparison functionality complete?",
-      "description": "Check whether the app includes features to compare prices, shipping costs, delivery times, and seller ratings across platforms. The system should sort or filter products based on user preferences. Deduct 5 points if only basic price comparison exists without additional factors, 3 points if comparison lacks visual representation. Full implementation should include side-by-side comparison with highlighting of the best options.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there a functional user preference and alert system?",
-      "description": "Assess whether the code implements user preferences storage, price drop alerts, and personalized recommendations. The system should allow users to set target prices and receive notifications. Deduct 5 points if no persistent storage is implemented, 3 points if alerts are missing. Give 10 points if the system includes machine learning for predictive price analysis and smart alerts.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as website structure changes, API failures, network interruptions, etc.) and provide graceful fallbacks or recovery mechanisms. Code with strong robustness should include retry mechanisms, cache systems, and alternate data sources. Give 10 points for comprehensive error handling, 5 points for basic exception handling, and 0 points if critical errors are unhandled.",
-      "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 integration for trying products virtually 2. Price history graphs with predictive analytics 3. Community-based reviews aggregation). 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 price sorting algorithms) 2. Function modules unrelated to shopping (e.g., built-in games) 3. Fancy effects that affect performance (e.g., excessive animations on product cards). 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 acquisition/processing/presentation layers), API abstraction for different shopping platforms, and caching strategy. 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 security measures for user data are inadequate. 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 product grid layouts. 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) Product loading and filtering response ≤ 300ms 2) Smooth infinite scrolling without janky performance 3) Clear visual feedback for price comparison selections. Deduct 5 points for each laggy interaction, 3 points for missing loading states during data fetching, and 5 points for unintuitive navigation between product categories. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Online Shopping",
-  "difficulty": "hard"
-}

package/library/web_applications-online_shopping/shopping-mall-registration-login-page.json

@@ -1,68 +0,0 @@
-{
-  "index": 1468,
-  "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. Develop a shopping mall registration and login page using HTML, CSS, and other technologies, with a login success notification feature.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the registration functionality fully implemented?",
-      "description": "Evaluate whether the registration form includes proper input fields (username, email, password, confirm password), client-side validation for each field, and appropriate submission handling. Score 0 if there's no form validation, 5 if basic validation exists but lacks comprehensive checks (password strength, email format), and 10 if it includes comprehensive validation with helpful error messages and AJAX submission without page refresh.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the login functionality properly developed?",
-      "description": "Check whether the login form includes necessary fields (username/email and password), implements proper validation, handles authentication errors gracefully, and provides options like 'Remember me' and 'Forgot password'. Deduct 3 points if password masking toggle is missing, 5 points if there's no proper error handling for failed login attempts, and 5 points if the form lacks security features like CSRF protection or rate limiting hints.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the login success notification feature implemented effectively?",
-      "description": "Assess whether the notification system works properly upon successful login, displaying a clear message that doesn't disrupt UX. The notification should be dismissible, appropriately positioned, and styled according to UI standards. Score 10 for an elegant toast/modal with animation and personalized welcome message, 5 for a basic static alert, and 0 if the notification is missing or malfunctioning.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the page responsive and mobile-friendly?",
-      "description": "Evaluate whether the registration and login pages adapt properly to different screen sizes (desktop, tablet, mobile). Check for media queries, flexible layouts, and touch-friendly UI elements. Deduct 3 points for each breakpoint where the layout breaks (mobile/tablet/desktop), 5 points if input fields aren't properly sized for mobile devices, and 5 points if touch targets are too small (<44px).",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as network issues during form submission, browser compatibility issues, form input errors) 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. Password strength meter with visual feedback 2. Social media login options 3. Interactive onboarding hints). 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 validation systems) 2. Function modules unrelated to registration/login (e.g., a full product catalog) 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 code organization (separation of HTML, CSS, and JavaScript), naming conventions, code reusability, and performance optimization. Deduct 5 points if styles are inline rather than in separate CSS files; deduct 3 points if JavaScript lacks proper namespacing or modularization; deduct 5 points if there's no consideration for performance (unminified resources, unoptimized images). 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 form layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the form interactions conform to human perception characteristics: 1) Form submission feedback delay ≤ 100ms 2) Input field focus/error animations controlled between 200-400ms 3) Clear visual cues for required fields and validation states. Deduct 5 points for each operation without feedback, 3 points for jarring transitions between form states, and 5 points for unclear or missing form submission status indicators. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Online Shopping",
-  "difficulty": "easy"
-}