@getollie/cli 0.0.5 → 0.2.1

package/library/utility_tools-daily_office_tasks/vue3-ts-save-page-as-pdf.json

@@ -1,68 +0,0 @@
-{
-  "index": 315,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable and functional. For Vue 3 + TypeScript: implement functionality to save the page content as PDF and download it when clicking a button on the page.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Vue 3 + TypeScript PDF export functionality correctly implemented?",
-      "description": "Check if the code correctly uses Vue 3 composition API with TypeScript for PDF generation. The implementation should include proper type definitions, reactive state management, and proper component structure. Score 0 if the core functionality is missing, 5 if basic functionality exists but with TypeScript errors, and 10 if fully typed and following Vue 3 best practices.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is HTML-to-PDF conversion handled properly?",
-      "description": "Evaluate the PDF generation approach - whether using libraries like jsPDF, html2canvas, or pdfmake. Check if the solution handles CSS styling, fonts, and layouts properly when converting to PDF. Deduct 5 points if text formatting is lost, 3 points if images aren't properly included, and 2 points if page breaks aren't handled. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the download mechanism implemented correctly?",
-      "description": "Check if the code properly creates a downloadable file with appropriate MIME type, generates a Blob or File object, and uses browser APIs (like URL.createObjectURL) to trigger downloads. Verify proper file naming with .pdf extension and cleanup of temporary objects. Deduct 5 points if the download doesn't work in major browsers, 3 points if filename handling is incorrect. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are progress indicators and error handling implemented?",
-      "description": "Check if the code includes loading states during PDF generation (which can be resource-intensive), error catching for failed conversions, and user feedback mechanisms. Score 10 points if it has comprehensive loading indicators, graceful error handling with user-friendly messages, and recovery options. Deduct 5 points if loading states are missing, 5 points if error handling is absent.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as large content, content with special characters, network interruptions during downloads, 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 before download 2. PDF customization options like headers/footers 3. Page size/orientation selection). 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 PDF generation methods 2. Unnecessary external dependencies when browser APIs would suffice 3. Over-engineered solutions for simple requirements. 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 from PDF generation logic), proper TypeScript typing, and component reusability. Deduct 5 points if global state pollution is found; deduct 5 points if the code duplication rate is too high; deduct 5 points if TypeScript types are ignored with 'any' types. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the PDF export button/UI follows modern design principles: 1) Clear button state (normal/loading/disabled) 2) Proper placement in the UI hierarchy 3) Consistent with Vue design patterns (like Vuetify or Element Plus if used). Deduct 3 points for confusing button placement, 5 points for inconsistent styling with the rest of the app, and 5 points for poor accessibility features. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the PDF generation process provides good UX: 1) Clear indication when generation starts 2) Progress feedback for large documents 3) Smooth transition between generation and download. Deduct 5 points for freezing UI during generation, 3 points for abrupt transitions, and 5 points for lack of feedback when the process is complete. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Daily Office Tasks",
-  "difficulty": "easy"
-}

package/library/utility_tools-daily_office_tasks/vue3-typescript-pdf-signature.json

@@ -1,68 +0,0 @@
-{
-  "index": 1599,
-  "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. Implement a PDF signature feature in a Vue 3 + TypeScript framework.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the PDF rendering and signature drawing system fully implemented?",
-      "description": "Review whether the code accurately implements the PDF rendering mechanism (using libraries like PDF.js) and a canvas-based signature system. Check if zooming, panning, and precise positioning of the signature on PDF pages are supported. Score 0 if core PDF display is missing, 5 if only basic rendering is available without proper user interaction, and 10 if the implementation handles multi-page documents with proper signature placement capabilities.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the drawing mechanics for signatures properly implemented?",
-      "description": "Evaluate the signature drawing functionality including stroke smoothing, pressure sensitivity (where supported), undo/redo capabilities, and saving signatures as vector formats (SVG preferred) or high-resolution bitmaps. Check if the drawing experience feels natural with anti-aliasing. Deduct 3 points if stroke smoothing is poor, 3 points if undo/redo is missing, and 4 points if the signature output quality is low. Give full 10 points only if the signature drawing feels professional-grade.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the PDF modification and saving functionality properly implemented?",
-      "description": "Check if the solution properly embeds signatures into the PDF document rather than just displaying them visually. Verify that the solution can save the signed document with proper metadata, preserving the original PDF structure and features. Deduct 5 points if signatures are not actually embedded in the PDF, 3 points if the modification doesn't maintain PDF integrity, and 2 points if metadata and audit information isn't properly updated. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is TypeScript used effectively throughout the implementation?",
-      "description": "Assess the TypeScript implementation for proper typing, interfaces for PDF structures, proper Vue 3 component typing, and type safety across the application. Check for use of advanced TypeScript features like generics, union types, and proper null handling. Deduct 3 points for any use of 'any' type, 4 points for inadequate interface definitions, and 3 points for missing type guards or type assertions where appropriate. 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 corrupt PDFs, browser compatibility issues, memory limitations with large files, offline usage scenarios). Code with strong robustness should provide friendly error messages and recovery mechanisms. Check for proper try-catch blocks and error boundaries. Give 10 points for comprehensive error handling, 5 points for average handling, and 0 points if exceptions aren't addressed.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Signature templates/history 2. Digital certificate integration 3. Batch signing capability 4. Accessibility features like keyboard navigation 5. Mobile responsiveness with touch optimization). Add 2 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 PDF processing operations that could impact performance 2. Unnecessary re-rendering of PDF content 3. Excessive third-party dependencies that could be consolidated. 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 Vue 3 Composition API usage, component structure, state management, and proper separation of concerns. Check for unit tests, particularly for critical PDF manipulation functions. Deduct 3 points for improper reactive state management, 4 points if components violate single-responsibility principle, and 3 points if the build process doesn't optimize PDF handling libraries. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the signing interface follows professional design principles: 1) Clear signature area with proper contrast against PDF background 2) Intuitive toolbar placement with proper iconography 3) Responsive layout that works on different screen sizes. Deduct 3 points for poor signature area visibility, 3 points for confusing tool placement, and 4 points for layout issues on different viewport sizes. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the PDF and signature interactions feel natural and responsive: 1) Signature appears without perceptible lag 2) PDF zooming and panning is smooth 3) Proper loading states for PDF rendering operations. Deduct 4 points for laggy signature drawing, 3 points for jerky PDF navigation, and 3 points for missing loading indicators during processing operations. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Daily Office Tasks",
-  "difficulty": "medium"
-}

package/library/utility_tools-daily_office_tasks/weather-forecast-mini-program-html-preview.json

@@ -1,68 +0,0 @@
-{
-  "index": 222,
-  "question": "You are a coding expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code for demonstration when possible. Develop a weather forecast mini-program and include an HTML preview.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the weather data fetching and integration functionality complete?",
-      "description": "Review whether the code connects to a reliable weather API (like OpenWeatherMap, WeatherAPI, etc.), implements proper API key management, and includes error handling. Check if the request includes geolocation capabilities and fallback mechanisms. Score 0 if no data fetching is implemented, 5 if basic fetching exists but lacks error handling, and 10 if complete with robust error handling, caching strategy and data refresh mechanisms.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the weather forecast display comprehensive and detailed?",
-      "description": "Evaluate whether the mini-program displays current conditions, hourly forecasts, and multi-day forecasts with appropriate weather metrics (temperature, humidity, wind speed/direction, precipitation probability, etc.). Check if weather icons/symbols are properly implemented and if temperature units can be toggled (°C/°F). Deduct 3 points if critical metrics are missing, 5 points if only current weather is shown without forecasts, and 2 points if weather condition icons are missing or inappropriate. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are geolocation features implemented properly?",
-      "description": "Check if the code implements browser geolocation API or IP-based geolocation, with appropriate permission requests and user-friendly error handling. Verify if manual location search functionality is available as an alternative. Score 0 if no location detection exists, 5 if only basic geolocation is implemented without alternatives, and 10 if both automatic and manual location options are available with proper error handling and location history/favorites.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are visual weather representations (charts/graphs) included?",
-      "description": "Assess whether the mini-program includes visual representations like temperature trend graphs, precipitation probability charts, or other meteorological visualizations using appropriate JavaScript libraries (Chart.js, D3.js, etc.). Score 0 if no visual elements are included, 5 if basic static visualizations exist, and 10 if interactive, responsive visualizations with proper legends and accessibility features are implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as API failures, network interruption, geolocation errors, 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. Weather alerts and notifications 2. Air quality index integration 3. Weather-based clothing recommendations 4. Historical weather data comparison). Add 2.5 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 API calls or data fetching mechanisms 2. Function modules unrelated to weather forecasting (e.g., a built-in game) 3. Fancy effects that affect performance (e.g., excessive animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating data/view/controller layers), code organization, and best practices implementation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 3 points if the code duplication rate is too high; deduct 2 points if there's no input validation or sanitization. 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 weather app design principles: 1) Weather-appropriate color schemes (cool tones for cold, warm for hot) 2) Proper layout spacing and hierarchy (important data more prominent) 3) Professional typography system (readable even with weather imagery backgrounds). Deduct 3 points for cluttered layouts, 4 points for poor contrast/readability, and 3 points for inconsistent design elements. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and responsive?",
-      "description": "Judge whether the mini-program is responsive across device sizes and has appropriate loading states: 1) Skeleton screens or loaders during API calls 2) Smooth transitions between forecast days/hours 3) Touch-friendly controls on mobile with appropriate tap targets. Deduct 4 points for lack of loading indicators, 3 points for janky scrolling or transitions, and 3 points for poor mobile optimization. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Education/Learning",
-  "difficulty": "medium"
-}

package/library/utility_tools-daily_office_tasks/weather-forecast-query-tool.json

@@ -1,68 +0,0 @@
-{
-  "index": 1330,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Be careful to ensure that the generated code is executable for demonstration. Generate a weather forecast query tool.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the weather data retrieval fully implemented?",
-      "description": "Review whether the code properly implements API calls to a weather service (like OpenWeatherMap, AccuWeather, etc.), with proper error handling for failed requests, rate limiting, and API key management. Score 0 if no actual data retrieval is implemented, 5 if basic retrieval without error handling is present, 10 if comprehensive handling with fallback mechanisms is included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is location detection or manual location input properly implemented?",
-      "description": "Check whether the tool allows for automatic geolocation detection (using browser API) and/or manual location input with proper validation and geocoding. Deduct 5 points if geolocation permissions are not properly handled, 3 points if there's no search suggestion/autocomplete for location names, and 5 points if location validation is missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is forecast visualization comprehensive and user-friendly?",
-      "description": "Evaluate whether the tool displays current conditions, hourly forecasts, and multi-day forecasts with appropriate visual representations (icons, graphs, etc.). Deduct 3 points if temperature trends aren't visualized graphically, 5 points if weather condition icons are missing or unclear, and 5 points if the forecast doesn't include essential metrics like precipitation probability, humidity, and wind. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there functionality for saving preferences or favorite locations?",
-      "description": "Check if the tool implements local storage or other persistence mechanisms to save user preferences (temperature units, locations, etc.) and allows for quick access to multiple saved locations. Deduct 5 points if no persistence is implemented, 3 points if only partial preferences are saved, and 5 points if there's no way to manage multiple locations. 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 network failures, API downtime, invalid user inputs, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Weather alerts/notifications 2. Historical weather data comparison 3. Interactive weather maps 4. Air quality or UV index information). 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 API calls for the same data 2. Function modules unrelated to weather forecasting 3. Fancy effects that affect performance (e.g., unnecessary animations that slow down the interface). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating API service/UI components/state management), proper error handling, and code maintainability. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no separation of concerns between data fetching and presentation. 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) Responsive design that works on multiple screen sizes. Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for non-responsive layouts. 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) Loading states shown when fetching data 2) Transition animation duration controlled between 300-500ms 3) Clear visual hierarchy and information architecture. Deduct 5 points for missing loading indicators during API calls, 3 points for jarring transitions between views, and 5 points for cluttered information display that overwhelms the user. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Daily Office Tasks",
-  "difficulty": "easy"
-}

package/library/utility_tools-daily_office_tasks/weather-forecast-software-design.json

@@ -1,68 +0,0 @@
-{
-  "index": 750,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Take care to ensure that the code you generate is executable and demonstrable. As a programmer, design a weather forecast software.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the weather data retrieval and processing system correctly implemented?",
-      "description": "Evaluate whether the code includes API integration with a weather service provider (like OpenWeatherMap, WeatherAPI, etc.), proper error handling for API calls, data parsing, and caching mechanisms. Score 0 if there's no data retrieval implementation, 5 if basic API calls are made without proper error handling or caching, and 10 if complete with error handling, rate limiting protection, and efficient caching strategy for offline access.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the forecast visualization component properly implemented?",
-      "description": "Check if the code implements appropriate visualization for weather conditions (temperature graphs, precipitation charts, wind direction indicators, etc.). Assess whether the visualizations are responsive and interactive. Score 0 if visualizations are missing, 5 if basic static visualizations exist, and 10 if interactive, responsive visualizations with appropriate transitions and animations are implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are location services and geolocation features properly implemented?",
-      "description": "Examine whether the application allows users to search for locations, automatically detect their current location, and save favorite locations. Check for proper geocoding/reverse geocoding implementation. Deduct 3 points if location search is missing, 3 points if current location detection is not implemented, and 4 points if there's no location management functionality. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the weather alert/notification system implemented?",
-      "description": "Verify if the application can send users notifications about severe weather conditions, weather changes, or daily forecasts. Check for implementation of customizable alert thresholds and notification preferences. Score 0 if notification features are absent, 5 if basic notifications exist without customization options, and 10 if a complete system with customizable alerts and multiple delivery channels is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as network failures, API errors, invalid user inputs, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Weather impact on daily activities recommendations 2. Historical weather data comparison 3. Weather-based outfit suggestions 4. Integration with smart home systems). 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 location detection methods without integration) 2. Function modules unrelated to weather forecasting (e.g., a built-in game) 3. Fancy effects that affect performance (e.g., excessive animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating data services/UI components/state management), 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 (weather-appropriate color schemes) 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 information hierarchy for weather data. Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance for changing weather conditions. Deduct 5 points for each operation without feedback, 3 points for visual after-images during forecast timeline navigation, 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/web-audio-visualizer-with-labeling.json

@@ -1,68 +0,0 @@
-{
-  "index": 249,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable. Implement the following requirements in HTML for VSCode:\n\n1. Add a button (called \"Select File\") to choose different wav files, with wav files as input\n2. Process data (of type two-dimensional array, where each data point has time, frequency, and intensity indicators) generated by backend code (no need to generate this code) and visualize it\n3. Plot with time on the x-axis, frequency on the y-axis, and represent intensity with color (deeper color for higher intensity)\n4. Implement zooming capability for the x-axis (time axis) with a range from 1s to 20s, and add a slider to set the specific display range\n5. Add a button and an input field to label the selected time segment (pressing the button will mark this time segment with the string from the input field)\n6. Add a button (called \"Reset\") to restore the webpage to its initial state\n7. After marking is complete, output a .py file with the following standard Python two-dimensional array format for easy reading:\nres_lis = [\n[start_point, end_point, label],\n[start_point, end_point, label],\n...\n[start_point, end_point, label]\n]\nwhere start_point and end_point are times in milliseconds, and label is a string\n8. Provide two code files: one for input functions and one for calculating intensity\n9. When no file is input, the page should display a Cartesian coordinate system\n\nCreate a web frontend implementation for these requirements.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the file selection function properly implemented?",
-      "description": "Check whether the code implements a functional 'Select File' button that allows users to choose wav files. The button should trigger a file input dialog, restrict file types to .wav format, and handle file selection events. The selected file name should be displayed to the user. Score 0 if missing, 5 if basic implementation exists but lacks validation, 10 if fully implemented with proper error handling.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the data visualization capability complete?",
-      "description": "Evaluate whether the code can properly process and visualize the two-dimensional array data (time, frequency, intensity). Check if the visualization correctly maps time to x-axis, frequency to y-axis, and intensity to color. The color mapping should use an appropriate gradient scale. Deduct 5 points if axes are incorrectly labeled, 3 points if the color scale is not intuitive, and 5 points if the visualization does not handle varying data ranges. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the time axis zoom functionality implemented?",
-      "description": "Verify if the code implements the zooming capability for the x-axis (time) with a range from 1s to 20s. The slider should adjust the visible time range dynamically, and the visualization should update accordingly without losing data integrity. Check if the slider has appropriate step sizes and if the zoom transitions are smooth. Score 0 if missing, 5 if basic implementation exists but is glitchy, and 10 if fully implemented with smooth transitions.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the time segment labeling system functional?",
-      "description": "Assess if the code implements a system to label selected time segments with user input. This should include: (1) A way to select a time segment (2) An input field for the label text (3) A button to confirm the labeling. Check whether the labeled segments are visually indicated on the visualization. Deduct 3 points if segment selection is unclear, 3 points if labels don't persist visually, and 5 points if multiple selections cause conflicts. 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 labels, overlapping time selections, etc.) and provide friendly error prompts. The code should prevent system crashes when users input unexpected values or perform operations in an unexpected order. Score 10 if robust error handling is implemented throughout, 5 if basic error handling exists but some edge cases are unaddressed, and 0 if no error handling is present.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Real-time frequency analysis visualization 2. Multiple visualization modes 3. Label categorization with color coding 4. Keyboard shortcuts for common operations). 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 reset the application) 2. Function modules unrelated to audio visualization (e.g., unnecessary animations) 3. Fancy effects that affect performance (e.g., excessive DOM manipulations). 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 processing/visualization/UI interaction layers), code organization, and maintainability. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the code lacks comments or documentation. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching in the visualization and UI elements 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 Python array output functionality properly implemented?",
-      "description": "Judge whether the code correctly implements the functionality to output labeled time segments in the required Python array format. The output should be downloadable as a .py file, properly formatted as specified, with accurate millisecond timestamps and preserved labels. Deduct 5 points if the format is incorrect, 3 points if the time unit conversion is inaccurate, and 5 points if the download functionality fails. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Daily Office Tasks",
-  "difficulty": "easy"
-}

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

@@ -1,68 +0,0 @@
-{
-  "index": 676,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Try to ensure that the generated code is executable for demonstration.\n\n## Role\nYou are an experienced code expert. Given a software development requirement description, you are required to generate project code based on the project requirements. Strictly follow the rules to help users generate complete project code with simple and easy-to-understand comments, and don't output anything else.\n\n## Output Rules\n1. You will always generate complete, runnable project code; please ensure the project is fully executable\n2. Ensure all code files you output are complete, don't omit any code\n3. Carefully review and check all code before final output, evaluating its executability. If the code cannot be executed or contains errors, regenerate it\n4. If the requirements include external API access or user data (images, videos, audio, etc.), please provide mock data\n\n## Project Requirements Description\nDevelop a screenshot and annotation tool where users can take screenshots of the current webpage through a browser or upload images, then add annotations such as text, arrows, shapes, etc. on the screenshot. The tool should support undo and redo functions, save edited images locally or to the cloud, and provide features for sharing to social media.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the screenshot capture functionality fully implemented?",
-      "description": "Evaluate whether the code properly implements both webpage screenshot capture and image upload capabilities. Check for browser compatibility across Chrome, Firefox, and Safari. The screenshot mechanism should handle different screen sizes and viewport considerations.0 points if core screenshot functionality is missing, 5 points if only basic screenshots work with limited browser support, 10 points for a complete implementation supporting all major browsers with proper error handling.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are annotation tools comprehensive and usable?",
-      "description": "Assess the implementation of annotation features including text, arrows, shapes, highlighting, and freehand drawing. Check for customization options like colors, line thickness, font styles, and opacity settings. Tools should be intuitive with proper cursor indicators.Deduct 2 points for each missing essential annotation type (text, arrow, rectangle, oval, freehand). Deduct 3 points if customization options are severely limited. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the undo/redo functionality properly implemented?",
-      "description": "Check for a robust state management system that tracks all user actions. Verify that undo/redo works correctly for all annotation types and maintains proper state history. Test edge cases like maximum history depth and performance with many operations.0 points if undo/redo is missing, 5 points if implementation is basic or has inconsistencies across annotation types, 10 points for comprehensive implementation with proper state management and keyboard shortcuts (Ctrl+Z/Ctrl+Y).",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are the save and export functions fully featured?",
-      "description": "Evaluate local saving options (PNG, JPEG, SVG formats) and cloud storage implementation. Check for proper file naming, compression options, and metadata handling. Verify that social media sharing includes proper preview generation and API integration.Deduct 3 points if only one file format is supported. Deduct 4 points if cloud storage is missing or poorly implemented. Deduct 3 points if social media sharing lacks proper API integration. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code handles common abnormal situations (such as invalid uploads, browser permission denials, network interruptions during save operations) and provides friendly error prompts or recovery mechanisms.Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. OCR text recognition in screenshots 2. Auto-blur for sensitive information 3. Smart shape recognition for hand-drawn annotations).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 tools 2. Function modules unrelated to screenshot/annotation purposes 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 annotation logic/UI components/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 and panel organization with appropriate icons and tooltips.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) Annotation placement feedback delay ≤ 100ms 2) Drag operations feel responsive with no visual lag 3) Clear visual feedback when selecting/moving annotations.Deduct 5 points for each operation without feedback, 3 points for visual stuttering during annotation movement, and 5 points for hard-to-find or confusing annotation controls. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Daily Office Tasks",
-  "difficulty": "hard"
-}

package/library/utility_tools-daily_office_tasks/wechat-mini-program-restrooms-tencent-maps.json

@@ -1,68 +0,0 @@
-{
-  "index": 1298,
-  "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. I want to create a WeChat Mini Program that will show public restrooms near the user's current location and mark them on Tencent Maps. Please write the entire project code using uniapp and following Vue 3's Composition API structure.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the location-based restroom finding functionality properly implemented?",
-      "description": "Review whether the code correctly uses the WeChat location API to obtain the user's current location, and then fetches nearby public restroom data. Check if the Tencent Maps integration correctly displays restroom locations with appropriate markers. Score 0 if location services are not implemented, 5 if basic location retrieval works but lacks error handling, and 10 if the implementation includes permission handling, location refresh mechanisms, and accurate geolocation conversion.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the Tencent Map integration complete and functional?",
-      "description": "Evaluate how well the Tencent Map SDK is integrated. Check for proper map initialization, marker handling, info windows for restroom details, and custom styling. The map should respond to user interactions like zooming, panning, and tapping on markers. Deduct 5 points if the map fails to properly render markers, 3 points if custom styling is missing, and 2 points if info windows don't provide useful information about restrooms. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the Vue 3 Composition API correctly utilized throughout the project?",
-      "description": "Examine if the code properly follows Vue 3's Composition API structure with the correct usage of setup(), ref(), reactive(), computed(), watch(), and lifecycle hooks. Check for proper component organization, reusable composables, and adherence to Vue 3 best practices. Deduct 5 points if the code mixes Options API with Composition API, 5 points if reactive state management is poorly implemented, and 3 points if lifecycle hooks are improperly used. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the uniapp framework correctly implemented for WeChat Mini Program?",
-      "description": "Verify that the code effectively uses uniapp's cross-platform capabilities while properly implementing WeChat Mini Program-specific features. Check for correct manifest.json configuration, proper use of uniapp's API (instead of direct WeChat API where applicable), and compatible component usage. Deduct 5 points if WeChat Mini Program specific configurations are missing, 3 points if platform detection is poor, and 5 points if uniapp APIs are bypassed in favor of direct platform APIs without justification. 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 location permission denial, network failure, map loading errors, empty data responses, 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. Restroom rating system 2. Accessibility information for each restroom 3. Navigation routing to selected restrooms 4. User contribution for new/missing restrooms 5. Offline map capability). Add 2 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 map initialization methods) 2. Function modules unrelated to restroom finding (e.g., weather forecasts) 3. Fancy effects that affect performance (e.g., excessive animations or complex UI transitions). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating API/view/state layers), proper error handling, code organization, and build process configuration. Deduct 5 points if global state management is poorly implemented; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the project structure is chaotic or if naming conventions are inconsistent. 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) Adherence to WeChat design guidelines. 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 4) Intuitive map interactions 5) Smooth marker clustering for dense areas. Deduct 5 points for each operation without feedback, 3 points for visual stuttering during map 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"
-}