@getollie/cli 0.0.1

package/library/utility_tools-daily_office_tasks/add-lunar-holidays-perpetual-calendar.json

@@ -0,0 +1,68 @@
+{
+  "index": 1656,
+  "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 and functional. Add lunar holidays and integrate them to create a perpetual calendar code.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the perpetual calendar core functionality fully implemented?",
+      "description": "Review whether the code accurately implements a perpetual calendar system that displays dates correctly across all years (past and future). Check that it properly handles leap years, month lengths, and weekday calculations. Score 0 if the core calendar logic is incorrect, 5 if basic functionality works but with edge case errors, and 10 if the calendar works flawlessly for any arbitrary date.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the lunar holiday integration complete and accurate?",
+      "description": "Evaluate the implementation of lunar holiday calculations. The code should accurately convert between Gregorian and lunar calendars and correctly identify lunar holidays. Verify the accuracy of the lunar date algorithm across different years. Deduct 5 points if the lunar calendar conversion has inaccuracies, 3 points if only major lunar holidays are included, and 2 points if regional lunar holidays are missing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are the solar (Gregorian) holidays properly implemented?",
+      "description": "Check whether the code includes major international and regional solar holidays, with proper handling of holidays that fall on specific weekdays (like 'First Monday of September'). Verify that the code handles holidays that change dates annually. Deduct 3 points if only fixed-date holidays are supported, 2 points if movable holidays are missing, and 5 points if holiday categorization is absent. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is there a comprehensive date navigation and search system?",
+      "description": "Assess the calendar's navigation capabilities, including the ability to jump between years/months, search for specific dates or holidays, and bookmark significant dates. Verify that users can easily find dates of interest through intuitive controls. Deduct 5 points if year/month navigation is cumbersome, 3 points if holiday search functionality is missing, and 2 points if there's no direct date input option. 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 dates, out-of-range years, unsupported locales, 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. Multi-cultural calendar systems integration 2. Historical event integration for significant dates 3. Personalized reminder system for recurring events). 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 date calculation algorithms 2. Function modules unrelated to calendar functionality (e.g., non-date-related widgets) 3. Unnecessarily complex visualizations that affect performance. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating calendar logic/view/data layers), unit test coverage for date calculations, and appropriate data structures for holiday storage. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no separation between the calendar engine and the UI. 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 calendar design principles: 1) Clear visual hierarchy between months, weeks, and days 2) Proper differentiation of weekdays, weekends, and holidays 3) Professional color-coding system for different types of holidays. Deduct 3 points for cluttered date displays, 5 points for poor holiday highlighting, and 5 points for inconsistent date cell sizing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the calendar interactions conform to user expectations: 1) Month/year switching transitions under 300ms 2) Immediate visual feedback when selecting dates 3) Smooth hover states for interactive elements. Deduct 5 points for laggy month transitions, 3 points for delayed holiday information display, and 5 points for unresponsive date selection. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Utility Tools-Daily Office Tasks",
+  "difficulty": "hard"
+}

package/library/utility_tools-daily_office_tasks/ant-design-vue-excel-import-export-table.json

@@ -0,0 +1,68 @@
+{
+  "index": 262,
+  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Make sure that the generated code is executable for demonstration purposes. Please write an import and export function with Ant Design Vue, requiring that when the import button is clicked, data from an Excel file will be imported into an <a-table> data table.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the import and export functionality fully implemented?",
+      "description": "Check if the code implements both import and export functions. Import should correctly parse Excel data and populate the table; export should generate a downloadable Excel file from table data. Score 0 if neither function works, 5 if only one direction works correctly, and 10 if bidirectional functionality is complete with proper file handling.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the Excel parsing implementation correct and robust?",
+      "description": "Evaluate if the code uses proper libraries (like SheetJS/xlsx) to handle Excel files. Check if it handles different Excel formats (.xls, .xlsx), sheet selection, handles headers correctly, and supports various data types (text, numbers, dates). Deduct 3 points if only basic data types are supported, 5 points if it fails with large files (>1MB), and 3 points if encoding issues aren't handled.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the Ant Design <a-table> integration properly implemented?",
+      "description": "Check if the table component is correctly initialized with dynamic columns based on imported data, if pagination works, if sorting/filtering is preserved during import/export, and if the table UI updates properly after import. Deduct 5 points if column mapping is hardcoded, 3 points if the table doesn't visually refresh after import, and 5 points if no loading state is displayed during operations.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is there appropriate user feedback during the import/export process?",
+      "description": "Verify if the code includes loading indicators, progress feedback, success/error notifications, and validation results display. Check if the user is warned about data loss when replacing existing table data. Deduct 5 points if no progress indication exists for large files, 3 points if error messages are generic/unhelpful, and 5 points if validation failures are not clearly highlighted.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid file formats, incomplete data, empty files, special characters in data) 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. Preview before import 2. Column mapping UI 3. Data validation with highlighting 4. Template download option). 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 libraries for the same purpose (e.g., multiple Excel parsing libraries) 2. Function modules unrelated to import/export (e.g., unnecessary filters) 3. Overly complex implementations that could be simplified. 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/service layers), error handling patterns, and reusability. 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 are no comments for complex logic. 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 Ant Design principles: 1) Consistent with Ant Design styles 2) Proper button placement and hierarchy 3) Clear visual feedback for states (idle, loading, success, error). Deduct 3 points for each UI element that breaks from Ant Design guidelines, 5 points for inconsistent visual style, and 5 points for poor information hierarchy. 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) Clear indication when file selection is in progress 2) Smooth transition when data loads into table 3) Appropriate animation for success/error states. Deduct 5 points for each operation without feedback, 3 points for jarring transitions between states, and 5 points if the import/export buttons are not disabled during processing to prevent multiple submissions. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Utility Tools-Daily Office Tasks",
+  "difficulty": "hard"
+}

package/library/utility_tools-daily_office_tasks/app-with-work-items-tasks-pomodoro-timer.json

@@ -0,0 +1,68 @@
+{
+  "index": 773,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code whenever possible. I want to create an APP that includes work item categorization, task lists, and a Pomodoro timer. What APP integration platform should I use, and can you provide the complete programming code?",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the work item categorization system properly implemented?",
+      "description": "Evaluate whether the code implements a comprehensive categorization system that allows for hierarchical organization (projects > categories > tasks), tag-based filtering, and priority assignment. Check if it includes data validation for category creation/editing and proper handling of category deletion (including orphaned tasks). Score 0 if categorization is absent, 5 if basic categorization exists, and 10 if advanced features like custom fields or category-based analytics are implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the task list functionality complete and intuitive?",
+      "description": "Examine the task list implementation for core features like task creation, editing, deletion, status tracking, due dates, reminders, and sorting/filtering options. Check if the code handles task dependencies, recurring tasks, and progress tracking. Deduct 5 points if basic CRUD operations are missing, and 3 points if there's no offline data persistence. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the Pomodoro timer properly implemented with standard features?",
+      "description": "Review the Pomodoro timer code for accurate time tracking, configurable work/break intervals, audio notifications, and session counting. Check if it handles background execution and device sleep modes correctly. Deduct 5 points if timer continues running in background without proper notifications, 3 points if customization options are limited, and 5 points if there's no session history. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the integration between components seamless and logical?",
+      "description": "Assess how well the three main components (categorization, task lists, and Pomodoro timer) are integrated. Check if tasks can be associated with timer sessions, if completed pomodoros update task progress, and if the categorization system affects task visibility. Deduct 5 points if components operate in isolation, 3 points if data sharing between components requires manual user intervention. 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 incorrect input data, network interruption, app backgrounding, 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-based task prioritization 2. Visual productivity analytics 3. Social accountability features 4. Voice command support). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple timer implementations) 2. Function modules unrelated to productivity management 3. Fancy effects that affect performance (e.g., excessive animations that slow down task entry). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating business logic/UI/data persistence layers), 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": "Utility Tools-Daily Office Tasks",
+  "difficulty": "medium"
+}

package/library/utility_tools-daily_office_tasks/baby-event-event-recorder.json

@@ -0,0 +1,68 @@
+{
+  "index": 1335,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate, professional responses. Be sure the code you generate is executable when presented. Please create a small program that can record baby feeding times, diaper change times, and other similar events.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core baby event tracking functionality fully implemented?",
+      "description": "Review whether the code accurately implements recording of feeding times (including type, duration, amount), diaper changes (including type, severity), and other critical baby care events. Score 0 if the core data entry logic is missing, 5 if only basic event logging is implemented without details, and 10 if comprehensive event tracking with timestamps and detailed parameters is fully included.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the data persistence mechanism properly implemented?",
+      "description": "Evaluate whether the application properly stores event data locally or through a backend service. Check for proper data structuring, consistent storage approach (localStorage, IndexedDB, file system, or database), and data retrieval mechanisms. Deduct 5 points if there's no data persistence, 3 points if data is poorly structured or prone to corruption. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Does the application provide adequate data visualization and reporting?",
+      "description": "Check whether the application offers meaningful ways to visualize baby care data (charts, timelines, etc.) and provides reports or summaries of trends. Evaluate if data can be filtered by date ranges and event types. Deduct 5 points if visualization is missing, 3 points if visualizations are present but not useful for parental decision-making. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the multi-caregiver functionality and notification system implemented?",
+      "description": "Assess whether the application supports multiple caregivers (user accounts or profiles) and implements notifications or reminders for scheduled care events. Check for synchronization between caregivers if applicable. Deduct 5 points if multi-caregiver support is missing, and 3 points if notification functionality is absent. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid input data, network issues if applicable, interrupted operations) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should effectively handle input validation, data type checking, and 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-based insights on baby patterns 2. Integration with smart baby monitors 3. Customizable event categories and fields). 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 log the same event type) 2. Function modules unrelated to baby care tracking (e.g., a built-in general calendar) 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), 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 interactions, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Utility Tools-Daily Office Tasks",
+  "difficulty": "easy"
+}

package/library/utility_tools-daily_office_tasks/browser-screenshot-tool-with-editing.json

@@ -0,0 +1,68 @@
+{
+  "index": 631,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the generated code is executable for demonstration purposes. Develop code for a screenshot tool that allows users to capture browser areas through simple button triggers, supporting three modes: selected area, current visible window, and entire webpage. Users should be able to perform simple edits on the screenshots (such as adding text, drawing boxes, marking with arrows). Finally, users should be able to save the screenshot as an image format and download it quickly.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the screenshot capture functionality fully implemented?",
+      "description": "Review whether the code accurately implements all three required screenshot modes (selected area, current visible window, and entire webpage). Check if the selection mechanism for the 'selected area' mode allows for precise rectangular selections with visual feedback. Score 0 if no capture functionality works, 5 if only some modes are implemented, and 10 if all three modes work correctly with proper user feedback.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "How well is the screenshot editing functionality implemented?",
+      "description": "Evaluate the implementation of the editing tools (text addition, rectangle drawing, and arrow marking). Check if the text tool supports font customization, if rectangle drawing allows for different colors/sizes, and if arrow markers can be properly positioned and oriented. Deduct 3 points if any required tool is missing, 2 points if a tool lacks essential customization options, and 5 points if the edit interface is not intuitive. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the image saving and downloading feature properly implemented?",
+      "description": "Check if the screenshot can be saved in common image formats (PNG/JPG) and if the download functionality works correctly. Verify that the download process initiates promptly, uses appropriate file naming conventions, and preserves image quality. Deduct 5 points if only one format is supported, 3 points if the download process is overly complicated, and 7 points if downloaded images show quality degradation. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "How well does the tool handle browser compatibility and permissions?",
+      "description": "Assess whether the code properly handles browser permissions for screen capture and considers compatibility across major browsers. Check if appropriate fallbacks or guidance is provided when permissions are denied or features are unsupported. Deduct 5 points if the tool only works in one specific browser, 3 points if permission handling is inadequate, and 5 points if there's no error handling for unsupported scenarios. 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 permission denials, failed captures, memory constraints with large screenshots, 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. OCR text recognition in screenshots 2. Auto-blur detection for sensitive information 3. Cloud storage integration 4. One-click sharing 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 perform the same capture) 2. Function modules unrelated to screenshot capture and editing (e.g., built-in image gallery) 3. Fancy effects that affect performance (e.g., unnecessary animations during capture). 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 capture/editing/storage logic), 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) Immediate visual feedback when initiating screenshot capture 2) Transition animations when switching between capture and edit modes (300-500ms) 3) Clear highlighting of active editing tools. Deduct 5 points for each operation without feedback, 3 points for laggy selection highlighting, and 5 points for hard-to-find editing controls. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Utility Tools-Daily Office Tasks",
+  "difficulty": "hard"
+}

package/library/utility_tools-daily_office_tasks/chrome-browser-sidebar-extension.json

@@ -0,0 +1,68 @@
+{
+  "index": 1134,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate, professional responses. Be sure to ensure that the code you generate can be executed and displayed properly. Please help me write a browser extension that runs in the Chrome browser sidebar.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Chrome extension manifest and core architecture properly implemented?",
+      "description": "Review whether the code includes a properly configured manifest.json (v3 or v2) with correct permissions, service worker registration, and sidebar panel configuration. Check if the extension architecture follows Chrome's extension development standards including proper message passing between content scripts, background scripts, and popup/sidebar components. Score 0 if manifest is missing or invalid, 5 if basic structure exists but lacks proper permissions or service worker setup, and 10 if fully compliant with Chrome extension standards including proper API usage.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the sidebar panel functionality correctly integrated with Chrome's Side Panel API?",
+      "description": "Evaluate whether the extension properly utilizes Chrome's Side Panel API (chrome.sidePanel) for sidebar implementation, including proper panel registration, opening/closing mechanisms, and tab-specific or global panel behavior. Check if the sidebar can be properly activated through extension actions and maintains proper lifecycle management. Deduct 5 points if using deprecated methods or workarounds instead of official Side Panel API, and 3 points if panel state management is inconsistent. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is cross-context communication and data persistence properly handled?",
+      "description": "Check whether the extension implements proper communication between different contexts (background, content script, sidebar panel) using chrome.runtime messaging or other appropriate APIs. Evaluate if data persistence is handled correctly using chrome.storage API with proper synchronization and error handling. Deduct 5 points if using unreliable communication methods (like DOM events for cross-context communication), and 3 points if storage operations lack proper error handling or data validation. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the extension's security model and permission handling implemented correctly?",
+      "description": "Review whether the extension follows Chrome's security best practices including Content Security Policy (CSP) compliance, minimal permission requests, and proper handling of user data. Check if the extension properly sandboxes potentially dangerous operations and validates all inputs. Deduct 5 points if requesting excessive permissions not used by the extension, and 5 points if CSP violations or XSS vulnerabilities are present. Give 10 points if security model is properly implemented with principle of least privilege.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as extension context invalidation, Chrome API failures, network interruptions, user permission denials, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should effectively handle extension-specific edge cases like context menu conflicts and tab lifecycle issues, 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 extension includes surprise features that enhance user productivity or browsing experience (e.g., 1. Smart content extraction and organization 2. Cross-tab data synchronization 3. Integration with external APIs for enhanced functionality 4. Keyboard shortcuts and accessibility features). Add 3 points for each practical innovative feature implemented that goes beyond basic sidebar functionality (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 storage mechanisms coexisting) 2. Function modules unrelated to the extension's core purpose (e.g., built-in games or unnecessary widgets) 3. Performance-heavy features that slow down browser experience (e.g., constant DOM polling or excessive background processing). Deduct 3 points for each redundancy found, and directly deduct 10 points if core extension functionality is 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/API layers), proper build process for extension packaging, and code organization following extension development best practices. Deduct 5 points if global namespace pollution is found or extension-specific patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process doesn't properly handle extension packaging and asset optimization. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the sidebar UI follows modern design principles and Chrome's design guidelines: 1) Harmonious color matching that integrates well with Chrome's interface (no more than 3 primary colors) 2) Proper layout spacing that works in narrow sidebar context (element spacing follows the 8px multiple principle) 3) Professional typography system (body font size ≥ 14px, line height over 1.5 times) 4) Responsive design for different sidebar widths. Deduct 3 points for each crowded visual element, 5 points for colors that clash with Chrome's theme, and 5 points for poor mobile responsiveness in sidebar context. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the sidebar interactions conform to browser extension UX standards: 1) Click feedback delay ≤ 100ms without blocking browser performance 2) Smooth transitions that don't interfere with main browser UI (300-500ms duration) 3) Clear visual focus guidance and keyboard navigation support 4) Proper loading states for async operations. Deduct 5 points for each operation without feedback, 3 points for animations that cause browser lag, and 5 points for poor accessibility or keyboard navigation support. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Utility Tools-Daily Office Tasks",
+  "difficulty": "medium"
+}

package/library/utility_tools-daily_office_tasks/classroom-student-selector-html-webpage.json

@@ -0,0 +1,68 @@
+{
+  "index": 1190,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure that the code you provide is executable and presentable. Please help me create a classroom student selector program as a HTML webpage with an attractive interface.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core student selection functionality fully implemented?",
+      "description": "Review whether the code implements a complete student selection system that can randomly or systematically choose students from a class roster. Check for features like random selection, exclusion of previously selected students, and ability to mark student participation. Score 0 if selection functionality is missing, 5 if basic random selection exists, and 10 if advanced selection logic with history tracking is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Does the program support student data management?",
+      "description": "Evaluate whether the code allows adding, editing, and removing students from the roster. Check if it supports importing/exporting student data (CSV/JSON) and persists data using localStorage or other methods. Deduct 5 points if there's no data persistence, 3 points if student information editing is limited. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is there a complete classroom interaction system?",
+      "description": "Check whether the program includes features that enhance classroom participation like tracking student performance, recording selection history, and providing statistics on student participation. Deduct 5 points if there's no participation tracking, 3 points if historical data isn't displayed visually. Give 10 points if a comprehensive interaction system is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the program have classroom-specific features?",
+      "description": "Assess whether the code includes classroom-relevant features such as timers for student responses, grouping functionality, seating chart integration, or other teacher assistance tools. Deduct 3 points for each missing key classroom feature. 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 student lists, duplicate names, invalid inputs, 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. Animation when selecting students 2. Sound effects for selection 3. Customizable themes for different classroom environments). 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 students) 2. Function modules unrelated to classroom selection (e.g., a built-in game unrelated to selection) 3. Fancy effects that affect performance (e.g., excessive 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 UI/logic/data management), code organization, and maintainability. Deduct 5 points if global variables are excessively used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no clear separation of concerns. 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 suitable for classroom environment (no distracting 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) Student selection animations are clear and informative 3) Responsive design works across device sizes. Deduct 5 points for each operation without feedback, 3 points for laggy animations during selection, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Utility Tools-Daily Office Tasks",
+  "difficulty": "easy"
+}

package/library/utility_tools-daily_office_tasks/code-editing-demo-arco-design-codemirror.json

@@ -0,0 +1,68 @@
+{
+  "index": 1044,
+  "question": "You are a code expert. Please utilize your professional knowledge to generate accurate and professional responses. Make sure that the code you generate is executable for demonstration. Create a code editing DEMO using arco-design and codemirror.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the code editor implementation complete?",
+      "description": "Check whether the CodeMirror integration with Arco Design is properly implemented. Verify if core editor functionality such as syntax highlighting, line numbers, and basic editing features are working. Score 0 if CodeMirror is not properly initialized, 5 if only basic functionality is included, and 10 if advanced features like code folding, search/replace, and auto-indentation are also implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is theme integration with Arco Design properly implemented?",
+      "description": "Evaluate if the CodeMirror editor is properly styled to match Arco Design's theme system. Check if the editor respects theme switching (light/dark mode) and uses consistent colors and styles from Arco Design. Deduct 5 points if the editor looks out of place within the Arco Design environment, and 3 points if theme switching is not synchronized between the UI and editor. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the toolbar/control panel functionality comprehensive?",
+      "description": "Assess whether the code editor includes a well-designed toolbar with essential coding operations (e.g., language selection, formatting, undo/redo). Check if the toolbar uses Arco Design components (Button, Select, etc.) correctly. Deduct 3 points for each missing essential functionality, and 5 points if the toolbar is not implemented at all. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is language support and syntax highlighting properly implemented?",
+      "description": "Check if the implementation supports multiple programming languages with proper syntax highlighting. The editor should support at least 3 common languages (e.g., JavaScript, HTML, CSS). Verify if language switching works correctly and if syntax highlighting updates accordingly. Deduct 3 points for each major language missing support, and 5 points if syntax highlighting fails. 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 input, large file loading, editor state 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. Real-time code linting/error checking 2. Code snippets library 3. Split-view editing or preview 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 ways to perform the same operation) 2. Function modules unrelated to code editing (e.g., unrelated media players) 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 editor logic/UI components/state management), component reusability, and code organization. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if proper component composition principles are not followed. 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 Arco Design principles: 1) Consistent use of Arco Design components without mixing other UI libraries 2) Proper layout spacing following Arco's spacing system 3) Professional typography adhering to Arco's font hierarchy. Deduct 3 points for each inconsistently styled component, 5 points for layout that breaks Arco grid system, and 5 points for typography that doesn't follow Arco guidelines. 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) Editor responsiveness with input lag ≤ 50ms 2) Smooth transitions between editor states/modes with duration controlled between 150-300ms 3) Clear visual feedback for actions. Deduct 5 points for perceptible input lag, 3 points for janky transitions, and 5 points for actions without visual feedback. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Utility Tools-Daily Office Tasks",
+  "difficulty": "easy"
+}