@getollie/cli 0.0.1

package/library/management_systems-frontend_backend_platforms/historical-business-interface-vue-frontend.json

@@ -0,0 +1,68 @@
+{
+  "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

@@ -0,0 +1,68 @@
+{
+  "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

@@ -0,0 +1,68 @@
+{
+  "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

@@ -0,0 +1,68 @@
+{
+  "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"
+}

package/library/management_systems-frontend_backend_platforms/html-attendance-system-with-table-import.json

@@ -0,0 +1,68 @@
+{
+  "index": 1575,
+  "question": "You are a code expert, please utilize your professional knowledge to generate accurate and professional responses. Be sure to create executable code that can be demonstrated. Include an HTML format attendance system that can import tables.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core attendance system functionality fully implemented?",
+      "description": "Review whether the code accurately implements the fundamental attendance tracking features, including user registration, check-in/check-out functionality, and attendance records storage. Score 0 if the core functions are missing, 5 if basic attendance tracking is implemented but lacks advanced features, and 10 if all necessary attendance tracking features are comprehensively included.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the table import functionality properly implemented?",
+      "description": "Check if the system allows importing attendance data from various table formats (CSV, Excel, etc.). Verify that the import process includes data validation, error handling, and proper display of imported data. Deduct 5 points if the import function is basic without validation, 3 points if only one format is supported, and 2 points if the UI for import is unintuitive. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are data validation and sanitation mechanisms implemented?",
+      "description": "Evaluate whether the code includes proper input validation for all form fields, handles edge cases (like duplicate entries, invalid dates/times), and sanitizes data to prevent XSS attacks. Score 0 if no validation exists, 5 if basic validation is implemented but with security gaps, and 10 if comprehensive validation and sanitation are present.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is there an effective data persistence and retrieval mechanism?",
+      "description": "Assess whether the attendance data is properly stored (client-side storage, server interaction, or both) and can be efficiently retrieved for reporting and analysis. Check if data persistence handles browser refreshes and includes backup mechanisms. Deduct 5 points for poor data structure design and 3 points if data retrieval is inefficient. 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 data input, failed imports, network issues, browser compatibility) 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 attendance analytics 2. Automatic absence notifications 3. Customizable reporting 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 implementation of similar functions (e.g., multiple ways to import the same data format) 2. Function modules unrelated to attendance tracking (e.g., a built-in calculator) 3. Fancy effects that affect performance (e.g., unnecessary animations for basic operations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating data/UI/import-export layers), code organization, and maintainability. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the code lacks comments or documentation. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern 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) Table sorting/filtering response time ≤ 300ms 3) Clear visual guidance for import process steps. Deduct 5 points for each operation without feedback, 3 points for sluggish table operations, and 5 points for confusing import/export workflows. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "medium"
+}

package/library/management_systems-frontend_backend_platforms/html-navicat-operation-interface.json

@@ -0,0 +1,68 @@
+{
+  "index": 1263,
+  "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 for display purposes. Use HTML to help me simulate a Navicat operation interface.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Navicat UI layout structure properly implemented?",
+      "description": "Evaluate whether the HTML code accurately replicates Navicat's signature three-pane layout (connection tree, object browser, and query/result panels). Score 0 if layout is completely different from Navicat, 5 if basic structure is present but with major differences, and 10 if the UI closely resembles the authentic Navicat interface with proper proportions and component placement.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are the essential Navicat database connection components implemented?",
+      "description": "Check for connection management interface elements including connection dialog, server type selection (MySQL, PostgreSQL, Oracle, etc.), connection parameters form, and test connection functionality. Deduct 3 points if connection dialog is missing, 3 points if server type selection is limited, and 4 points if connection parameter fields are incomplete. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the database object browser functionality simulated?",
+      "description": "Verify implementation of the hierarchical tree view for databases, tables, views, stored procedures, etc. Tree nodes should be expandable/collapsible and provide contextual actions. Deduct 5 points if the tree structure is flat or non-interactive, 3 points if context menus are missing, and 2 points if icons don't properly represent object types. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the SQL query editor and results display implemented?",
+      "description": "Assess whether the code includes a proper SQL input area with syntax highlighting, execution controls, and a tabulated results panel. Deduct 4 points for missing syntax highlighting, 3 points for absence of execution controls, and 3 points if result display doesn't support pagination or column sorting. 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 SQL syntax, connection failures, large result sets, 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. Dark/light theme switching 2. SQL history with search function 3. Visual query builder). 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 query execution methods) 2. Function modules unrelated to database management (e.g., built-in games) 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 UI components, database logic, and state management), code organization, and maintainability. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's excessive inline styling instead of CSS classes. 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 matching Navicat's professional look 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 for database operations. Deduct 5 points for each operation without feedback, 3 points for visual after-images during interface transitions, 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/html-patrol-plan-management.json

@@ -0,0 +1,68 @@
+{
+  "index": 1687,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code generated is executable for display when possible. Continue with HTML to create a patrol plan:\n\nSelect patrol route: Choose from preset routes or customize your own route.\n\nSet patrol time: Select start and end times.\n\nAssign patrol personnel: Select patrol officers from the personnel list.\n\nSave plan: Click the \"Save\" button to activate the plan.\n\nEdit patrol plan: Select an existing plan, modify the route, time, or personnel, then click \"Save.\"\n\nDelete patrol plan: Select a plan and click \"Delete.\"\n\nView plan list: Display all patrol plans with filtering options by date, route, and personnel.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the patrol route selection functionality fully implemented?",
+      "description": "Check if the code includes both preset route selection and custom route creation capabilities. The interface should display route options visually (e.g., on a map or as a list) and allow for interactive selection. For custom routes, verify if waypoint creation, modification, and deletion are supported. Score 0 if route selection is missing, 5 if only preset routes are available, and 10 if both preset and fully functional custom route creation are implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are patrol time settings properly implemented?",
+      "description": "Evaluate if the time selection interface provides intuitive date and time pickers for both start and end times. Check if the implementation validates time inputs (preventing end time before start time), handles time zones appropriately, and offers recurring schedule options. Verify if the interface shows visual feedback for selected time periods. Score 0 if time settings are missing, 5 if basic time selection exists but lacks validation, and 10 if time selection is complete with validation and visual indicators.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is personnel assignment functionality complete?",
+      "description": "Review whether the personnel selection interface displays staff availability, shows qualification badges/ratings, and prevents scheduling conflicts. Check if the implementation allows multi-selection of patrol officers and displays their work hours/schedule conflicts. Verify if capacity planning (minimum/maximum officers per patrol) is enforced. Score 0 if personnel assignment is missing, 5 if basic selection exists without conflict checking, and 10 if it's fully implemented with availability checks and qualification filtering.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are plan management operations (save, edit, delete) properly implemented?",
+      "description": "Test if the save, edit, and delete operations are correctly implemented with proper confirmation dialogs, undo capabilities, and data validation. Check if edited plans maintain their historical records and if deletion includes archiving options. Verify if the system prevents deletion of active patrols without supervisor confirmation. Score 0 if these operations are missing, 5 if they exist but lack validation or confirmation features, and 10 if they're fully implemented with all safety measures.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid inputs, network interruptions, concurrent edits, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Real-time GPS tracking integration 2. Weather overlay on patrol routes 3. Mobile notifications for patrol officers 4. AI-suggested optimal patrol routes based on historical incident 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 ways to select personnel with inconsistent UIs) 2. Function modules unrelated to patrol planning (e.g., an embedded social media feed) 3. Fancy effects that affect performance (e.g., unnecessary animations that slow down the interface). 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/service/view layers), component reusability, and responsive design implementation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the code doesn't adapt to different screen sizes. 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": "easy"
+}

package/library/management_systems-frontend_backend_platforms/html-patrol-record-table-device-testing.json

@@ -0,0 +1,68 @@
+{
+  "index": 1758,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code for demonstration purposes. Create a patrol record table for reliability device testing using HTML.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the basic HTML structure for the patrol record table properly implemented?",
+      "description": "Check if the HTML document has a complete structure with DOCTYPE declaration, head, and body sections. Verify if semantic HTML5 elements are used appropriately (table, thead, tbody, etc.). Table should include proper column headers and data cells for patrol records. Deduct 5 points if basic structure is missing, 3 points if semantic HTML is not used, 2 points if accessibility attributes are missing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are all necessary data fields for reliability device testing included in the table?",
+      "description": "Evaluate if the table contains essential fields for reliability testing: device ID, device name, inspection date/time, inspector name, test parameters, test results, anomalies, action taken, and next inspection date. Deduct 2 points for each critical field missing, and 1 point for auxiliary fields (like location, comments). Full implementation with comprehensive fields scores 10 points, basic implementation scores 5 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is data input validation implemented for the reliability testing form?",
+      "description": "Check if form validation is implemented for data entry, including required fields, input type restrictions (numbers for measurements, dates for timestamps), valid ranges for test parameters, and data format validation. Deduct 3 points if required field validation is missing, 3 points if numeric validation is absent, 2 points if date format validation is missing, and 2 points if there's no error feedback. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the table include data filtering and sorting capabilities?",
+      "description": "Review if the table implements sorting functionality (by date, device ID, test results) and filtering options (by pass/fail status, date range, device type). Verify if dynamic reordering works without page reload. Deduct 5 points if sorting is missing, 3 points if filtering is absent, and 2 points if the UI controls are not intuitive. Full implementation scores 10 points, partial implementation scores 5 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as empty data, malformed input, edge cases in data display) 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. Color-coded status indicators 2. Interactive data visualization of test results 3. Responsive design for mobile devices 4. Export to CSV/PDF functionality). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple sorting mechanisms) 2. Function modules unrelated to reliability testing (e.g., unrelated animations) 3. Fancy effects that affect performance (e.g., excessive animations or transitions). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating data/view/controller layers), code reusability, and maintainability. Deduct 5 points if global variables are overused or if code organization is poor; deduct 3 points if the code duplication rate is too high; deduct 2 points if naming conventions are 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 (consistent color scheme for status indicators) 2) Proper layout spacing (table cells properly padded, headers distinguished) 3) Professional font system (readable font sizes, proper contrast). Deduct 3 points for each crowded visual element, 5 points for poor color contrast, and 5 points for inconsistent alignment or spacing. 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 is immediate 2) Sorting/filtering actions respond within 100ms 3) Clear visual indicators for interactive elements. Deduct 5 points for each operation without feedback, 3 points for laggy interactions when handling large datasets, and 5 points for confusing navigation or interaction patterns. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "easy"
+}