@getollie/cli 0.0.1

package/library/utility_tools-daily_office_tasks/vue-uni-app-writing-pad-finger-trajectories.json

@@ -0,0 +1,68 @@
+{
+  "index": 1531,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable when possible. Write Vue code using uni-app to implement a writing pad program that can record the user's finger movement trajectories on the screen and display them exactly as drawn.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core drawing functionality correctly implemented?",
+      "description": "Check if the code accurately captures touch/mouse events and renders the drawing trajectory in real-time. Verify that the path follows the exact finger movement with proper event handling (touchstart, touchmove, touchend or equivalent). Score 0 if drawing is not implemented, 5 if basic drawing works but with noticeable lag or inaccuracies, and 10 if the drawing experience is smooth and precise.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the uni-app framework properly utilized for cross-platform compatibility?",
+      "description": "Evaluate whether the code correctly uses uni-app APIs and components for touch events and canvas operations. Check if platform-specific adaptations are implemented (App/H5/WeChat Mini Program). Deduct 3 points if platform-specific conditions are missing, 5 points if only one platform is supported, and 7 points if critical uni-app features are ignored. Give 10 points for full cross-platform implementation.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the drawing configuration customizable?",
+      "description": "Assess if the writing pad provides customization options like line thickness, color, opacity, and stroke style. Check if these settings are reactive and properly applied to the drawing operations. Deduct 2 points for each missing essential customization feature. Award full 10 points if all common drawing settings are available and correctly implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are important writing pad operations supported?",
+      "description": "Verify implementation of essential operations: clear canvas, undo/redo functionality, save/export drawing, and erase mode. Deduct 2 points for each missing operation. For operations that are present but partially implemented (e.g., undo without redo), deduct 1 point each. 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 multi-touch conflicts, rapid drawing movements, edge-of-screen handling, device rotation, 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. Pressure sensitivity support 2. Stylus-specific optimizations 3. Drawing playback feature 4. Handwriting recognition). 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 event handlers or listeners that might cause memory leaks 2. Unnecessary re-rendering of the canvas 3. Fancy effects that affect drawing performance (e.g., complex animations during drawing). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core drawing 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 drawing logic/UI controls/data management), component reusability, and proper Vue lifecycle management. Deduct 5 points if global state is used improperly; deduct 3 points if Vue reactivity system is not used effectively; deduct 5 points if the code structure violates uni-app best practices. 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 drawing interaction smooth and responsive?",
+      "description": "Judge whether the drawing performance meets user expectations: 1) Line rendering delay ≤ 16ms (60fps) 2) No visible gap between touch point and rendered line 3) Smooth curves without jagged edges or pixelation. Deduct 5 points for noticeable lag between touch and drawing, 3 points for jerky line rendering during fast movements, and 5 points for poor performance on complex drawings. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Utility Tools-Daily Office Tasks",
+  "difficulty": "medium"
+}

package/library/utility_tools-daily_office_tasks/vue2-data-dictionary-component.json

@@ -0,0 +1,68 @@
+{
+  "index": 205,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the code you generate is executable and displayable. Vue 2 data dictionary component and its implementation.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Vue 2 data dictionary component architecture properly implemented?",
+      "description": "Review whether the component follows Vue 2 best practices (proper use of props, data, computed properties, watch, methods, lifecycle hooks). Check if the component is registered correctly either globally or locally. Verify the component has clear single responsibility. Score 0 if Vue 2 syntax is incorrect, 5 if basic structure exists but with architectural flaws, and 10 if the component follows Vue 2 architecture patterns properly.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the data dictionary data structure design well-conceived?",
+      "description": "Evaluate whether the data structure efficiently handles key-value pairs, supports nested dictionaries, and includes proper typing. Check if data organization allows for easy lookups, filtering, and modifications. Deduct 5 points if the structure doesn't account for complex dictionary relationships, and 3 points if key uniqueness validation is missing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Does the component provide comprehensive dictionary manipulation features?",
+      "description": "Check if the component offers essential dictionary operations: adding entries, editing values, removing entries, searching/filtering, sorting, and importing/exporting dictionary data. Deduct 2 points for each missing core feature. Verify if batch operations are supported. Award full 10 points only if the component handles both simple and complex dictionary operations efficiently.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the component implement proper data binding and reactivity?",
+      "description": "Assess if the code correctly leverages Vue 2's reactivity system. Verify that the component properly uses v-model or equivalent two-way binding when necessary, and utilizes Vue's reactivity features (computed properties, watchers) appropriately. Deduct 5 points if reactivity breaks during complex operations, 3 points if unnecessary deep watchers are used affecting performance. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid data formats, empty dictionaries, duplicate keys, asynchronous loading 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. Real-time dictionary validation 2. Interactive visualization of dictionary relationships 3. Drag-and-drop dictionary management 4. Intelligent auto-completion for dictionary 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 ways to edit dictionary entries) 2. Function modules unrelated to dictionary management 3. Fancy effects that affect performance (e.g., unnecessary animations when displaying dictionary data). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating UI/logic/data layers), component reusability, prop validation, and adherence to Vue style guide. Deduct 5 points if global state is mismanaged; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no documentation or 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 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 when navigating through dictionary entries. Deduct 5 points for each operation without feedback, 3 points for jarring transitions between dictionary views, 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/vue2-download-component-with-a-tag.json

@@ -0,0 +1,68 @@
+{
+  "index": 1295,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate, professional responses. Make sure the code you generate is executable and ready for demonstration. Write a download component in Vue 2 that receives a src property. When its icon is clicked, it should open a new window and download the file. Implement the download functionality using an a tag.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Vue 2 component structure correctly implemented?",
+      "description": "Review whether the code follows Vue 2 component specifications with proper props definition, template structure, and component registration. Check if the 'src' prop is correctly defined with appropriate type validation and default values. Score 0 if basic Vue component structure is missing, 5 if component is defined but lacks proper prop validation, and 10 if all Vue 2 best practices are followed including proper prop types, validators, and component naming conventions.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the download functionality properly implemented using anchor tag?",
+      "description": "Evaluate whether the download mechanism correctly uses HTML anchor tag with 'href' and 'download' attributes. Check if the component handles different file types, cross-origin scenarios, and fallback mechanisms for unsupported browsers. Deduct 5 points if download attribute is missing, 3 points if cross-origin downloads aren't handled, and 2 points if file extension detection is not implemented. Full score requires proper URL validation and error handling.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Does the new window opening mechanism work correctly?",
+      "description": "Check whether the component properly opens files in new windows using window.open() or target='_blank' attributes. Verify popup blocker handling, window focus management, and proper cleanup of opened windows. Deduct 5 points if popup blockers aren't handled, 3 points if window references aren't properly managed, and 2 points if the new window doesn't have appropriate dimensions or positioning.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the icon click interaction properly implemented?",
+      "description": "Assess whether the icon click event is correctly bound with proper event handling, loading states, and user feedback. Check if the component provides visual feedback during download initiation and handles multiple rapid clicks appropriately. Deduct 5 points if click events aren't properly bound, 3 points if no loading state is shown, and 2 points if rapid clicking causes multiple downloads without prevention.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid URLs, network failures, missing files, browser compatibility issues, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should effectively handle edge cases like malformed URLs, CORS issues, and unsupported file types, giving 10 points. If robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Download progress indication 2. File type icon detection 3. Download history tracking 4. Batch download support 5. Custom download naming). Add 2 points for each practical innovative feature implemented (maximum 10 points). Features should be genuinely useful and not just decorative.",
+      "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 download methods coexisting unnecessarily) 2. Function modules unrelated to downloading (e.g., built-in file preview, unnecessary animations) 3. Over-engineered solutions for simple requirements. Deduct 3 points for each redundancy found, and directly deduct 10 points if core download functionality is compromised by unnecessary complexity.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review component structure, prop validation, event handling patterns, and Vue 2 best practices compliance. Check for proper component lifecycle usage, memory leak prevention, and reusability. Deduct 5 points if Vue reactivity is misused or component lifecycle isn't properly managed; deduct 3 points if props aren't validated; deduct 2 points if event listeners aren't cleaned up. Full score requires excellent separation of concerns and maintainable code structure.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface design meet professional standards?",
+      "description": "Evaluate whether the download icon and component styling follows modern design principles: 1) Appropriate icon choice and sizing (minimum 24px for touch targets) 2) Proper hover and active states 3) Consistent spacing and alignment 4) Accessible color contrast ratios (minimum 4.5:1). Deduct 3 points for each poor visual design choice, 5 points for unclear iconography, and 3 points for missing interaction states. Full score requires professional, intuitive visual design.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the download interaction conforms to user experience standards: 1) Click feedback delay ≤ 100ms 2) Smooth hover transitions (200-300ms) 3) Clear loading indicators during download initiation 4) Appropriate cursor changes and visual feedback. Deduct 5 points for each missing interaction feedback, 3 points for laggy hover effects, and 5 points for confusing or missing download status indicators. Full score requires polished, responsive user interactions.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Utility Tools-Daily Office Tasks",
+  "difficulty": "easy"
+}

package/library/utility_tools-daily_office_tasks/vue2-download-pdf-open-canvas.json

@@ -0,0 +1,68 @@
+{
+  "index": 228,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and expert responses. Pay attention to ensuring that the code you generate is executable for demonstration. How to download a PDF file and open it using canvas in Vue 2.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the PDF file download functionality properly implemented?",
+      "description": "Review whether the code correctly implements PDF file download using appropriate methods (fetch/axios/XMLHttpRequest) with proper headers and response type handling. Check if progress tracking, error handling for network failures, and CORS handling are included. Score 0 if download fails completely, 5 if basic download works but lacks error handling, and 10 if includes progress tracking, proper headers (Content-Type: application/pdf), and comprehensive error handling.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the PDF rendering on Canvas correctly implemented?",
+      "description": "Evaluate whether PDF.js library is properly integrated and configured to render PDF content on HTML5 Canvas element. Check if the implementation includes proper page scaling, quality settings (devicePixelRatio consideration), and viewport configuration. Deduct 5 points if rendering quality is poor or pixelated, 3 points if scaling doesn't work properly. Full score requires crisp rendering with proper DPI handling and responsive scaling.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is Vue 2 integration and component lifecycle properly managed?",
+      "description": "Check whether the implementation properly utilizes Vue 2 lifecycle hooks (mounted, beforeDestroy), reactive data properties, and component methods. Evaluate if PDF loading states are properly managed with Vue's reactivity system and if canvas references are correctly handled. Deduct 5 points if lifecycle management is missing, 3 points if reactivity is not properly utilized. Full score requires proper integration with Vue 2 patterns and state management.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are advanced PDF interaction features implemented?",
+      "description": "Assess whether the implementation includes essential PDF interaction features such as page navigation (next/previous), zoom controls (zoom in/out/fit), page number display, and multi-page support. Check if bookmark/outline navigation is available for complex PDFs. Deduct 5 points if only single page display is supported, 3 points if zoom functionality is missing. Full score requires comprehensive PDF navigation and interaction capabilities.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust and handles edge cases properly?",
+      "description": "Evaluate whether the code can handle common problematic scenarios (corrupted PDF files, network timeouts, large file sizes, unsupported PDF versions, mobile device limitations). Code should provide meaningful error messages and graceful degradation. Strong robustness with comprehensive error handling gets 10 points, basic error handling gets 5 points, no exception handling gets 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there innovative features that enhance PDF viewing experience?",
+      "description": "Check whether the code includes valuable enhancement features (e.g., 1. Text selection and search functionality 2. Annotation tools or highlighting 3. Thumbnail preview sidebar 4. Full-screen mode 5. Print functionality). Add 2-3 points for each well-implemented innovative feature that adds real value to the PDF viewing experience (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant or unnecessary implementations?",
+      "description": "Strictly identify three types of redundancy: 1. Multiple PDF rendering libraries loaded simultaneously 2. Unnecessary file conversion processes 3. Overly complex animations that impact PDF rendering performance 4. Duplicate canvas elements or rendering loops. Deduct 3 points for each redundancy found, and deduct 10 points if redundant code significantly impacts core PDF functionality.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code demonstrate good engineering practices?",
+      "description": "Review component modularity (separation of PDF service, canvas renderer, UI controls), proper async/await usage, memory management (canvas cleanup, PDF document disposal), and Vue 2 best practices. Deduct 5 points if memory leaks are present or improper async handling; deduct 5 points if code organization is poor; deduct 5 points if no error boundaries or loading states. Full score requires clean architecture and proper resource management.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the PDF viewer interface meet professional design standards?",
+      "description": "Evaluate whether the PDF viewer UI follows modern design principles: 1) Clean toolbar design with intuitive icons 2) Proper contrast for PDF content readability 3) Responsive layout that works on different screen sizes 4) Loading states and progress indicators. Deduct 3 points for cluttered UI elements, 5 points for poor readability or contrast issues, and 5 points for non-responsive design that breaks on mobile devices.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Are PDF interactions smooth and provide immediate feedback?",
+      "description": "Judge whether PDF operations provide smooth user experience: 1) Page transitions without flickering 2) Zoom operations with smooth scaling (≤300ms) 3) Loading indicators during PDF processing 4) Responsive controls with immediate visual feedback (≤100ms). Deduct 5 points for each laggy operation, 3 points for missing loading states, and 5 points for unresponsive or hard-to-find navigation controls.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Web Visuals",
+  "difficulty": "medium"
+}

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

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

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

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

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