@getollie/cli 0.0.5 → 0.2.1

package/library/management_systems-frontend_backend_platforms/equipment-inventory-ledger-management.json

@@ -1,68 +0,0 @@
-{
-  "index": 1045,
-  "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. Help me create an equipment inventory/ledger similar to this, including fields such as: serial number, station internal number, product number, equipment model name, asset value, main technical specifications, manufacturer, production date, purchase date, whether it's a measuring instrument, accuracy level, calibration status, equipment condition status, service life, dedicated personnel, and department. At the top, summarize the items that are in normal use, idle, under repair, scrapped, and the total count. Please implement this step by step, with detailed instructions as if for a beginner.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the database schema for the equipment inventory properly designed?",
-      "description": "Check if the schema includes all required fields (serial number, station internal number, product number, equipment model name, asset value, technical specifications, manufacturer, production date, purchase date, measuring instrument flag, accuracy level, calibration status, equipment condition, service life, dedicated personnel, department). Ensure proper data types are used (e.g., dates for dates, numeric for values, enums for statuses). Verify that appropriate constraints are implemented (primary keys, foreign keys, not-null constraints for critical fields). Score 0 if missing more than 5 fields, 5 if missing 1-4 fields, 10 if complete and properly typed.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the equipment status summary dashboard implemented effectively?",
-      "description": "Evaluate whether the code implements a summary section that accurately counts and displays equipment by status categories (normal use, idle, under repair, scrapped) and shows the total count. Check if the summary automatically updates when inventory changes. Verify if visualizations (charts/graphs) are used to represent the data. Score 0 if the summary is missing, 5 if it's static or incomplete, 10 if it's dynamic, complete, and visually informative.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are CRUD operations fully implemented for equipment management?",
-      "description": "Review the implementation of Create, Read, Update, and Delete operations. Verify if the code allows adding new equipment with all required fields, viewing equipment details (individual and list views), updating equipment information, and removing/archiving equipment records. Check for validation of input data before processing. Score 0 if missing multiple CRUD operations, 5 if basic operations exist but lack validation or have limited functionality, 10 if all operations are fully implemented with proper validation.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the beginner-friendly step-by-step implementation guide comprehensive?",
-      "description": "Assess whether the response includes clear, detailed instructions for implementation that a beginner could follow. Check if it breaks down complex concepts, explains technical terms, includes code comments, and provides guidance on potential pitfalls. Verify if it covers setup instructions, dependencies installation, and deployment steps. Score 0 if instructions are highly technical or missing, 5 if they cover basics but lack details, 10 if they are truly beginner-friendly and comprehensive.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid input data, missing fields, duplicate entries, database connection issues, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Equipment maintenance scheduling/alerts 2. QR code generation for physical asset tagging 3. Historical tracking of status changes 4. Depreciation calculation 5. Export functionality to various formats). Add 2 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 equipment inventory (e.g., unnecessary integrations) 3. Fancy effects that affect performance (e.g., excessive animations or UI elements). 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/business logic/view layers), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times) 4) Responsive design for various screen sizes. Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the 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 4) Intuitive filtering and sorting mechanisms for equipment lists. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast interactions, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "easy"
-}

package/library/management_systems-frontend_backend_platforms/equipment-owner-pocket-station-with-blueprints-sockets.json

@@ -1,68 +0,0 @@
-{
-  "index": 1169,
-  "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. Help me design a mini-program called \"Equipment Owner's Pocket Station,\" which needs to have features for importing substation blueprints and special method materials, as well as socket functionality.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the blueprint import functionality completely implemented?",
-      "description": "Review whether the code properly handles various blueprint formats (SVG, DXF, PDF), implements proper parsing and rendering of technical drawings, and maintains accurate scale/proportion. Score 0 if import functionality is missing, 5 if only basic formats are supported without validation, and 10 if the implementation includes format validation, error handling, and proper scaling mechanisms.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the special method materials management system well-designed?",
-      "description": "Assess whether the code implements a comprehensive materials library that includes categorization, search functionality, and metadata management. Check if material properties are properly modeled with appropriate data structures. Deduct 5 points if searching/filtering is not implemented, 3 points if material versioning is missing. Give 10 points for a complete implementation that includes material compatibility checks and usage recommendations.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the socket functionality properly implemented?",
-      "description": "Evaluate the WebSocket/Socket.IO implementation for real-time data exchange between clients and servers. Check for proper connection management, error handling, reconnection strategies, and data serialization. Deduct 5 points if there's no heartbeat mechanism, 3 points if security measures (authentication/encryption) are missing. The full score is 10 points for robust bidirectional communication with proper error handling.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the application have a complete equipment management workflow?",
-      "description": "Check whether the code implements a full equipment lifecycle management system, including inventory tracking, maintenance scheduling, inspection records, and alert mechanisms. Deduct 5 points if historical tracking is not implemented, and 3 points if the maintenance reminder system is missing. Give 10 points if the implementation includes condition monitoring and predictive maintenance features.",
-      "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 interruption, user operation errors, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Augmented reality for equipment visualization 2. Voice command integration for hands-free operation 3. QR code scanning for quick equipment 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 ways to import the same blueprint format) 2. Function modules unrelated to equipment management (e.g., a built-in game) 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 business logic/UI/network 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/feedback-management-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 919,
-  "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. Clicking \"Submit Feedback\" will open a new page for writing feedback; change \"Feedback Notification\" to \"Historical Feedback\"; delete all content below \"Try to create a feedback box below\" and replace it with \"Resolved Feedback List\" for display, clicking on any specific feedback item will take you to the detailed feedback page; please provide me with all the code.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the feedback form submission system fully implemented?",
-      "description": "Review whether the code accurately implements a complete feedback form with proper validation, submission handling, and page navigation. Check if clicking 'Submit Feedback' correctly opens a new page with a functional feedback form including input fields, validation logic, and submission processing. Score 0 if no form implementation exists, 5 if only basic form structure is present without validation, and 10 if complete form with validation, error handling, and successful submission flow is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the dynamic content replacement functionality correctly implemented?",
-      "description": "Evaluate whether the code successfully changes 'Feedback Notification' to 'Historical Feedback' and replaces content below 'Try to create a feedback box below' with 'Resolved Feedback List'. Check if the DOM manipulation is clean and doesn't cause layout issues. Deduct 5 points if text replacement is incomplete, 3 points if DOM manipulation causes visual glitches, and 5 points if the replacement doesn't maintain proper styling consistency. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the feedback list display and navigation system properly constructed?",
-      "description": "Check whether the code implements a functional feedback list that displays feedback items correctly and provides clickable navigation to detailed feedback pages. Evaluate if the list items are properly structured, clickable, and lead to appropriate detail pages. Deduct 5 points if list items are not properly formatted, 5 points if click navigation doesn't work, and 3 points if the detail page structure is missing or incomplete. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the complete page routing and state management implemented?",
-      "description": "Assess whether the code includes proper page routing between the main page, feedback submission page, and feedback detail pages. Check if state management maintains data consistency across page transitions and if browser navigation (back/forward) works correctly. Deduct 5 points if routing is implemented but buggy, 5 points if state is lost during navigation, and 3 points if browser navigation doesn't work properly. Give 10 points if fully implemented with smooth transitions.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid form input, missing data, navigation errors, DOM manipulation failures, etc.) and provide friendly error messages or recovery mechanisms. Code with strong robustness should effectively handle edge cases like empty submissions, malformed data, and failed page transitions. Give 10 points for comprehensive error handling, 5 points for basic error handling, and 0 points if no exception handling exists.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that enhance user experience?",
-      "description": "Check whether the code includes valuable enhancements such as: 1) Auto-save draft functionality for feedback forms 2) Search/filter capability for feedback lists 3) Real-time form validation with helpful hints 4) Smooth page transitions with loading states 5) Responsive design adaptations. Add 2-3 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 form validation methods) 2) Features unrelated to the feedback system (e.g., embedded games or unrelated widgets) 3) Over-engineered effects that don't serve the core purpose (e.g., excessive animations that slow down interactions). Deduct 3 points for each redundancy found, and deduct 10 points if redundant code interferes with core functionality.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code demonstrate good engineering practices?",
-      "description": "Review code organization, modularity (separation of HTML structure, CSS styling, and JavaScript logic), proper naming conventions, and maintainability. Check for clean separation of concerns, reusable components, and consistent coding patterns. Deduct 5 points for poor code organization or heavy coupling; deduct 5 points if code duplication exceeds 30%; deduct 5 points for inconsistent naming or lack of proper code structure. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface design meet professional visual standards?",
-      "description": "Evaluate whether the overall design follows modern UI principles: 1) Consistent color scheme with appropriate contrast ratios 2) Proper typography hierarchy and readability (font sizes ≥ 14px, adequate line spacing) 3) Balanced layout with appropriate whitespace and element spacing 4) Clear visual hierarchy and information organization. Deduct 3 points for each visual inconsistency, 5 points for poor color choices affecting readability, and 5 points for cluttered or unprofessional layout. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Are the interactions smooth and provide clear user feedback?",
-      "description": "Assess whether user interactions provide immediate and clear feedback: 1) Button clicks show visual response within 100ms 2) Form submissions provide loading states and success/error feedback 3) Page transitions are smooth and indicate progress 4) Hover states and focus indicators are clearly visible 5) Navigation is intuitive and predictable. Deduct 5 points for each interaction lacking proper feedback, 3 points for slow response times, and 5 points for confusing navigation patterns. Full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "easy"
-}

package/library/management_systems-frontend_backend_platforms/file-database-system-shell-management.json

@@ -1,68 +0,0 @@
-{
-  "index": 1340,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable whenever possible. Now, let's implement specific functionality: for file management, implement current directory display and modification, current directory tree view, and provide file editing, modification, deletion, and download functions. For database management, implement database type selection like MySQL/PostgreSQL, etc., and provide various input fields for database connection. After successful connection, enable database operations. For system shell, implement an interactive command-line terminal that can execute system commands.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the file management system fully implemented?",
-      "description": "Review whether the code accurately implements directory navigation, tree view display, and file operations through HTML/JavaScript. Check if it includes file upload/download functionality, file editing capabilities, and proper file type handling (text files, images, etc.). Score 0 if core file operations are not implemented, 5 if only basic file listing is implemented, and 10 if all file management features including editing, deletion, and download are fully functional.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the database management functionality properly implemented?",
-      "description": "Check whether the database connection system supports multiple database types (MySQL/PostgreSQL/SQLite), implements secure connection parameter handling, and provides query execution capabilities. Evaluate if it includes connection pooling, error handling for failed connections, and proper SQL query interface. Deduct 5 points if connection security is compromised, and 3 points if database type switching is not seamless. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the interactive command-line terminal fully functional?",
-      "description": "Evaluate whether the terminal implementation provides real-time command execution, proper output display, and command history functionality. Check if it handles both synchronous and asynchronous commands correctly, implements command auto-completion, and provides proper error handling for invalid commands. Deduct 5 points if command execution blocks the UI, and 3 points if terminal output formatting is poor. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the system security and permission management properly designed?",
-      "description": "Check whether the code implements proper access control for file operations, secure database credential handling, and command execution restrictions. Evaluate if it includes user authentication, file permission validation, and prevents dangerous command execution. Deduct 5 points if sensitive operations lack authorization checks, and 5 points if database credentials are stored insecurely. Give 10 points if comprehensive security measures are implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as file access errors, database connection failures, command execution timeouts, 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 file preview with syntax highlighting 2. Database query result visualization 3. Terminal command suggestions with AI assistance 4. Integrated file diff viewer). 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 file deletion methods coexisting) 2. Function modules unrelated to system management (e.g., built-in games or entertainment features) 3. Fancy effects that affect performance (e.g., excessive animations during file operations). 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 file management/database/terminal modules), error handling consistency, and configuration management. 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 configuration is hardcoded without environment variables. 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 for different modules (no more than 3 primary colors) 2) Proper layout spacing with clear module separation (element spacing follows the 8px multiple principle) 3) Professional font system for code display (monospace fonts for terminal/code, 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) File operation feedback delay ≤ 100ms 2) Database query progress indicators with proper loading states 3) Terminal command execution with real-time output streaming 4) Clear visual focus guidance between different management modules. Deduct 5 points for each operation without feedback, 3 points for blocking UI during long operations, and 5 points for hard-to-find navigation between modules. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "easy"
-}

package/library/management_systems-frontend_backend_platforms/file-upload-download-management-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 683,
-  "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. Please develop an online file upload and download management system where users can upload files through a front-end interface, with support for displaying current upload progress and file size. Administrators should be able to view all uploaded files through a back-end interface, with functionality for file downloading and deletion.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the file upload functionality fully implemented?",
-      "description": "Evaluate whether the code correctly implements file selection, validation, and upload to server. Check for multiple file upload support, file type restrictions, file size limits, and proper error handling when uploads fail. Score 0 if core upload functionality is missing, 5 if basic upload works but lacks validation, 10 if all features including proper validation and error handling are implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the progress tracking feature properly implemented?",
-      "description": "Check if the upload progress is accurately displayed with real-time updates. Verify implementation of progress bar or percentage indicators that update dynamically using XHR/Fetch with progress events. Assess if the system shows current upload speed and estimated time remaining. Deduct 5 points if progress updates aren't real-time, 3 points if speed/time estimates are missing. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the file download functionality correctly implemented?",
-      "description": "Review whether users can download files with proper content disposition headers, correct MIME types, and optional download progress indicators. Check if large file downloads are handled efficiently (streaming vs. full memory load). Deduct 5 points if downloads lack proper headers or MIME types, 5 points if large files cause memory issues. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the admin management interface comprehensive and secure?",
-      "description": "Evaluate if the admin interface provides complete file management capabilities including listing, sorting, searching, downloading, and deletion. Check for proper authentication and authorization mechanisms to protect the admin functions. Deduct 5 points if search/sort functionality is missing, 5 points if authentication is weak or absent, 3 points if bulk operations aren't supported. 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 interruptions, server errors, invalid file types, oversized 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. Drag-and-drop upload support 2. Image/document previews 3. Client-side file compression 4. Resumable uploads for large files 5. Dark/light mode toggle). Add 2 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 file upload handlers) 2. Function modules unrelated to file management (e.g., unnecessary analytics) 3. Fancy effects that affect performance (e.g., excessive animations on file listings). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating UI components/API services/state management), error handling patterns, and code organization. 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 proper security measures for file uploads are missing (like sanitization). 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 file listing and preview design (clear hierarchical information display). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic file listing layouts. 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) Upload button and drag area clearly visible 2) File status changes (queued, uploading, complete, error) with clear visual feedback 3) Smooth transitions between upload states with appropriate animations (300-500ms). Deduct 5 points for each operation without feedback, 3 points for jarring transitions between states, and 5 points for confusing status indicators. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "easy"
-}

package/library/management_systems-frontend_backend_platforms/film-crew-management-weather-scenes-gantt.json

@@ -1,68 +0,0 @@
-{
-  "index": 473,
-  "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. Develop a film and TV crew announcement management system that includes weather API displays for shooting locations and automatic costume-role associations with scenes. Include daily progress comparison with planned Gantt charts, with delayed scenes displaying impact factor tags (weather/actors/etc.).",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core film and TV crew announcement management system fully implemented?",
-      "description": "Review whether the code accurately implements CRUD operations for crew announcements, schedule management, and role assignments. Check if the system supports different user roles (director, producer, crew members) with appropriate access controls. Score 0 if the core announcement system is not implemented, 5 if only basic announcement functions exist, and 10 if comprehensive management features are included with proper data validation.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the weather API integration properly implemented?",
-      "description": "Evaluate whether the weather API is correctly integrated with location-based data, showing current and forecasted conditions for shooting locations. Check if the code handles API rate limits, connection failures, and data caching. The implementation should include visual indicators for weather conditions affecting shooting. Deduct 5 points if the API integration is basic without error handling, 3 points if weather data is not linked to shooting locations properly. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the costume-role association with scenes functionality complete?",
-      "description": "Check if the system maintains a database of costumes and characters with proper relationships to scenes. The code should allow for automatic assignment based on scene requirements and handle conflicts. Verify if costume tracking includes availability status and maintenance schedules. Deduct 5 points if associations are manual only, 3 points if costume tracking lacks detail. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the progress comparison with Gantt charts and impact factor tagging implemented effectively?",
-      "description": "Review whether the code implements visual Gantt chart comparisons between planned and actual progress, with dynamic updates based on daily reports. Check if delayed scenes are properly tagged with impact factors (weather/actors/logistics/equipment) and if these tags are programmatically determined based on system data. Deduct 5 points if Gantt visualization is static, 5 points if impact factors are not automatically associated. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as API failures, network interruptions, concurrent user edits, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Real-time notifications with priority system 2. AI-based schedule optimization suggestions 3. Visual weather impact projection). 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 film crew management (e.g., a built-in game for waiting times) 3. Fancy effects that affect performance (e.g., unnecessary animations in critical workflow screens). 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/UI/data access layers), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast sliding, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "hard"
-}

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

@@ -1,68 +0,0 @@
-{
-  "index": 506,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code can be executed as shown. ======== ROLE ========\nYou are an experienced code specialist. Given a software development requirement description, you are asked to generate project code based on these requirements. Strictly follow the rules to help users generate complete project code that is fully commented with simple, easy-to-understand language, without outputting anything else.\n\n======== OUTPUT RULES ========\n1. Always generate complete, runnable project code; ensure 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 need to use user data (images, videos, audio, etc.), please provide simulated data\n\n======== PROJECT REQUIREMENTS ========\nPlease write code to implement a financial management system where finance personnel can enter income and expense items and generate financial reports; administrators can view all financial records and perform data analysis and statistics.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the financial data management system fully implemented?",
-      "description": "Review whether the code accurately implements income and expense entry functionality through HTML/JavaScript forms, including data validation, category classification, and amount calculation. Check if it supports multiple transaction types (income/expense), date selection, description fields, and category management. Score 0 if core financial entry logic is not implemented, 5 if only basic income/expense recording is available, and 10 if comprehensive financial transaction management with validation is fully included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the financial report generation function implemented?",
-      "description": "Evaluate whether the system can generate comprehensive financial reports including income statements, expense summaries, and period-based analysis. Check for chart visualization (pie charts, bar charts, line graphs), export functionality (PDF/Excel), and customizable date ranges. Deduct 5 points if no visual charts are provided, and 3 points if export functionality is missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the role-based access control and user management designed?",
-      "description": "Check whether the system implements proper role separation between finance personnel and administrators, with appropriate permission controls. Finance staff should only access entry and basic reports, while administrators can view all records and perform advanced analytics. Deduct 5 points if role authentication is missing, and 3 points if permission boundaries are not properly enforced. Verify login/logout functionality and session management. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the data analysis and statistics module constructed?",
-      "description": "Evaluate whether the code includes comprehensive data analysis features such as trend analysis, category-wise spending patterns, monthly/yearly comparisons, and statistical summaries. Check for filtering capabilities, search functionality, and advanced analytics like budget vs actual comparisons. Deduct 5 points if only basic listing is provided without analysis, and 3 points if statistical calculations are inaccurate. Give 10 points if fully implemented with interactive analytics.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid financial amounts, date format errors, unauthorized access attempts, data corruption, 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 financial management experience (e.g., 1. Automated expense categorization using AI 2. Budget alerts and notifications 3. Receipt image upload and OCR processing 4. Financial goal tracking 5. Multi-currency 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 calculation logics coexisting) 2. Function modules unrelated to financial management (e.g., a built-in game or social features) 3. Fancy effects that affect performance (e.g., excessive animations on financial data). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core financial 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), input validation, and code organization. Deduct 5 points if global state pollution is found or MVC patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if no proper error handling or logging mechanisms exist. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the financial interface follows professional business application design: 1) Clean and trustworthy color scheme (preferably blues/grays for financial apps) 2) Proper data table layouts with clear headers and sorting 3) Professional typography (financial figures clearly readable, proper alignment). Deduct 3 points for each cluttered data presentation, 5 points for unprofessional color choices that reduce trust, and 5 points for poor number formatting or alignment. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the financial data interaction smooth and intuitive?",
-      "description": "Judge whether the financial operations are user-friendly: 1) Form submission feedback ≤ 100ms 2) Data loading states and progress indicators 3) Intuitive navigation between different financial views 4) Clear visual feedback for successful transactions. Deduct 5 points for each operation without proper feedback, 3 points for slow data rendering that affects user experience, and 5 points for confusing navigation that makes financial tasks difficult to complete. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "medium"
-}

package/library/management_systems-frontend_backend_platforms/fitness-club-membership-management-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 544,
-  "question": "You are a code expert. Please use your expertise to generate accurate and professional responses. Make sure the generated code is executable and displayable.\n\n## Role\nYou are an experienced code expert. You are provided with a software development requirement description, and you are required to generate project code based on these requirements. Follow the rules strictly to help users generate a complete project code with simple and understandable comments, and don't output anything else.\n\n## Output Rules\n1. You should always generate complete, runnable project code. Please ensure the project is fully executable.\n2. Ensure all code files you output are complete, don't omit any code.\n3. Before final output, carefully review and check all code to evaluate its executability. If the code cannot be executed or contains errors, regenerate it.\n4. If the requirements involve external API access or need to use user data (images, videos, audio, etc.), please provide simulated data.\n\n## Project Requirements Description\nPlease write code to implement a fitness club membership management system. Administrators can add, delete, and edit member information, manage course registrations and attendance records. Members can log in to view available courses, register for courses, and check their own attendance and course records. The system should support a course scheduling calendar, automatically remind members of upcoming courses, and generate member attendance statistical reports.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the member management system fully implemented?",
-      "description": "Review whether the code accurately implements CRUD operations for member profiles, including name, contact information, membership status, payment records, and membership expiry tracking. Score 0 if core member management is missing, 5 if basic functionality is implemented but lacks validation or proper data relationships, and 10 if all member management features are fully implemented with data integrity checks.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the course management system properly implemented?",
-      "description": "Check if the system can handle course creation, scheduling, capacity management, instructor assignment, and course descriptions. Validate if the code implements proper validation for course scheduling conflicts, room availability, and instructor availability. Deduct 3 points if scheduling conflict detection is missing, 3 points if capacity management is incomplete, and 2 points if instructor assignment logic is flawed. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the attendance tracking system complete?",
-      "description": "Evaluate if the system can record member attendance, handle check-ins/check-outs, track no-shows, and provide attendance history. Check whether the system implements proper date/time handling for accurate attendance tracking. Deduct 3 points if attendance records can't be queried by date ranges, 3 points if attendance status validation is missing, and 2 points if the system lacks attendance modification audit trails. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the notification and reminder system implemented?",
-      "description": "Assess whether the code includes course reminder functionality, including configurable reminder timing (e.g., 24 hours before class), multiple notification channels (email/SMS/in-app), and handling of notification delivery failures. Deduct 3 points if only one notification channel is implemented, 3 points if notification scheduling is hardcoded, and 2 points if there's no notification status tracking. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as concurrent user edits, invalid data inputs, network interruptions, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should include comprehensive input validation, transaction management for database operations, and graceful error handling, 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. Automated fitness progress tracking 2. Personalized class recommendations based on attendance history 3. Virtual class waitlist with priority algorithms 4. Integration with wearable fitness devices). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple user authentication systems) 2. Function modules unrelated to fitness club management (e.g., a built-in general chat system) 3. Fancy effects that affect performance (e.g., unnecessary animations in reporting views). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating business logic/view/data access layers), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast sliding, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "hard"
-}