@getollie/cli 0.0.1

package/library/web_applications-online_shopping/wechat-selling-clothes-mini-program.json

@@ -0,0 +1,68 @@
+{
+  "index": 1025,
+  "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. Help me write a WeChat Mini Program for selling clothes. Requirement: Make it similar to the popular milk tea ordering Mini Program \"Bawang Chaji\".",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the clothing e-commerce core functionality well implemented?",
+      "description": "Review whether the code accurately implements essential e-commerce features: product listing, category filtering, item detail pages, shopping cart, and checkout process. Score 0 if core shopping flow is absent, 5 if basic functionality exists but lacks refinement, and 10 if the implementation is complete with smooth transitions between screens.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Does the Mini Program implement a proper user authentication system?",
+      "description": "Check whether the code utilizes WeChat's authentication APIs correctly, includes user profile management, and securely handles user session. Deduct 5 points if login functionality is missing, 3 points if user profile management is incomplete, and 2 points if session handling is insecure. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the product customization functionality similar to 'Bawang Chaji' implemented?",
+      "description": "Evaluate whether the code implements clothing customization options (size selection, color variants, style options) similar to how 'Bawang Chaji' allows beverage customization. Deduct 5 points if customization is absent, 3 points if options cannot be combined, and 2 points if user selections aren't visually reflected. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the Mini Program implement proper state management and data synchronization?",
+      "description": "Check whether the code uses appropriate state management solutions (like Mobx, Redux patterns in WXML context), maintains consistency across pages, and properly synchronizes with backend services. Deduct 5 points for global state issues, 3 points for inconsistent data across pages, and 5 points if offline capability is missing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code handles common edge cases (network failures, payment failures, item out-of-stock situations) and provides user-friendly error messages. Code with strong error handling should recover gracefully from errors, giving 10 points. If error handling is average, give 5 points, and if exceptions are unhandled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the shopping experience (e.g., 1. AR virtual try-on 2. Social sharing with discount incentives 3. Personalized outfit recommendations). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Duplicate functionality across different pages 2. Features unrelated to clothing e-commerce (e.g., built-in games not tied to purchasing) 3. Excessive animations that affect performance on lower-end devices. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core shopping experience is compromised by bloat.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (separation of UI components, business logic, and API services), component reusability, and WeChat Mini Program best practices. Deduct 5 points if global app instance is overused; deduct 5 points for excessive duplicate WXML/WXSS; deduct 5 points if file structure is chaotic or custom components are not properly utilized. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the design follows WeChat Mini Program design principles: 1) Consistent with WeChat's visual language 2) Proper use of white space (following 8px grid system) 3) Typography hierarchy (at least 3 distinct text styles for different content types). Deduct 3 points for each inconsistent UI element, 5 points for poor readability due to contrast issues, and 5 points for layouts that don't adapt to different device sizes. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether interactions follow WeChat Mini Program conventions: 1) Page transitions complete within 300ms 2) Skeleton screens during data loading 3) Appropriate haptic feedback for important actions. Deduct 5 points for each interaction without loading state, 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": "hard"
+}

package/library/web_applications-online_shopping/wholesale-retail-condiments-seasonings-product-showcase.json

@@ -0,0 +1,68 @@
+{
+  "index": 1320,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you provide is executable for demonstration. Create a small program for showcasing products for a store that sells wholesale and retail condiments and seasonings.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the product showcase system fully implemented?",
+      "description": "Review whether the code accurately implements a product catalog system for condiments and seasonings, including product listings, categories, search functionality, and detailed product views. Score 0 if the core display logic is not implemented, 5 if only basic product listing is implemented, and 10 if the complete showcase with filtering and sorting options is fully included.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the wholesale/retail price differentiation properly implemented?",
+      "description": "Check whether the code handles both wholesale and retail pricing models, including quantity-based discounts, minimum order quantities for wholesale, price comparison features, and unit price calculations. Deduct 5 points if wholesale pricing logic is missing, and 3 points if quantity discounts are not handled. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the product data management system properly designed?",
+      "description": "Evaluate whether the product data structure is well-designed with proper attributes for condiments (such as ingredients, allergens, volume/weight, origin, expiration information, etc.). Check if data can be loaded from external sources and if the system supports CRUD operations. Deduct 5 points if the data model is overly simplistic, and 3 points if data validation is missing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the shopping cart or order management functionality implemented?",
+      "description": "Check whether the code includes functionality for adding products to cart, managing quantities, calculating totals (with appropriate tax/shipping considerations for wholesale vs retail), and facilitating the checkout process. Deduct 5 points if cart persistence is not implemented, and 3 points if the quantity management for bulk orders is inadequate. Give 10 points if fully implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid input, out-of-stock items, pricing calculation edge cases, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Interactive product visualization 2. Flavor profile comparison tools 3. Recipe suggestions based on selected condiments). 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 calculation methods) 2. Function modules unrelated to condiment/seasoning sales (e.g., an unrelated news feed) 3. Fancy effects that affect performance (e.g., excessive animations on product hover). 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 data/view/cart logic layers), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (appropriate for a food/culinary business with no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance for product selection and cart operations. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast scrolling through product lists, and 5 points for hard-to-find key function buttons like 'add to cart' or 'checkout'. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Online Shopping",
+  "difficulty": "medium"
+}

package/library/web_applications-other/create-capsule-page-with-editor.json

@@ -0,0 +1,68 @@
+{
+  "index": 303,
+  "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. Now, start creating a capsule page according to your design concept:\n\nUse a step-by-step design, for example:\nInput title and description.\nUpload images or videos.\nSet opening time (supporting date and time picker).\nAdd tags (optional).\n\nRich text editor:\nSupport text formatting (bold, italic, underline, etc.).\nSupport inserting images, videos, emoticons, etc.\n\nAnimation effects:\nAdd a \"capsule sealed\" animation effect (such as capsule closing, time-lapse animation) after the user completes creation.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the step-by-step capsule creation design fully implemented?",
+      "description": "Review whether the code correctly implements all required steps (title/description input, image/video upload, date/time picker for opening time, optional tags). Score 0 if the core steps are missing, 5 if basic functionality is implemented but lacks proper field validation, 10 if all steps are fully implemented with appropriate user guidance and input validation.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the rich text editor implemented with all required features?",
+      "description": "Evaluate if the editor includes text formatting (bold, italic, underline), media insertion capabilities (images, videos), and emoticon support. Check for proper toolbar implementation, keyboard shortcuts, and formatting preservation. Score 3 for basic text formatting only, 7 for formatting plus media support, and 10 for complete implementation including emoticons and proper state management.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the 'capsule sealed' animation effect properly implemented?",
+      "description": "Assess whether the animation effect is triggered after user completes creation, provides visual feedback that enhances the capsule creation experience, and uses modern animation techniques (CSS animations, SVG animations, or JavaScript libraries like GSAP). Score 0 if animation is missing, 5 if basic animation exists but lacks polish, and 10 if animation is smooth, thematically appropriate, and enhances the user experience.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the media handling implementation robust and user-friendly?",
+      "description": "Verify if the code handles image/video uploads properly, including file type validation, size limits, preview functionality, progress indicators, and error handling. Check if the implementation supports multiple file formats and provides options for cropping/editing. Score 3 for basic upload, 7 for upload with previews and validation, 10 for complete media management with editing capabilities.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid inputs, network issues during upload, browser compatibility 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. Preview of how the capsule will appear when opened 2. Social sharing integration 3. Customizable capsule themes/templates). 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 insert the same type of media) 2. Function modules unrelated to the capsule creation (e.g., unrelated settings or features) 3. Fancy effects that affect performance (e.g., excessive animations that slow down the interface). 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, and state management), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance. Deduct 5 points for each operation without feedback, 3 points for visual after-images during step transitions, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Other",
+  "difficulty": "easy"
+}

package/library/web_applications-other/mini-program-self-service-car-washing.json

@@ -0,0 +1,68 @@
+{
+  "index": 1168,
+  "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 and demonstrable. How do I develop a mini-program for self-service car washing? Please provide detailed information, including the complete project deployment process and steps on the server. The backend uses PHP language with Hyperf framework, and the frontend uses Vue3 framework.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the car washing self-service mini-program frontend implementation complete?",
+      "description": "Review whether the Vue3 frontend code includes essential modules: user registration/login, car wash service selection, payment integration, booking/scheduling system, and service status tracking. Score 0 if core modules are missing, 5 if basic functionality exists but with limited features, and 10 if all essential user flows are fully implemented with proper state management (Pinia/Vuex).",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the PHP Hyperf backend architecture properly implemented?",
+      "description": "Evaluate if the backend code properly implements Hyperf's coroutine-based architecture with appropriate middleware, controllers, services, and models. Check for RESTful API design patterns, proper dependency injection, and use of Hyperf's built-in features (async tasks, crontab, etc.). Deduct 5 points if missing proper authentication middleware, and 3 points if database models lack validation. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the payment integration and transaction management system complete?",
+      "description": "Check whether the code implements secure payment gateway integration, transaction record keeping, refund capabilities, and receipt generation. The system should include payment state machine handling various scenarios (success, failure, timeout, partial payment). Deduct 5 points if security measures (like idempotency keys) are missing, 3 points if webhook handlers for payment callbacks are incomplete. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the hardware control system properly integrated with the software stack?",
+      "description": "Assess whether the application includes proper interfaces to control car washing hardware (water pumps, sensors, dispensers) through API calls, with appropriate error handling and status reporting. Check for device management dashboards and real-time monitoring features. Deduct 5 points if hardware status polling is missing, 3 points if offline operation mode is not 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 payment failures, network interruption, hardware malfunctions, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should include comprehensive try-catch blocks, input validation, and graceful degradation. Give 10 points if robust error handling exists throughout, 5 points if average, and 0 points if exceptions aren't handled.",
+      "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. AI-based car recognition to personalize services 2. Gamification elements to reward frequent users 3. Real-time consumption tracking with water/energy-saving tips). 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 handling systems) 2. Function modules unrelated to car washing (e.g., news feed) 3. Fancy effects that affect performance (e.g., heavy animations that slow down critical functions). 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 (separation of concerns between frontend/backend, proper component structure in Vue), comprehensive test coverage (unit tests for both PHP and Vue components), and deployment automation (CI/CD pipeline, containerization with Docker). 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 deployment process is manual. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the UI follows modern mobile design principles: 1) Consistent color scheme aligned with brand identity 2) Proper spacing and touch targets (minimum 44×44px for interactive elements) 3) Professional typography system with proper hierarchy. Deduct 3 points for each navigation issue that affects usability, 5 points for non-responsive design elements, 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 app interactions meet mobile user expectations: 1) Immediate feedback for user actions 2) Loading states for asynchronous operations 3) Smooth transitions between app states (500ms or less). Deduct 5 points for unresponsive UI during backend operations, 3 points for jarring transitions, and 5 points if critical functions (like payment confirmation) lack clear visual feedback. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Other",
+  "difficulty": "hard"
+}

package/library/web_applications-other/real-estate-vr-showcase.json

@@ -0,0 +1,68 @@
+{
+  "index": 533,
+  "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. Create a real estate showcase website with virtual reality (VR) functionality. The homepage should feature a full-screen video background with a transparent navigation bar at the top. The property listing page should use a card layout, with each card displaying brief information and a 360° panorama preview icon when hovered over. Clicking on a property card takes users to a detail page, where the top section displays a property photo carousel with thumbnail navigation and gesture-based swiping. Add a 3D floor plan viewer that allows users to switch between different floors and room views. Implement a VR house tour feature where users can virtually navigate through rooms using VR glasses or their phone's gyroscope. Add a property comparison tool that can simultaneously compare multiple properties' features and prices.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the homepage with full-screen video background and transparent navigation properly implemented?",
+      "description": "Review whether the code correctly implements a full-screen video background with autoplay, appropriate compression for performance, and fallback content. The navigation bar should have proper transparency effects with readable text that remains visible against varying video backgrounds. Score 0 if none implemented, 5 if basic implementation with flaws (e.g., poor mobile responsiveness, performance issues with video), 10 if flawlessly implemented with responsive design and performance optimization.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the property listing page with card layout and 360° preview functionality properly implemented?",
+      "description": "Check if the property cards display essential information (price, location, bedrooms, bathrooms) in an organized layout. Each card should show a 360° panorama icon on hover, with proper transitions. Score 0 if card layout is missing, 5 if cards exist but lack hover effects or have poor responsive design, and 10 if cards are fully functional with smooth hover transitions and optimized loading of preview thumbnails.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the property detail page with photo carousel and thumbnail navigation effectively implemented?",
+      "description": "Evaluate the implementation of the photo carousel with gestures for swiping on mobile and tablet devices. Check if thumbnail navigation properly syncs with the main carousel view. Score 0 if carousel is absent, 5 if basic carousel exists but lacks gesture support or thumbnail navigation, and 10 if fully implemented with smooth transitions, preloading of adjacent images, and proper touch/mouse event handling.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are the 3D floor plan viewer and VR house tour features properly implemented?",
+      "description": "Assess whether the 3D floor plan viewer can switch between different floors and room views as specified. The VR tour should work with both VR glasses and phone gyroscopes. Score 0 if features are missing, 5 if implemented but with limited functionality (e.g., only works on certain devices, poor performance), and 10 if fully implemented with optimized 3D rendering, appropriate textures, and smooth navigation controls.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as missing property data, slow network connections, browser compatibility issues, device orientation changes) 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. AI-powered property recommendations 2. Augmented reality measurement tools for room dimensions 3. Virtual furniture placement to visualize spaces). 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 viewers with overlapping purposes) 2. Function modules unrelated to real estate showcase (e.g., unnecessary social media feeds) 3. Fancy effects that affect performance (e.g., excessive particle animations in background). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating UI components, data fetching, and 3D/VR rendering services), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern real estate website principles: 1) Harmonious color matching that reflects luxury/comfort (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) VR navigation responds within 100ms to prevent motion sickness 2) 3D floor plan interactions feel natural with appropriate weight/physics 3) Clear visual cues for interactive elements vs. static content. Deduct 5 points for each operation without feedback, 3 points for jitter or frame drops during VR navigation, and 5 points for disorienting transitions between views. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Online Shopping",
+  "difficulty": "medium"
+}

package/library/web_applications-other/vue-spring-movie-seat-selection.json

@@ -0,0 +1,68 @@
+{
+  "index": 237,
+  "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.\n\n<template>\n  <div id=\"app\">\n    <!-- Global navigation bar -->\n    <nav class=\"navbar\">\n      <div class=\"container\">\n        <!-- Logo on the left -->\n        <router-link to=\"/movielist\" class=\"logo\">Movie Ticket Booking System</router-link>\n\n        <!-- Login and registration links on the right -->\n        <div class=\"auth-links\">\n          <router-link to=\"/login\" class=\"auth-link\">Login</router-link>\n          <router-link to=\"/register\" class=\"auth-link\">Register</router-link>\n        </div>\n      </div>\n    </nav>\n\n    <!-- Main content area -->\n    <main class=\"main-content\">\n      <router-view></router-view> <!-- Dynamically render route components -->\n    </main>\n\n    <!-- Global footer -->\n    <footer class=\"footer\">\n      <div class=\"container\">\n        <p>&copy; 2023 Movie Ticket Booking System. All rights reserved.</p>\n      </div>\n    </footer>\n  </div>\n</template>\n\n<script>\nexport default {\n  name: 'App',\n};\n</script>\n\n<style>\n/* Global styles */\nbody {\n  margin: 0;\n  font-family: Arial, sans-serif;\n}\n\n#app {\n  display: flex;\n  flex-direction: column;\n  min-height: 100vh;\n}\n\n.navbar {\n  background-color: #333;\n  color: white;\n  padding: 10px 0;\n  position: sticky; /* Fixed navigation bar */\n  top: 0; /* Fixed at the top */\n  z-index: 1000; /* Ensure navigation bar is on top layer */\n}\n\n.navbar .container {\n  display: flex;\n  justify-content: space-between; /* Left and right alignment */\n  align-items: center;\n  max-width: 1200px;\n  margin: 0 auto;\n  padding: 0 20px;\n}\n\n.navbar .logo {\n  color: white;\n  text-decoration: none;\n  font-size: 20px;\n  font-weight: bold;\n}\n\n.auth-links {\n  display: flex;\n  gap: 15px; /* Space between login and register links */\n}\n\n.auth-link {\n  color: white;\n  text-decoration: none;\n  font-size: 14px;\n}\n\n.auth-link:hover {\n  text-decoration: underline;\n}\n\n.main-content {\n  flex: 1;\n  padding: 20px;\n  max-width: 1200px;\n  margin: 0 auto;\n}\n\n.footer {\n  background-color: #333;\n  color: white;\n  text-align: center;\n  padding: 5px 0;\n  position: sticky; /* Fixed navigation bar */\n  bottom: 0; /* Fixed at the bottom */\n  z-index: 1000; /* Ensure navigation bar is on top layer */\n}\n</style>\n\nThis is the frontend homepage. The schedules table structure is:\nCREATE TABLE `schedules` (\n  `schedule_id` int NOT NULL AUTO_INCREMENT,\n  `movie_id` int NULL DEFAULT NULL,\n  `movie_name` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL,\n  `hall_id` int NULL DEFAULT NULL,\n  `hall_name` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL,\n  `start_time` datetime NULL DEFAULT NULL,\n  `end_time` datetime NULL DEFAULT NULL,\n  `price` decimal(38, 2) NOT NULL,\n  PRIMARY KEY (`schedule_id`) USING BTREE,\n  INDEX `movie_id`(`movie_id` ASC) USING BTREE,\n  INDEX `hall_id`(`hall_id` ASC) USING BTREE,\n  CONSTRAINT `schedules_ibfk_1` FOREIGN KEY (`movie_id`) REFERENCES `movies` (`movie_id`) ON DELETE RESTRICT ON UPDATE RESTRICT,\n  CONSTRAINT `schedules_ibfk_2` FOREIGN KEY (`hall_id`) REFERENCES `halls` (`hall_id`) ON DELETE RESTRICT ON UPDATE RESTRICT\n)\n\nThe halls table structure is:\nDROP TABLE IF EXISTS `halls`;\nCREATE TABLE `halls` (\n  `hall_id` int NOT NULL AUTO_INCREMENT,\n  `name` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL,\n  `seat_count` int NOT NULL,\n  `layout` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL,\n  `equipment` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL,\n  PRIMARY KEY (`hall_id`) USING BTREE\n)\n\nThe seats table structure is:\nDROP TABLE IF EXISTS `seats`;\nCREATE TABLE `seats` (\n  `seat_id` int NOT NULL AUTO_INCREMENT,\n  `hall_id` int NULL DEFAULT NULL,\n  `row_number` int NULL DEFAULT NULL,\n  `column_letter` int NULL DEFAULT NULL,\n  `is_available` tinyint(1) NULL DEFAULT 1,\n  PRIMARY KEY (`seat_id`) USING BTREE,\n  INDEX `hall_id`(`hall_id` ASC) USING BTREE,\n  CONSTRAINT `seats_ibfk_1` FOREIGN KEY (`hall_id`) REFERENCES `halls` (`hall_id`) ON DELETE RESTRICT ON UPDATE RESTRICT\n)\n\nPlease provide the implementation code for movie screening selection and seat selection, using Vue 3 for frontend and Spring Boot for backend implementation.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the movie screening selection feature fully implemented?",
+      "description": "Review whether the code provides a comprehensive movie screening selection interface with appropriate filters (by date, time, genre), clear display of available screenings with essential details (movie title, hall, start time, end time, price), and proper integration with the backend API. The component should handle loading states and errors gracefully.Score 0 if the feature is completely missing, 5 if only basic listing is implemented without filtering, and 10 if all functionality including advanced filtering, pagination, and sorting is properly implemented with proper state management.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the seat selection functionality complete and intuitive?",
+      "description": "Evaluate the seat selection interface for visual representation of the theater layout, clear indication of available/unavailable seats, ability to select/deselect seats, and real-time feedback. Check if the implementation retrieves seat data from the backend correctly and validates selected seats against the database before proceeding to checkout.Score 0 if seat selection is not implemented, 5 if basic functionality exists but lacks visual representation or validation, and 10 if the feature offers an intuitive theater layout view with color-coded seats, responsive selection, and proper backend validation.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are the Spring Boot backend endpoints properly implemented for the required functionality?",
+      "description": "Check if the backend provides all necessary REST endpoints for retrieving schedules, hall information, seat availability, and processing seat reservations. Verify that the endpoints implement proper error handling, input validation, and follow RESTful design principles. The API should handle concurrent seat selection scenarios correctly.Score 0 if backend endpoints are missing, 5 if basic endpoints exist but lack proper validation or concurrency handling, and 10 if all required endpoints are implemented with comprehensive error handling, validation, and transaction management.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is there proper integration between Vue 3 frontend and Spring Boot backend?",
+      "description": "Assess how well the Vue 3 components interact with Spring Boot endpoints. Check for proper API calls using Axios or Fetch, appropriate handling of responses and errors, and consistent data structures between frontend and backend. Verify that the integration handles authentication for protected endpoints if applicable.Score 0 if integration is missing, 5 if basic integration exists but with inconsistent error handling or data structures, and 10 if the integration is seamless with proper loading states, error handling, and consistent data formats.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as network failures, concurrent seat bookings, invalid user inputs) and provide friendly error prompts or recovery mechanisms. Check if proper validations are in place for all user inputs and if the system can handle edge cases gracefully.Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Real-time seat availability updates 2. Interactive seat price visualization 3. Recommended seating based on group size 4. Virtual theater view with screen perspective).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 select seats) 2. Function modules unrelated to movie booking (e.g., unnecessary social features) 3. Fancy effects that affect performance (e.g., excessive animations that slow down the booking 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 presentation/business logic/data access layers), component reusability, state management approach, and build process automation. Examine the code structure, naming conventions, and adherence to Vue 3 and Spring Boot best practices.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 seat selection and screening interfaces follow modern design principles: 1) Harmonious color matching that clearly indicates seat availability status 2) Proper layout spacing that makes the theater layout easy to understand 3) Professional typography with clear labeling of rows, columns, and screen position.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) Immediate feedback when selecting/deselecting seats 2) Smooth transitions when filtering movie screenings 3) Clear visual cues for selected seats and pricing updates. Pay special attention to how the system handles concurrent selections by different users.Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast interactions, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Online Shopping",
+  "difficulty": "easy"
+}

package/library/web_applications-other/web-30-minute-countdown-timer.json

@@ -0,0 +1,68 @@
+{
+  "index": 412,
+  "question": "You are a coding expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable for demonstration purposes. Please create a 30-minute countdown timer webpage and output it in HTML format.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core countdown timer functionality fully implemented?",
+      "description": "Review whether the code accurately implements a 30-minute countdown timer with proper time calculations. Check for accurate second-by-second countdown, correct time formatting (MM:SS), and proper termination when reaching zero. Score 0 if the timer doesn't work at all, 5 if it has minor time calculation errors, and 10 if it precisely counts down from 30 minutes to zero.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are essential timer controls implemented?",
+      "description": "Evaluate whether the timer includes necessary control functions such as start, pause, resume, and reset. Each function should work correctly without glitches. Deduct 3 points if any single control is missing, and 5 points if controls are present but malfunction. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is visual feedback provided during countdown?",
+      "description": "Check whether the timer provides visual feedback during the countdown process. This could include changing colors as time decreases, progress indicators, or visual cues when reaching specific time thresholds (e.g., last 5 minutes, last minute). Deduct 5 points if no visual feedback exists beyond the numbers changing, give 5 points for basic visual feedback, and 10 points for comprehensive visual indicators that enhance user awareness of time progression.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is there audio/visual notification when the timer ends?",
+      "description": "Evaluate whether the timer provides clear indication when it reaches zero. This should include visual alerts (color change, animation) and ideally audio notification. Give 3 points for basic visual indication, 7 points for enhanced visual effects, and 10 full points if both visual and audio notifications are implemented professionally.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as rapid button clicking, browser tab switching/background processing, or page refresh) and provide 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. Customizable time presets 2. Theme switching 3. Session counting or history 4. Pomodoro-style 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 timer engines running simultaneously) 2. Function modules unrelated to a countdown timer (e.g., a built-in calculator) 3. Fancy effects that affect performance (e.g., excessive animations that slow down the page). 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 timer logic/view/control layers), code organization, and maintainability. Deduct 5 points if global variables are excessively used or if the code structure is chaotic; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no error handling or if the code is poorly commented. 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 (timer digits clearly visible from distance, appropriate contrast). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for poor readability of the timer digits. 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) Button click feedback delay ≤ 100ms 2) Smooth second/minute transitions 3) Clear visual focus on the current time remaining. Deduct 5 points for each operation without feedback, 3 points for jerky time transitions, and 5 points for hard-to-find control buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Utility Tools-Calculation Tools",
+  "difficulty": "easy"
+}

package/library/web_applications-other/wechat-mini-program-self-service-car-wash.json

@@ -0,0 +1,68 @@
+{
+  "index": 1498,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Ensure that the code you generate is executable for demonstration purposes. Design a WeChat Mini Program page for a self-service car wash that has a beautiful interface and is suitable for commercial use.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core business logic of the self-service car wash fully implemented?",
+      "description": "Review whether the code accurately implements the complete car wash service flow through WeChat Mini Program framework, including service selection (basic wash/premium wash/wax service), time slot booking, payment integration, and real-time status tracking. Score 0 if core business logic is missing, 5 if only basic service selection is implemented, and 10 if complete commercial workflow including WeChat Pay integration is fully functional.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the WeChat Mini Program native functionality properly utilized?",
+      "description": "Check whether the implementation leverages WeChat Mini Program's native capabilities including location services (wx.getLocation), camera for QR code scanning (wx.scanCode), real-time messaging (WebSocket), and proper lifecycle management (onLoad/onShow/onHide). Deduct 5 points if location-based services are not implemented, 3 points if QR code scanning is missing, and 2 points if WeChat sharing functionality is absent. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the data persistence and state management architecture properly designed?",
+      "description": "Evaluate whether the mini program implements proper data flow management using WeChat's storage APIs (wx.setStorageSync/wx.getStorageSync), handles network requests with proper error handling, and maintains consistent state across page navigations. Check if user session management and order history persistence are implemented. Deduct 5 points if data consistency issues exist, 3 points if offline capability is missing. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the commercial-grade user experience workflow complete?",
+      "description": "Check whether the code includes complete commercial features such as user registration/login, service history tracking, membership system, promotional coupon management, and customer feedback mechanism. Evaluate if the booking confirmation process includes proper validation and confirmation steps. Deduct 5 points if payment flow is incomplete, 3 points if user account management is missing, 2 points if no feedback mechanism exists. Give 10 points if fully commercial-ready.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as network failures, WeChat API errors, payment interruptions, invalid user inputs, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should include proper error boundaries, fallback UI states, and graceful degradation. Give 10 points for comprehensive error handling, 5 points for basic error handling, and 0 points if no exception handling exists.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that enhance commercial value?",
+      "description": "Check whether the code includes value-added features that enhance user experience (e.g., 1. AR car wash preview using camera 2. AI-powered service recommendations based on car type 3. Real-time queue monitoring with estimated wait times 4. Social sharing of wash completion with before/after photos). 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) 2. Function modules unrelated to car wash services (e.g., built-in games or social features) 3. Excessive animations that affect Mini Program performance limits. Deduct 3 points for each redundancy found, and directly deduct 10 points if core business functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design following WeChat Mini Program best practices (proper page/component separation, utils organization), code reusability, and adherence to WeChat Mini Program development standards. Deduct 5 points if global state pollution is found or improper use of Mini Program lifecycle; deduct 5 points if code duplication rate is too high (over 30%); deduct 5 points if not following WeChat Mini Program coding standards. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface design meet commercial Mini Program standards?",
+      "description": "Evaluate whether the UI design follows WeChat Design Guidelines and commercial standards: 1) Consistent with WeChat's visual language and color schemes 2) Proper use of WeChat UI components (weui) 3) Professional branding elements suitable for car wash business 4) Clear visual hierarchy with proper spacing (following 8px grid system) 5) Readable typography (minimum 28rpx font size). Deduct 3 points for each non-compliant visual element, 5 points for poor color harmony, and 5 points for unprofessional commercial appearance. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the interaction design smooth and Mini Program compliant?",
+      "description": "Judge whether the interactions conform to WeChat Mini Program UX standards: 1) Touch feedback within 100ms following WeChat guidelines 2) Page transitions using proper Mini Program navigation APIs 3) Loading states with WeChat-style indicators 4) Proper use of Mini Program gestures and interactions 5) Accessibility considerations for diverse users. Deduct 5 points for each interaction not following WeChat standards, 3 points for performance issues during navigation, and 5 points for non-intuitive user flow. Full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Online Shopping",
+  "difficulty": "hard"
+}