@getollie/cli 0.0.5 → 0.2.0

package/library/utility_tools-daily_office_tasks/intelligent-screenshot-annotation-tool.json

@@ -1,68 +0,0 @@
-{
-  "index": 694,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the code you generate is executable for demonstration purposes. Develop an intelligent screenshot annotation tool that supports adding arrows/mosaic/text annotations after capturing a region, implementing undo/redo functionality for annotation history, saving preset annotation styles, and supporting export to PNG and copying to clipboard.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the screenshot capture function properly implemented?",
-      "description": "Review whether the code correctly implements screen region selection with visual guidance (crosshair cursor, marquee selection box). Check if the captured area is accurately represented in the annotation canvas. Verify if the tool handles multiple monitors and different screen resolutions correctly. Score 0 if screen capture is not implemented, 5 if basic region capture works but has limitations, and 10 if the implementation is robust across different environments.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are all required annotation tools (arrows/mosaic/text) implemented and functional?",
-      "description": "Examine if the code provides complete implementations for arrows (with customizable direction, thickness, color), mosaic effects (with adjustable blur/pixelation levels), and text annotations (with font selection, size, color, and positioning). Each tool should have proper mouse interaction patterns. Deduct 3 points for each missing tool. Deduct 2 points for tools with limited customization options. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the undo/redo functionality properly implemented with comprehensive history tracking?",
-      "description": "Assess whether the code maintains a complete operation history stack that tracks all annotation actions separately. Verify that undo/redo works correctly for complex sequences of operations and after switching between annotation tools. Check if the implementation handles composite operations properly. Score 0 if history management is missing, 5 if basic undo/redo works for simple cases, and 10 if the implementation is robust for all scenarios.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the tool support saving and applying preset annotation styles?",
-      "description": "Evaluate whether users can save custom styles (color combinations, line thickness, text fonts, mosaic patterns) as presets and apply them with a single click. Check if presets persist between sessions and if the preset management UI is intuitive. Deduct 5 points if presets are not persistent, 3 points if preset UI is confusing, and 2 points if style application is inconsistent across annotation types. 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 selections, large images, memory limitations, operating system restrictions, 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. Smart object detection for auto-annotation 2. Voice commands for annotation 3. Automatic annotation suggestions based on content 4. Multi-layer annotation 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 annotation functions (e.g., multiple text insertion methods) 2. Function modules unrelated to screenshot annotation (e.g., a built-in image editor for other purposes) 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 UI/annotation logic/storage 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 toolbar organization (grouped by function, with clear icons). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic tool arrangement. 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 during annotation drawing 2) Smooth transitions between annotation states 3) Clear visual indicators for selection and focus. Deduct 5 points for laggy annotation rendering, 3 points for jerky tool switching transitions, and 5 points for unclear selection state indicators. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Daily Office Tasks",
-  "difficulty": "medium"
-}

package/library/utility_tools-daily_office_tasks/medication-reminders-mini-program-elderly.json

@@ -1,68 +0,0 @@
-{
-  "index": 1610,
-  "question": "You are a coding expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you produce is executable and ready for demonstration. Please help me write a complete mini-program for medication reminders for elderly people that I can directly copy and paste for use.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the medication reminder core functionality fully implemented?",
-      "description": "Evaluate whether the code implements essential medication reminder features: scheduling reminders, setting medication details (name, dosage, frequency), notification system, and acknowledgment of taken medication. Score 0 if core functionality is missing, 5 if basic reminders are implemented without flexibility, and 10 if the system includes multiple scheduling options (daily, weekly, specific times) with medication details management.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the elderly user interface properly designed for accessibility?",
-      "description": "Check if the UI follows elderly-friendly design principles: large text (at least 16px), high contrast colors (contrast ratio ≥ 7:1), simplified navigation, clear buttons (minimum 44x44px touch targets), and minimal steps to complete tasks. Deduct 3 points for each accessibility guideline violated. Award full points only if the interface demonstrates specific considerations for elderly users including font scaling options.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Does the application include caregiver integration features?",
-      "description": "Assess whether the code implements caregiver monitoring capabilities: missed medication alerts, medication adherence tracking, remote monitoring dashboard, and emergency contact integration. Deduct 3 points if remote monitoring is missing, 3 points if adherence tracking is absent, and 4 points if emergency contact functionality is not implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is data persistence and offline functionality properly implemented?",
-      "description": "Evaluate if the code properly handles data storage (local storage or database implementation), synchronization mechanisms, and offline functionality. Check for proper data validation, backup mechanisms, and recovery procedures. Deduct 5 points if medication data isn't persistent after app restart, and 5 points if the app requires constant internet connection to function. Full score for complete offline capability with data integrity protection.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as incorrect inputs, network interruption, system notifications being blocked, 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. Medication identification using camera 2. Voice-based reminders and commands 3. Adaptive reminder timing based on user habits 4. Gamification elements for medication adherence). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple notification systems coexisting) 2. Function modules unrelated to medication reminders (e.g., a built-in games section) 3. Fancy effects that affect performance (e.g., unnecessary animations that might confuse elderly users). 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/notification 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 ≥ 16px for elderly users, 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 elderly users' perception characteristics: 1) Clear feedback for every action 2) Transition animation duration controlled between 400-700ms (slightly longer for elderly users) 3) Obvious visual and possibly auditory cues for important actions. Deduct 5 points for each operation without feedback, 3 points for confusing transitions, 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": "hard"
-}

package/library/utility_tools-daily_office_tasks/meeting-schedule-qq-music-reminder-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 448,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable whenever possible. Help me write a simple software code for a meeting schedule recording reminder system that allows users to input schedule arrangements and dates. When the reminder button is clicked, on the corresponding date, the interface will automatically open QQ Music to play \"Today Is a Good Day.\" When the stop button is clicked, QQ Music will exit and the music will stop playing.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the meeting schedule input and storage system fully implemented?",
-      "description": "Review whether the code accurately implements schedule input functionality through HTML forms/JavaScript, including date picker, time selector, and schedule description fields. Check if data validation is implemented (date format, required fields, conflict detection). Score 0 if basic input functionality is missing, 5 if only simple input is implemented without validation, and 10 if complete input system with validation and local storage is included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the reminder scheduling and timing mechanism properly implemented?",
-      "description": "Check whether the reminder system uses appropriate timing mechanisms (setTimeout/setInterval) to monitor scheduled dates and times. Evaluate if the system can handle multiple concurrent reminders and accurately trigger at specified times. Deduct 5 points if timing accuracy is poor (>30 seconds deviation), and 3 points if background timing doesn't work when browser tab is inactive. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the QQ Music integration and external application control implemented?",
-      "description": "Evaluate whether the system successfully integrates with QQ Music application launch functionality. Check if the code uses appropriate methods (shell commands, registry, or protocol handlers) to open and close QQ Music. Verify if the specific song 'Today Is a Good Day' can be automatically played. Deduct 5 points if only basic app launch is implemented without specific song control, and 3 points if the stop functionality doesn't properly terminate the music application.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the complete reminder lifecycle and state management constructed?",
-      "description": "Check whether the code includes complete reminder lifecycle management, including reminder creation, modification, deletion, and completion marking. Evaluate if the system maintains proper state tracking for active/inactive reminders and handles reminder history. Deduct 5 points if reminder persistence is not implemented, and 3 points if there's no mechanism to handle missed or expired reminders. Give 10 points if fully implemented with comprehensive state management.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid date input, system permission denial for external app launch, missing QQ Music installation, etc.) and provide friendly error prompts or fallback mechanisms. Code with strong robustness should effectively handle these edge cases, giving 10 points. If 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 user experience (e.g., 1. Custom ringtone selection 2. Snooze functionality 3. Meeting category classification 4. Calendar view integration 5. Notification sound volume control). 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 mechanisms coexisting) 2. Function modules unrelated to meeting reminders (e.g., built-in games or weather widgets) 3. Overly complex animations that affect performance (e.g., excessive visual effects during reminder triggers). Deduct 3 points for each redundancy found, and directly deduct 10 points if core reminder 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 management/UI/reminder logic layers), code organization, and error handling implementation. Deduct 5 points if global state pollution is found or proper separation of concerns is not implemented; deduct 5 points if code duplication rate is too high (over 30%); deduct 5 points if no configuration management is implemented for external application paths. 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 UI/UX principles: 1) Harmonious color scheme suitable for productivity tools (no more than 3 primary colors) 2) Proper layout spacing with clear visual hierarchy (element spacing follows 8px grid system) 3) Professional typography (body font size ≥ 14px, line height ≥ 1.5). Deduct 3 points for each cluttered visual element, 5 points for poor color contrast affecting readability, and 5 points for inconsistent layout structure. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the user interaction smooth and intuitive?",
-      "description": "Judge whether the interaction design follows usability principles: 1) Form input feedback delay ≤ 100ms 2) Smooth transitions between different views (300-500ms duration) 3) Clear visual feedback for reminder states and actions 4) Intuitive button placement and labeling. Deduct 5 points for each operation lacking immediate feedback, 3 points for confusing navigation flow, and 5 points for poorly positioned critical function buttons (reminder/stop). Full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Daily Office Tasks",
-  "difficulty": "medium"
-}

package/library/utility_tools-daily_office_tasks/memo-application-with-audio-playback.json

@@ -1,68 +0,0 @@
-{
-  "index": 993,
-  "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 is executable for demonstration purposes. Could you write a memo application that can play audio?",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the memo functionality fully implemented?",
-      "description": "Review whether the code implements complete memo functionality including creating, editing, saving, and deleting memos. Check for proper text formatting options, search functionality, and categorization features. Score 0 if the basic memo operations are missing, 5 if only rudimentary operations exist, and 10 if all expected features of a modern memo application are present.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the audio playback integration complete?",
-      "description": "Evaluate the audio playback implementation including controls (play, pause, stop, seek), support for common audio formats (MP3, WAV, OGG), volume adjustment, and playback rate control. Check if proper error handling for unsupported formats or playback failures exists. Deduct 3 points if basic playback controls are missing, 3 points if format support is limited, and 4 points if error handling is inadequate. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Does the application handle audio recording capabilities?",
-      "description": "Check whether the application allows users to record audio directly within the memo interface, including microphone access permissions handling, recording indicators, and saving recorded audio with the memo. Verify that the recording quality options are available and that recordings can be edited/trimmed before saving. Deduct 5 points if recording functionality is missing, 3 points if quality control is absent, and 2 points if editing capabilities are not provided. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is proper audio-text association implemented?",
-      "description": "Assess whether the application effectively links audio files with the corresponding memo text, such as timestamps for audio references in text, visual indicators for audio attachments, and the ability to navigate text while audio plays. Check for synchronization between text edits and associated audio. Deduct 4 points if audio-text linking is absent, 3 points if visual indicators are missing, and 3 points if navigation during playback isn't supported. 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 audio format incompatibility, recording permission denials, storage limitations, 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. Speech-to-text transcription of audio memos 2. Voice command controls 3. Audio visualization during playback 4. AI-powered audio summarization). 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 audio playback engines coexisting) 2. Function modules unrelated to memo or audio purposes (e.g., a built-in game) 3. Fancy effects that affect performance (e.g., excessive animations during audio playback). 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 memo logic/audio handling/UI 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. Assess audio-specific interactions such as waveform responsiveness and playback progress indicators. 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/merge-multiple-excel-workbooks.json

@@ -1,68 +0,0 @@
-{
-  "index": 1765,
-  "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. You are a web design expert, specializing in HTML code.\n\nI currently have many Excel workbooks that need to be merged into a single worksheet.\n\nI need you to create a web tool that can merge multiple workbook files. This tool should implement the following features:\n1. Provide an upload button that allows users to select multiple Excel workbooks they want to upload.\n2. Provide a merge button that, when clicked, will combine all the user-uploaded workbooks into a single worksheet.\n3. Provide a download link to let users download the merged worksheet.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the file upload mechanism properly implemented?",
-      "description": "Review whether the HTML/JavaScript code correctly implements a file upload component that allows multiple Excel file selection. Check if it includes proper file type validation (accepts .xlsx, .xls formats), provides visual feedback during the selection process, and handles large files appropriately. Score 0 if file upload is not implemented, 5 if basic uploading works but lacks validation, and 10 if fully implemented with comprehensive error handling.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the Excel workbook parsing functionality complete?",
-      "description": "Evaluate if the code uses appropriate libraries (like SheetJS/xlsx) to parse Excel workbooks, handles different Excel formats correctly, and properly extracts data from multiple sheets. Check if it maintains data types (numbers, dates, formulas) and handles formatting. Deduct 5 points if only one Excel format is supported, 3 points if complex Excel features (merged cells, formulas) are ignored, and 5 points if parsing errors are not handled gracefully. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the workbook merging algorithm properly implemented?",
-      "description": "Assess whether the merging logic correctly combines data from multiple workbooks into a single worksheet, maintaining data integrity. Check if the algorithm handles duplicate header rows, preserves column order, and provides options for how to merge (append/concatenate). Deduct 5 points if the merge strategy is overly simplistic, 5 points if column mismatches between workbooks aren't handled, and 3 points if there's no conflict resolution mechanism. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the file download functionality properly implemented?",
-      "description": "Verify that the code provides a working download mechanism for the merged Excel file. Check if it correctly converts the merged data back to Excel format, creates a downloadable file with appropriate naming, and handles large datasets efficiently. Deduct 5 points if the download link appears before processing is complete, 3 points if the file naming is not user-configurable, and 5 points if download fails for large datasets. 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 file formats, empty worksheets, memory limitations with large files, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Preview of merged data before download 2. Custom column mapping between different workbooks 3. Filtering options for which data to include). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple file parsing methods) 2. Function modules unrelated to Excel merging (e.g., unnecessary data visualization) 3. Fancy effects that affect performance (e.g., excessive animations during processing). 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/processing/download logic), error handling consistency, 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 there's no progress indication during processing of large files. 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) Clear visual feedback during file processing with progress indicators 2) Smooth transitions between upload, processing, and download states 3) Clear visual focus guidance. Deduct 5 points for operations without feedback, 3 points for lack of processing indicators during long operations, and 5 points for confusing workflow that doesn't clearly guide users through the steps. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Daily Office Tasks",
-  "difficulty": "medium"
-}

package/library/utility_tools-daily_office_tasks/mini-program-survey-generator.json

@@ -1,68 +0,0 @@
-{
-  "index": 1124,
-  "question": "You are a code expert. Please utilize your professional knowledge to generate accurate and professional responses. Be sure to provide executable code when possible. Write a mini-program that can generate surveys.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the survey creation functionality completely implemented?",
-      "description": "Review whether the code accurately implements a survey creation system that allows users to define questions, answer options, and survey structure. Score 0 if core survey building functionality is not implemented, 5 if only basic question types are supported (e.g., multiple choice only), and 10 if multiple question types (multiple choice, short answer, rating scales, etc.) are fully supported with proper validation.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the survey response collection and storage mechanism properly implemented?",
-      "description": "Check whether the implementation includes methods to collect user responses, validate input data, and store responses securely. Examine if there's proper handling of different data types based on question types. Deduct 5 points if validation is missing, 3 points if data persistence is not implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Does the program include survey management features?",
-      "description": "Evaluate if the code provides functionality to manage surveys (create, edit, delete, publish/unpublish) and includes survey lifecycle management. Check if there's a way to track survey completion status and results. Deduct 5 points if editing capabilities are missing, and 3 points if there's no survey status management. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there a results analysis or reporting component?",
-      "description": "Check if the code includes features for analyzing survey results, such as data visualization, summary statistics, or export capabilities. Assess whether users can easily understand the gathered data. Deduct 5 points if no visualization is included, 3 points if only raw data is shown without analysis. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid inputs, server errors, data validation issues, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Logic branching based on responses 2. Survey templates library 3. Real-time collaboration on survey creation). 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 create the same question type) 2. Function modules unrelated to surveys (e.g., a built-in calendar unrelated to survey scheduling) 3. Fancy effects that affect performance (e.g., excessive animations when switching between questions). 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 survey model/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/mobile-qr-code-scanner-webpage.json

@@ -1,68 +0,0 @@
-{
-  "index": 1733,
-  "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. Could you write a webpage that allows users to scan QR codes using their mobile phone camera and save the data?",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the QR code scanning functionality fully implemented?",
-      "description": "Check if the code utilizes an appropriate QR code scanning library (like jsQR, quagga.js, or ZXing) and properly integrates with the device camera API. The implementation should include proper initialization of the camera stream, frame analysis for QR detection, and accurate decoding. Score 0 if no scanner is implemented, 5 if basic scanning works but with limitations, and 10 if it handles different QR code formats and scanning scenarios efficiently.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is camera access properly implemented with permissions handling?",
-      "description": "Evaluate whether the code includes proper camera permission requests using the MediaDevices API, handles denied permissions gracefully with user-friendly messages, and provides fallback options. Check if it supports both front and rear cameras with a toggle option. Deduct 5 points if permissions are not handled properly or if the code crashes when permissions are denied. Deduct 3 points if there's no camera selection option. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the data saving functionality properly implemented?",
-      "description": "Check if the code provides multiple options for saving scanned QR data (e.g., copy to clipboard, download as file, save to browser storage, share via API). Verify that the data saving process includes validation and handles different data types appropriately. The implementation should confirm successful saves with user feedback. Deduct 5 points if only one saving method is implemented without error handling, and 3 points if there's no confirmation of successful saves. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there a scan history and management system?",
-      "description": "Evaluate whether the code implements a scan history feature that stores previous scans, allows users to revisit and manage their scan history (delete, export, organize), and persists data between sessions. Check if there's a clear way to view scan details with timestamps and categories. Deduct 5 points if history doesn't persist between sessions, and 3 points if basic management features are missing. Give 10 points if fully implemented with search/filter capabilities.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as camera access errors, invalid QR codes, browser compatibility issues, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Batch scanning mode 2. Automatic data recognition for common formats (URLs, contacts, Wi-Fi) 3. QR code generation capability). 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 scanning methods 2. Function modules unrelated to QR scanning or data saving (e.g., unnecessary social media sharing) 3. Fancy effects that affect scanning performance (e.g., excessive animations that slow down camera processing). 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 scanner logic/UI/storage 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) Immediate visual feedback when a QR code is detected 2) Transition animation duration controlled between 300-500ms for result displays 3) Clear visual focus guidance for camera positioning. Deduct 5 points for each operation without feedback, 3 points for laggy camera feed, and 5 points for confusing scanning interface that doesn't guide users. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Daily Office Tasks",
-  "difficulty": "easy"
-}

package/library/utility_tools-daily_office_tasks/online-text-to-speech-tts-tool.json

@@ -1,68 +0,0 @@
-{
-  "index": 513,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Translation\n\nYou are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure any code you generate is executable and can be demonstrated.\n\n======== ROLE ========\nYou are an experienced code expert. You are provided with a software development requirement description, and you are asked to generate project code based on this requirement. Strictly follow the rules to help users generate complete project code that is fully annotated with simple and easy-to-understand language. Do not output anything else.\n\n======== OUTPUT RULES ========\n1. You should always generate complete, runnable project code. Please ensure the project is complete and executable.\n2. Ensure all code files you output are complete, do not omit any code.\n3. Before delivering the final output, carefully review and check all code, evaluating its executability. If the code cannot be executed or contains errors, it needs to be regenerated.\n4. If the requirements include external API access needs or require the use of user data (images, videos, audio, etc.), please provide simulated data.\n\n======== PROJECT REQUIREMENTS ========\nBuild an online text-to-speech (TTS) tool where users can input text, select voice type (such as male/female, slow/fast), generate corresponding audio files, and play them back.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the text input functionality properly implemented?",
-      "description": "Check if the application provides a robust text input area that can handle various lengths of text (short sentences to paragraphs), supports different character sets, and includes proper validation. The input component should have appropriate placeholder text, character count, and potentially allow for file uploads of text documents.Score 0 if text input is missing or severely limited, 5 if basic input exists but lacks validation or support for longer texts, and 10 if the implementation is complete with validation, character limits, and proper handling of special characters.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the voice selection options comprehensive and well-implemented?",
-      "description": "Evaluate whether the code implements multiple voice options (male/female, slow/fast, different accents/languages) as specified, and if the selection UI is intuitive. Voice options should be clearly labeled and organized logically with preview functionality.Deduct 3 points for each missing major voice type category (gender, speed, accent), 2 points if voice previewing is absent, and 2 points if the selection UI is confusing or poorly labeled. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the TTS conversion and audio generation properly implemented?",
-      "description": "Assess whether the code properly implements the TTS conversion process, either through a browser API (like SpeechSynthesis API) or a simulated external API. Check if there's appropriate error handling for API failures, loading states during conversion, and proper audio file generation.Score 0 if TTS functionality is not implemented, 5 if basic conversion works but lacks error handling or fails with longer texts, and 10 if the implementation is complete with proper error handling, progress indicators, and support for various text lengths.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the audio playback functionality fully implemented?",
-      "description": "Check if the application provides complete audio playback controls including play, pause, stop, volume adjustment, playback speed, and a progress bar with seeking functionality. The UI should update dynamically to reflect the current playback state.Deduct 2 points for each missing essential control (play/pause, volume, progress tracking), 3 points if seeking functionality is absent, and 2 points if visual feedback during playback is missing. 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 input, very long text, network interruption during TTS conversion, unsupported voice types, 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. Realtime text highlighting during playback 2. Export options for audio in multiple formats 3. Voice customization beyond basic options 4. Batch processing of multiple text entries).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 audio player implementations) 2. Function modules unrelated to TTS (e.g., a built-in image editor) 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 components, TTS logic, and audio playback), code organization, performance optimization techniques, and proper use of modern web development practices.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 modern web development practices are ignored. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times) 4) Clear visual hierarchy between text input, voice selection, and playback sections.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) Visual feedback when generating audio ≤ 200ms 2) Smooth transitions between different states (idle, processing, playback) 3) Intuitive controls that respond immediately to user input 4) Clear loading indicators during TTS processing.Deduct 5 points for each operation without feedback, 3 points for laggy transitions during state changes, and 5 points for confusing interaction patterns. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Daily Office Tasks",
-  "difficulty": "hard"
-}