@getollie/cli 0.0.1

package/library/utility_tools-daily_office_tasks/merge-multiple-excel-workbooks.json

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

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

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

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

package/library/utility_tools-daily_office_tasks/password-generation-management-tool.json

@@ -0,0 +1,68 @@
+{
+  "index": 636,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure that the code you generate is executable. Implement a password generation and management tool where users can set the password length and include specific character types (such as letters, numbers, special characters) to generate random passwords that meet the requirements. The tool should support saving generated passwords locally and allow editing and deleting operations on the saved passwords.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the password generation functionality fully implemented?",
+      "description": "Review whether the code accurately implements core password generation with customizable options: length selection, character type inclusion (uppercase letters, lowercase letters, numbers, special characters). Score 0 if the core functionality is missing, 5 if only basic generation exists without all options, and 10 if all customization options are fully implemented with proper validation (e.g., minimum length checks, at least one character type selected).",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the password strength evaluation implemented?",
+      "description": "Check whether the code includes password strength evaluation using industry standards (entropy calculation, character diversity analysis, common pattern detection). Deduct 3 points if only basic length-based evaluation is used, 5 points if no evaluation exists. Full score requires visual strength indicators (color bars or descriptive text) and specific improvement suggestions for weak passwords.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the password storage and management system properly implemented?",
+      "description": "Evaluate the implementation of password saving, editing, and deleting functionality. Assess whether passwords are stored with associated metadata (website/service name, username, creation date). Deduct 5 points if any core CRUD operation is missing, 3 points if passwords are stored without encryption. The full score requires proper data persistence (localStorage, IndexedDB, or File API) with data integrity checks.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is there a secure clipboard interaction mechanism?",
+      "description": "Check whether the tool provides convenient copy-to-clipboard functionality with appropriate security measures. Evaluate whether the clipboard content is automatically cleared after a timeout period, and if visual feedback is provided on successful copy. Deduct 5 points if copy functionality is missing, 3 points if no feedback is provided, and 3 points if no auto-clear security feature exists.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid inputs, storage access failures, concurrent operations) 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. Password history tracking 2. Password expiration notifications 3. Breach detection API integration 4. Master password protection). 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 storage mechanisms active simultaneously) 2. Function modules unrelated to password management (e.g., built-in calendar) 3. Fancy effects that affect performance (e.g., excessive animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating UI/logic/storage layers), input validation thoroughness, and code 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 explaining complex logic or security considerations. 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": "easy"
+}

package/library/utility_tools-daily_office_tasks/pdf-text-extraction-tool.json

@@ -0,0 +1,68 @@
+{
+  "index": 671,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable for demonstration. Implement a PDF text extraction tool that allows users to upload PDF files, extract text content, perform simple editing on the content, and save it in new file formats (txt, docx, etc.).",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the PDF upload and parsing functionality correctly implemented?",
+      "description": "• Check if the code properly handles PDF file uploads with validation for file types and size limits. Verify if a reliable PDF parsing library (like pdf.js, pdfminer, PyPDF2, etc.) is correctly implemented and properly handles both text-based and scanned PDFs (with OCR if applicable). Deduct 5 points if only basic PDF handling is implemented without error handling, 3 points if no validation exists. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the text extraction feature complete and accurate?",
+      "description": "• Evaluate the accuracy and completeness of text extraction, including proper handling of formatting, special characters, multi-column layouts, and embedded fonts. Check if the extraction preserves paragraph structure, headings, and lists. Score 0 if extraction fails on common PDFs, 5 if basic extraction works but loses formatting, and 10 if extraction is comprehensive and preserves document structure.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the text editing functionality properly implemented?",
+      "description": "• Assess whether the code includes a complete set of text editing features (search/replace, formatting options, paragraph management, etc.) with proper text selection and cursor positioning. Check if changes are tracked properly and can be undone/redone. Deduct 3 points if basic formatting is missing, 5 points if undo/redo is not implemented, and give 10 points for comprehensive editing capabilities.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the export to multiple file formats correctly implemented?",
+      "description": "• Verify if the code supports exporting to various formats (txt, docx, rtf, html, etc.) with appropriate libraries and maintains formatting during conversion. Check if metadata and document properties are preserved where applicable. Deduct 3 points for each missing major format, 5 points if formatting is lost during export. 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 corrupted PDFs, memory-intensive large files, network interruption during upload/download, 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 processing of multiple PDFs 2. Advanced text analysis like keyword extraction 3. PDF annotation preservation 4. Table detection and conversion to spreadsheet formats). 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 text processing engines) 2. Function modules unrelated to PDF handling or text editing (e.g., a built-in calculator) 3. Fancy effects that affect performance (e.g., unnecessary 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 upload/parsing/editing/export components), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "• Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 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) Progress indicators for long-running PDF operations 2) Transition animation duration controlled between 300-500ms 3) Clear visual feedback for text selection and editing actions. Deduct 5 points for operations without loading indicators during processing, 3 points for laggy text editing experience, 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/ping-pong-score-counter-html-mobile-devices.json

@@ -0,0 +1,68 @@
+{
+  "index": 1097,
+  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Make sure that the code you generate is executable. Create a ping pong score counter in HTML that can run on mobile devices.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the ping pong score counter functionality fully implemented?",
+      "description": "Check if the code accurately implements the basic score counting mechanism, including incrementing scores for each player, correctly identifying the serving player, and handling game points according to standard ping pong rules (first to 11 with 2-point lead). Score 0 if the core functionality is missing, 5 if only basic scoring is implemented, and 10 if it includes game/match logic with proper rules enforcement.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the mobile device compatibility properly implemented?",
+      "description": "Evaluate whether the code includes mobile-specific features like responsive design (using viewport meta tags, media queries, flexible units), touch event handling (touchstart/touchend instead of just click events), and prevents zooming/scrolling issues during play. Deduct 3 points if responsive design is missing, 4 points if touch events aren't properly implemented, and 3 points if mobile gestures aren't prevented when needed. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Does the interface provide clear visual feedback for score changes?",
+      "description": "Check if score increments are visually acknowledged through animations, color changes, or other feedback mechanisms. The current server should be clearly indicated and switch automatically according to the rules. Deduct 5 points if score changes have no visual feedback, 3 points if the serving player isn't clearly indicated, and 2 points if there's no visual difference between regular points and game points. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is there state persistence or match history functionality?",
+      "description": "Evaluate whether the application can save the current state (using localStorage/sessionStorage), allow for game resets without page reload, and potentially track match history. Deduct 5 points if there's no way to persist state between page refreshes, 3 points if the reset functionality requires page reload, and 2 points if there's no match history tracking. 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 rapid consecutive tapping, device rotation, browser back navigation, accidentally closing the browser, etc.) and provide friendly error handling 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. Sound effects for points/games 2. Vibration feedback on mobile 3. Voice announcements of scores 4. Customizable player names). 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 scoring systems coexisting) 2. Function modules unrelated to ping pong scoring (e.g., a built-in calculator) 3. Fancy effects that affect performance (e.g., unnecessary animations that slow down score updates). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating UI/logic/state management), code maintainability, and performance optimization. Deduct 5 points if global state pollution is found; deduct 3 points if the code duplication rate is too high; deduct 2 points if event listeners aren't properly managed (potential memory leaks). 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) Score update feedback delay ≤ 100ms 2) Button touch area ≥ 44x44px for easy tapping 3) Clear visual distinction between interactive and non-interactive elements. Deduct 5 points for each operation without feedback, 3 points for laggy animations, and 5 points for hard-to-tap buttons on mobile. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Utility Tools-Daily Office Tasks",
+  "difficulty": "easy"
+}

package/library/utility_tools-daily_office_tasks/read-excel-display-data-html.json

@@ -0,0 +1,68 @@
+{
+  "index": 923,
+  "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 for demonstration. Read excel file and display data, HTML code",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Excel file reading functionality properly implemented?",
+      "description": "Check if the code correctly implements file input for Excel files (.xlsx, .xls, .csv) and handles different Excel formats. Score 0 if no file loading is implemented, 5 if only basic file reading is done, and 10 if the implementation handles various Excel formats with robust error checking for file corruption or format issues.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the data parsing and extraction logic complete?",
+      "description": "Verify that the code correctly extracts data from Excel sheets, handling different data types (text, numbers, dates, formulas), empty cells, and merged cells. Deduct 3 points if certain data types aren't properly handled, 5 points if merged cells cause issues, and 3 points if there's no error handling for invalid data. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the HTML display of Excel data implemented effectively?",
+      "description": "Evaluate whether the HTML representation maintains the original Excel structure (tables, rows, columns) with appropriate styling that resembles Excel's visual layout. Check if column widths, row heights, cell alignments, and text formatting are preserved. Score 0 if data is just dumped without structure, 5 if basic table structure exists, and 10 if the display closely resembles Excel's appearance.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are interactive data manipulation features implemented?",
+      "description": "Check if the HTML implementation includes features like sorting, filtering, searching, or basic cell editing. Deduct 3 points for each missing core feature (sorting, filtering, search). Award full 10 points only if the implementation allows for data manipulation comparable to basic Excel functionality.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid Excel files, large datasets, unexpected data formats, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Live data visualization options 2. Excel formula support in the HTML view 3. Multi-sheet navigation tabs). 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 similar functions (e.g., multiple Excel parsers loaded) 2. Function modules unrelated to Excel data display (e.g., unnecessary animations) 3. Overly complex implementations that affect performance (e.g., excessive DOM manipulation). 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 file loading/parsing/display logic), error handling coverage, and proper documentation. 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 explaining 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 modern data presentation principles: 1) Clean table styling with appropriate borders and spacing 2) Visual hierarchy that makes headers distinct from data 3) Consistent typography and alignment across the table. Deduct 3 points for cluttered visual presentation, 5 points for inconsistent styling that makes data hard to read, and 5 points for poor responsive design on different screen sizes. 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 user expectations: 1) File upload feedback is immediate 2) Large data sets load with progress indicators 3) Sorting/filtering operations complete within 300ms for standard datasets. Deduct 5 points for operations without loading indicators for large files, 3 points for jerky scrolling on large tables, and 5 points for unresponsiveness during data processing. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Utility Tools-Daily Office Tasks",
+  "difficulty": "medium"
+}