@getollie/cli 0.0.5 → 0.2.0

package/library/management_systems-frontend_backend_platforms/coupon-management-and-usage.json

@@ -1,68 +0,0 @@
-{
-  "index": 1038,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the code generated is executable for display.\n\nMy Coupons - Display a list of coupons I've redeemed with points, showing coupon type, quantity, usage rules, validity period, status, and other information.\n\nConsumption - When I make a purchase, the order page automatically displays available coupons that I can choose to use or not use. When selected, the amount is automatically deducted.\n\nCoupon Usage List - Display a list of coupon usage, including information such as time of use, merchant, original amount, actual payment amount, and discount amount.\n\nDivide into 6 parts",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the coupon listing interface fully implemented?",
-      "description": "Review whether the code properly implements a scrollable coupon list with clear visual categorization. Check if each coupon properly displays: type (discount/cash/free shipping), quantity, usage rules (minimum spend, restrictions), validity period (with expiring soon indicators), and status (valid/expired/used). Score 0 if core coupon display is missing, 5 if basic display without filtering/sorting is implemented, 10 if comprehensive with search/filter/sort capabilities.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the coupon selection mechanism during purchase properly implemented?",
-      "description": "Evaluate the automatic coupon detection and application system during checkout. The system should: identify eligible coupons based on cart contents, display available coupons clearly with expected discount amounts, allow toggling selection with immediate price updates, and handle complex cases like coupon stacking rules or exclusivity. Deduct 5 points if automatic eligibility detection is missing, 3 points if real-time price updates aren't implemented. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the coupon usage history display complete and detailed?",
-      "description": "Check if the usage history includes: timestamps of redemption/usage, merchant information, original order amount, discount applied, and final payment amount. The list should support filtering (by date range, merchant, status) and provide usage analytics/statistics. Deduct 5 points if only basic information is shown without filtering capabilities, 3 points if the display lacks transaction details. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are the six required sections properly structured and interconnected?",
-      "description": "Verify that the implementation correctly divides functionality into the specified 6 parts with clear separation of concerns: 1) Coupon listing 2) Redemption mechanism 3) Checkout integration 4) Usage history 5) Eligibility engine 6) Data management layer. Evaluate navigation between sections and ensure data consistency across components. Deduct 3 points per missing or improperly implemented section. 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 expired coupons, network errors during redemption, overlapping coupon rules, 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. Expiry notifications with calendar integration 2. Visual savings tracker over time 3. Smart coupon recommendation based on shopping habits). 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 coupon validation logics coexisting) 2. Function modules unrelated to coupon management (e.g., a built-in currency converter) 3. Fancy effects that affect performance (e.g., excessive animations when selecting coupons). 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 coupon data models/views/controllers), unit test coverage (especially for discount calculation logic), and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance when selecting coupons. Deduct 5 points for each operation without feedback, 3 points for visual after-images during list scrolling, and 5 points for hard-to-find coupon selection controls. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "medium"
-}

package/library/management_systems-frontend_backend_platforms/course-manager-system-for-students.json

@@ -1,68 +0,0 @@
-{
-  "index": 1650,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Course Manager System (Essential for Students)\n\n## 1. Course Assistant\n- 📅 **Smart Schedule Import**\n  - Support for photo recognition of class schedules/Excel import\n  - Automatic synchronization to phone calendar\n  - Vibration reminder 15 minutes before class\n- 🧭 **Classroom Navigation System**\n  - AR live navigation (guides classroom direction through phone camera)\n  - 3D floor plans of academic buildings\n  - Congestion alerts (predicts crowded hallway periods based on historical data)\n\n## 2. Learning Assistant (Efficiency Booster)\n- 📸 **Homework Smart Recognition**\n  - Photo scanning of paper homework questions\n  - Automatic categorization and organization of wrong answers (supports PDF export)\n  - Integration with question bank APIs to display similar question types and analyses\n- 📊 **Grade Analyzer**\n  - Line graphs showing grade trends\n  - Radar charts analyzing strengths and weaknesses in different subjects\n  - GPA prediction calculator",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Smart Schedule Import system fully implemented?",
-      "description": "Review whether the code implements photo recognition of class schedules using OCR technology (such as Tesseract.js or cloud OCR APIs), Excel file parsing capabilities, and automatic calendar synchronization. Check if the schedule parsing accuracy handles various formats of timetables and converts them to structured data. Score 0 if OCR functionality is missing, 5 if only basic schedule display is implemented, and 10 if full recognition with high accuracy (>85%) and calendar integration are included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the AR Classroom Navigation System properly developed?",
-      "description": "Evaluate whether the AR navigation uses device camera API with real-time rendering, implements 3D floor plan visualization (WebGL/Three.js), and includes congestion prediction algorithms based on historical data analysis. Check if the AR overlay accurately displays directional indicators and building layouts. Deduct 5 points if AR camera integration is missing, 3 points if 3D rendering performance is poor (<30fps), and 2 points if congestion prediction lacks data visualization. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the Homework Smart Recognition feature comprehensively implemented?",
-      "description": "Check whether the system includes image preprocessing, OCR text extraction, mathematical formula recognition, automatic categorization algorithms, and PDF export functionality. Verify integration with external question bank APIs and similarity matching algorithms. Score 0 if no image recognition is implemented, 5 if only basic text OCR works, 8 if mathematical formula recognition is included, and 10 if complete workflow with API integration and export features are functional.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the Grade Analyzer with visualization charts fully constructed?",
-      "description": "Evaluate whether the code implements interactive line charts for grade trends, radar charts for subject analysis, and GPA prediction algorithms using statistical models. Check if charts are responsive and use appropriate visualization libraries (Chart.js/D3.js). Verify calculation accuracy of GPA predictions and trend analysis. Deduct 5 points if charts are static, 3 points if GPA calculations are incorrect, and 2 points if data visualization lacks interactivity. 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 camera permission denial, OCR recognition failures, network interruption, invalid schedule formats, 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 student experience (e.g., 1. Voice-activated schedule queries 2. Study habit analytics with recommendations 3. Collaborative study group formation 4. Integration with learning management systems 5. Offline mode with local data sync). 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 schedule parsers coexisting) 2. Function modules unrelated to course management (e.g., built-in games or social media features) 3. Fancy effects that affect performance (e.g., excessive AR animations or complex 3D models). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core academic 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 OCR processing/data management/UI layers), error handling for API integrations, and mobile optimization. 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 mobile responsiveness is not implemented. 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 mobile-first design principles: 1) Student-friendly color scheme (no more than 3 primary colors, high contrast for readability) 2) Proper touch-friendly spacing (minimum 44px touch targets, 8px grid system) 3) Educational typography (body font size ≥ 16px for mobile, line height over 1.4 times). Deduct 3 points for each cramped interface element, 5 points for poor color accessibility, and 5 points for illegible text on mobile devices. 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 student usage patterns: 1) Camera/OCR processing feedback with loading indicators 2) Chart animations duration controlled between 300-800ms 3) Clear navigation between different modules with breadcrumbs 4) Smooth AR rendering without jitter. Deduct 5 points for each operation without loading feedback, 3 points for laggy camera preview, 3 points for confusing navigation flow, and 2 points for choppy chart animations. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "medium"
-}

package/library/management_systems-frontend_backend_platforms/create-shift-schedule-calendar-format.json

@@ -1,68 +0,0 @@
-{
-  "index": 1704,
-  "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 purposes. I want to create a shift schedule based on a calendar format, and I would like you to help me with the design.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the calendar base structure properly implemented?",
-      "description": "Review whether the code accurately implements a calendar view with proper month/week navigation, date selection, and display of current/selected dates. Score 0 if the calendar structure is missing, 5 if basic calendar display is implemented, and 10 if the calendar includes advanced features like multi-view options (month/week/day) and proper date handling across month boundaries.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the shift scheduling functionality fully implemented?",
-      "description": "Evaluate whether the code allows for creating, editing, and deleting shifts on the calendar. Check if the implementation supports multiple shifts per day, shift categorization (morning/afternoon/night), and proper validation for overlapping shifts. Score 0 if shift scheduling is not implemented, 5 if basic scheduling is available, and 10 if comprehensive shift management with conflict resolution is provided.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the employee/resource allocation system implemented?",
-      "description": "Check if the code includes functionality to assign employees/resources to shifts, manage employee availability, and handle shift swapping or reassignment. Deduct 5 points if employee management is missing, and 3 points if conflict detection for employee scheduling is not implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there data persistence and import/export functionality?",
-      "description": "Assess whether the schedule can be saved (local storage or backend), and if import/export features are available (CSV, iCal, etc.). Check if the system handles data recovery in case of browser crashes. Deduct 5 points if no persistence mechanism exists, and 3 points if import/export features are missing. Give 10 points if fully implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid date inputs, overlapping shifts, browser timezone differences, 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 shift assignment 2. Automated shift distribution algorithms 3. Mobile responsiveness with touch gestures 4. Visual indicators for shift coverage/understaffing). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple date pickers or calendar views) 2. Function modules unrelated to scheduling (e.g., unnecessary analytics that complicate the UI) 3. Fancy effects that affect performance (e.g., excessive animations when switching 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 calendar logic/scheduling logic/UI components), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors, with clear differentiation between shift types) 2) Proper layout spacing (element spacing follows the 8px multiple principle, with clear cell boundaries) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times, with proper hierarchy for calendar elements). 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 for shift creation/editing 2) Transition animation duration controlled between 300-500ms for calendar navigation 3) Clear visual focus guidance for current selection. Deduct 5 points for each operation without feedback, 3 points for visual after-images during calendar navigation, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "hard"
-}

package/library/management_systems-frontend_backend_platforms/create-student-info-website-xampp-vscode.json

@@ -1,68 +0,0 @@
-{
-  "index": 318,
-  "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. How do I use VS Code and XAMPP panel to create a website for entering information, creating a personal information form that includes name, class, gender, age, student ID, and then store this information in a database so that teachers can access it through an IP address?",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the complete website form structure implemented correctly?",
-      "description": "Check if the HTML/CSS form includes all required fields (name, class, gender, age, student ID) with proper validation attributes. Form should have clear labels, appropriate input types (text for name, number for age, radio/select for gender), and submission controls. Deduct 3 points if any field is missing, 2 points for improper input validation, and 5 points if the form lacks a proper submission mechanism. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the database design and connection properly implemented?",
-      "description": "Evaluate the MySQL database schema creation with appropriate field types (VARCHAR for names, INT for age/ID), constraints (PRIMARY KEY, NOT NULL), and indexes. Check if PHP includes proper database connection parameters and error handling. Deduct 5 points if the schema lacks proper constraints, 3 points if connection strings contain hardcoded credentials without config files, and 5 points if there's no error handling for failed connections. Full score is 15 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is data processing and storage correctly implemented?",
-      "description": "Review the server-side PHP code that processes form submissions. Code should validate input data, sanitize against SQL injection, and properly insert records into the database. Verify that feedback is provided to users after submission. Deduct 5 points for missing input validation, 10 points if SQL injection protection is absent, and 3 points if user feedback is missing. Full score is 15 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the teacher access interface functional and secure?",
-      "description": "Check if the teacher access portal includes authentication (username/password), secure session management, and effective data display functionality. The interface should allow sorting/filtering student records and include pagination for large datasets. Deduct 10 points if authentication is missing, 5 points for unsecured sessions, and 3 points if data viewing features are limited. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as duplicate submissions, invalid data entries, database connection 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 form validation with visual feedback 2. Export functionality to CSV/Excel 3. Dashboard with visual statistics for teachers). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple validation logics) 2. Function modules unrelated to the student information system 3. Fancy effects that affect performance. 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 database/logic/view layers), code organization (proper directory structure for XAMPP deployment), and maintainability (comments, consistent naming). Deduct 5 points if global state pollution is found; deduct 5 points if the code duplication rate is too high (over 30%); deduct 3 points if deployment instructions for XAMPP are unclear. 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) Form submission feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance for form fields. Deduct 5 points for each operation without feedback, 3 points for jarring page refreshes, and 5 points for confusing navigation between student and teacher interfaces. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "easy"
-}

package/library/management_systems-frontend_backend_platforms/create-web-based-information-management-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 1622,
-  "question": "You are a coding expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to make the code you generate executable for demonstration purposes. How do I write a simple web-based information management system?",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core CRUD functionality fully implemented?",
-      "description": "Review whether the code implements all four basic operations (Create, Read, Update, Delete) for managing information entities. Check if form validation exists for data entry, and if data retrieval supports filtering and sorting. Score 0 if core operations are missing, 5 if basic operations exist without validation, and 10 if all operations are implemented with proper validation and error handling.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is there a proper database integration or data persistence mechanism?",
-      "description": "Evaluate whether the code includes database connectivity (SQL or NoSQL) or alternative data persistence methods (like localStorage for demo purposes). Check for prepared statements or ORM to prevent SQL injection. Deduct 5 points if data persistence is completely missing, 3 points if it's implemented but without security considerations. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is there user authentication and authorization functionality?",
-      "description": "Check if the system implements user login/registration with proper password hashing, session management, and role-based access control. Examine whether different user roles have appropriate access restrictions. Deduct 5 points if authentication is missing, 3 points if it exists but with security flaws (like plaintext passwords). The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the application architecture well-structured?",
-      "description": "Assess if the code follows a clear architectural pattern (MVC, MVVM, etc.) with separation of concerns. Look for proper modularization between data access, business logic, and presentation layers. Deduct 5 points for monolithic code without layer separation, 3 points if some structure exists but with significant coupling issues. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code handles common abnormal situations (invalid inputs, server errors, network issues, etc.) and provides friendly error messages. Check for input sanitization to prevent XSS attacks. Code with strong robustness should effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Real-time data visualization 2. Export functionality to PDF/Excel 3. Dark mode toggle 4. Responsive design for mobile compatibility). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple ways to perform the same search) 2. Function modules unrelated to information management (e.g., a built-in game) 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 code organization (file/folder structure), naming conventions, commenting practices, and reusability. Check for dependency management and build process. Deduct 5 points if global variables are overused; deduct 5 points if the code lacks comments or has poor naming; deduct 5 points if there's no clear build/deployment strategy. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface design meet professional standards?",
-      "description": "Evaluate whether the UI follows modern design principles: 1) Consistent color scheme (no more than 3 primary colors) 2) Proper white space and layout (following grid systems) 3) Typography hierarchy (clear difference between headings, body text). Deduct 3 points for cluttered layouts, 5 points for inconsistent styling across pages, and 5 points for poor information hierarchy. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the user experience intuitive and efficient?",
-      "description": "Judge whether the system prioritizes usability: 1) Navigation is clear and consistent 2) Forms have proper validation with instant feedback 3) Loading states are indicated 4) Confirmation is required for destructive actions. Deduct 5 points for confusing navigation, 3 points for missing feedback on user actions, and 5 points for workflows that require excessive clicks. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "easy"
-}

package/library/management_systems-frontend_backend_platforms/customer-salesperson-login-welcome-page.json

@@ -1,68 +0,0 @@
-{
-  "index": 1009,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Ensure that the generated code is executable for demonstration. First, complete the registration and login modules: for individual customers/corporate customers/individual salespeople, provide complete page files. The welcome page should include a redirect button for \"I am a customer, I want to buy insurance\" and a redirect button for \"I am a salesperson, I want to sell insurance\". Modular development is required. Provide the complete file for the welcome page.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the welcome page with proper redirects fully implemented?",
-      "description": "Evaluate if the welcome page includes clearly visible and properly styled redirect buttons for 'I am a customer, I want to buy insurance' and 'I am a salesperson, I want to sell insurance'. Check if clicking these buttons correctly redirects users to appropriate registration/login pages. Score 0 if no welcome page is provided, 5 if the page exists with basic redirects, and 10 if the welcome page is comprehensive with proper routing, responsive design, and intuitive navigation.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are all registration modules for different user types implemented?",
-      "description": "Verify the implementation of registration forms for all specified user types: individual customers, corporate customers, and individual salespeople. Each form should include appropriate fields (e.g., personal details for individuals, company information for corporate users). Assess validation logic for each field (email format, password strength, required fields). Deduct 3 points for each missing user type registration, and 2 points for inadequate validation. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are login modules for all user types functional?",
-      "description": "Check if login functionality exists for all user types with proper authentication logic. Evaluate if login forms include username/email and password fields, 'remember me' option, and 'forgot password' link. Test if authentication errors display appropriate messages. Deduct 3 points for each missing user type login, 2 points if error handling is inadequate, and 2 points if session management is not implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is modular development properly implemented?",
-      "description": "Assess code organization: components should be properly separated, reusable, and follow a logical structure (e.g., separate components for forms, buttons, headers). Check if CSS is modularized (using CSS modules, styled-components, or similar approaches). Verify imports/exports are correctly used. Deduct 5 points if code is monolithic rather than modular, 3 points if styling is not modularized, and 3 points if there's significant code duplication. 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 form validation errors, network issues during login/registration, browser compatibility issues). Test edge cases (e.g., submitting empty forms, very long inputs). Code with strong robustness should provide friendly error prompts and recovery mechanisms. Give 10 points if thoroughly handled, 5 points if basic validation exists but edge cases are missed, and 0 points if no error handling is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Multi-factor authentication 2. Social media login integration 3. Personalized welcome messages 4. Interactive onboarding tour 5. Localization/language selection). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple validation systems) 2. Function modules unrelated to registration/login (e.g., unnecessary widgets) 3. Fancy effects that affect performance (e.g., heavy animations that slow page loading). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (separate components for UI, business logic, and data handling), code organization, naming conventions, and commenting quality. Assess if the code follows industry standard patterns (e.g., React component patterns). Deduct 5 points if global state pollution is found; deduct 5 points if the code duplication rate is high; deduct 5 points if variable/function naming is inconsistent or unclear. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional form design (clear labels, appropriate input sizes, visible focus states) 4) Consistent typography (heading hierarchy, readable font sizes). Deduct 3 points for each design inconsistency, 5 points for accessibility issues (poor contrast, missing ARIA attributes), and 5 points for unprofessional visual appearance. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the form interactions and page transitions conform to user expectations: 1) Form submission feedback is immediate 2) Error messages appear inline near relevant fields 3) Loading states are visually indicated 4) Transitions between pages are smooth. Deduct 5 points for abrupt page changes without feedback, 3 points for delayed form validation feedback, and 5 points for confusing navigation flow. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "easy"
-}

package/library/management_systems-frontend_backend_platforms/data-center-server-management-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 485,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the code you generate is executable for demonstration. Please implement a data center server management system where employees can view the real-time operating status of company servers (CPU usage, memory usage, etc.) through a front-end page; administrators can log into the backend system to manually update server information, display historical performance logs of servers, and mark server health status.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the real-time server monitoring dashboard successfully implemented?",
-      "description": "Evaluate whether the front-end visualization properly displays real-time metrics (CPU usage, memory usage, etc.) with appropriate charts and gauges. Check if WebSocket or polling mechanism is implemented for real-time updates. Score 0 if no visualization exists, 5 if only basic static displays are implemented, and 10 if the dashboard shows comprehensive real-time metrics with appropriate refresh mechanisms.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the admin management backend system fully functional?",
-      "description": "Review whether the admin panel includes secure authentication, server information update forms, and proper validation. Check for CRUD operations on server entries and whether the UI provides clear feedback after operations. Score 3 points for basic authentication, 3 points for complete server management forms, and 4 points for proper validation and error handling.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the historical performance logging and visualization implemented?",
-      "description": "Check if the system stores and displays historical performance data with time-series charts. Evaluate whether filtering by date ranges, server IDs, and metric types is supported. Verify if data aggregation for different time periods (hourly, daily, weekly) is implemented. Score 0 if missing, 5 for basic logs without visualization, and 10 for comprehensive historical data analysis with interactive charts.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the server health status marking and alerting system functioning?",
-      "description": "Review if admins can mark server health statuses (healthy, warning, critical) and if the system has automated threshold-based alerts. Check if notifications are delivered through the UI and possibly email/SMS. Score 3 points for manual status marking, 4 points for threshold configuration, and 3 points for a functional alert delivery system.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code handles edge cases such as server disconnection, data inconsistencies, permission errors, and network issues. Check for proper error boundaries in the UI and graceful degradation. Score 10 points for comprehensive error handling, 5 points for basic error messages, and 0 points if exceptions aren't handled.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check for unique features such as: 1) Predictive analytics for server failures 2) Automated resource optimization suggestions 3) Interactive server topology map 4) Customizable dashboards for different roles. Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1) Multiple implementations of the same monitoring functionality 2) Unnecessary data processing that impacts performance 3) Overly complex visualizations that don't add practical value. Deduct 3 points for each redundancy found, and directly deduct 10 points if core monitoring functionality is compromised by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (separation of data fetching, state management, and UI components), code reusability, and maintainability. Check for consistent error handling patterns and appropriate use of design patterns. Deduct 5 points if global state is poorly managed; deduct 5 points if code duplication exceeds 30%; deduct 5 points if there's no separation between UI and business logic. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the dashboard follows data visualization best practices: 1) Consistent color coding for status indicators 2) Proper information hierarchy with critical metrics prominently displayed 3) Responsive layout that works on different screen sizes. Deduct 3 points for misleading visualizations, 5 points for poor information density (too cluttered or too sparse), and 5 points for inaccessible color schemes. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the system provides smooth user experience: 1) Immediate feedback for admin actions 2) Smooth transitions when switching between views 3) Loading states for asynchronous operations. Deduct 5 points for operations without visual feedback, 3 points for jerky transitions between dashboard states, and 5 points for UI freezes during data processing. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "medium"
-}

package/library/management_systems-frontend_backend_platforms/data-source-list-page-improved-design.json

@@ -1,68 +0,0 @@
-{
-  "index": 1410,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate, professional responses. Make sure the code you generate is executable for demonstration. Help me write a data source list page with an improved interface design, and also include the code file names.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the data list component fully implemented?",
-      "description": "Review whether the code implements a complete data list component including table structure, column headers, data rows, pagination, and sorting functionality. Score 0 if core list rendering is missing, 5 if only basic display is implemented without interactions, and 10 if the list includes proper data binding with dynamic rendering capabilities.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are filtering and search functions properly implemented?",
-      "description": "Check whether the implementation includes comprehensive data filtering mechanisms such as text search, dropdown filters, date range filters, and advanced filtering options. Deduct 3 points if only basic text search is available, 5 points if filters lack real-time feedback, and 7 points if there's no filter persistence between sessions. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the data management functionality complete?",
-      "description": "Evaluate if the code implements CRUD operations (Create, Read, Update, Delete) for the data list. Check for proper form validation, confirmation dialogs for destructive actions, and optimistic UI updates. Deduct 5 points if any CRUD operation is missing, 3 points if validation is incomplete, and 2 points if there's no error handling. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the interface design improved as requested?",
-      "description": "Assess whether the implementation includes significant UI/UX improvements over standard data lists such as responsive design, visual hierarchy, appropriate whitespace usage, and consistent styling. Deduct 5 points for using default/basic styling without customization, 3 points for inconsistent UI patterns, and 5 points for non-responsive designs. 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 empty data sets, network failures, large data volumes, 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. Inline data editing 2. Data visualization elements 3. Keyboard shortcuts for navigation/actions). 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 search mechanisms) 2. Function modules unrelated to data listing (e.g., unnecessary analytics) 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/view/controller layers), component reusability, naming conventions, 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 file structure with appropriate file naming is missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast scrolling, 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"
-}