@getollie/cli 0.0.1

package/library/management_systems-frontend_backend_platforms/device-repair-platform-with-qr-and-realtime-tracking.json

@@ -0,0 +1,68 @@
+{
+  "index": 664,
+  "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 displayed.\n\n======== Role ========\nYou are an experienced code expert. You have been provided with a software development requirement description and are asked to generate project code based on these requirements. Strictly follow the rules to help users generate complete project code with simple and easy-to-understand comments, without outputting anything else.\n\n======== Output Rules ========\n1. Always generate complete, runnable project code, ensuring the project is fully executable\n2. Ensure all code files you output are complete, do not omit any code\n3. Carefully review and check all code before final output, evaluating its executability. If the code cannot be executed or contains errors, regenerate it\n4. If the requirements involve external API access needs, or require using user data (images, videos, audio, etc.), please provide simulated data\n\n======== Project Requirements Description ========\nCreate a device repair platform where users can scan device QR codes to automatically populate device information and submit repair orders (including fault video uploads). After maintenance staff accept the order, the status changes to \"in process\", and users can view the maintenance staff's location on a map in real-time. Completion requires user electronic signature confirmation.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the QR code scanning and device information retrieval functionality fully implemented?",
+      "description": "Check if the code implements a camera interface to scan QR codes using HTML5 navigator.mediaDevices or a dedicated library like jsQR/zxing.Verify if there's proper error handling when the camera cannot be accessed or the QR code format is invalid.Review whether the code includes logic to parse the QR code data and query a device database/API to populate device information automatically.Examine if the UI clearly shows the scanning process and provides feedback during scanning. 0 points if QR scanning is missing, 5 points for basic QR scanning without auto-population, 10 points if fully implemented with error handling and proper device information retrieval",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the repair order submission system with video upload functionality implemented correctly?",
+      "description": "Verify if the form includes all necessary fields for a repair order (device info, issue description, contact details).Check if video recording/uploading is implemented using MediaRecorder API or file upload with proper format validation.Examine if there's progress indication during video uploads and proper handling of large files.Review whether the code implements client-side validation before submission and server-side validation upon receipt. 0 points if order submission is missing, 5 points if basic form exists without video upload, 10 points if complete with video upload functionality and proper validation",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the order status management system properly implemented?",
+      "description": "Check if the code implements a proper state machine for order status (submitted, accepted, in-process, completed).Verify if status changes trigger appropriate notifications to users.Review whether maintenance staff have an interface to accept orders and update status.Examine if the status is visually clear to users at all stages of the repair process. 0 points if status management is missing, 5 points if basic status tracking exists but lacks notifications or maintenance interface, 10 points if fully implemented with all required functionality",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the real-time location tracking of maintenance staff properly implemented?",
+      "description": "Verify if the code uses Geolocation API for staff location tracking with proper update frequency.Check if a mapping library (like Google Maps, Leaflet) is correctly integrated with proper API key management.Review whether the map updates in real-time using WebSockets or a polling mechanism.Examine if there are privacy controls for maintenance staff and appropriate user permissions. 0 points if location tracking is missing, 5 points if basic mapping exists without real-time updates, 10 points if fully implemented with real-time tracking and privacy controls",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (offline usage, location services disabled, camera access denied).Check if there's appropriate error handling and user feedback for all possible error states.Review whether the application implements data persistence in case of disconnection.Verify if there are fallback mechanisms when key features aren't available. 0 points if no exception handling exists, 5 points if basic error handling is implemented, 10 points if comprehensive error handling and recovery mechanisms are in place",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check for unexpected useful features (e.g., AR view for device troubleshooting, voice-guided repair instructions, repair history analytics).Review if there are smart suggestions based on common device issues.Examine if there are accessibility features beyond standard requirements.Verify if there are features that enhance user experience significantly. Add 3 points for each practical innovative feature implemented (maximum 10 points)",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Check for duplicate implementations of similar functions.Identify function modules unrelated to the repair platform core functionality.Look for performance-heavy animations or effects that aren't essential.Review if any features detract from the main user flow. 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 separating concerns (device scanning, order management, location tracking, user authentication).Check for unit tests covering critical functionality.Verify if there's a build process with proper asset optimization.Examine code organization, naming conventions, and documentation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is high; 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 color scheme consistency across the application.Check spacing and layout consistency following design principles.Review typography hierarchy and readability.Verify if the UI is responsive across different device sizes. 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 electronic signature confirmation system properly implemented?",
+      "description": "Verify if the signature capture uses an appropriate drawing mechanism (Canvas API or dedicated library).Check if signatures are properly validated before acceptance.Review if signatures are securely stored with proper timestamping.Examine if the signature process is legally compliant with clear terms shown to users. 0 points if signature functionality is missing, 5 points if basic signature capture exists without validation, 10 points if fully implemented with security measures and legal compliance",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "hard"
+}

package/library/management_systems-frontend_backend_platforms/drone-management-system-with-admin-frontend.json

@@ -0,0 +1,68 @@
+{
+  "index": 663,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable whenever possible.\n\n## Role\nYou are an experienced code expert. Given a software development requirement description, you are asked to generate project code according to the project requirements. Strictly follow the rules to help users generate complete project code with simple and easy-to-understand comments, without outputting anything else.\n\n## Output Rules\n1. You will always generate complete, runnable project code. Please ensure the project is fully executable\n2. Ensure that all code files you output are complete, without omitting any code\n3. Carefully review and check all code before final output, evaluating its executability. If the code cannot be executed or contains errors, regenerate it\n4. If the requirements involve external API access or need to use user data (images, videos, audio, etc.), please provide simulated data\n\n## Project Requirements\nDevelop a drone management system where employees can check drone flight status (such as in-flight, landing, malfunction) on the frontend page, and control drone takeoff and landing (simulated); administrators (username: uavadmin, password: 321321) can add new drone information.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the drone status display system fully implemented?",
+      "description": "Review whether the code accurately implements a dashboard for monitoring drone flight status (in-flight, landing, malfunction). Check if the frontend provides visual indicators for each status with appropriate color coding (e.g., green for flying, red for malfunction). Score 0 if status monitoring is not implemented, 5 if only basic status display is provided, and 10 if comprehensive status monitoring with historical data visualization is included.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the drone control functionality properly implemented?",
+      "description": "Evaluate whether the takeoff and landing control features are properly implemented with appropriate command validation and safety checks. Check whether the system includes confirmation dialogs before executing critical commands and provides immediate feedback after actions. Deduct 5 points if there's no validation mechanism, and 3 points if the feedback system is inadequate. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the drone management functionality for administrators complete?",
+      "description": "Check whether administrators can perform CRUD operations on drone data. Verify that the specified admin credentials (username: uavadmin, password: 321321) work as expected and that proper access control prevents unauthorized users from accessing admin functions. Score 0 if admin management is missing, 5 if basic management exists but lacks proper security, and 10 if full management with proper validation and security is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the authentication and authorization system secure?",
+      "description": "Evaluate whether the authentication system includes proper password hashing, secure session management, and appropriate role-based access control. Check if the system prevents unauthorized users from accessing restricted areas and properly validates user input. Deduct 5 points for storing plain text passwords, 3 points for using weak token systems, and 5 points if CSRF protection is missing. 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, user operation errors, malfunction alerts, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Real-time drone trajectory visualization 2. Predictive maintenance alerts 3. Geospatial mapping of drone locations). 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 status checking methods coexisting) 2. Function modules unrelated to drone management (e.g., unnecessary social features) 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 drone logic/view/API 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 (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast operations, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "medium"
+}

package/library/management_systems-frontend_backend_platforms/drone-specifications-database-design.json

@@ -0,0 +1,68 @@
+{
+  "index": 722,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Try to ensure that the code you generate is executable. Very good. Now I'm providing fields from another database. Help me design code for the database, Python side, and front-end Avue. Please refer to the following:\n\n\"QianXun Wing Q30\":\n  \"Manufacturer\": \"QianXun Position\"\n  \"Dimensions\": \"4.128m×1.93m×0.75m\"\n  \"Cruising Range\": 280km\n  \"Rain Resistance\": \"Medium Rain\"\n  \"Wind Resistance\": \"Level 7\"\n  \"Maximum Load\": 10kg\n  \"Type\": \"Compound Wing\"\n\"QianXun Wing Q20\":\n  \"Manufacturer\": \"QianXun Position\"\n  \"Dimensions\": \"3.378m×1.5m×0.5m\"\n  \"Cruising Range\": 210km\n  \"Rain Resistance\": \"Medium Rain\"\n  \"Wind Resistance\": \"None\"\n  \"Maximum Load\": 3kg\n  \"Type\": \"Compound Wing\"\n\"QianXun Wing X8\":\n  \"Manufacturer\": \"QianXun Position\"\n  \"Dimensions\": ''\n  \"Cruising Range\": ''\n  \"Rain Resistance\": \"None\"\n  \"Wind Resistance\": \"Level 7\"\n  \"Maximum Load\": 5.5kg\n  \"Type\": \"Multi-Rotor Wing\"\n\"Extreme Fly M2000\":\n  \"Manufacturer\": \"Guangzhou Extreme Fly Technology Co., Ltd.\"\n  \"Dimensions\": ''\n  \"Cruising Range\": 86km\n  \"Rain Resistance\": \"None\"\n  \"Wind Resistance\": \"None\"\n  \"Maximum Load\": ''\n  \"Type\": \"Fixed Wing\"\n\"Extreme Fly V50-Pro\":\n  \"Manufacturer\": \"Guangzhou Extreme Fly Technology Co., Ltd.\"\n  \"Dimensions\": ''\n  \"Cruising Range\": ''\n  \"Rain Resistance\": \"None\"\n  \"Wind Resistance\": \"None\"\n  \"Maximum Load\": 20kg\n  \"Type\": \"Multi-Rotor Wing",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the database schema properly designed for the UAV data?",
+      "description": "Review whether the database schema correctly defines tables, fields, and relationships for storing UAV information. Check for proper field types (string for text fields, numeric for measurements, etc.), primary keys, and indexes. Evaluate normalization to avoid redundancy while maintaining query efficiency.Award 0 points if no schema is provided, 5 points for basic table creation without proper constraints, and 10 points for a complete schema with appropriate data types, constraints, and indexes optimized for UAV data retrieval.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is there a complete Python backend implementation for CRUD operations?",
+      "description": "Examine the Python code for comprehensive Create, Read, Update, and Delete operations on the UAV database. Check for proper error handling, input validation (especially for measurements and technical specifications), and appropriate ORM usage if applicable.Deduct 3 points if any CRUD operation is missing, 2 points for inadequate input validation, and 2 points for poor error handling. Award 10 points for a complete implementation with proper data validation, error handling, and efficient database operations.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is there a Python API layer that properly interfaces with the frontend?",
+      "description": "Verify if the Python code includes API endpoints (using frameworks like Flask or FastAPI) that expose the necessary data to the Avue frontend. Check for proper routing, authentication mechanisms, data serialization, and RESTful design principles.Award 0 points if no API is implemented, 5 points for basic endpoints without authentication or proper error responses, and 10 points for complete API implementation with authentication, proper status codes, and comprehensive documentation.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the Avue frontend configuration properly implemented for UAV data display?",
+      "description": "Evaluate whether the Avue configuration correctly displays all UAV fields with appropriate form components (text fields, dropdowns for type selection, number inputs with proper units for measurements). Check for proper layout organization that logically groups related UAV specifications.Deduct 2 points for each missing or improperly configured field. Deduct 3 points if field validation is missing. Award full 10 points only if all UAV fields are properly displayed with appropriate input types and validation rules.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as empty fields in the provided data, malformed input, network issues, etc.) and provide friendly error handling. Check for input validation, null checks, and graceful degradation.Award 10 points for comprehensive error handling including input validation, meaningful error messages, and graceful degradation. Award 5 points if basic error handling exists but edge cases are missed. Award 0 points if no error handling is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes additional features that enhance usability (e.g., 1. UAV comparison visualization 2. Specification filtering system 3. Performance metrics charts 4. Integrated search functionality for UAV data).Add 3 points for each practical innovative feature implemented (maximum 10 points). Features must be relevant to UAV data management and visualization.",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant data storage or processing logic 2. Functionality unrelated to UAV data management 3. Overly complex UI elements that don't add value to UAV data visualization.Deduct 3 points for each redundancy found, and directly deduct 10 points if core UAV data management functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (separation of data access, business logic, and presentation layers), code reusability, appropriate comments, and adherence to language-specific conventions (PEP 8 for Python, standard JS practices for frontend).Deduct 5 points if code lacks separation of concerns; deduct 5 points if code duplication rate is over 30%; deduct 5 points if there are no meaningful comments or documentation. Award full 10 points for well-structured, documented, and maintainable code.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the Avue interface follows modern design principles: 1) Appropriate color scheme for technical data 2) Proper layout with logical grouping of UAV specifications 3) Consistent typography enhancing readability of technical specifications.Deduct 3 points for each crowded visual element, 5 points for inappropriate color schemes for technical data, and 5 points for poor information hierarchy making UAV data hard to scan. Award 10 points for a clean, professional interface optimized for UAV data presentation.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the data visualization effective and intuitive?",
+      "description": "Judge whether the data presentation helps users understand UAV specifications: 1) Visual comparison of UAV capabilities 2) Appropriate charts for numeric specifications 3) Clear visual indicators for missing data points in the UAV specifications.Deduct 5 points for raw data display without any visualization, 3 points for basic visualization without comparative capabilities, and 5 points for visualizations that don't effectively communicate UAV performance differences. Award 10 points for comprehensive, intuitive data visualization that aids decision-making.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "easy"
+}

package/library/management_systems-frontend_backend_platforms/e-commerce-product-collection-management.json

@@ -0,0 +1,68 @@
+{
+  "index": 912,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Collection Pages\n│   ├── Product Collection\n│   ├── Collection List\n├── Shopee\n│   ├── Product Listing\n│   │   ├── Store Product Drafts\n│   │   ├── Global Product Drafts\n│   │   ├── Publishing Records\n│   │   ├── Pricing Templates\n│   ├── Online Products\n│   │   ├── Store Products\n│   │   ├── Global Products\n│   ├── Marketing Management\n│       ├── Discount Templates\n│       └── Discount Campaigns\n├── Lazada\n│   ├── Product Listing\n│   │   ├── Store Product Drafts\n│   │   ├── Global Product Drafts\n│   │   ├── Publishing Records\n│   ├── Online Products\n│       └── Store Products",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the full hierarchical structure of the navigation system properly implemented?",
+      "description": "Check whether the code accurately implements the nested menu structure using appropriate HTML/CSS/JS components. Verify proper indentation visual cues, expand/collapse functionality for submenus, and breadcrumb navigation. Score 0 if the hierarchy is not represented, 5 if basic structure is implemented but lacks visual distinctions, and 10 if the full hierarchy with proper interaction is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the cross-platform e-commerce product management functionality implemented?",
+      "description": "Evaluate whether the code handles both Shopee and Lazada platforms with their distinct features. Check for platform-specific API integrations, data models for different product types (Store/Global), and unified management interfaces. Deduct 5 points if platform-specific features are missing, 3 points if data synchronization between platforms is not implemented. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are the product draft and publishing workflows properly implemented?",
+      "description": "Assess the implementation of product lifecycles including draft creation, editing, and publishing processes. Check for status tracking, version control, and publishing validation rules. Verify that publishing records are maintained properly. Deduct 5 points if validation rules are missing, 3 points if status transitions are incomplete. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the marketing management functionality properly integrated with product data?",
+      "description": "Examine the relationship between products and marketing features (discount templates/campaigns). Check for data consistency between product listings and promotional features, including pricing template integration. Deduct 5 points if product-discount relationships are not properly modeled, 3 points if promotional features lack scheduling capabilities. 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, invalid product data, concurrent edits, 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. Cross-platform bulk operations 2. AI-powered product categorization 3. Smart pricing recommendations based on market data). 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 implementation of similar functions across platforms 2. Unused or legacy code paths 3. Unnecessarily complex UI components 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 platform-specific logic from common functionality), 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 when navigating complex menu structures. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast navigation, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "hard"
+}

package/library/management_systems-frontend_backend_platforms/educational-management-system-teaching-lab-experiments.json

@@ -0,0 +1,68 @@
+{
+  "index": 1453,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the code you generate is executable for demonstration. Using educational management as an example, help me write a comprehensive system that includes teaching courses, laboratory courses, and experiments. In this educational management system, laboratory courses are part of the teaching management, laboratory courses contain experiments, teachers create experiment-related information, and students learn through experiments.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core educational management system fully implemented?",
+      "description": "Review whether the code accurately implements the fundamental educational management system components including course management (creation, updating, deletion), teacher/student registration, enrollment functionality, and grade tracking. Score 0 if no core functionality is implemented, 5 if only basic CRUD operations are available, and 10 if a complete system with role-based permissions and workflow is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the laboratory course management subsystem properly integrated?",
+      "description": "Evaluate whether laboratory courses are properly implemented as a specialized type of course with appropriate inheritance/composition relationships to the main course structure. Check if lab courses have distinct properties (equipment requirements, capacity limits, safety protocols) while maintaining core course attributes. Deduct 5 points if labs are implemented as completely separate entities without proper integration, and 3 points if lab-specific attributes are missing. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the experiment management functionality comprehensive?",
+      "description": "Check whether experiments within laboratory courses have complete lifecycle management including creation by teachers, assignment to students, submission by students, evaluation, and feedback mechanisms. Verify if experiments have appropriate metadata (time estimates, difficulty levels, prerequisites, learning objectives). Deduct 5 points if the experiment submission workflow is incomplete, and 3 points if metadata or learning analytics are missing. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the teacher-student interaction model properly designed?",
+      "description": "Assess whether the system successfully models teacher-student relationships across regular courses and laboratory experiments. Check if teachers can create, assign, track, and evaluate student experiment participation, and if students can view assignments, submit work, receive feedback, and track progress. Deduct 5 points if the notification system for new assignments/submissions is missing, and 3 points if the feedback mechanism is one-directional. 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 duplicate enrollments, scheduling conflicts, submission after deadlines, 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 educational experience (e.g., 1. AI-assisted grading system 2. Interactive virtual laboratory simulations 3. Learning analytics dashboard with performance predictions). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple user management systems coexisting) 2. Function modules unrelated to educational management (e.g., a built-in social network) 3. Fancy effects that affect performance (e.g., unnecessary animations in critical workflows). 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/data access 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 (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast sliding, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "hard"
+}

package/library/management_systems-frontend_backend_platforms/electricity-consumption-data-management-vue-upgrade.json

@@ -0,0 +1,68 @@
+{
+  "index": 1125,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the generated code is executable when possible. Provide functionality for manual entry of historical electricity consumption data for various company yards in 2022 and 2023. Input information includes electricity consumption category, equipment code, equipment name, energy consumption, workload, unit consumption, electricity consumption month, and other information. The functionality should include adding, modifying, editing, deleting, importing, and exporting yard electricity consumption data.\n\nThe frontend needs to be upgraded from Vue 2.0 to Vue 3.0, and the functionality migrated to the Yuheng development framework. Adjust functional components and styles to adapt to the new framework, and switch the usage methods of common entity classes and utility classes to ensure comprehensive adjustment and adaptation of code functionality.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the electricity consumption data entry functionality fully implemented?",
+      "description": "Review whether the code implements all required data fields (electricity consumption category, equipment code, equipment name, energy consumption, workload, unit consumption, electricity consumption month, etc.) with appropriate validation. Check for field type enforcement, range validation, and required field handling. Score 0 if core data structures are missing, 5 if basic fields are implemented but lack validation, and 10 if complete with comprehensive validation.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are all CRUD operations properly implemented for yard electricity consumption data?",
+      "description": "Evaluate whether the code properly implements adding, modifying, editing, deleting operations with appropriate state management. Check for optimistic updates, proper error handling during operations, and confirmation dialogs for destructive actions. Deduct 2 points for each missing operation, 3 points if operations don't update the UI appropriately, and 3 points if there's no validation feedback. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the data import/export functionality properly implemented?",
+      "description": "Check for robust import/export capabilities including file format support (CSV, Excel), validation of imported data, progress indicators for large datasets, and error reporting. Verify that exported files contain complete and accurate data. Deduct 3 points if import validation is missing, 3 points if export formatting options are limited, and 5 points if large file handling isn't optimized. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Has the Vue 2.0 to Vue 3.0 migration been properly executed?",
+      "description": "Evaluate whether the code successfully migrates from Vue 2.0 to 3.0, including: replacing the Options API with Composition API where appropriate, converting event bus patterns to provide/inject or state management, updating lifecycle hooks, and proper handling of reactive state. Deduct 5 points if deprecated Vue 2 syntax is still used, 3 points if reactivity isn't properly implemented with Vue 3 methods, and 5 points if there are console errors related to API incompatibilities. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as network errors, invalid user input, API failures) 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. Smart data entry suggestions based on historical patterns 2. Interactive data visualization for consumption trends 3. Automated data anomaly detection). 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 data validation logic coexisting) 2. Function modules unrelated to electricity consumption tracking (e.g., unnecessary animations or widgets) 3. Performance-impacting features that don't add value to the core functionality. 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 models/view components/service layers), unit test coverage, and build process adaptation to the Yuheng framework. 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 integration with the Yuheng development framework is incomplete. 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 form design (consistent field widths, clear grouping of related fields). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic form layout. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Form submission feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual feedback for data operation success/failure. Deduct 5 points for each operation without feedback, 3 points for UI freezing during data processing, and 5 points for confusing navigation patterns. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "easy"
+}

package/library/management_systems-frontend_backend_platforms/electricity-consumption-vue3-upgrade.json

@@ -0,0 +1,68 @@
+{
+  "index": 1380,
+  "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. Provide functionality for manual data entry of electricity consumption original data for various companies in 2022 and 2023. Data entry items include electricity consumption category, equipment code, equipment name, energy consumption amount, workload, unit consumption, electricity consumption month, and other information. Features include adding, modifying, editing, deleting, importing, and exporting electricity consumption data.\n\nBased on manually entered or imported electricity consumption data, automatically calculate the per-container energy consumption for standard containers and natural containers for equipment in the corresponding month.\n\nUpgrade the front-end from Vue 2.0 to Vue 3.0, and migrate the functionality to the Yuheng development framework. Adjust function components and styles to adapt to the new framework, and switch the usage methods of common entity classes and utility classes to ensure comprehensive adjustment and adaptation of code functionality.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "1. Is the electricity consumption data entry functionality fully implemented?",
+      "description": "Review whether the code accurately implements all required data entry fields (electricity consumption category, equipment code, equipment name, energy consumption amount, workload, unit consumption, electricity consumption month, etc.) with proper validation. Check if the form layout is responsive and user-friendly.Score 0 if core data entry fields are missing, 5 if basic fields are implemented without validation, and 10 if all fields are implemented with proper validation, formatting, and user guidance.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "2. Are all CRUD operations properly implemented for electricity consumption data?",
+      "description": "Evaluate the implementation of adding, modifying, editing, deleting, importing, and exporting electricity consumption data. Check for proper state management, error handling, and user feedback during these operations.Deduct 2 points for each missing operation. Deduct 1 point for each operation lacking proper error handling or user feedback. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "3. Is the automatic calculation of per-container energy consumption correctly implemented?",
+      "description": "Check if the code correctly calculates the per-container energy consumption for both standard containers and natural containers based on the entered data. Verify calculation logic, formula implementation, and dynamic updates when source data changes.Deduct 5 points if either standard container or natural container calculations are missing or incorrect. Deduct 3 points if calculations don't update dynamically. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "4. Has the migration from Vue 2.0 to Vue 3.0 been properly executed?",
+      "description": "Evaluate whether the code correctly implements Vue 3 Composition API instead of Options API, replaces Vue 2 specific features with Vue 3 equivalents, and properly handles migration of global plugins and components. Check for the use of script setup, Teleport, Fragments and other Vue 3 features.Deduct 3 points if reactive state management isn't using Vue 3 patterns, 3 points if lifecycle hooks aren't properly migrated, 2 points if template syntax isn't updated, and 2 points if Vue 3 specific features aren't leveraged. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "5. Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid data input, network interruption, empty data sets, etc.) and provide friendly error prompts or recovery mechanisms.Code with strong robustness should be able to effectively handle 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": "6. 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 data visualization 2. Smart data validation and suggestions 3. Keyboard shortcuts for power users 4. Batch processing operations).Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "7. Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple data validation methods) 2. Function modules unrelated to electricity consumption data management 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": "8. Does the code have engineering quality?",
+      "description": "Review modular design (such as separating data management/UI components/business logic), unit test coverage, and adherence to Yuheng development framework standards. Check for proper TypeScript usage, component reusability, and maintainable code structure.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 Yuheng framework standards aren't followed. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "9. 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": "10. 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 electricity data entry flows.Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast form navigation, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "easy"
+}

package/library/management_systems-frontend_backend_platforms/electricity-price-model-configuration.json

@@ -0,0 +1,68 @@
+{
+  "index": 1537,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure that the generated code is executable for demonstration. Based on this information, could you help me create a product prototype for an \"Electricity Price Model Configuration Module\"? Either provide an image directly or give me an HTML file that I can open in my browser myself.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the electricity price model configuration interface fully implemented?",
+      "description": "Review whether the code accurately implements configurable electricity pricing models through HTML/JavaScript, including time-of-use (TOU) pricing, tiered pricing, demand charges, and seasonal rate adjustments. Check if the interface allows users to set multiple rate periods, define price thresholds, and configure complex pricing structures. Score 0 if no pricing model configuration is implemented, 5 if only basic single-rate configuration exists, and 10 if comprehensive multi-tier pricing models with time-based variations are fully supported.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the dynamic price calculation and preview functionality implemented?",
+      "description": "Evaluate whether the system provides real-time calculation of electricity costs based on configured parameters, with live preview of pricing impact. Check if the code includes validation for price configuration conflicts, automatic calculation of blended rates, and graphical representation of price structures. Deduct 5 points if calculation logic is missing or incorrect, and 3 points if no visual feedback is provided for price changes. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the configuration data management and persistence mechanism designed?",
+      "description": "Check whether the prototype includes proper data structure for storing pricing configurations, supports import/export of pricing templates, and provides version control for different pricing schemes. Evaluate if the system can handle multiple utility rate schedules and allows for easy switching between configurations. Deduct 5 points if no data persistence is implemented, and 3 points if configuration templates cannot be saved or loaded. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the pricing model validation and testing framework constructed?",
+      "description": "Review whether the code includes comprehensive validation for pricing model consistency, conflict detection between overlapping rate periods, and scenario testing capabilities. Check if the system provides simulation tools to test pricing models against sample usage data and generates accuracy reports. Deduct 5 points if no validation logic exists, and 3 points if edge cases in pricing periods are not handled. Give 10 points if fully implemented with comprehensive testing scenarios.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid price inputs, overlapping time periods, negative rates, extreme values, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should effectively validate all user inputs, handle edge cases gracefully, and prevent system crashes from malformed data, 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 user experience (e.g., 1. Interactive pricing calendar with drag-and-drop rate setting 2. Smart pricing recommendations based on usage patterns 3. Real-time cost impact visualization 4. Pricing model comparison tools). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple price calculation engines coexisting) 2. Function modules unrelated to electricity pricing (e.g., weather widgets or unrelated utilities) 3. Fancy effects that affect usability (e.g., excessive animations during price configuration). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core pricing configuration 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 pricing logic/UI components/data models), code organization, and maintainability. Deduct 5 points if global state pollution is found or proper separation of concerns is not implemented; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the code structure is not scalable for adding new pricing models. 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 enterprise application design principles: 1) Professional color scheme suitable for utility management interfaces (no more than 3 primary colors) 2) Clear information hierarchy with proper spacing (element spacing follows the 8px multiple principle) 3) Professional typography system (body font size ≥ 14px, line height over 1.5 times) 4) Intuitive form layouts for complex pricing data. Deduct 3 points for each crowded visual element, 5 points for unprofessional color combinations, and 5 points for confusing data presentation layout. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and intuitive for configuration tasks?",
+      "description": "Judge whether the interface interactions are optimized for complex configuration tasks: 1) Form input feedback delay ≤ 100ms 2) Smooth transitions when switching between pricing models (300-500ms) 3) Clear visual indicators for active configuration sections 4) Intuitive navigation between different pricing parameters. Deduct 5 points for each configuration action without proper feedback, 3 points for confusing navigation flow, and 5 points for hard-to-locate critical configuration options. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "medium"
+}