@getollie/cli 0.0.4 → 0.2.0

package/library/management_systems-frontend_backend_platforms/hardware-electrical-retail-inventory-management-tool.json

@@ -1,68 +0,0 @@
-{
-  "index": 781,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure that the code you generate is executable when possible. Write code for a hardware and electrical retail store inventory management tool that will allow me to create a simple and user-friendly inventory management software.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core inventory management system properly implemented?",
-      "description": "Review whether the code accurately implements CRUD operations for inventory items, including fields for SKU, product name, category, price, quantity, supplier information, and reorder thresholds. Score 0 if basic inventory operations are missing, 5 if only basic operations are implemented without validation, and 10 if comprehensive inventory management with data validation is included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Does the system include hardware/electrical specific features?",
-      "description": "Check whether the code includes domain-specific features for hardware/electrical retail such as: serial number tracking, warranty management, compatibility indicators, bulk pricing, and technical specifications management. Deduct 2 points for each missing essential feature. Give 10 points if all retail-specific features are implemented appropriately.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the database design and persistence layer well-implemented?",
-      "description": "Evaluate whether the database schema is properly normalized with appropriate relationships between entities (products, suppliers, categories, transactions). Check if the persistence layer handles data integrity, includes backup mechanisms, and uses efficient querying patterns. Deduct 5 points if the database design is flat/denormalized without justification, and 3 points if transaction safety is not implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the system provide comprehensive reporting and analytics?",
-      "description": "Assess whether the code implements essential retail analytics: inventory valuation, sales velocity, stockout prediction, reorder recommendations, and category performance visualization. Deduct 2 points for each missing critical report. The system should allow custom date ranges and export capabilities. Give 10 points if all key metrics are available with visualization.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as duplicate SKUs, negative quantities, invalid price inputs, concurrent access, and data corruption) 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. Barcode/QR code scanning integration 2. Supplier communication module 3. Automated reordering based on sales velocity). 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 update inventory) 2. Function modules unrelated to inventory management (e.g., a built-in game or irrelevant tools) 3. Fancy effects that affect performance (e.g., unnecessary 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 access/business logic/presentation 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 user-friendly?",
-      "description": "Judge whether the interface is truly user-friendly for retail staff: 1) Common operations require ≤ 3 clicks 2) Form auto-completion and validation 3) Clear visual feedback for actions 4) Consistent keyboard shortcuts. Deduct 5 points if bulk operations are not supported, 3 points for confusing navigation paths, and 5 points for operations that require unnecessary confirmation steps. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "hard"
-}

package/library/management_systems-frontend_backend_platforms/harmonyos-login-page-ui-with-logo.json

@@ -1,68 +0,0 @@
-{
-  "index": 292,
-  "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.\n\n```\nbuild() {\n  Column(){\n    Image($r('app.media.logo'))\n      .width(120)\n      .height(120)\n      .margin({bottom: 30})\n    \n    Text('User Login')\n      .fontSize(32)\n      .fontWeight(FontWeight.Bold)\n      .margin({bottom: 40})\n      .fontColor('#333')\n    \n    TextInput({placeholder: 'Please enter username'})\n      .width('80%')\n      .height(50)\n      .margin({bottom: 20})\n      .fontSize(18)\n      .borderRadius(8)\n      .backgroundColor('#f5f5f5')\n      .padding({left: 15})\n      .onChange((value: string) => {this.username = value})\n    \n    TextInput({placeholder: 'Please enter password'})\n      .width('80%')\n      .height(50)\n      .margin({bottom: 30})\n      .fontSize(18)\n      .borderRadius(8)\n      .backgroundColor('#f5f5f5')\n      .padding({left: 15})\n      .type(InputType.Password)\n      .onChange((value: string) => {this.password = value})\n    \n    Button('Login')\n      .width('80%')\n      .height(50)\n      .margin({bottom: 15})\n      .fontSize(18)\n      .fontWeight(FontWeight.Medium)\n      .backgroundColor('#4285f4')\n      .borderRadius(25)\n      .onClick(() => {this.handleLogin()})\n    \n    Button('Register')\n      .width('80%')\n      .height(50)\n      .fontSize(18)\n      .fontWeight(FontWeight.Medium)\n      .backgroundColor('#34a853')\n      .borderRadius(25)\n      .onClick(()=>{\n        router.pushUrl({url:'pages/RegisterPage'})\n      })\n  }\n  .width('100%')\n  .height('100%')\n  .justifyContent(FlexAlign.Center)\n  .backgroundImage($r('app.media.background'))\n  .backgroundImageSize(ImageSize.Cover)\n}\n```\n\nPlease improve the style to make it look better and add a logo.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the login interface layout properly implemented and visually balanced?",
-      "description": "Review whether the layout elements (logo, title, input fields, buttons) are properly aligned, spaced, and sized. Check if the column arrangement provides a clear visual hierarchy and if the justifyContent property correctly centers the content. Deduct 3 points if elements appear crowded or misaligned, 5 points if the visual hierarchy is confusing, and 5 points if responsive layout considerations are missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the input fields properly designed with appropriate user feedback?",
-      "description": "Evaluate if text input fields include proper validation feedback, focus states, and error handling. Check if the password field properly obscures text and if there are clear visual cues for input status. Deduct 3 points if validation feedback is missing, 3 points if there's no visual indication of focus state, and 4 points if there's no error handling for invalid inputs. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the authentication flow complete with proper error handling?",
-      "description": "Assess whether the handleLogin() function includes proper user authentication logic, loading states, error messages, and security measures (like input sanitization). Deduct 5 points if there's no loading state during authentication, 5 points if error handling is inadequate, and 5 points if no security measures are implemented for handling credentials. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the navigation between login and registration pages properly implemented?",
-      "description": "Check if the navigation using router.pushUrl() is correctly implemented with proper state management between pages. Verify if there's a way to return to the login page from registration and if the navigation preserves user input when appropriate. Deduct 3 points if back navigation is missing, 4 points if state isn't preserved appropriately between navigations, and 3 points if there are no animations for page transitions. 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 inputs, network issues during login, memory leaks) 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. Biometric authentication option 2. Remember me functionality 3. Password strength indicator 4. Social login options). 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 style declarations (e.g., multiple margin definitions) 2. Unnecessary components that don't contribute to the login functionality 3. Overly complex animations that might affect performance on lower-end devices. 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/logic/state management), reusability of components, and proper organization of resources. Deduct 5 points if business logic is mixed with UI code; deduct 5 points if there's significant code duplication; deduct 5 points if resources like images are not properly organized. 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 consistent principles) 3) Professional font system (appropriate font sizes and weights for hierarchy). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for inconsistent visual styling. 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) Immediate visual feedback for button presses 2) Smooth transitions between states 3) Appropriate loading indicators. Deduct 5 points for each interaction without feedback, 3 points for jarring transitions, and 5 points for confusing interaction patterns. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Multimedia Editing-Image Editing",
-  "difficulty": "medium"
-}

package/library/management_systems-frontend_backend_platforms/hbuilder-html-ward-management-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 900,
-  "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. Help me create an HTML for a ward management system that can run on Hbuilder.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the ward management system's core functionality implemented?",
-      "description": "Evaluate whether the code implements essential ward management features: patient registration, bed assignment, staff scheduling, and patient records management. Score 0 if core functionalities are missing, 5 if only basic features are implemented, and 10 if comprehensive ward management capabilities are included with proper data validation.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the UI structure properly designed for a ward management system?",
-      "description": "Check whether the HTML structure follows proper hierarchy with semantic elements (header, nav, main, section, footer). Verify the presence of responsive design for different screen sizes (desktop, tablet, mobile) since ward staff may use various devices. Deduct 3 points if semantic HTML is not used, 3 points if responsiveness is missing, and 4 points if the navigation structure is confusing.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the data management and persistence properly implemented?",
-      "description": "Assess whether the system implements proper data handling mechanisms: local storage usage, form validation, and state management. Check for data integrity features like input validation and proper data structures. Deduct 5 points if no data persistence is implemented, and 5 points if input validation is inadequate or missing.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is HBuilder compatibility considered in the implementation?",
-      "description": "Verify whether the code utilizes HBuilder-specific features or plugins properly, like HTML5+ API integration, MUI components, or other HBuilder capabilities. Check if the app is configured for HBuilder deployment. Deduct 5 points if HBuilder compatibility issues exist, and 5 points if no HBuilder-specific optimizations are included.",
-      "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 issues, or user operation errors) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Real-time bed occupancy visualization 2. Patient critical status alerts 3. Drag-and-drop bed assignment interface). 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 patient search methods) 2. Function modules unrelated to ward management (e.g., a built-in game for staff) 3. Fancy effects that affect performance (e.g., unnecessary 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), code organization, and maintainability. Deduct 5 points if global variable pollution is found or if proper JavaScript patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the code structure makes future maintenance difficult. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface design meet healthcare UI standards?",
-      "description": "Evaluate whether the UI follows healthcare design principles: 1) Clean, professional color scheme appropriate for medical settings 2) Proper information hierarchy with critical patient data easily accessible 3) Consistent typography suitable for clinical reading (body font size ≥ 14px, clear headings). Deduct 3 points for visual clutter, 5 points for inappropriate color schemes for healthcare, and 5 points for poor information architecture. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and user-friendly for healthcare staff?",
-      "description": "Judge whether the system is optimized for healthcare workflows: 1) Quick access to critical patient information (≤ 2 clicks) 2) Form completion and submission within 30 seconds 3) Clear visual indicators for patient status changes. Deduct 5 points for each workflow requiring excessive steps, 3 points for slow-loading interfaces, and 5 points for confusing navigation between key system areas. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "easy"
-}

package/library/management_systems-frontend_backend_platforms/higher-math-grade-management-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 835,
-  "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. Design a main interface for a higher mathematics grade information management system after student login, including functions such as grade inquiry, grade analysis, information notifications, and comparison with previous grades.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the student login system fully implemented?",
-      "description": "Examine whether the code implements secure user authentication with proper session management, input validation, and protection against common security threats (like SQL injection, XSS). Check if it includes password hashing, CSRF protection, and proper error handling. Score 0 if authentication is missing, 5 if basic login exists with security flaws, and 10 if a complete, secure authentication system is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the grade inquiry feature complete and user-friendly?",
-      "description": "Verify if the grade inquiry system provides comprehensive views (by subject, semester, academic year), allows filtering/sorting, and includes detailed grade breakdown. Check for data visualization elements that enhance readability. Deduct 5 points if only basic listing is available without filtering options; deduct 3 points if there's no visual representation of grades. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Does the grade analysis functionality provide meaningful insights?",
-      "description": "Evaluate whether the analysis includes statistical measures (mean, median, standard deviation), percentile rankings, performance trends over time, and subject-specific analytics. Check for comparative analysis against class/department averages. Deduct 5 points if only basic statistics are shown; deduct 5 points if visualizations (charts, graphs) are missing or poorly implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the notification system properly implemented with comparison features?",
-      "description": "Assess whether the system includes real-time notifications for new grades, important announcements, and grade changes. Check if the grade comparison feature allows side-by-side analysis between current and previous performance with clear visual indicators for improvement/decline. Deduct 5 points if notifications are static only; deduct 5 points if comparison lacks visual differentiation or trend analysis. 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 missing grade data, network issues, edge cases in calculations, etc.) and provide friendly error messages 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. Predictive grade forecasting based on current performance 2. Personalized study recommendations based on weak areas 3. Peer anonymized performance comparison). 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 view the same information) 2. Function modules unrelated to grade management (e.g., a built-in general calculator) 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 logic/view/controller 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/historical-business-interface-vue-frontend.json

@@ -1,68 +0,0 @@
-{
-  "index": 1023,
-  "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 display. The system's \"Historical Business\" interface. The function bar at the top supports searching processes through different methods: process name \"supports fuzzy search\"; process code \"does not support fuzzy search\"; creation time \"select start time\"; business type \"select business type\". Below the search bar are two buttons \"Search\" and \"Reset\". At the bottom of the interface is a menu table with columns: \"Process Name\", \"Task Name\", \"Initiator\", \"Handler\", \"Creation Time\", \"End Time\", \"Duration\", and \"Operation (History)\".\nBased on the above description, please help me write a frontend code snippet using Vue.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the search functionality fully implemented?",
-      "description": "Review whether the code accurately implements all search methods: process name (fuzzy search), process code (exact match), creation time (date selection), and business type (dropdown selection). Check if the search logic properly filters data based on these criteria. Score 0 if search functionality is missing, 5 if only basic search is implemented without proper validation, and 10 if all search methods are correctly implemented with appropriate validation and error handling.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the Search and Reset buttons properly implemented?",
-      "description": "Check whether the Search button triggers the correct filtering action with proper loading states and the Reset button clears all filters and restores the original data display. Verify that clicking Search with empty filters shows all records or provides appropriate feedback. Deduct 5 points if the Reset functionality is incomplete, and 3 points if the Search button doesn't handle loading states properly. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the data table implementation complete and correct?",
-      "description": "Evaluate whether all required columns are included in the table: Process Name, Task Name, Initiator, Handler, Creation Time, End Time, Duration, and Operation (History). Check if the table handles empty states, loading states, and pagination properly. Verify that the History operation link/button works correctly. Deduct 3 points for each missing column, 5 points for missing pagination, and 5 points if the table doesn't handle empty or error states. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the Vue component structure properly designed?",
-      "description": "Assess whether the code follows Vue best practices with proper component organization, Vue lifecycle hooks usage, computed properties for derived data, and watchers where appropriate. Check for proper prop validation and event handling. Deduct 5 points for global variable abuse, 3 points for monolithic component design without proper separation of concerns, and 5 points for direct DOM manipulation outside Vue's reactive system. 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, empty search results, invalid input data, 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. Saved search filters 2. Customizable table columns 3. Export functionality for table data). 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 filtering logics) 2. Function modules unrelated to the business history interface (e.g., unrelated menus or widgets) 3. Fancy effects that affect performance (e.g., unnecessary animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating data fetching/UI/business logic), component reusability, and code organization. Deduct 5 points if global state management is poorly implemented; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no error handling for API calls. 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 loading/filtering, 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/housekeeping-recruitment-backend-dashboard-vue3-elementplus.json

@@ -1,68 +0,0 @@
-{
-  "index": 801,
-  "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 write a super cool and amazing housekeeping recruitment backend management system console page DashBoard.vue using Vue3 + ElementPlus.\n\nThe content includes multiple sections:\n1. Some menu item shortcuts, which can be displayed directly with small icons + names below\n2. Use statistical components to display data, such as total users, new user messages/feedback, pending review items and quantities\n3. Chart information: weekly registered users bar chart component\n4. Administrator personal information: avatar, name, last login time\n\nPlease display these contents with perfect layout - you can reference other well-known designs for deciding which content should appear at the top or bottom.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Vue3 + ElementPlus dashboard structure properly implemented?",
-      "description": "Review whether the code correctly uses Vue3 Composition API with ElementPlus components to build a complete dashboard layout. Check if el-container, el-header, el-main are properly structured, and if reactive data management is implemented using ref/reactive. Score 0 if basic Vue3 syntax is incorrect, 5 if only basic layout is achieved, and 10 if all Vue3 best practices are followed with proper component composition.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the menu shortcuts and statistical components fully functional?",
-      "description": "Evaluate whether menu shortcuts are implemented with proper icons and click handlers, and if statistical components (total users, messages, pending reviews) display dynamic data with proper formatting. Check for el-card, el-statistic, or custom stat components with hover effects. Deduct 5 points if icons are missing or not properly aligned, 3 points if statistical data is static without proper number formatting. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the weekly registered users bar chart correctly implemented?",
-      "description": "Check whether a proper charting library (ECharts, Chart.js, etc.) is integrated to display weekly user registration data as a bar chart. The chart should be responsive, interactive, and properly styled. Deduct 5 points if chart data is not dynamic or realistic, 3 points if chart is not responsive to container size changes, and 5 points if chart styling doesn't match the overall theme. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the administrator personal information section well-designed?",
-      "description": "Evaluate whether the admin profile section includes a proper avatar display, name, and last login time with appropriate formatting. Should use el-avatar, proper date formatting, and responsive layout. Check if the personal info section is positioned logically (typically top-right or dedicated card). Deduct 3 points for poor date formatting, 5 points if avatar is not properly displayed, and 5 points for poor positioning. 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, missing data, component loading errors, etc.) and provide friendly error prompts or fallback mechanisms. Code with strong robustness should include proper error boundaries, loading states, and empty data 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 dashboard experience (e.g., 1. Real-time data updates with WebSocket 2. Dark/light theme toggle 3. Customizable widget arrangement 4. Data export functionality 5. Quick action shortcuts). 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 dashboard widgets 2. Features unrelated to housekeeping management (e.g., built-in games or irrelevant tools) 3. Excessive animations that affect dashboard performance. Deduct 3 points for each redundancy found, and directly deduct 10 points if core dashboard functionality is interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review component modularity (separating dashboard widgets into reusable components), proper Vue3 composition, and TypeScript usage if applicable. Deduct 5 points if components are not properly separated or props/emits are not well-defined; deduct 5 points if code organization is poor with mixed concerns; deduct 5 points if no proper state management is implemented for dashboard data. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface design meet professional dashboard standards?",
-      "description": "Evaluate whether the dashboard design follows modern admin panel principles: 1) Consistent ElementPlus theme with proper color hierarchy 2) Grid-based layout with proper spacing (8px/16px multiples) 3) Clear visual hierarchy with proper card shadows and borders 4) Professional typography with readable font sizes (≥14px). Deduct 3 points for each inconsistent visual element, 5 points for poor color contrast or accessibility issues, and 5 points for cramped or misaligned layouts. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dashboard interaction smooth and intuitive?",
-      "description": "Judge whether the dashboard interactions follow UX best practices: 1) Hover effects on interactive elements with ≤100ms response 2) Smooth transitions for data updates (300-500ms) 3) Clear loading states for async operations 4) Intuitive navigation flow between dashboard sections. Deduct 5 points for each missing hover state, 3 points for jarring transitions or layout shifts, and 5 points for unclear or hard-to-find key dashboard functions. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "easy"
-}

package/library/management_systems-frontend_backend_platforms/housing-construction-pre-sales-demo-addresses.json

@@ -1,68 +0,0 @@
-{
-  "index": 1095,
-  "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 write a hyperlink page for accessing different system addresses, which needs to be published through Windows IIS (so please tell me the detailed publishing method). The page should be titled \"Housing and Construction Business Group Pre-sales Demonstration Address Collection\" and present system names, descriptions, and addresses in list format. The page should allow manual maintenance of system names, addresses, and descriptions. Please implement this page with code, enabling me to maintain system information and publish it myself. Add a search box, and at the bottom, include a fixed line of text that is not affected by scrolling: Copyright: Guangdong Nanfang Digital Technology Co., Ltd.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the basic HTML structure properly implemented for an IIS-hosted page?",
-      "description": "Check if the code includes a complete HTML structure with proper DOCTYPE, meta tags (including charset and viewport), title element set to 'Housing and Construction Business Group Pre-sales Demonstration Address Collection', and appropriate CSS/JS references. Verify that file extensions are compatible with IIS (.html, .aspx, etc.). Score 0 if the structure is incomplete, 5 if basic structure exists but lacks important meta tags, and 10 if fully implemented with proper IIS considerations.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the system address listing functionality fully implemented?",
-      "description": "Evaluate whether the code correctly implements the core functionality to display system names, descriptions, and addresses in a structured list format. Check if the list is properly styled, organized, and renders correctly. Score 5 if only basic unstyled listing is implemented, 8 if the listing has proper styling but lacks organization, and 10 if the implementation includes proper sectioning, styling, and visual hierarchy that enhances readability.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the manual maintenance functionality properly implemented?",
-      "description": "Assess whether the code provides a complete interface for adding, editing, and deleting system information (names, addresses, descriptions). Check for form validation, data persistence mechanism (localStorage, server-side storage, etc.), and intuitive editing UI. Score 0 if maintenance functionality is missing, 5 if basic functionality exists but lacks validation or proper UI, and 10 if full CRUD operations with validation and user-friendly interface are implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the search box functionality correctly implemented?",
-      "description": "Verify that the search functionality works as expected - filtering systems by name, description, or address in real-time or upon submission. Check if the search is case-insensitive, handles partial matches, and provides appropriate feedback when no results are found. Score 0 if search is missing, 5 if basic search exists but has limitations, and 10 if search is fully functional with filtering options and proper user feedback.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as empty data, malformed inputs, storage limitations) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should prevent XSS attacks when displaying user-entered content. Score 10 points for comprehensive error handling, 5 points for partial handling of edge cases, and 0 points if critical exceptions aren't addressed.",
-      "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. Export functionality to CSV/PDF 2. Dark/light mode toggle 3. Responsive design for mobile access). 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 methods) 2. Function modules unrelated to address listing (e.g., unnecessary widgets) 3. Fancy effects that affect performance (e.g., heavy 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), code organization, and maintainability. Check for proper comments, consistent naming conventions, and separation of concerns. Deduct 5 points if global variables are excessively used; deduct 5 points if the code has high duplication; deduct 5 points if CSS, HTML, and JS are mixed without clear separation. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface design meet professional 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": "Are IIS deployment instructions clear and accurate?",
-      "description": "Assess whether the provided IIS publishing method is detailed, accurate, and complete. Instructions should include file placement, IIS configuration, permissions setup, and any required Windows configurations. Score 0 if instructions are missing, 5 if basic instructions are provided but lack important details, and 10 if comprehensive step-by-step instructions with screenshots or diagrams are included to ensure successful deployment even by someone unfamiliar with IIS.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "easy"
-}

package/library/management_systems-frontend_backend_platforms/how-to-achieve-excellence-daily-habits.json

@@ -1,68 +0,0 @@
-{
-  "index": 1313,
-  "question": "You are a Code Expert\n\nYou are a code expert. Please use your professional knowledge to generate accurate and professional responses. Try to ensure that any code you provide is executable.\n\nTo become excellent, a person needs to make continuous efforts and optimizations in multiple aspects. Here are some key suggestions to help a person move towards excellence every day:\n\n### 1. **Set Clear Goals**\n   - **Short-term goals**: Set specific, achievable small goals every day to maintain motivation and direction.\n   - **Long-term goals**: Clarify long-term life or career goals and develop step-by-step plans.\n\n### 2. **Efficient Time Management**\n   - **Priority ranking**: Use the \"Important-Urgent\" matrix to prioritize important and urgent tasks.\n   - **Time planning**: Create daily plans, allocate time reasonably, and avoid procrastination.\n   - **Focus and rest**: Use techniques like the \"Pomodoro Technique\" to maintain a balance between efficient work and appropriate rest.\n\n### 3. **Continuous Learning and Growth**\n   - **Reading and learning**: Spend time daily reading books, articles, or learning new skills to keep knowledge updated.\n   - **Reflection and summary**: Reflect on the day's gains and shortcomings at the end of each day, record growth points.\n   - **Learn from others**: Actively seek advice from excellent people, absorb their experience and wisdom.\n\n### 4. **Cultivate Healthy Habits**\n   - **Regular routine**: Maintain adequate sleep, go to bed early and rise early to ensure energy.\n   - **Healthy diet**: Focus on balanced nutrition, avoid excessive intake of junk food.\n   - **Consistent exercise**: Exercise appropriately every day to maintain physical and mental health.\n\n### 5. **Positive Mindset and Emotional Management**\n   - **Self-motivation**: Give yourself positive affirmation every day to maintain a positive mindset.\n   - **Emotional regulation**: Learn to manage stress and negative emotions, maintain inner peace and stability.\n   - **Gratitude and optimism**: Record things to be grateful for every day, cultivate an optimistic attitude toward life.\n\n### 6. **Social and Interpersonal Relationships**\n   - **Build quality relationships**: Associate with positive people, stay away from negative energy.\n   - **Help others**: Do some good deeds within your ability every day, cultivate altruistic spirit.\n   - **Communication and listening**: Improve communication skills, learn to listen to others' opinions and suggestions.\n\n### 7. **Focus and Deep Work**\n   - **Reduce distractions**: Stay away from phones, social media, and other distractions to focus on important tasks.\n   - **Deep thinking**: Spend time daily on deep thinking, solving complex problems, or innovating.\n\n### 8. **Continuous Improvement and Iteration**\n   - **Accept feedback**: Actively seek feedback from others to improve your shortcomings.\n   - **Courage to try**: Don't fear failure, try new things every day and accumulate experience.\n   - **Iterative optimization**: Regularly review your plans and methods, continuously optimize and adjust.\n\n### 9. **Maintain Curiosity and Creativity**\n   - **Explore the unknown**: Expose yourself to new fields or knowledge every day, maintain curiosity about the world.\n   - **Cultivate creativity**: Stimulate creativity through writing, drawing, music, and other means.\n\n### 10. **Financial and Life Management**\n   - **Financial planning**: Pay attention to your financial situation daily, make reasonable consumption and savings plans.\n   - **Simplify life**: Reduce unnecessary material needs, focus on what truly matters.\n\n### Sample Daily Schedule:\n- **Morning**: Early rise, exercise, meditation, reading or learning.\n- **Morning**: Handle important tasks, focus on work or study.\n- **Noon**: Healthy lunch, short break.\n- **Afternoon**: Continue work or study, handle secondary tasks.\n- **Evening**: Summarize the day, read or study, communicate with family and friends.\n- **Before bed**: Relax, prepare plans for the next day.\n\n### Conclusion\nExcellence is not achieved overnight but accumulated through daily small habits and continuous effort. The key lies in perseverance, self-discipline, and constantly optimizing your lifestyle. As long as you move toward your goals every day, you will eventually become a better self.\n\nI meant to create a board based on this.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the personal excellence tracking board fully implemented?",
-      "description": "Review whether the code accurately implements a visual dashboard for tracking personal excellence metrics across all 10 categories mentioned (goals, time management, learning, habits, mindset, relationships, deep work, improvement, curiosity, finances). Score 0 if the board is not implemented, 5 if only basic tracking is available, and 10 if comprehensive tracking with data visualization for all categories is included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the daily task management and tracking system implemented?",
-      "description": "Check if the implementation includes functionality for setting daily tasks, marking completion, and visualizing progress over time. The board should include prioritization features (Important-Urgent matrix) and time planning elements. Deduct 3 points if task prioritization is missing, 4 points if progress tracking over time is absent, and 3 points if there's no visual feedback on completion. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the habit tracking and streak visualization feature implemented?",
-      "description": "Evaluate whether the code provides mechanisms to define recurring habits, track streaks, and visualize consistency. Should include graphical representations for habit completion rates and streak maintenance. Deduct 4 points if streak visualization is missing, 3 points if habit categories are not customizable, and 3 points if there's no data export/backup feature. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the goal setting framework with progress tracking implemented?",
-      "description": "Check if the board implements both short-term and long-term goal tracking with visual progress indicators. Should include milestone tracking, deadline management, and goal categorization. Deduct 3 points if goal hierarchy (short vs long-term) is not implemented, 4 points if progress visualization is missing, and 3 points if reminders/alerts for upcoming deadlines aren't included. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid inputs, browser storage limitations, data inconsistencies, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. AI-powered habit recommendations 2. Mood tracking correlation with productivity 3. Social accountability integrations 4. Pomodoro timer with customizable work/break periods). 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 tracking metrics (e.g., multiple overlapping habit trackers) 2. Function modules unrelated to personal excellence (e.g., a built-in game) 3. Fancy effects that affect performance (e.g., excessive animations that slow loading). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating data/view/controller 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"
-}