@getollie/cli 0.0.5 → 0.2.0

package/library/management_systems-frontend_backend_platforms/intelligent-manufacturing-command-center.json

@@ -1,68 +0,0 @@
-{
-  "index": 1254,
-  "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 purposes. Change the data to 'Intelligent Manufacturing Base Command Center' with table headers as follows: Order Number, Work Order, Work Order Description, Project Quantity, Planned Progress, Actual Progress, Planned Start Time, Planned Completion Time, Actual Start Time, Current Process, Status, Abnormal Status. Please randomly generate data according to these headers and return the complete code.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the intelligent manufacturing command center data structure correctly implemented?",
-      "description": "Review whether the code accurately implements all required table headers (Order Number, Work Order, Work Order Description, Project Quantity, Planned Progress, Actual Progress, Planned Start Time, Planned Completion Time, Actual Start Time, Current Process, Status, Abnormal Status) with appropriate data types and logical relationships. Score 0 if core data fields are missing, 5 if basic structure exists but lacks proper validation, and 10 if all fields are properly structured with realistic manufacturing data patterns.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the random data generation logic realistic and comprehensive?",
-      "description": "Check whether the randomly generated data follows manufacturing industry standards and logical consistency (e.g., actual start time should not precede planned start time, progress values should be between 0-100%, status should correlate with progress). Deduct 5 points if data lacks manufacturing context realism, 3 points if temporal logic is inconsistent. Full score requires at least 20+ realistic data entries with proper manufacturing workflow simulation.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the command center dashboard visualization effectively implemented?",
-      "description": "Evaluate whether the interface resembles a professional manufacturing command center with appropriate data presentation methods (tables, charts, status indicators). Should include real-time status visualization and progress tracking elements. Deduct 5 points if only basic table display is implemented, 3 points if missing manufacturing-specific visual elements like progress bars or status indicators. Full score requires comprehensive dashboard layout.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are manufacturing-specific features and interactions properly integrated?",
-      "description": "Check whether the code includes manufacturing command center specific functionalities such as filtering by status, sorting by priority, progress monitoring, and abnormal status alerts. Should provide search/filter capabilities for work orders and real-time status updates. Deduct 5 points if basic manufacturing workflow features are missing, 3 points if interaction capabilities are limited. Give 10 points if comprehensive manufacturing management features are implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid date ranges, null data entries, progress value overflows, status inconsistencies, 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 manufacturing command center experience (e.g., 1. Real-time production efficiency analytics 2. Predictive delay warnings 3. Interactive Gantt chart visualization 4. Export functionality for production 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 sorting mechanisms coexisting) 2. Function modules unrelated to manufacturing command center (e.g., built-in games or entertainment features) 3. Fancy effects that affect performance (e.g., excessive animations on data tables). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core manufacturing data display 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 generation/presentation/interaction layers), code organization, and maintainability. 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 code structure is not scalable for additional manufacturing data types. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional command center design standards?",
-      "description": "Evaluate whether the overall design follows industrial command center aesthetics: 1) Professional color scheme suitable for manufacturing environment (dark themes preferred) 2) Clear data hierarchy and readable typography (body font size ≥ 14px, line height over 1.5 times) 3) Appropriate use of status colors (red for abnormal, green for normal, yellow for warning). Deduct 3 points for each unclear visual element, 5 points for unprofessional color combinations, and 5 points for poor data readability. 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 command center operation requirements: 1) Data loading and filtering response time ≤ 200ms 2) Smooth table sorting and pagination transitions 3) Clear visual feedback for user interactions 4) Appropriate hover and selection states. Deduct 5 points for each operation without feedback, 3 points for laggy data operations, and 5 points for unclear interactive elements. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "hard"
-}

package/library/management_systems-frontend_backend_platforms/intelligent-meeting-room-booking-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 1686,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable for demonstration purposes. Explain how to implement an intelligent meeting room booking system using qwen-vl-max frontend, with detailed booking information displayed on the page that can be edited.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the intelligent meeting room booking system interface fully implemented?",
-      "description": "Review whether the code accurately implements the meeting room booking interface with essential components like calendar view, room selection, time slot picking, and booking form. Score 0 if core UI elements are missing, 5 if only basic interface is implemented without intelligent features, 10 if the complete system with intelligent recommendations and visual feedback is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the qwen-vl-max integration properly implemented for image recognition?",
-      "description": "Check if the code properly integrates with qwen-vl-max for intelligent visual features (such as recognizing room occupancy from images, detecting equipment in meeting rooms, or processing floor plans). Deduct 5 points if the integration is superficial, 3 points if error handling for API calls is missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the booking information display and editing functionality complete?",
-      "description": "Evaluate whether users can view detailed booking information (meeting title, time, participants, room details) and edit this information with proper validation. Check for real-time updates and conflict prevention. Deduct 5 points if editing lacks validation, 3 points if the display is incomplete. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there intelligent recommendation or optimization in the booking system?",
-      "description": "Assess whether the system includes AI-powered features such as room recommendations based on meeting size, equipment needs, or user preferences; smart conflict resolution; or predictive scheduling. Deduct 5 points if recommendations are generic, 3 points if user preferences aren't considered. 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, concurrent bookings, invalid user inputs, 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 room availability indicators 2. Meeting analytics dashboard 3. Integration with calendar systems 4. Voice commands for booking). 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 calendar components) 2. Function modules unrelated to meeting room booking (e.g., a news feed) 3. Fancy effects that affect performance (e.g., unnecessary 3D 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 booking logic/UI components/API services), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern 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/intelligent-turtle-tank-management-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 1459,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to generate executable code for demonstration when possible. Create an intelligent turtle tank management system.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the turtle tank monitoring system fully implemented?",
-      "description": "Review whether the code accurately implements essential monitoring functionalities such as water temperature, pH level, clarity sensors, and automatic alerts. Score 0 if the core monitoring logic is not implemented, 5 if only basic parameter tracking is included, and 10 if comprehensive monitoring with threshold-based alerts is fully implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the automated feeding system properly designed?",
-      "description": "Check whether the code includes a scheduling mechanism for feeding, portion control, and feeding history logs. Verify if there's a manual override option and emergency protocols if the feeding system malfunctions. Deduct 3 points if scheduling is inflexible, 3 points if portion control isn't implemented, and 4 points if there's no failure handling mechanism. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the water quality maintenance system implemented?",
-      "description": "Evaluate whether the system includes water filtration control, water change scheduling, and water quality trend analysis. Check if there are automatic responses to water quality degradation and predictive maintenance alerts. Deduct 5 points if automatic responses are missing and 5 points if trend analysis isn't implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the turtle health monitoring and tracking system designed?",
-      "description": "Assess whether the code includes functionalities for tracking individual turtle data (weight, size, activity levels, feeding patterns), health anomaly detection, and growth visualization tools. Deduct 3 points if individual tracking is absent, 4 points if health anomaly detection isn't implemented, and 3 points if there's no historical data visualization. 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 sensor failures, power outages, connectivity issues, or hardware malfunctions) and provide failsafe mechanisms or recovery procedures. Code with strong robustness should gracefully 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": "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 turtle behavior analysis 2. Augmented reality view of the tank ecosystem 3. Voice-controlled system commands). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple notification systems that serve the same purpose) 2. Function modules unrelated to turtle care (e.g., a built-in game) 3. Resource-intensive features that affect system performance (e.g., unnecessary high-definition video processing). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (separating sensor/control/UI layers), test coverage for critical functions (especially safety-related ones), and deployment configuration. Deduct 5 points if global state pollution is found or proper design patterns are not used; deduct 5 points if error handling is inconsistent or inadequate; deduct 5 points if there's no configuration for different deployment environments. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the dashboard design follows modern design principles: 1) Harmonious color matching that prioritizes data readability 2) Proper layout with critical information prominently displayed 3) Consistent iconography and information hierarchy. Deduct 3 points for cluttered displays, 5 points for poor color choices that reduce readability, and 5 points for confusing navigation between system functions. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the system interactions meet usability standards: 1) Real-time data updates without UI freezing 2) Clear visual feedback for user actions 3) Intuitive control flows for routine tasks. Deduct 5 points for laggy or freezing interfaces, 3 points for confusing action confirmations, and 5 points for requiring excessive clicks for common tasks. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "hard"
-}

package/library/management_systems-frontend_backend_platforms/inventory-management-app-with-pricing-and-time.json

@@ -1,68 +0,0 @@
-{
-  "index": 734,
-  "question": "You are a code expert. Please utilize your professional knowledge to generate accurate and professional responses. Be sure to provide executable code when possible. Can you help me design an inventory management app? It should include features for tracking purchase prices, sales prices, and time-related information.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the inventory data management system fully implemented?",
-      "description": "Review whether the code accurately implements inventory item tracking with proper data structures for storing purchase prices, sales prices, quantities, and time-related information (purchase date, expiry date, last updated). Check if CRUD operations are properly implemented with data validation. Score 0 if core inventory operations are missing, 5 if only basic add/remove is implemented, and 10 if comprehensive inventory management with price tracking and temporal data is fully included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the price tracking and profit calculation functionality implemented?",
-      "description": "Check whether the system includes accurate purchase price recording, sales price management, and automatic profit margin calculations. Verify if price history tracking is implemented and supports multiple pricing tiers. Deduct 5 points if profit calculations are incorrect, and 3 points if price history is not maintained. Evaluate whether bulk pricing and discount mechanisms are handled properly. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is comprehensive time-based tracking and reporting designed?",
-      "description": "Evaluate whether the system implements proper timestamp management for all inventory operations, including purchase dates, sales transactions, and stock movements. Check if time-based reports (daily, weekly, monthly sales) are generated accurately. Deduct 5 points if date filtering is not functional. Verify if expiry date tracking and low-stock alerts based on time thresholds are implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is data persistence and backup mechanism constructed?",
-      "description": "Check whether the code includes reliable data storage solutions (localStorage, IndexedDB, or server-side database integration) with proper data serialization. Evaluate if backup and restore functionality is implemented to prevent data loss. Deduct 5 points if data persistence is unreliable, and 3 points if no backup mechanism exists. Verify if data export/import features (CSV, JSON) are available. Give 10 points if fully implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid price inputs, negative quantities, date format errors, data corruption, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should validate all user inputs, handle edge cases gracefully, and provide clear error messages. Give 10 points for comprehensive error handling, 5 points if robustness is average, and 0 points if no exceptions are handled.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes value-added features that enhance inventory management (e.g., 1. Barcode scanning integration 2. Automated reorder point calculations 3. Supplier comparison tools 4. Mobile-responsive design 5. Advanced analytics dashboard). Evaluate practical utility and implementation quality. Add 3 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 price calculation methods coexisting) 2. Function modules unrelated to inventory management (e.g., built-in games or social features) 3. Excessive animations or effects that slow down inventory operations. Deduct 3 points for each redundancy found, and directly deduct 10 points if core inventory 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 layer/business logic/presentation layers), code organization, and maintainability. Deduct 5 points if global state pollution is found or proper architecture patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if no error logging or debugging mechanisms exist. Evaluate if the codebase follows consistent naming conventions and documentation standards. 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 business application principles: 1) Professional color scheme suitable for business use (no more than 3 primary colors) 2) Proper data table layout with clear hierarchy (consistent spacing following 8px grid) 3) Readable typography system (body font ≥ 14px, proper contrast ratios). Deduct 3 points for each cluttered interface element, 5 points for unprofessional color choices, and 5 points for poor data presentation layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and efficient?",
-      "description": "Judge whether the interface interactions optimize workflow efficiency: 1) Form submission feedback ≤ 100ms 2) Data loading transitions between 300-500ms 3) Clear visual feedback for all user actions 4) Efficient keyboard shortcuts for common operations. Deduct 5 points for each operation without immediate feedback, 3 points for slow data table rendering, and 5 points for confusing navigation or hard-to-find essential functions. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "medium"
-}

package/library/management_systems-frontend_backend_platforms/inventory-management-system-with-alerts.json

@@ -1,68 +0,0 @@
-{
-  "index": 619,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Ensure that the code you generate is executable for demonstration. Please build an inventory management system. Merchants can add new products through the front-end interface, edit product information (name, price, inventory quantity, etc.), and set low inventory alert functions (displaying warnings when inventory falls below a threshold).",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the product CRUD functionality fully implemented?",
-      "description": "Review whether the code accurately implements all Create, Read, Update, and Delete operations for products. Check if the form validation includes required fields (name, price, quantity), data type validation (price as number), and constraint checks (non-negative values for price and quantity). Score 0 if core CRUD operations are missing, 5 if basic operations are implemented without proper validation, and 10 if all operations are implemented with comprehensive validation.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the inventory alert system properly implemented?",
-      "description": "Evaluate whether merchants can set custom threshold values for low inventory alerts. Check if the system provides visual indicators (color coding, icons) when inventory falls below thresholds, and if notifications are displayed in an appropriate manner (not blocking normal operation). Deduct 5 points if threshold configuration is missing, 3 points if visual indicators aren't clear, and 2 points if there's no way to manage/dismiss alerts. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the data persistence mechanism properly designed?",
-      "description": "Check whether the application implements proper data storage (local storage, IndexedDB, or backend database) with error handling for storage failures. Verify if data synchronization occurs at appropriate times (after edits, periodically) and if there's data loss protection when the browser unexpectedly closes. Deduct 5 points for lack of persistence, 3 points for insufficient error handling, and 2 points for missing optimization strategies (like batch updates). The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the inventory history and tracking system implemented?",
-      "description": "Verify if the system tracks inventory changes with timestamps and user information. Check for features like inventory audit trails, change history visualization, and inventory trend analysis. The system should allow filtering/sorting of history records. Deduct 3 points if timestamp tracking is missing, 3 points if there's no way to view history, and 4 points if the history doesn't capture all relevant events (additions, edits, threshold changes). 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 invalid inputs, network failures, concurrent edits, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should prevent data corruption and have proper exception handling throughout the application. Give 10 points for comprehensive error handling, 5 points for basic validation only, and 0 points if errors cause the application to crash.",
-      "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. Barcode/QR code scanning for quick product lookup 2. Export/import functionality for bulk operations 3. Dashboard with inventory analytics 4. Image management for products). 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 edit the same data) 2. Function modules unrelated to inventory management (e.g., built-in games or media players) 3. Fancy effects that affect performance (e.g., excessive animations or 3D effects). 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/UI components/services), code organization, naming conventions, and reusability. Deduct 5 points if global state management is poorly implemented; deduct 3 points if there's significant code duplication; deduct 2 points if naming conventions are inconsistent or unclear. Check for appropriate comments and documentation. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the UI follows modern inventory management design principles: 1) Clean data display with proper table/grid layouts 2) Consistent color coding for inventory status (low/normal/excess) 3) Professional forms with clear labels and validation feedback. Deduct 3 points for cluttered information display, 4 points for poor information hierarchy, and 3 points for inconsistent styling across the application. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the interactions serve business efficiency: 1) Quick-edit capabilities without excessive page reloads 2) Bulk operations for managing multiple products 3) Responsive filtering and searching with < 200ms response time. Deduct 4 points for requiring multiple clicks for common tasks, 3 points for sluggish responses in data operations, and 3 points for lack of keyboard shortcuts or efficiency features. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "easy"
-}

package/library/management_systems-frontend_backend_platforms/inventory-management-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 480,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be mindful to ensure the generated code is executable for demonstration. Develop an inventory management system where users can add, edit and delete inventory items, track inventory quantities, set minimum inventory warning thresholds, generate inventory reports, and support barcode scanning functionality.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the inventory item CRUD system fully implemented?",
-      "description": "Review whether the code accurately implements complete inventory item management through proper data structures and UI components, including add/edit/delete operations with field validation (item name, SKU, category, price, quantity, etc.). Score 0 if core CRUD operations are not implemented, 5 if only basic add/delete is implemented, and 10 if all operations include proper validation, duplicate prevention, and batch operations.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the inventory quantity tracking and threshold warning system implemented?",
-      "description": "Check whether the system includes real-time inventory quantity tracking with automatic updates, configurable minimum stock thresholds, and proactive warning mechanisms (visual alerts, notifications, email triggers). Deduct 5 points if quantity updates are not real-time, and 3 points if warning thresholds cannot be customized per item. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the inventory reporting and analytics functionality designed comprehensively?",
-      "description": "Evaluate whether the system generates comprehensive inventory reports including stock levels, movement history, low-stock alerts, and value calculations. Reports should support multiple formats (PDF, Excel, CSV) and date range filtering. Deduct 5 points if reports lack visual charts/graphs, and 3 points if export functionality is missing. Check whether historical data tracking and trend analysis are implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the barcode scanning functionality integrated effectively?",
-      "description": "Check whether the code includes barcode scanning capabilities using camera API or external scanner integration, with proper barcode format recognition (UPC, EAN, Code128, etc.). Evaluate scanner UI responsiveness, error handling for unrecognized codes, and seamless integration with inventory lookup/addition workflows. Deduct 5 points if camera permission handling is missing, and 3 points if multiple barcode formats are not supported. Give 10 points if fully implemented with offline scanning capability.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid input data, network failures, database connection issues, concurrent access conflicts, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should include input sanitization, transaction rollback, and graceful degradation, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. AI-powered demand forecasting 2. Mobile app with offline sync 3. Integration with suppliers for automatic reordering 4. Multi-location inventory tracking 5. Photo recognition for item identification). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple validation logics for the same field) 2. Function modules unrelated to inventory management (e.g., built-in games or social features) 3. Overly complex animations that affect performance (e.g., excessive transitions on data tables). Deduct 3 points for each redundancy found, and directly deduct 10 points if core inventory 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 layer/business logic/presentation layers), proper error handling, database optimization, and security measures. Deduct 5 points if SQL injection vulnerabilities exist or input validation is missing; deduct 5 points if the code lacks proper separation of concerns; deduct 5 points if database queries are not optimized for large datasets. 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 with proper contrast ratios for accessibility 2) Consistent layout spacing using grid systems 3) Professional typography with readable font sizes (≥14px for body text) 4) Intuitive navigation and information hierarchy. Deduct 3 points for each cluttered interface section, 5 points for poor color accessibility, and 5 points for inconsistent design patterns. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects enhance user experience: 1) Form submissions provide immediate feedback 2) Data table sorting/filtering responds within 200ms 3) Loading states are clearly indicated 4) Barcode scanning provides real-time visual feedback. Deduct 5 points for each operation without proper feedback, 3 points for slow data table performance with large datasets, and 5 points for confusing navigation or unclear action buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "medium"
-}

package/library/management_systems-frontend_backend_platforms/investment-project-economic-evaluation-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 1444,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code for demonstration whenever possible. Help me create an investment project economic evaluation system.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core financial calculation system properly implemented?",
-      "description": "Check whether the code accurately implements essential financial metrics (NPV, IRR, ROI, payback period, etc.) with correct mathematical formulas. Score 0 if core financial calculations are missing, 5 if basic calculations exist but contain formula errors, and 10 if all calculations are accurate with proper edge case handling (e.g., negative cash flows, irregular periods).",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the investment project data modeling comprehensive?",
-      "description": "Evaluate if the code includes a complete data model for investment projects with appropriate entities (project details, cash flow projections, financing sources, risk factors, etc.). Deduct 3 points if key financial parameters are missing, 3 points if there's no provision for different investment types, and 4 points if time-value adjustments (inflation, discounting) aren't supported. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are sensitivity and risk analysis functions implemented?",
-      "description": "Check whether the system can perform sensitivity analysis on key parameters and quantify risk factors (e.g., Monte Carlo simulation, scenario analysis). Deduct 5 points if sensitivity analysis is missing, 3 points if risk quantification methods are absent, and 2 points if there's no visualization of risk distribution. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the comparative analysis system functional?",
-      "description": "Assess whether the code enables direct comparison between multiple investment options, including ranking mechanisms, standardized metrics, and weighted multi-criteria decision support. Deduct 4 points if no direct comparison visualization exists, 3 points if the comparison lacks normalization for different project scales, and 3 points if there's no support for custom evaluation criteria. 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 invalid inputs, missing data, calculation errors, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should include input validation, error handling for financial edge cases (like division by zero in calculations), and data integrity checks. Give 10 points for comprehensive error handling, 5 points for partial implementation, and 0 points if exceptions are unhandled.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Real-time market data integration 2. AI-powered investment recommendations 3. Automated report generation with executive summaries 4. Industry benchmarking). 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 calculations (e.g., multiple NPV calculation methods) 2. Function modules unrelated to investment evaluation (e.g., accounting features that should be in a separate system) 3. Overly complex visualizations that obscure financial insights. 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 calculation logic/view/data layers), unit test coverage especially for financial calculations, 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 financial software standards?",
-      "description": "Evaluate whether the design follows professional financial software principles: 1) Clean, business-appropriate color scheme (preferably with white background and accent colors for highlighting) 2) Well-organized data tables and charts with proper spacing 3) Clear visual hierarchy for financial metrics (primary KPIs emphasized). Deduct 3 points for cluttered financial dashboards, 5 points for poor data visualization choices, and 5 points for inconsistent financial terminology. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the data visualization effective and insightful?",
-      "description": "Judge whether the financial visualizations follow best practices: 1) Appropriate chart types for different financial metrics (e.g., cash flow waterfall charts, IRR comparison bar charts) 2) Interactive elements allowing drill-down into calculation details 3) Clear labeling of financial data with proper units and time periods. Deduct 5 points for misleading visualizations, 3 points for poor choice of chart types, and 5 points for missing critical financial context in charts. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "hard"
-}

package/library/management_systems-frontend_backend_platforms/investment-system-with-realtime-market-data.json

@@ -1,68 +0,0 @@
-{
-  "index": 457,
-  "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. I am committed to making investment my lifelong hobby and second career. I want to build a stable and profitable investment system that includes stock selection, buy/sell point identification, and position management functions. I need to integrate these features into a frontend software. This software should be able to automatically and independently obtain real-time information about stocks and other markets from public free sources. I have Visual Studio Code software. Please help me generate standalone software that can meet all my requirements above.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the stock selection system fully implemented?",
-      "description": "Review whether the code implements comprehensive stock selection criteria including technical indicators (e.g., RSI, MACD, Moving Averages), fundamental analysis (P/E ratio, EPS growth, etc.), and market sentiment analysis. Check if the system allows for customizable screening parameters and saving favorite screening configurations. Score 0 if no selection system is implemented, 5 if only basic technical indicators are available, and 10 if it includes a comprehensive multi-factor model with backtesting capabilities.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the buy/sell signal identification algorithms implemented effectively?",
-      "description": "Evaluate whether the code includes multiple technical analysis algorithms for identifying entry/exit points (candlestick patterns, support/resistance levels, volume analysis). Check if it provides visual indicators on charts for identified signals and includes confidence levels for each signal. The system should allow for customizable signal parameters. Deduct 5 points if signals are based solely on single indicators without confirmation strategies, and 3 points if historical accuracy metrics for signals are not provided. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the position management functionality comprehensive?",
-      "description": "Assess whether the code implements portfolio management features including position sizing calculations, risk management rules (stop-loss, take-profit settings), diversification analysis, and overall portfolio performance metrics. Check if it includes scenario analysis for different market conditions. Deduct 5 points if position sizing is simplistic (e.g., fixed percentages only), and 3 points if there's no correlation analysis between holdings. Give 10 points if fully implemented with dynamic risk adjustment capabilities.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the real-time data acquisition system robust and compliant?",
-      "description": "Evaluate if the code effectively obtains market data from free public APIs (like Yahoo Finance, Alpha Vantage) with proper rate limiting, fallback mechanisms, and cache strategies. Check for data validation and error handling for API failures. System must respect API terms of service and include proper attribution. Deduct 5 points for hardcoded API keys, 5 points for missing retry logic, and 5 points for no data freshness indicators. 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, network interruption, invalid user inputs, 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-based sentiment analysis from news sources 2. Auto-correlation with major economic indicators 3. Pattern recognition from historical market crashes 4. Visualized risk exposure heat maps). 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 indicators (e.g., multiple versions of RSI calculations) 2. Function modules unrelated to investment analysis (e.g., a built-in social media client) 3. Fancy visualizations that sacrifice performance (e.g., 3D charts that obscure data). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating data acquisition/analysis/visualization layers), unit test coverage for calculation accuracy, 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 financial dashboard standards?",
-      "description": "Evaluate whether the design follows professional financial interface principles: 1) Color schemes appropriate for financial data (red/green contrasts for gains/losses, muted backgrounds) 2) Information density optimized for scanning large datasets 3) Professional typography for numerical data (monospaced fonts for alignment, appropriate decimal precision). Deduct 3 points for cluttered dashboards, 5 points for indistinguishable data series in charts, and 5 points for poor information hierarchy. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and responsive for investment decision-making?",
-      "description": "Judge whether the interface facilitates rapid investment decisions: 1) Chart interactions respond in under 100ms 2) Data refresh rates are configurable based on market volatility 3) Critical alerts have distinct visual and optional audio cues. Deduct 5 points for charts that lag during period changes, 3 points for confusing tooltip behaviors, and 5 points for hard-to-access critical functions during market hours. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "hard"
-}