@getollie/cli 0.0.1

package/library/web_applications-online_shopping/web-based-express-delivery-tracker.json

@@ -0,0 +1,68 @@
+{
+  "index": 775,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure that the code you generate is executable for demonstration. Can you create a web-based program for tracking express deliveries?",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the express delivery tracking core functionality fully implemented?",
+      "description": "Review whether the code accurately implements tracking number input/validation, delivery status display, and real-time progress updates through HTML/JavaScript. Should include package status parsing (shipped, in-transit, out-for-delivery, delivered), timeline visualization, and estimated delivery time calculation. Score 0 if core tracking logic is not implemented, 5 if only basic status display is available, and 10 if comprehensive tracking with detailed progress indicators is fully included.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the multi-carrier API integration properly implemented?",
+      "description": "Check whether the system integrates with multiple shipping carriers (FedEx, UPS, DHL, USPS, etc.) through their respective APIs, includes proper API key management, rate limiting, and error handling for failed requests. Should support automatic carrier detection from tracking numbers. Deduct 5 points if only one carrier is supported, 3 points if API error handling is missing, and 2 points if rate limiting is not implemented. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is real-time notification and tracking history management designed?",
+      "description": "Evaluate whether the system provides real-time notifications (email/SMS/push) for status changes, implements tracking history storage with timestamps, and offers package comparison features. Should include notification preferences and delivery alerts. Deduct 5 points if no notification system exists, 3 points if tracking history is not persistent, and 2 points if notification preferences are not customizable. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is comprehensive package management and user experience constructed?",
+      "description": "Check whether the code includes complete package lifecycle management, including saved tracking lists, delivery address management, package categorization, and export functionality. Should support bulk tracking operations and delivery scheduling. Deduct 5 points if package persistence is not implemented, 3 points if bulk operations are missing, and 2 points if no export/sharing functionality exists. 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 (invalid tracking numbers, API timeouts, network interruption, malformed carrier responses, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should gracefully handle API failures, provide offline caching, and show meaningful error messages, 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 tracking experience (e.g., 1. Interactive delivery map with real-time location 2. Delivery time prediction using ML 3. Package photo confirmation 4. Delivery attempt scheduling 5. Carbon footprint tracking). 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 tracking functions (e.g., multiple API call mechanisms coexisting) 2. Function modules unrelated to delivery tracking (e.g., built-in shopping features) 3. Fancy effects that affect performance (e.g., excessive animations on tracking updates). Deduct 3 points for each redundancy found, and directly deduct 10 points if core tracking functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (separating API handlers/UI components/data models), proper error handling, configuration management, and code organization. Deduct 5 points if API keys are hardcoded or global state pollution is found; deduct 5 points if code duplication rate is too high (over 30%); deduct 5 points if no proper separation of concerns exists. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the tracking interface follows modern design principles: 1) Clear visual hierarchy for tracking information 2) Consistent color coding for delivery statuses 3) Proper spacing and typography (body font ≥ 14px, line height > 1.5x) 4) Mobile-responsive design. Deduct 3 points for each cluttered tracking display, 5 points for poor status color differentiation, and 5 points for non-responsive layout. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether tracking interactions conform to user expectations: 1) Tracking number input with instant validation feedback 2) Smooth loading states during API calls (≤ 2s perceived wait) 3) Clear visual feedback for tracking updates 4) Intuitive navigation between multiple packages. Deduct 5 points for each operation without loading feedback, 3 points for jarring transitions during status updates, and 5 points for confusing tracking information layout. Full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Online Shopping",
+  "difficulty": "hard"
+}

package/library/web_applications-online_shopping/web-novel-reading-project-vue-pages.json

@@ -0,0 +1,68 @@
+{
+  "index": 1370,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate, professional responses. Be sure to provide executable code when possible. Help me write a web-based novel reading project using Vue and its ecosystem, including home page, bookstore, summer vacation, and my profile pages.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Vue.js project structure correctly implemented?",
+      "description": "Review whether the code properly structures a Vue application with appropriate component hierarchy, Vue Router configuration, and state management (Vuex/Pinia). Score 0 if core Vue setup is missing, 5 if basic structure exists but lacks organization, and 10 if follows Vue best practices with proper separation of concerns.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the home page functionality complete?",
+      "description": "Evaluate whether the home page includes necessary features: featured novels carousel, reading recommendations, categorized novel listings, and search functionality. Deduct 3 points if responsive design is missing, 3 points for missing search, and 2 points for poor content organization. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the bookstore implementation comprehensive?",
+      "description": "Check whether the bookstore page includes novel filtering by genre/popularity/rating, pagination, novel detail cards with cover images, and sorting options. Deduct 3 points if filtering is missing, 2 points if pagination isn't implemented, and 3 points if novel previews lack essential metadata. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are the summer vacation and profile pages properly implemented?",
+      "description": "Assess whether the summer vacation page features seasonal reading lists, special offers, and themed collections; and whether the profile page includes user settings, reading history, bookmarks, and personalization options. Deduct 3 points for each major missing component per page, with particular attention to reading progress tracking. 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 failures, missing data, slow network connections, 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. Night reading mode with customizable typography 2. Audio narration integration 3. Social reading features like annotations or comments). 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 state management approaches mixed) 2. Function modules unrelated to novel reading (e.g., unnecessary gaming elements) 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 API/components/views), component reusability, code maintainability, and build process configuration. Deduct 5 points if global state pollution is found or Vue composition API/options API are inconsistently mixed; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process lacks optimization for production. 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 suitable for extended reading (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional typography system (body font size ≥ 16px, line height over 1.5 times for reading comfort). 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) Page transitions feel natural with content persistence where appropriate 2) Loading states for asynchronous operations 3) Clear navigation and reading position indicators. Deduct 5 points for jarring page transitions, 3 points for missing loading indicators during data fetching, and 5 points for difficult navigation between book sections. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Online Shopping",
+  "difficulty": "medium"
+}

package/library/web_applications-online_shopping/wechat-delivery-platform-sf-express-integration.json

@@ -0,0 +1,68 @@
+{
+  "index": 1533,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable when demonstrated. Write code suitable for the WeChat Developer Tool and store it in separate plain documents for easy maintenance. The code needs to implement a delivery platform that integrates with SF Express City Services. The provided code must be functional and runnable. Also, inform me about what type of legal domain name is required, as I already have a registered legal domain name. Store the code in demo and home files, which will serve as two separate tabs.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the WeChat Mini Program structure and SF Express API integration fully implemented?",
+      "description": "Review whether the code accurately implements WeChat Mini Program framework structure with proper app.js, app.json configuration, and successfully integrates SF Express City Services API including order creation, tracking, and status management. Score 0 if core API integration is missing, 5 if only basic order creation is implemented, and 10 if complete delivery lifecycle management is included with proper error handling and response parsing.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are the demo and home tab functionalities properly separated and implemented?",
+      "description": "Check whether the code provides clear separation between demo and home modules as separate tabs, with demo showcasing platform features and home providing actual delivery services. Evaluate navigation consistency, data sharing between tabs, and independent functionality. Deduct 5 points if tab switching is not smooth, and 3 points if data persistence between tabs is not handled properly. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the delivery platform core business logic comprehensively designed?",
+      "description": "Evaluate whether the platform includes essential delivery features: address management, delivery scheduling, real-time tracking, price calculation, and order history. Check if the code handles different delivery types (same-city, express), time slot selection, and recipient management. Deduct 5 points if order status synchronization is missing, and 5 points if address validation is not implemented. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is WeChat Mini Program compliance and domain configuration properly handled?",
+      "description": "Check whether the code includes proper WeChat Mini Program authorization flows, payment integration preparation, and domain whitelist configuration guidance. Evaluate if HTTPS requirements are addressed and if the code provides clear instructions for domain setup. Deduct 5 points if WeChat compliance requirements are not met, and 3 points if domain configuration guidance is incomplete. Give 10 points if fully compliant with WeChat ecosystem requirements.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as network timeouts, API failures, invalid addresses, payment errors, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should effectively handle WeChat Mini Program lifecycle events and API rate limiting, 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 enhance delivery experience?",
+      "description": "Check whether the code includes value-added features that improve user experience (e.g., 1. Real-time delivery tracking with map visualization 2. Smart address suggestions based on location 3. Delivery time prediction with traffic analysis 4. Multi-language support for international users). 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 address validation logics) 2. Function modules unrelated to delivery services (e.g., built-in games or social features) 3. Excessive animations that affect performance on mobile devices. Deduct 3 points for each redundancy found, and directly deduct 10 points if core delivery functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have proper WeChat Mini Program engineering quality?",
+      "description": "Review modular design following WeChat Mini Program best practices (proper component separation, utils organization, API encapsulation), code reusability, and build optimization. Deduct 5 points if global data pollution is found or WeChat-specific patterns are not used; deduct 5 points if code duplication rate is too high (over 30%); deduct 5 points if WeChat Mini Program performance optimization is not implemented. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface design meet WeChat Mini Program and delivery platform standards?",
+      "description": "Evaluate whether the UI follows WeChat Design Guidelines and delivery platform conventions: 1) Consistent with WeChat native components styling 2) Clear delivery status indicators and progress tracking 3) Mobile-optimized layout with proper touch targets (≥44px) 4) Appropriate use of WeChat color scheme. Deduct 3 points for each non-compliant UI element, 5 points for poor mobile adaptation, and 5 points for inconsistent design patterns. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the mobile interaction smooth and delivery-focused?",
+      "description": "Judge whether interactions are optimized for mobile delivery scenarios: 1) Quick address input with location services 2) One-tap order placement with minimal steps 3) Smooth scrolling in order lists and tracking pages 4) Appropriate loading states for API calls 5) Clear feedback for delivery status changes. Deduct 5 points for each clunky interaction, 3 points for slow API response handling, and 5 points for unclear delivery status communication. Full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Online Shopping",
+  "difficulty": "hard"
+}

package/library/web_applications-online_shopping/wechat-mall-app-rewards-delivery-frontend-backend.json

@@ -0,0 +1,68 @@
+{
+  "index": 1519,
+  "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 whenever possible. Write a WeChat mall application that includes sign-in rewards, lottery rewards, product categorization, in-store redemption, express delivery options, and directly applicable frontend and backend code. Also provide clear installation and practical usage instructions.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the WeChat mall core e-commerce system fully implemented?",
+      "description": "Review whether the code accurately implements product management (CRUD operations), shopping cart functionality, order processing workflow, and payment integration through frontend/backend architecture. Check if product categorization with filtering/search is properly implemented, and whether inventory management is included. Score 0 if core shopping features are missing, 5 if only basic product display is implemented, and 10 if complete e-commerce workflow including payment processing is fully functional.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are the gamification features (sign-in rewards and lottery system) properly integrated?",
+      "description": "Evaluate whether sign-in reward system includes consecutive day tracking, reward escalation logic, and anti-cheating mechanisms. Check if lottery system implements fair probability distribution, prize inventory management, and user participation limits. Deduct 5 points if reward algorithms are exploitable, 3 points if user progress tracking is inaccurate. Verify integration with user points/credits system and reward redemption flow. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the dual fulfillment system (in-store redemption + express delivery) architected correctly?",
+      "description": "Check whether the system properly handles two distinct fulfillment workflows: in-store pickup with QR code generation/scanning and express delivery with shipping integration. Evaluate if inventory is properly allocated between channels, location-based store selection is implemented, and delivery tracking is functional. Deduct 5 points if inventory conflicts between channels exist, 3 points if store location services are missing. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is WeChat ecosystem integration and user authentication properly implemented?",
+      "description": "Assess whether WeChat OAuth integration is correctly implemented for user login, WeChat Pay integration is functional, and WeChat sharing capabilities are included. Check if WeChat Mini Program APIs are properly utilized and user session management follows WeChat guidelines. Deduct 5 points if WeChat Pay integration is missing or non-functional, 3 points if user authentication flow has security vulnerabilities. Verify social sharing and Mini Program compliance. 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 payment failures, network interruptions, inventory conflicts, invalid user inputs, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should effectively handle edge cases like concurrent user actions, session timeouts, and API failures, giving 10 points. If robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the mall experience (e.g., 1. AI-powered product recommendations 2. Social sharing with referral rewards 3. Live streaming integration 4. AR product preview 5. Voice search functionality). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple payment processing logics coexisting) 2. Function modules unrelated to mall operations (e.g., built-in games unrelated to rewards) 3. Fancy effects that affect performance (e.g., excessive animations during checkout). Deduct 3 points for each redundancy found, and directly deduct 10 points if core mall functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (separating business logic/API/database layers), database schema design, API documentation, and deployment configuration. Deduct 5 points if database relationships are poorly designed or lack proper indexing; deduct 5 points if APIs lack proper validation or documentation; deduct 5 points if no environment configuration management exists. 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 mall design follows modern e-commerce UI principles: 1) Product imagery with consistent aspect ratios and quality 2) Clear pricing display with proper currency formatting 3) Intuitive navigation with breadcrumbs 4) Mobile-responsive design optimized for WeChat browser. Deduct 3 points for each poorly designed product card, 5 points for confusing checkout flow, and 5 points for non-mobile-optimized layouts. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the shopping interaction smooth and conversion-optimized?",
+      "description": "Judge whether the shopping experience follows e-commerce best practices: 1) Add-to-cart feedback ≤ 200ms 2) Smooth checkout flow with progress indicators 3) Clear call-to-action buttons with proper sizing for mobile 4) Loading states for all async operations. Deduct 5 points for each step in checkout without clear progress indication, 3 points for slow cart updates, and 5 points for hard-to-tap buttons on mobile. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Online Shopping",
+  "difficulty": "hard"
+}

package/library/web_applications-online_shopping/wechat-menu-ordering-mini-program.json

@@ -0,0 +1,68 @@
+{
+  "index": 1671,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Try to ensure the generated code is executable. I want to create a WeChat mini program. I'm a complete beginner with no knowledge at all. Now I need a piece of code to help me implement these functions: this is a menu mini program where I can freely add or remove dishes. Each dish needs to have an image, name, and description. Since there are many dishes, a search bar is necessary, and dishes need to be categorized, such as meat, hot dishes, cold dishes, etc. Please ensure the interface looks nice, not just plain white. I need a powerful mini program, please design it like restaurant ordering mini programs.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the dish management system fully implemented?",
+      "description": "Review whether the code accurately implements CRUD operations for dishes (Create, Read, Update, Delete). Check if each dish object contains the required properties (image, name, description, category) with proper validation. Score 0 if the core functionality is missing, 5 if only basic operations are implemented without validation, and 10 if full management with data validation is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the dish categorization system properly implemented?",
+      "description": "Evaluate whether the code implements a flexible category system that allows proper organization of dishes (meat, hot dishes, cold dishes, etc.). Check if categories can be dynamically added/edited/removed. Deduct 3 points if categories are hardcoded, deduct 5 points if dishes cannot be reassigned to different categories. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the search functionality effective and optimized?",
+      "description": "Check whether the search implementation allows filtering by dish name, description, and category with proper indexing. Verify if the search performs efficiently with debouncing (≤300ms delay). Deduct 3 points if search doesn't support partial matching, 5 points if it doesn't support multi-field search, and 3 points if there's no visual feedback during search. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the image handling properly implemented for dishes?",
+      "description": "Assess whether the code handles image uploads, storage, compression, and display efficiently. Check if it implements lazy loading, proper caching strategies, and fallback images. Deduct 3 points if image size validation is missing, 3 points if no compression is implemented, and 5 points if there's no placeholder during loading. 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 interruptions, invalid 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 experience (e.g., 1. Dish recommendation system 2. Seasonal menu highlights 3. Nutritional information display 4. Animated dish presentations). 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 search mechanisms coexisting) 2. Function modules unrelated to menu management (e.g., a built-in weather forecast) 3. Fancy effects that affect performance (e.g., unnecessary animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating data/logic/UI layers), component reusability, and adherence to WeChat Mini Program best practices. Deduct 5 points if global state management is missing or poorly implemented; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if custom components aren't properly encapsulated. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional restaurant app standards?",
+      "description": "Evaluate whether the design follows modern restaurant app design principles: 1) Appetizing color scheme suitable for food display 2) Proper visual hierarchy highlighting dishes 3) Professional typography system (dish names should stand out). Deduct 3 points for cluttered layouts, 5 points for non-food-appropriate color schemes, and 5 points for poor image-to-content balance. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and intuitive?",
+      "description": "Judge whether the interactions follow WeChat Mini Program conventions: 1) Natural swipe gestures for browsing dishes 2) Smooth category switching without jarring transitions 3) Intuitive dish detail expansion animations. Deduct 5 points for each unresponsive interaction, 3 points for inconsistent navigation patterns, and 5 points for hard-to-discover key functions. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Online Shopping",
+  "difficulty": "hard"
+}

package/library/web_applications-online_shopping/wechat-mini-program-campus-second-hand-trading.json

@@ -0,0 +1,68 @@
+{
+  "index": 1209,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code whenever possible. Write a WeChat Mini Program using JavaScript for campus second-hand trading.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core functionality for second-hand trading fully implemented?",
+      "description": "Review whether the code accurately implements essential trading features: product listing, search functionality, transaction processing, and user authentication. Score 0 if core features are missing, 5 if only basic listing is implemented, and 10 if the complete transaction flow (listing, browsing, negotiation, payment mechanism) is included.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the WeChat Mini Program structure properly constructed?",
+      "description": "Check if the code follows WeChat Mini Program architecture with app.js, app.json, app.wxss correctly configured, and proper page directory structure. Examine if lifecycle hooks are properly utilized (onLoad, onShow, etc.) and if global configuration is appropriately set. Deduct 5 points if core Mini Program components (like wx:for, wx:if) are missing or misused, and 3 points if page routing is improperly handled. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is user authentication and profile management implemented?",
+      "description": "Evaluate whether the code includes WeChat login integration, user profile creation/editing, and proper session management using wx.login() and getUserProfile(). Check if university verification mechanism exists to ensure campus-only trading. Deduct 5 points if authentication is insecure, and 3 points if profile management is incomplete. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are messaging and notification systems properly implemented?",
+      "description": "Assess whether the code includes real-time messaging between buyers and sellers, notification system for price updates or new messages, and transaction status updates. Check if message persistence is implemented. Deduct 5 points if real-time messaging is missing, and 3 points if notifications aren't implemented. 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 interruption, invalid input, image upload failures, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should implement error boundaries and precise error messages, 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 preview of products 2. Item condition verification system 3. Campus delivery integration 4. Price trend analytics). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple product listing methods) 2. Function modules unrelated to campus trading (e.g., a built-in calculator) 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 business logic/view/API layers), component reusability, and consistent coding standards. Deduct 5 points if global state management is chaotic; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if no error logging mechanism exists. 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 WeChat Mini Program design principles: 1) Consistent with WeChat UI style 2) Proper layout spacing (element spacing follows WeChat's guidelines) 3) Professional typography (following WeChat's font hierarchy). Deduct 3 points for each UI component that breaks WeChat's design language, 5 points for cluttered layouts, and 5 points for poor information hierarchy. 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 WeChat Mini Program standards: 1) Page transitions are smooth and consistent 2) Loading states are properly indicated 3) Form interactions provide immediate feedback. Deduct 5 points for each operation without feedback, 3 points for jerky animations, and 5 points for confusing navigation patterns. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Online Shopping",
+  "difficulty": "medium"
+}

package/library/web_applications-online_shopping/wechat-mini-program-family-water-card.json

@@ -0,0 +1,68 @@
+{
+  "index": 1576,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code when possible. How to design a WeChat Mini Program: Design a \"Family Water Card\" feature that supports monthly top-ups and automatic delivery reminders.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the WeChat Mini Program structure properly implemented?",
+      "description": "Check whether the code includes the necessary Mini Program files (app.js, app.json, app.wxss, pages structure) and follows the official WeChat development standards. Verify the proper implementation of the application lifecycle functions. Score 0 if the basic structure is incorrect, 5 if the structure is present but incomplete, and 10 if it follows all WeChat Mini Program best practices.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the monthly top-up feature fully implemented?",
+      "description": "Evaluate if the code implements a complete top-up system with multiple payment options, transaction records, and receipt generation. Check for WeChat Payment API integration, balance calculation, and proper error handling during payment processes. Deduct 5 points if payment verification is missing, 3 points if receipt generation isn't implemented, and 2 points if transaction records aren't stored properly. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the water delivery reminder system properly designed?",
+      "description": "Review whether the code includes a comprehensive reminder system with customizable frequency settings, push notifications using the wx.requestSubscribeMessage API, and intelligent prediction of next delivery date based on usage patterns. Deduct 5 points if notifications aren't implemented correctly, 3 points if reminder scheduling is inflexible, and 2 points if there's no usage pattern analysis. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the family sharing functionality implemented?",
+      "description": "Examine whether the code allows for family member management, role-based permissions (admin vs. regular users), and shared access to the water card balance and history. Check if the solution handles multi-user synchronization and conflict resolution. Deduct 5 points if member management is missing, 3 points if permission controls aren't implemented, and 2 points if data synchronization issues aren't addressed. 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, payment errors, permission denials, 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. Water usage statistics and visualization 2. Integration with home IoT water purifiers 3. Environmental impact calculation based on water consumption). 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 notification systems) 2. Function modules unrelated to water card management (e.g., a built-in game) 3. Fancy effects that affect performance (e.g., unnecessary 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 business logic/UI/network layers), component reusability, and consistent coding style. 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 naming conventions are inconsistent. 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 WeChat design guidelines: 1) Consistent with WeChat's visual language 2) Proper layout spacing and component sizing 3) Professional typography system. Deduct 3 points for each UI element that doesn't follow WeChat standards, 5 points for inconsistent visual hierarchy, and 5 points for poor information architecture. 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 200-400ms 3) Clear visual feedback for all user actions. Deduct 5 points for each operation without feedback, 3 points for jerky animations during transitions, and 5 points for confusing navigation patterns. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Online Shopping",
+  "difficulty": "medium"
+}

package/library/web_applications-online_shopping/wechat-mini-program-fast-food-ordering-system.json

@@ -0,0 +1,68 @@
+{
+  "index": 1641,
+  "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. Help me write a fast food ordering system based on WeChat Mini Program, similar to the style of \"Little Vegetable Garden.\" Please include the source code.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core ordering flow implemented completely?",
+      "description": "Review whether the code implements a complete ordering flow (browsing menu, adding to cart, checkout, payment). Check if it includes necessary features like item customization (e.g., spice level, size options), quantity adjustment, and order summary. Score 0 if the core ordering flow is missing, 5 if only basic item selection is implemented, and 10 if the complete flow with customization options is included.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the Mini Program structure properly implemented?",
+      "description": "Evaluate whether the code follows WeChat Mini Program architecture with proper page structure, app.json configuration, and utilizes Mini Program components (e.g., swiper, picker, navigator). Check for proper use of the lifecycle methods and page routing. Deduct 3 points if global configuration is incorrect, 4 points if native components are not used appropriately, and 5 points if the project structure doesn't follow Mini Program conventions. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the user management and authentication system implemented?",
+      "description": "Check if the code includes WeChat authentication integration, user profile management, and authorization handling using wx.login() and open APIs. Verify proper storage of user session data and token management. Deduct 5 points if there's no login mechanism, 3 points if user authorization lacks error handling, and 3 points if user data persistence is missing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the payment integration properly implemented for the Mini Program?",
+      "description": "Assess whether the code includes WeChat Payment API integration with proper order creation, signed package preparation, and payment result handling. Check for payment callback processing and order status updates. Deduct 5 points if the payment API integration is missing, 3 points if security measures for payment are inadequate, and 3 points if order synchronization after payment 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 network interruption, payment failures, API timeouts, 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. Food recommendation system based on order history 2. Real-time order preparation status 3. Loyalty points system with mini-games). 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 manipulation methods) 2. Function modules unrelated to food ordering (e.g., excessive social features) 3. Fancy effects that affect performance (e.g., complex animations that slow down the ordering 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 data/UI/logic layers), component reusability, and proper use of MVVM pattern for Mini Program. Deduct 5 points if global state management is chaotic; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if custom components aren't properly encapsulated. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards similar to 'Little Vegetable Garden'?",
+      "description": "Evaluate whether the UI design follows the fresh, simple style of 'Little Vegetable Garden' with: 1) A cohesive green and white color scheme with accent colors 2) Clean card-based layout with appropriate whitespace 3) Consistent typography and iconography. Deduct 3 points for inconsistent visual elements, 5 points for cluttered layouts, and 5 points for designs that don't match the referenced style. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and optimized for mobile touch?",
+      "description": "Judge whether the interactions are optimized for touch controls: 1) Touch targets are at least 44×44px 2) Swipe gestures for common actions like removing cart items 3) Proper feedback for all interactions within 100ms. Deduct 5 points for small, hard-to-tap elements; 3 points for missing visual feedback on interactions; and 5 points for jerky animations or transitions. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Online Shopping",
+  "difficulty": "medium"
+}