@getollie/cli 0.0.4 → 0.2.0

package/library/management_systems-frontend_backend_platforms/medical-equipment-maintenance-management-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 598,
-  "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 for demonstration. Please write code to implement a medical equipment maintenance management system for managing the maintenance and upkeep of various medical devices in a hospital (such as CT scanners, MRI machines, ultrasound devices, etc.). The system needs to record basic information for each device (device ID, name, model, manufacturer, purchase date, department, etc.), technical parameters, and maintenance requirements (such as maintenance cycle, key inspection items, etc.). Equipment administrators (username: equipment, password: 123456) can create periodic maintenance schedules, and the system automatically generates maintenance tasks and reminders according to the schedule. Maintenance engineers (username: engineer, password: 123456) receive tasks, perform maintenance work, fill out maintenance records (inspection items, test data, replaced parts, maintenance results, etc.), and upload on-site photos or test reports. Medical staff can report device malfunctions (describing the fault symptoms, urgency level, etc.), and maintenance engineers accept the orders, process them, and record the repair process. System administrators (username: admin, password: 123456) can view maintenance history of all equipment, fault frequency statistics, average repair time and other metrics, and generate equipment reliability analysis reports. The system should also support spare parts inventory management functions, recording the inventory status of spare parts needed for maintenance and issuing warnings when inventory is insufficient.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core equipment management system properly implemented?",
-      "description": "Review whether the code accurately implements CRUD operations for medical equipment (device ID, name, model, manufacturer, purchase date, department, technical parameters, maintenance requirements). Check if there's proper data validation for equipment registration and updates, and if the system enforces unique device IDs. Score 0 if equipment management is missing, 5 if basic registration exists without validation, and 10 if complete with proper validation and relationship modeling.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the maintenance schedule generation and task management system fully functional?",
-      "description": "Evaluate whether the system automatically generates maintenance tasks based on equipment maintenance cycles. Check if it includes notification mechanisms for upcoming maintenance, proper task assignment to engineers, and status tracking (pending, in-progress, completed). Deduct 5 points if automatic scheduling is missing, and 3 points if notification system is not implemented. Score 10 if the system handles recurring maintenance with proper prioritization algorithms.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are the maintenance record keeping and fault reporting workflows properly implemented?",
-      "description": "Check if engineers can properly log maintenance activities with required fields (inspection items, test data, replaced parts, results) and if medical staff can submit fault reports with appropriate urgency levels. Verify if the system supports photo/document uploads and maintains a complete audit trail. Deduct 5 points if file upload functionality is missing, 3 points if the workflow has logical gaps. Score 10 if the complete maintenance lifecycle is properly tracked.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the spare parts inventory management system functional?",
-      "description": "Assess whether the system tracks spare parts inventory with proper stock level monitoring. Verify if it includes low-stock alerts, integration with maintenance records for automatic inventory deduction, and inventory history. Score 0 if inventory management is missing, 5 if basic tracking exists without alerts, and 10 if complete with proper integration to maintenance workflows and automated threshold alerts.",
-      "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, concurrent edits, server failures) and provide friendly error prompts or recovery mechanisms. Code should implement proper exception handling, input validation, and transaction management. If the robustness is excellent with comprehensive error handling, give 10 points. If it's 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. Predictive maintenance using equipment usage patterns 2. Mobile app integration with QR code scanning for equipment 3. Interactive equipment location maps 4. AI-based fault diagnosis suggestions). 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 record the same maintenance data) 2. Function modules unrelated to medical equipment maintenance (e.g., a built-in general chat system) 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 data access/business logic/presentation layers), unit test coverage, and build process automation. Examine proper use of design patterns appropriate for maintenance workflows. Deduct 5 points if global state pollution is found; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if 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 suitable for a healthcare setting: 1) Clean, professional color scheme (predominantly white with accent colors) 2) Proper layout spacing with clear hierarchical information display 3) Professional font system optimized for readability in clinical environments. Deduct 3 points for each cluttered screen, 5 points for inappropriate color schemes in a medical context, and 5 points for poor information hierarchy. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects support efficient workflows for busy healthcare professionals: 1) Quick response times for common operations (≤ 100ms) 2) Appropriate feedback for maintenance task status changes 3) Clear visual indicators for urgent items requiring attention. Deduct 5 points for each critical operation without feedback, 3 points for confusing state transitions, and 5 points for hard-to-locate critical functions like emergency repair requests. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "hard"
-}

package/library/management_systems-frontend_backend_platforms/meeting-feedback-tracker-with-attendance.json

@@ -1,68 +0,0 @@
-{
-  "index": 1806,
-  "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 for demonstration whenever possible. I need to create a webpage for tracking feedback from meeting participants with the following features: 1. Ability to import multiple attendance lists containing departments, personnel, and phone numbers. 2. The webpage should be able to compile and summarize departments, personnel, and phone numbers. 3. Remove duplicate entries, and implement this in an intranet environment.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the data import functionality fully implemented?",
-      "description": "Review whether the code provides multiple methods for importing attendance data (CSV, Excel, JSON, manual entry), handles various file formats correctly, and includes proper error handling for malformed data. Check if the import validates the required fields (departments, personnel, phone numbers). Score 0 if import functionality is missing, 5 if only basic import is available, and 10 if multiple import methods with validation are implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the data compilation and summarization feature implemented effectively?",
-      "description": "Evaluate whether the code properly compiles and summarizes the imported data, providing statistical information by department, personnel counts, and contact information. Check if the system offers sorting, filtering, and search capabilities. Score 0 if summarization is missing, 5 if basic compilation exists but lacks advanced features, and 10 if comprehensive data summarization with multiple viewing options is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Does the duplicate detection and removal system work properly?",
-      "description": "Assess the duplicate detection algorithm to confirm it can identify duplicate entries based on multiple criteria (exact matches, fuzzy matching on names, similar phone numbers). Verify that the system allows for manual review of potential duplicates before removal and maintains an audit log of merged/removed entries. Deduct 5 points if only exact matching is used, and 3 points if no user confirmation for removal exists. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the solution compatible with intranet environment constraints?",
-      "description": "Check if the implementation works entirely client-side or uses minimal server requirements suitable for intranet deployment. Verify that it doesn't rely on external services, CDNs, or APIs that would be inaccessible in an isolated network. Evaluate if local storage or internal database options are properly implemented for data persistence. Score 0 if incompatible with intranet, 5 if partially compatible with modifications needed, and 10 if fully intranet-ready.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as malformed input data, missing fields, network interruption, user operation errors, 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. Intelligent duplicate suggestion system 2. Data visualization of attendance patterns 3. Export options with customizable reports). 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 perform the same data processing) 2. Function modules unrelated to attendance tracking (e.g., a built-in calendar system) 3. Fancy effects that affect performance (e.g., unnecessary animations or transitions). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating data processing logic from UI components), 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 scrolling through attendance lists, 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/meeting-room-reservation-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 656,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable for demonstration whenever possible. \n\n======== Role ========\nYou are an experienced code expert. You're given a software development requirement description and asked to generate project code based on these requirements. Strictly follow the rules to help users generate complete project code with simple, easy-to-understand comments, and don't output 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, don't 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 or need to use user data (images, videos, audio, etc.), please provide mock data\n\n======== Project Requirements Description ========\nPlease write a meeting room reservation system. Users can select meeting rooms, dates, and time slots through the front-end interface. If a meeting room has already been reserved, the system needs to update status in real-time and remind users to select another time. Administrators can view all reservation records through the back-end interface and modify or cancel reservations.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the meeting room reservation interface fully implemented?",
-      "description": "Review whether the code accurately implements the room selection, date picker, and time slot selection components through HTML/CSS/JavaScript. Check if it includes visual indicators for available vs. reserved slots, interactive selection functionality, and form validation for booking details. Score 0 if the core reservation UI is not implemented, 5 if only basic selection is available, and 10 if complete with validation and user feedback.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the real-time status update mechanism implemented?",
-      "description": "Evaluate whether the system includes real-time updates when meeting rooms become reserved by other users, either through WebSockets, polling, or other event-driven mechanisms. Check if the UI immediately reflects changes and provides clear notifications to users when their selected slot becomes unavailable. Deduct 5 points if updates require page refresh, 3 points if notifications are unclear. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the administrator backend interface complete?",
-      "description": "Check if the admin interface includes comprehensive views for all reservations with filtering/sorting capabilities, and provides functionality to modify or cancel any reservation. Evaluate whether it includes user management, reporting features, and audit logs. Deduct 5 points if modification functionality is missing, 3 points if filtering/sorting is limited, and 5 points if the interface lacks responsive design. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the data persistence and state management well-designed?",
-      "description": "Assess whether the system implements proper data storage for reservations, with appropriate database schema design (or equivalent state management). Check if reservation conflicts are correctly prevented through locking mechanisms or transaction handling. Deduct 5 points if race conditions are possible, 3 points if data validation is incomplete, and 3 points if the system lacks proper error handling for database operations. 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 concurrent bookings, network interruption, invalid date/time selections, 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. Calendar heat map showing busy periods 2. Room layout visualization with equipment details 3. Integration with calendar apps for automatic reminders). 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 date picker implementations) 2. Function modules unrelated to room reservation (e.g., built-in chat system) 3. Fancy effects that affect performance (e.g., unnecessary animations on every page load). 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 reservation logic/view/data 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 calendar or room switching, 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/mini-program-video-monitoring-playback.json

@@ -1,68 +0,0 @@
-{
-  "index": 1675,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure the code you generate is executable and demonstrable. Write a mini program to implement features such as real-time monitoring video viewing, historical playback, etc., including time-based viewing functionality.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the real-time video monitoring system fully implemented?",
-      "description": "Review whether the code properly implements real-time video streaming functionality using technologies like WebRTC, HLS, or RTSP. Check if it handles stream initialization, buffering strategies, and quality adaptation based on network conditions. Score 0 if video monitoring is not implemented, 5 if basic streaming is implemented without optimizations, and 10 if it includes adaptive bitrate streaming with minimal latency (<2 seconds).",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the historical video playback functionality complete?",
-      "description": "Evaluate whether the code implements a robust video archive system with features like seeking, timestamp navigation, and different playback speeds. Check if it uses efficient video indexing for quick access to specific time segments and if it handles large video files properly. Deduct 5 points if seeking is not smooth or has significant lag, and 3 points if playback speed controls are missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is time-based viewing functionality properly implemented?",
-      "description": "Check if the time navigation system allows precise selection of date/time ranges with proper calendar UI and timeline scrubbing. Verify if the code efficiently handles time zone conversions and displays timestamps accurately. Deduct 4 points if the timeline UI is not intuitive, 3 points if it lacks proper date range selection, and 3 points if timestamp display is inaccurate. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there a seamless transition between live and recorded content?",
-      "description": "Evaluate if the program provides smooth transitions between live streaming and historical playback modes without requiring page reloads or significant UI changes. Check if the application maintains context when switching modes and properly manages the video buffer. Deduct 5 points if mode switching requires page refresh, 3 points if UI consistency is broken between modes, and 2 points if there's noticeable delay (>1s) during transitions. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code handles common video streaming issues (network interruptions, codec incompatibilities, broken streams) and provides graceful error handling with informative user feedback. Check for proper memory management during long streaming sessions and resilience against unexpected inputs. Give 10 points for comprehensive error handling with recovery strategies, 5 points for basic error detection without recovery options, and 0 points if errors crash the application.",
-      "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 motion detection alerts 2. Video analytics/object recognition 3. Multi-camera synchronized viewing 4. Smart bookmarking of important events). 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. Multiple competing implementations of similar video processing functions 2. Excessive UI elements unrelated to video surveillance (e.g., unnecessary social features) 3. Resource-intensive visual effects that impact streaming performance. Deduct 3 points for each redundancy found, and directly deduct 10 points if core video functionality is compromised by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating video processing logic/UI components/data management), code reusability, and performance optimization techniques. Deduct 5 points if global state management is chaotic; deduct 3 points if stream handling and UI rendering are not properly separated; deduct 2 points if the codebase lacks comments or documentation. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional surveillance system standards?",
-      "description": "Evaluate whether the design follows professional video monitoring principles: 1) Clear video display area with proper aspect ratio preservation 2) Non-intrusive controls that don't obscure important content 3) High-contrast UI elements for visibility in dark environments. Deduct 3 points for each poorly arranged control panel, 4 points for improper video scaling/cropping, and 3 points for color schemes that strain the eyes during extended viewing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the video playback interaction smooth and responsive?",
-      "description": "Judge whether the video controls behave according to user expectations: 1) Seeking response time ≤ 200ms 2) Play/pause toggle ≤ 100ms 3) Intuitive timeline navigation with preview thumbnails. Deduct 4 points for laggy timeline scrubbing, 3 points for delayed playback controls, and 3 points for confusing timeline indicators that make it difficult to locate specific moments. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "medium"
-}

package/library/management_systems-frontend_backend_platforms/mobile-app-online-food-ordering.json

@@ -1,68 +0,0 @@
-{
-  "index": 1486,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you produce is executable and ready for demonstration. I want to create a mobile app specifically for online food ordering, where customers can select menu items and place orders. Please help me generate a set of cloud-based code for this.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core food ordering system fully implemented?",
-      "description": "Review whether the code accurately implements the essential functions of a food ordering app: menu display, item selection, cart management, and order submission. Check if it includes proper validation for required order details (items, quantities, special instructions) and handles edge cases like out-of-stock items. Score 0 if the core ordering functionality is missing, 5 if only basic item selection is implemented, and 10 if the complete ordering flow with validation is present.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the cloud backend properly configured for the mobile app?",
-      "description": "Evaluate if the backend infrastructure uses appropriate cloud services (Firebase, AWS, Azure, etc.) with proper API endpoints for authentication, data storage, and order processing. Check if the implementation includes security measures like API keys, request validation, and data encryption. Deduct 5 points if there's no proper authentication system, and 3 points if there's no error handling for API failures. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is user authentication and profile management implemented?",
-      "description": "Check if the app includes secure user registration, login, and profile management features. Verify implementation of password hashing, session management, and account recovery options. Examine if user preferences and order history are stored securely. Deduct 5 points if authentication lacks multi-factor options or secure password policies, 3 points if profile editing is limited or missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the payment processing system secure and functional?",
-      "description": "Analyze if the code includes integration with payment gateways, handles payment validation, and provides order confirmation. Check for implementation of secure payment methods, encryption of financial data, and compliance with financial regulations. Deduct 5 points if there's no payment validation logic, 3 points if receipt generation is missing, and 5 points if financial data isn't handled according to industry standards. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as network failures during ordering, payment processing errors, invalid input data, etc.) and provides friendly error prompts or recovery mechanisms. Code with strong robustness should 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 order tracking 2. AI-based food recommendations 3. Augmented reality menu visualization 4. Dietary preference filtering). 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 add items to cart) 2. Function modules unrelated to food ordering (e.g., a built-in game while waiting) 3. Fancy effects that affect performance (e.g., excessive animations when browsing menu). 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/business logic/data layers), unit test coverage, and build process automation. Examine the use of appropriate design patterns for mobile development. Deduct 5 points if global state pollution is found; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no CI/CD pipeline configuration. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the UI design follows modern mobile app design principles: 1) Consistent color scheme (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows touch-target size principles) 3) Professional typography system (readable font sizes, proper contrast ratios). Deduct 3 points for each cluttered screen, 5 points for non-responsive layouts, and 5 points for poor information hierarchy. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the app interactions conform to mobile UX best practices: 1) Touch response delay ≤ 100ms 2) Loading indicators for network operations 3) Smooth transitions between screens 4) Proper keyboard handling for form inputs. Deduct 5 points for each interaction without feedback, 3 points for jerky animations, and 5 points for difficult-to-access primary functions. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "medium"
-}

package/library/management_systems-frontend_backend_platforms/monthly-assessment-score-management-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 1509,
-  "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 possible.\n\nBased on the CREATE TABLE `tb_mon_assessment_score` (\n  `N_PK_ID` bigint NOT NULL COMMENT 'Primary Key ID',\n  `C_TEAM_CODE` varchar(32) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci DEFAULT NULL COMMENT 'Team Code',\n  `C_SALSE_CODE` varchar(32) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci DEFAULT NULL COMMENT 'Salesperson Code',\n  `C_LEADER_CODE` varchar(32) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci DEFAULT NULL COMMENT 'Team Leader',\n  `C_DEPT_CODE` varchar(32) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci DEFAULT NULL COMMENT 'Affiliated Organization',\n  `C_ASSESSMENT` varchar(10) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci DEFAULT NULL COMMENT 'Assessment Month',\n  `N_ASSESSMENT_SCORE` decimal(24,2) DEFAULT NULL COMMENT 'Assessment Score',\n  `C_REMARK` text CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci COMMENT 'Core Work This Week',\n  `C_DEL_FLAG` varchar(5) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci DEFAULT NULL COMMENT 'Delete Flag 1=Deleted, 0=Not Deleted',\n  `C_CRTR_CODE` varchar(20) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci DEFAULT NULL COMMENT 'Creator',\n  `D_CRTR_TIME` datetime DEFAULT NULL COMMENT 'Creation Time',\n  `C_UPTR_CODE` varchar(20) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci DEFAULT NULL COMMENT 'Updater',\n  `D_UPTR_TIME` datetime DEFAULT NULL COMMENT 'Update Time',\n  PRIMARY KEY (`N_PK_ID`) USING BTREE\n) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci COMMENT='Monthly Assessment Score Table';\n\nSearch Criteria:\n- Salesperson's Organization | Dropdown | Optional\n- Affiliated Team | Dropdown | Optional  \n- Salesperson | Dropdown | Optional\n- Month | Date control, range, yyyy-MM | Optional\n\nQuery List:\n- Salesperson | Auto-populated\n- Affiliated Team | Auto-populated\n- Team Leader | Auto-populated\n- Affiliated Organization | Auto-populated\n- Assessment Month | Auto-populated\n- Assessment Score | Auto-populated\n- Import Time | Auto-populated\n- Operations\n\nOperations:\n- Modify | Modify assessment score in the current list. Assessment score can only be a positive integer greater than 0. Cannot be modified if it crosses months compared to import time.\n- Delete | Cannot be modified if it crosses months compared to import time.\n\nButtons:\n- Search | Button\n- Reset | Button\n- Import | Button | Verify salesperson information, month, and assessment score during import. Generate according to previous format.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the database interaction layer fully implemented?",
-      "description": "Review whether the code correctly implements CRUD operations for the tb_mon_assessment_score table, including proper SQL query construction, parameter binding, and connection management. Check if all table fields are properly mapped and handled. Score 0 if basic database operations are missing, 5 if only basic queries are implemented without proper error handling, and 10 if all operations including complex filtering and pagination are fully implemented with proper transaction management.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the search criteria and filtering functions properly implemented?",
-      "description": "Evaluate whether all four search criteria (Organization dropdown, Team dropdown, Salesperson dropdown, Month date range) are correctly implemented with proper data validation and SQL query construction. Check if dropdowns are populated from related tables and if the month range picker works correctly with yyyy-MM format. Deduct 3 points for each missing or malfunctioning search criterion. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are the business logic validations correctly enforced?",
-      "description": "Check whether the code implements critical business rules: 1) Assessment score validation (positive integer > 0) 2) Cross-month modification restrictions based on import time 3) Data import validation for salesperson, month, and score. Review if proper error messages are displayed when validation fails. Deduct 5 points if cross-month validation is missing, 3 points if score validation is incomplete, and 2 points for each missing import validation rule. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the data import functionality robust and complete?",
-      "description": "Evaluate whether the import feature includes file format validation, data parsing, duplicate checking, batch processing, and rollback mechanisms on failure. Check if the system properly validates salesperson existence, month format, and score values during import. Deduct 5 points if batch processing is not implemented, 3 points if validation feedback is unclear, and 2 points if rollback mechanism 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 database connection failures, invalid input data, file upload errors, concurrent access issues, 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 enhance user experience?",
-      "description": "Check whether the code includes practical features that improve usability (e.g., 1. Bulk operations for multiple records 2. Export functionality with custom filters 3. Real-time validation feedback 4. Auto-save draft functionality 5. Advanced search with multi-criteria combinations). Add 2 points for each well-implemented innovative feature (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple validation logics for the same field) 2. Function modules unrelated to assessment management (e.g., built-in calculators or unrelated widgets) 3. Over-engineered features that don't add business value (e.g., complex animations on data grids). Deduct 3 points for each redundancy found, and directly deduct 10 points if 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 access layer/business logic/presentation layer), proper error handling, logging mechanisms, and code maintainability. Deduct 5 points if there's tight coupling between layers or no separation of concerns; deduct 5 points if the code duplication rate is too high (over 30%); deduct 3 points if proper logging and monitoring are not implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface design meet professional management system standards?",
-      "description": "Evaluate whether the UI follows enterprise application design principles: 1) Consistent color scheme suitable for business environment 2) Proper data grid layout with clear column headers and sorting indicators 3) Professional form design with clear labels and validation feedback 4) Intuitive navigation and operation buttons placement. Deduct 3 points for each poorly designed form element, 5 points for unprofessional color choices, and 3 points for unclear data presentation. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the user interaction smooth and intuitive?",
-      "description": "Judge whether the system interactions are optimized for business users: 1) Quick response to search and filter operations (≤ 2 seconds for typical queries) 2) Clear feedback for all operations including success/error states 3) Intuitive workflow from search to edit to save 4) Proper loading states and progress indicators. Deduct 5 points for each operation without clear feedback, 3 points for slow response times, and 5 points for confusing operation workflows. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "medium"
-}

package/library/management_systems-frontend_backend_platforms/multi-system-demo-overview.json

@@ -1,68 +0,0 @@
-{
-  "index": 1741,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Take care to ensure the code you generate is executable. Our company has 10 systems, and we now need to create a large preview page, similar to a navigation homepage, where all systems are placed together. Through accessing a domain address, with automatically filled username and password, customers can easily click to see a demonstration page. Please develop a design that is visually appealing and impressive.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the navigation homepage layout well-designed?",
-      "description": "Evaluate the layout structure for the 10 system previews. Check if it uses responsive grid design, appropriate spacing, and visual hierarchy. The layout should maintain consistency across different screen sizes. Award 10 points for a professional grid system with breakpoints for multiple devices; 5 points if only basic layout is implemented without responsiveness; 0 points if systems are placed randomly without proper structure.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the automatic authentication mechanism properly implemented?",
-      "description": "Verify the implementation of automatic username/password filling. Check if it uses secure methods (like JWT, OAuth, or secure cookies) rather than hardcoded credentials. Examine if the authentication is seamless for customers while maintaining security standards. Award 10 points for secure, seamless implementation; deduct 5 points if credentials are exposed in client-side code; 0 points if authentication doesn't work.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are the system preview cards/tiles designed professionally?",
-      "description": "Review the visual design of each system preview card/tile. Check for consistent styling, appropriate information hierarchy, system logos/icons, and clear call-to-action buttons. Each preview should give users a clear understanding of the system's purpose. Award 10 points for professionally designed cards with all necessary elements; 5 points for basic implementation; deduct points for inconsistent design across cards.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the single sign-on (SSO) mechanism for accessing multiple systems implemented?",
-      "description": "Examine how the solution handles authentication across the 10 different systems. Check if it implements proper SSO functionality to prevent users from having to log in multiple times. Verify if session management and token passing between systems are handled securely. Award 10 points for a complete SSO implementation; 5 points if only basic inter-system authentication exists; 0 points if users must authenticate separately for each system.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as authentication failures, network errors, system unavailability, 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 system previews/thumbnails 2. Custom theme selector for the navigation interface 3. Usage statistics dashboard for each system). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple authentication methods coexisting) 2. Function modules unrelated to navigation/preview (e.g., a built-in calculator) 3. Fancy effects that affect performance (e.g., heavy animations that slow page loading). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating authentication/UI/navigation logic), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern 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": "easy"
-}

package/library/management_systems-frontend_backend_platforms/murder-mystery-game-material-management.json

@@ -1,68 +0,0 @@
-{
-  "index": 466,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable for demonstration. ======== ROLE ========\nYou are an experienced code expert. You are given a software development requirement description, and you need to generate project code according to this requirement. 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 that the project is fully executable\n2. Ensure that all code files you output are complete, do not omit any code\n3. Carefully review and check all code before the final output, evaluating its executability. If the code cannot be executed or contains errors, it needs to be regenerated\n4. If the requirements involve external API access or the need to use user data (images, videos, audio, etc.), please provide simulated data\n\n======== PROJECT REQUIREMENTS ========\nImplement a murder mystery game material management system that supports uploading character scripts and clue card images and associating them with plot nodes. Provide clue distribution control functions (unlocked according to game progress), including player-side APP data synchronization interface (displaying obtained clues).",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core data model structure for the mystery game management system properly implemented?",
-      "description": "Evaluate whether the data model includes essential entities: Game/Case, Characters, Plot Nodes, Clues, and their relationships. The model should support hierarchical relationships between these entities. Score 0 if core entities are missing, 5 if basic relationships exist but lack necessary fields, and 10 if the model is comprehensive with proper normalization and indexing for efficient queries.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the character script management functionality complete?",
-      "description": "Check if the system allows uploading, editing, versioning, and associating character scripts to specific plot nodes. The implementation should include script formatting, character-specific views, and timeline organization. Deduct 3 points if versioning is missing, 4 points if there's no ability to associate scripts with plot points, and 3 points if formatting options are limited. Full score requires conflict resolution for collaborative editing.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the clue card image management system properly implemented?",
-      "description": "Assess whether the system handles image uploads with proper validation (file types, size limits), provides image manipulation features (cropping, resizing), includes metadata management, and allows tagging/categorization of clues. Deduct 3 points for missing image validation, 3 points for lack of preview functionality, and 4 points if there's no option to associate images with specific plot points or characters.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the plot node progression system and clue distribution logic implemented?",
-      "description": "Evaluate the implementation of conditional unlocking of clues based on game progress. The system should include a rule engine for triggering clue availability, dependencies between clues, and time-based or action-based unlock mechanisms. Deduct 5 points if conditions can't be customized, 3 points if there's no visual timeline/flowchart representation, and 2 points if testing/simulation tools for progression are missing.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid uploads, concurrent edits, network interruption, user operation errors, 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. AI-assisted mystery plot generation 2. Real-time collaborative game master tools 3. Voice narration for clues 4. Augmented reality clue visualization). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple image upload systems coexisting) 2. Function modules unrelated to mystery game management (e.g., a built-in social network) 3. Fancy effects that affect performance (e.g., unnecessary animations in admin panels). 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 model/controller/view 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 player-side APP data synchronization interface well-implemented?",
-      "description": "Judge whether the synchronization mechanism meets requirements: 1) REST/GraphQL API for clue retrieval with proper authentication 2) Real-time updates via WebSockets/polling with ≤ 2s delay 3) Offline mode with local storage and conflict resolution when reconnecting. Deduct 4 points if authentication is weak or missing, 3 points if synchronization is only one-way, and 3 points if there's no offline capability. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "hard"
-}