@getollie/cli 0.0.5 → 0.2.1

package/library/management_systems-frontend_backend_platforms/student-scoring-math-groups.json

@@ -1,68 +0,0 @@
-{
-  "index": 389,
-  "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. Write an HTML code with the functionality of: scoring students in different math groups.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the student grouping and management system fully implemented?",
-      "description": "Review whether the code accurately implements student group creation, editing, and deletion through HTML/JavaScript, and whether it includes dynamic group member management (add/remove students), group information display, and group switching functionality. Score 0 if core grouping logic is not implemented, 5 if only basic group display is implemented, and 10 if complete group management with validation is included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the scoring system comprehensively implemented?",
-      "description": "Check whether the scoring functionality includes multiple input methods (individual scoring, batch scoring, import from file), score validation (range checking, format validation), real-time score updates, and score history tracking. Deduct 5 points if input validation is missing, and 3 points if score modification/deletion functionality is not handled. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the data persistence and storage mechanism designed?",
-      "description": "Evaluate whether the system uses appropriate client-side storage (localStorage/sessionStorage/IndexedDB) to persist student data, group configurations, and scoring records. Check whether data import/export functionality is provided (JSON/CSV format support). Deduct 5 points if data is lost on page refresh. Check whether backup and recovery mechanisms are implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are statistical analysis and reporting features constructed?",
-      "description": "Check whether the code includes comprehensive statistical analysis such as group performance comparison, individual student progress tracking, average/median/percentile calculations, and visual charts or graphs. Deduct 5 points if no statistical calculations are implemented, and 3 points if results are not displayed in an organized manner. Give 10 points if comprehensive analytics with visual representation are fully implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid input, empty data sets, duplicate student names, malformed import files, 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. Automatic grade calculation with customizable weights 2. Progress tracking with timeline visualization 3. Collaborative scoring with multiple teacher accounts 4. Mobile-responsive design with touch interactions). 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 scoring input methods that serve the same purpose) 2. Function modules unrelated to student scoring (e.g., built-in games or entertainment features) 3. Excessive animations that affect usability (e.g., overly complex transitions for simple operations). 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 management/UI rendering/calculation logic), code organization and structure, and consistent coding patterns. Deduct 5 points if global state pollution is found or proper separation of concerns is not implemented; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if inconsistent naming conventions or poor code documentation. 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 educational software design principles: 1) Clean and professional color scheme suitable for educational context (no more than 3 primary colors) 2) Proper layout spacing with clear visual hierarchy (element spacing follows consistent grid system) 3) Readable typography (body font size ≥ 14px, sufficient contrast ratios). Deduct 3 points for each cluttered visual element, 5 points for unprofessional color combinations, and 5 points for poor information architecture. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the user interactions conform to educational software usability standards: 1) Form input feedback and validation in real-time 2) Smooth transitions between different views/groups (300-500ms duration) 3) Clear visual indicators for active states and user actions 4) Intuitive navigation and workflow. Deduct 5 points for each operation without proper feedback, 3 points for confusing user flow, and 5 points for hard-to-discover 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/subway-arrival-time-display-board.json

@@ -1,68 +0,0 @@
-{
-  "index": 961,
-  "question": "You are a coding expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the code you generate is executable for demonstration. Design a program for a subway arrival time display board.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core subway arrival time display functionality implemented?",
-      "description": "Review whether the code accurately implements real-time display of train arrival times, including station names, train destinations, and countdown timers. Score 0 if the core display functionality is missing, 5 if only static data is shown, and 10 if dynamic updates with simulated or real data feeds are implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Does the implementation include multi-line subway information handling?",
-      "description": "Evaluate the code's ability to handle and display information for multiple subway lines simultaneously, with proper visual differentiation (color coding, icons, etc.). Deduct 5 points if only a single line is supported, 3 points if multiple lines are supported but poorly differentiated. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is there a data update and synchronization mechanism?",
-      "description": "Check whether the code includes mechanisms for fetching and updating train arrival data (API calls, WebSocket connections, or simulated data generation). Score 0 if no update mechanism exists, 5 if basic periodic updates are implemented, and 10 if there's a robust real-time synchronization system with error handling for connectivity issues.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the implementation include user-focused features?",
-      "description": "Assess whether user-friendly features are implemented, such as station selection, line filtering, platform identification, or accessibility options. Deduct 5 points if no user interaction is possible, 3 points if minimal options are available. Give 10 points for comprehensive user features that enhance the practical usability of the display board.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as data feed interruptions, malformed data, missing trains, etc.) and provide fallback displays 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. Transit alerts/notifications 2. Multilingual support 3. Interactive map integration). 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 display the same information) 2. Function modules unrelated to subway displays (e.g., a built-in weather forecaster) 3. Fancy effects that affect performance (e.g., excessive animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating data fetching/processing/display layers), code reusability, and maintenance considerations. 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 there's no consideration for deployment or configuration options. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional transit display standards?",
-      "description": "Evaluate whether the design follows transit information display best practices: 1) High contrast for readability at distance 2) Clear visual hierarchy prioritizing essential information 3) Appropriate use of color coding for line identification. Deduct 3 points for each readability issue, 5 points for confusing information architecture, and 5 points for poor contrast that would affect visibility in public spaces. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the display responsive to different viewing contexts?",
-      "description": "Judge whether the display adapts appropriately to different viewing scenarios: 1) Different screen sizes and orientations 2) Visibility considerations for public displays (large text, high contrast) 3) Performance optimization for continuous operation. Deduct 5 points for fixed-size designs that don't scale, 3 points for display elements that would be illegible at typical viewing distances, and 5 points for implementations that would degrade with continuous operation. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "easy"
-}

package/library/management_systems-frontend_backend_platforms/supermarket-smart-locker-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 1210,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the code you generate is executable and demonstrable. Please write a complete smart locker system for a supermarket and teach me how to use it.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the smart locker hardware simulation system fully implemented?",
-      "description": "Review whether the code accurately simulates locker hardware through HTML/JavaScript, including locker grid layout, electronic lock status indicators, RFID/QR code scanning simulation, and payment terminal integration. Score 0 if core hardware simulation is missing, 5 if only basic locker display is implemented, and 10 if complete hardware interaction simulation including sensors, displays, and payment systems is fully included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the user authentication and rental process implemented?",
-      "description": "Check whether the system includes multiple authentication methods (QR code, RFID card, mobile app), rental flow management, and real-time locker availability updates. The system should handle user registration, payment processing, and locker assignment logic. Deduct 5 points if payment integration is missing, and 3 points if user session management is not handled properly. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the locker management and monitoring system designed with admin functionality?",
-      "description": "Evaluate whether the admin panel includes real-time locker status monitoring, maintenance alerts, usage analytics, and remote control capabilities. The system should provide occupancy tracking, fault detection, and automated cleaning schedules. Deduct 5 points if real-time monitoring is not implemented, and 3 points if maintenance workflow is missing. Check whether emergency override and bulk operations are available. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the complete rental lifecycle and data persistence constructed?",
-      "description": "Check whether the code includes complete rental lifecycle management, including booking, access, extension, and return processes. Evaluate data persistence for user history, payment records, and system logs. Deduct 5 points if database integration is not implemented, and 3 points if rental history tracking is missing. Give 10 points if complete data management with backup and recovery mechanisms are fully implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as payment failures, hardware malfunctions, network interruptions, invalid access attempts, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should include retry mechanisms, fallback procedures, and comprehensive error logging, 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 user experience (e.g., 1. AI-powered optimal locker recommendation 2. Mobile app integration with push notifications 3. Social sharing of locker locations 4. Predictive maintenance alerts 5. Multi-language support). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple payment processing logics coexisting) 2. Function modules unrelated to locker management (e.g., built-in games or social media feeds) 3. Overly complex animations that affect performance (e.g., excessive 3D effects on locker doors). Deduct 3 points for each redundancy found, and directly deduct 10 points if core locker 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/payment/hardware control layers), database schema design, API structure, and error handling patterns. Deduct 5 points if global state pollution is found or proper MVC/MVP patterns are not used; deduct 5 points if code duplication rate is too high (over 30%); deduct 5 points if no input validation or security measures are implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface design meet professional kiosk standards?",
-      "description": "Evaluate whether the UI design follows kiosk usability principles: 1) High contrast colors suitable for various lighting conditions 2) Large touch targets (minimum 44px) with adequate spacing 3) Clear visual hierarchy with prominent call-to-action buttons 4) Accessibility features for disabled users. Deduct 3 points for each hard-to-read text element, 5 points for poor color contrast ratios, and 5 points for cramped button layouts unsuitable for touch interaction. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the user workflow intuitive and efficient?",
-      "description": "Judge whether the user journey is optimized for quick transactions: 1) Rental process completable within 60 seconds 2) Clear progress indicators and next-step guidance 3) Minimal cognitive load with simple instructions 4) Effective error recovery paths. Deduct 5 points for each confusing workflow step, 3 points for missing progress feedback, and 5 points for unclear error messages that don't guide users to resolution. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "hard"
-}

package/library/management_systems-frontend_backend_platforms/survey-analysis-tool-with-advanced-features.json

@@ -1,68 +0,0 @@
-{
-  "index": 611,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be careful to ensure that the code you generate is executable for demonstration. Implement a survey analysis tool that supports creation of various question types, setting up skip logic, and generating statistical charts (such as heatmaps for matrix questions) after collecting results. The implementation should include CSV export of response data and progress tracking for form completion.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the survey creation system fully implemented?",
-      "description": "Review whether the code provides a comprehensive interface for creating various question types (single choice, multiple choice, matrix, open-ended, rating scales). Check if the question configuration allows for required/optional settings, help text, and input validation. Award 3 points for each major question type fully implemented, 0 if core question types are missing, and 10 if all standard survey question types plus advanced options are present.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the skip logic functionality properly implemented?",
-      "description": "Evaluate the complexity of conditional logic the system supports. Check for: 1) Basic conditional display based on previous answers, 2) Multiple condition combinations (AND/OR logic), 3) Skip patterns that can span multiple questions, 4) Proper validation handling with skip logic. Deduct 3 points if only basic conditions are supported, 5 points if complex conditions aren't handled, and 10 points if skip logic is missing entirely. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are the statistical visualization components properly implemented?",
-      "description": "Review the statistical charts implementation, especially focusing on heatmaps for matrix questions. Check if visualizations: 1) Accurately represent collected data, 2) Include proper scales and legends, 3) Are responsive across devices, 4) Provide interactive features (hovering, filtering, etc.). Award 2 points for each chart type properly implemented with 10 points maximum. Deduct 5 points if heatmap visualization for matrix questions is missing or poorly implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the data export and progress tracking functionality working correctly?",
-      "description": "Verify that the CSV export functionality correctly formats all question types and responses, includes metadata (timestamps, user IDs), and handles special characters. Check if the progress tracking system accurately reflects completion percentage, saves partial progress, and provides visual feedback. Deduct 5 points if CSV export is missing essential data or has formatting issues, and 5 points if progress tracking is inaccurate or incomplete. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid inputs, partial form submissions, browser refresh/navigation, data parsing errors) and provide friendly error prompts or recovery mechanisms. Test edge cases like extremely long responses or special characters in answers. Deduct 3 points for each major vulnerability found. The full score is 10 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 collaborative editing of surveys, 2. AI-assisted question suggestions, 3. Advanced sentiment analysis for open responses, 4. Response validation with machine learning). 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 data processing pipelines (e.g., multiple parsing mechanisms for the same data type) 2. Function modules unrelated to survey analysis (e.g., unnecessary social media integrations) 3. Heavy visual effects that affect performance (e.g., excessive animations in data visualizations). 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 survey creation/data collection/analysis layers), unit test coverage for critical functions like skip logic and data aggregation, and build process automation. Check for proper data validation before processing. Deduct 5 points if global state pollution is found; deduct 5 points if the code duplication rate is too high; deduct 5 points if there are no data validation safeguards. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the survey tool follows modern design principles: 1) Clean form layouts with proper grouping 2) Consistent visual hierarchy for questions and controls 3) Professional typography with proper line spacing (≥1.5) and contrast ratios (≥4.5:1) for accessibility. Check how charts are styled and if they follow data visualization best practices. Deduct 3 points for cluttered layouts, 5 points for poor information hierarchy, and 5 points for inaccessible design choices. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the survey tool provides appropriate interactions: 1) Instant validation feedback for user inputs 2) Smooth transitions between question sections 3) Responsive chart interaction with tooltips and hover states. Test on different devices and screen sizes. Deduct 5 points if form submission lacks clear feedback, 3 points for janky transitions between questions, and 5 points if visualizations don't resize properly on different screens. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "hard"
-}

package/library/management_systems-frontend_backend_platforms/survey-generator-with-qr-codes.json

@@ -1,68 +0,0 @@
-{
-  "index": 1368,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the code you generate is executable. Help me create a program that can generate surveys, where the surveys produced by our program can be accessed via QR code.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the survey generation system complete and functional?",
-      "description": "Review whether the code provides a complete survey creation workflow including form definition, question types (multiple choice, text input, ratings), validation rules, and survey publishing. Score 0 if the core survey creation is not implemented, 5 if only basic question types are supported, and 10 if it includes advanced features like branching logic and conditional questions.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the QR code generation properly implemented?",
-      "description": "Evaluate if the QR code generation uses established libraries (like qrcode.js or QRious) with proper error handling. Check if the QR codes store proper URLs with unique identifiers for each survey, and if they're generated with appropriate error correction levels (M or Q recommended for reliability). Deduct 5 points if the QR codes don't link directly to the surveys, and 3 points if the resolution or size options are missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Does the system have a survey data storage and retrieval mechanism?",
-      "description": "Check if the program implements proper data persistence for both survey definitions and responses. The system should use a database (SQL or NoSQL) or at minimum localStorage with proper data structures. Verify if there's data validation before storage and proper error handling for failed saves. Deduct 5 points if there's no response data aggregation, and 5 points if there's no secure authentication for accessing results. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there a responsive survey viewing interface for QR code recipients?",
-      "description": "Evaluate if the survey interface adapts to different screen sizes (desktop, tablet, mobile) since QR codes are often scanned on mobile devices. Check for touch-friendly UI elements, appropriate font sizes (minimum 16px on mobile), and proper viewport configuration. Deduct 5 points if the survey doesn't render properly on mobile screens, and 5 points if the survey submission process isn't optimized for touch interfaces. 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 survey submission, malformed input data, QR code scanning failures, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Real-time response analytics 2. Survey templates library 3. Multi-language support for international surveys 4. Offline completion capability with sync when online). 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 QR code generators coexisting) 2. Function modules unrelated to survey management (e.g., a built-in image editor) 3. Fancy effects that affect performance (e.g., excessive animations in survey forms). 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 survey definition/rendering/data collection layers), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast sliding, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "hard"
-}

package/library/management_systems-frontend_backend_platforms/task-allocation-tracking-tool.json

@@ -1,68 +0,0 @@
-{
-  "index": 517,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Try to ensure the generated code is executable for demonstration.\n\n======== ROLE ========\nYou are an experienced code expert. You are provided with 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 fully annotated with simple and easy-to-understand language, without outputting anything else.\n\n======== OUTPUT RULES ========\n1. Always generate complete, runnable project code, ensuring the project is fully executable\n2. Ensure all code files you output are complete, do not omit any code\n3. Carefully review and check all code before final output, evaluating its executability. If the code cannot be executed or contains errors, regenerate it\n4. If the requirements involve external API access or user data (images, videos, audio, etc.), please provide simulated data\n\n======== PROJECT REQUIREMENTS ========\nCreate a task allocation and tracking tool where project managers can create tasks, assign them to team members, set deadlines and priorities, and team members can update task status and add notes.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the task management core functionality fully implemented?",
-      "description": "Review whether the code accurately implements task CRUD operations (Create, Read, Update, Delete) with proper data validation, task assignment logic, and status tracking mechanisms. Check if task properties include title, description, assignee, deadline, priority levels, and status transitions. Score 0 if basic task operations are missing, 5 if only simple CRUD is implemented, and 10 if complete task lifecycle management with validation is included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the user role management and permission system implemented?",
-      "description": "Evaluate whether the system properly distinguishes between project managers and team members with appropriate permission controls. Check if project managers can create/assign tasks while team members can only update assigned tasks. Verify user authentication, role-based access control, and secure session management. Deduct 5 points if role separation is unclear, and 3 points if permission validation is missing on sensitive operations. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the data persistence and state management properly designed?",
-      "description": "Check whether the application uses appropriate data storage mechanisms (localStorage, database integration, or API endpoints) with proper data modeling for tasks, users, and relationships. Evaluate if state management follows consistent patterns and handles concurrent updates correctly. Deduct 5 points if data loss occurs on page refresh, and 3 points if state synchronization issues exist between different views. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are the tracking and notification features comprehensively implemented?",
-      "description": "Assess whether the system includes progress tracking dashboards, deadline monitoring, status change notifications, and activity logging. Check if the interface provides clear visual indicators for overdue tasks, progress summaries, and task history. Deduct 5 points if tracking visualization is missing, and 3 points if status updates don't trigger appropriate notifications. Give 10 points if comprehensive tracking with analytics is fully implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust and handles edge cases properly?",
-      "description": "Evaluate whether the code can handle common abnormal situations (invalid input data, missing user assignments, date validation errors, concurrent modifications, etc.) and provides friendly error messages with recovery mechanisms. Code with strong robustness should effectively validate all user inputs and handle edge cases gracefully, giving 10 points. If robustness is average, give 5 points, and if no error handling exists, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there innovative features that enhance productivity?",
-      "description": "Check whether the code includes valuable productivity features that go beyond basic requirements (e.g., 1. Drag-and-drop task prioritization 2. Automated deadline reminders 3. Task dependency mapping 4. Time tracking integration 5. Export/import functionality 6. Advanced filtering and search). Add 2 points for each well-implemented innovative feature (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant or unnecessary features?",
-      "description": "Strictly identify three types of redundancy: 1. Duplicate functionality implementations (e.g., multiple task creation forms) 2. Features unrelated to task management (e.g., built-in games or social media integration) 3. Over-engineered components that impact performance (e.g., excessive animations on data operations). Deduct 3 points for each redundancy found, and directly deduct 10 points if redundant code interferes with core functionality.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code demonstrate professional engineering quality?",
-      "description": "Review architectural separation (data layer, business logic, presentation layer), code organization with proper modules/components, consistent naming conventions, and maintainability. Deduct 5 points if global state pollution or poor separation of concerns is found; deduct 5 points if code duplication exceeds 25%; deduct 5 points if no code comments or documentation exists. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface design meet professional UX/UI standards?",
-      "description": "Evaluate whether the design follows modern interface principles: 1) Consistent color scheme with proper contrast ratios (WCAG AA compliant) 2) Logical information hierarchy with appropriate typography (minimum 14px font size, 1.4+ line height) 3) Intuitive navigation and clear visual grouping of related elements. Deduct 3 points for each accessibility violation, 5 points for poor color choices that strain visibility, and 5 points for cluttered or confusing layout structure. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Are the interactions smooth and provide excellent user experience?",
-      "description": "Judge whether user interactions follow UX best practices: 1) Immediate visual feedback for all clickable elements (≤ 100ms response) 2) Smooth transitions between states (200-400ms duration) 3) Clear loading states and progress indicators 4) Intuitive keyboard navigation support. Deduct 5 points for each unresponsive interaction, 3 points for jarring visual transitions, and 5 points for confusing navigation flow or hidden critical functions. Full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "hard"
-}

package/library/management_systems-frontend_backend_platforms/tauri-svelte-crud-frontend-rust-backend.json

@@ -1,68 +0,0 @@
-{
-  "index": 1247,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code whenever possible. Please create a frontend CRUD example for customers and users using Tauri+Vite+Svelte, with an existing Rust+Actix-web+MySQL backend already in place.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Tauri+Vite+Svelte frontend architecture properly implemented?",
-      "description": "Review whether the code correctly configures Tauri with Vite and Svelte, including proper tauri.conf.json setup, frontend build configuration, and IPC (Inter-Process Communication) bridge implementation. Check if the Svelte components are properly structured with reactive state management. Score 0 if the Tauri integration is missing or broken, 5 if basic setup exists but lacks proper IPC implementation, and 10 if all components are seamlessly integrated with proper error handling.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are complete CRUD operations fully implemented for both customers and users?",
-      "description": "Evaluate whether all Create, Read, Update, Delete operations are implemented for both customer and user entities. Check if the frontend properly communicates with the Rust+Actix-web backend through HTTP requests or Tauri commands. Verify data validation, form handling, and proper state updates after operations. Deduct 3 points for each missing CRUD operation, 2 points if data validation is incomplete, and 2 points if state management is inconsistent. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the backend integration with Rust+Actix-web+MySQL properly handled?",
-      "description": "Check whether the frontend correctly interfaces with the existing Rust+Actix-web backend, including proper API endpoint usage, request/response handling, and MySQL data persistence. Verify error handling for network failures, database connection issues, and API response parsing. Deduct 4 points if API integration is incomplete, 3 points if error handling is missing, and 3 points if data persistence verification is absent. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the data flow and state management architecture well-designed?",
-      "description": "Evaluate whether the application implements proper state management using Svelte stores or similar patterns for handling customer and user data. Check if the data flow between components is logical, if loading states are handled, and if the UI updates reactively to data changes. Deduct 4 points if state management is chaotic, 3 points if loading states are not handled, and 3 points if component communication is poorly implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as network failures, invalid input data, backend service unavailability, Tauri API 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 CRUD experience (e.g., 1. Real-time data synchronization with WebSocket 2. Advanced search and filtering capabilities 3. Data export/import functionality 4. Offline mode with local storage 5. Bulk operations for multiple records). 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 form validation logics coexisting) 2. Function modules unrelated to CRUD operations (e.g., built-in games or unnecessary utilities) 3. Overcomplicated UI components that don't add value (e.g., excessive animations for simple operations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core CRUD functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating API layer/components/stores), proper TypeScript usage, component reusability, and build process configuration. Deduct 5 points if global state pollution is found or Svelte best practices are not followed; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if Vite configuration is not optimized or build process has issues. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the CRUD interface 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) 4) Consistent form design and table layouts. Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic form/table layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the CRUD operations provide smooth user experience: 1) Form submission feedback delay ≤ 100ms 2) Loading indicators for async operations 3) Smooth transitions between list/detail views 4) Clear visual feedback for successful/failed operations 5) Intuitive navigation between customer and user management. Deduct 5 points for each operation without proper feedback, 3 points for jarring transitions, and 5 points for confusing navigation patterns. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "medium"
-}

package/library/management_systems-frontend_backend_platforms/team-scheduling-project-management-mini-program.json

@@ -1,68 +0,0 @@
-{
-  "index": 1179,
-  "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 want to develop a complete team scheduling and project management mini-program that includes closed-loop functionality and the ability to upload image files for completed results.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the team member management system fully implemented?",
-      "description": "Review whether the code properly implements user registration, role assignment (admin/team member), permissions control, and team structure visualization. Score 0 if user management is missing, 5 if basic user profiles exist but lack role differentiation, and 10 if there's complete RBAC (Role-Based Access Control) with proper authorization flows.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the project management functionality comprehensively developed?",
-      "description": "Check whether the code includes essential project management features: task creation, assignment, prioritization, deadline setting, status tracking, and dependency management. Deduct 5 points if project hierarchical structure (projects→milestones→tasks) is missing, 3 points if there's no critical path visualization, and 2 points if resource allocation conflicts aren't detected. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the file upload system for completed results properly implemented?",
-      "description": "Evaluate whether the image upload functionality includes: proper file type validation, size restrictions, compression before storage, preview capability, and secure storage implementation. Check if progress indicators and error handling during uploads are present. Deduct 5 points for missing image processing (resizing/compression), 3 points for lack of preview functionality, and 5 points for security vulnerabilities in file handling. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the closed-loop project workflow properly implemented?",
-      "description": "Assess whether the code implements a complete project lifecycle: task assignment → progress tracking → result submission → approval → completion/revision requests. Check if notifications for each stage transition exist and if analytics on completion rates and bottlenecks are available. Deduct 5 points if approval workflows are missing, 3 points if there's no historical tracking of changes, and 2 points if reporting functions are absent. 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 uploads, concurrent edits, permission conflicts, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should include data validation, proper exception handling, and graceful degradation. Give 10 points for comprehensive error handling, 5 points if basic validation exists but edge cases aren't covered, and 0 points if exceptions 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-powered task estimation 2. Automated workload balancing 3. Interactive Gantt charts with drag-drop scheduling 4. In-app team communication tools). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple notification systems coexisting) 2. Function modules unrelated to team management or project tracking 3. Fancy effects that affect performance (e.g., excessive 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 business 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 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"
-}