@getollie/cli 0.0.5 → 0.2.1

package/library/utility_tools-automation/tauri-react-shadcn-tailwind-auto-update-project.json

@@ -1,68 +0,0 @@
-{
-  "index": 1074,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Be sure to make the generated code executable for demonstration. Help me create a project using Tauri, React, Shadcn, and Tailwind.css with auto-update functionality.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Tauri application architecture correctly implemented?",
-      "description": "Review whether the code properly configures Tauri with React integration, including correct tauri.conf.json setup, proper Rust backend commands, and IPC (Inter-Process Communication) between frontend and backend. Check if the build process generates functional native executables for target platforms. Score 0 if Tauri core functionality is missing, 5 if basic setup exists but lacks proper IPC, and 10 if fully functional with secure command invocations and proper error handling.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the React + Shadcn + Tailwind integration properly configured?",
-      "description": "Evaluate whether React components utilize Shadcn UI components effectively with proper Tailwind CSS styling. Check for correct package.json dependencies, proper component imports, and theme configuration. Verify that Tailwind classes are purged correctly and Shadcn components render with consistent styling. Deduct 3 points if component library integration is incomplete, 5 points if styling conflicts exist, and 2 points if build optimization is missing. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the auto-update functionality fully implemented and secure?",
-      "description": "Check whether the auto-update mechanism includes proper version checking, secure download verification (signature validation), and graceful update installation. Evaluate if the updater handles network failures, provides user notifications, and supports rollback mechanisms. Verify that update endpoints are configured correctly and SSL/TLS is enforced. Deduct 5 points if signature verification is missing, 3 points if no fallback mechanism exists, and 5 points if update UI feedback is inadequate. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the project structure and configuration management comprehensive?",
-      "description": "Assess whether the project includes proper environment configuration, build scripts for multiple platforms, and deployment workflows. Check for proper TypeScript configuration, ESLint/Prettier setup, and development/production environment separation. Verify that all necessary configuration files (vite.config.js, tailwind.config.js, components.json) are properly set up. Deduct 3 points for missing TypeScript support, 4 points for inadequate build configuration, and 3 points for missing development tooling. 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 during updates, file system permissions errors, invalid user input, and Tauri API failures) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should include proper error boundaries, async error handling, and graceful degradation. Give 10 points if fully implemented, 5 points if basic error handling exists, and 0 points if no exception 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 Tauri application experience (e.g., 1. System tray integration with context menus 2. Native notifications and system integration 3. Custom window controls and themes 4. Local database integration 5. Cross-platform native file handling). Add 2-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 state management solutions coexisting) 2. Unnecessary dependencies that bloat the bundle size 3. Over-engineered components that don't utilize Tauri's native capabilities effectively. Deduct 3 points for each redundancy found, and directly deduct 10 points if redundant code significantly impacts application performance or bundle size.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (proper separation of Tauri commands, React components, and utility functions), TypeScript type safety, and automated build processes. Check for proper component composition, custom hooks usage, and build optimization. Deduct 5 points if TypeScript types are poorly defined; deduct 5 points if component architecture is monolithic; deduct 5 points if build process lacks platform-specific optimizations. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface design meet professional standards?",
-      "description": "Evaluate whether the UI follows modern design principles using Shadcn components effectively: 1) Consistent design system with proper Tailwind utility usage 2) Proper spacing using Tailwind's spacing scale 3) Accessible color contrast ratios and focus states 4) Responsive design that works across different screen sizes. Deduct 3 points for inconsistent component usage, 5 points for poor color accessibility, and 5 points for non-responsive layouts. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the native desktop interaction smooth and intuitive?",
-      "description": "Judge whether the desktop application provides native-like user experience: 1) Proper window management and native controls 2) Keyboard shortcuts and accessibility support 3) Smooth transitions utilizing Tauri's performance benefits 4) Native context menus and system integration. Deduct 5 points for web-like behavior that doesn't leverage native capabilities, 3 points for poor keyboard navigation, and 5 points for lack of system integration features. Full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Automation",
-  "difficulty": "medium"
-}

package/library/utility_tools-automation/user-agent-switcher-with-presets-and-detection.json

@@ -1,68 +0,0 @@
-{
-  "index": 563,
-  "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 User-Agent switcher that provides presets for common devices (iOS/Android/PC), supports custom UA strings, and can detect the current page's UA for quick testing and switching.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the UA switcher core functionality fully implemented?",
-      "description": "Check if the code provides a complete UA switcher that can modify the User-Agent string in the browser. It should include functionality to get the current UA, set a new UA, and restore the original UA. Score 0 if the core functionality is missing, 5 if basic switching is implemented but with limitations, and 10 if the implementation is complete with all required features.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are presets for common devices (iOS/Android/PC) properly implemented?",
-      "description": "Verify that the code includes accurate and up-to-date UA string presets for common device types (at least iOS, Android, and PC/Desktop browsers). Each preset should contain the correct string format for the respective platform and major browser versions. Deduct 3 points if any major platform is missing, 2 points if the UA strings are outdated, and 2 points if the preset selection UI is not intuitive. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is custom UA string input functionality properly implemented?",
-      "description": "Assess whether users can input, save, and apply custom UA strings. The interface should validate input to ensure it's a valid UA string format, provide feedback on application success, and maintain a history of custom entries. Deduct 3 points if validation is missing, 3 points if there's no persistence mechanism, and 2 points if the UI for custom input is confusing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is current page UA detection and quick switching implemented?",
-      "description": "Evaluate if the code can detect and display the current page's UA string, and provide a mechanism for quickly switching between different UAs without requiring page reload. Check if the detection works across different browsing contexts and if the switching is instantaneous. Deduct 5 points if detection only works on the initial page load, and 5 points if switching requires a page reload. 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 browser API restrictions, permission issues, incompatible browsers, 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. UA comparison visualization 2. Device emulation preview 3. Analytics for website behavior under different UAs). 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 methods to change UA) 2. Function modules unrelated to UA switching (e.g., a built-in screenshot tool) 3. Fancy effects that affect performance (e.g., unnecessary animations when switching). 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 UA management/UI/storage layers), browser compatibility considerations, and code organization. Deduct 5 points if global namespace 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 proper error handling or logging. 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) UA switching feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual indication of active UA. Deduct 5 points for each operation without feedback, 3 points for jarring transitions when switching UAs, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Automation",
-  "difficulty": "medium"
-}

package/library/utility_tools-automation/video-camera-detection-line-crossing-counting.json

@@ -1,68 +0,0 @@
-{
-  "index": 1005,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable. Disregard sections 4.4 and 4.5, and write out the software page display based on the following content:\n\n1) Video Detection Demonstration\n1. Click the open video icon to choose a video for detection, and the detection results will be displayed automatically. Clicking this button again will close the video.\n2. After opening the video, click \"Draw Line Segment\" and use the left mouse button to click two points on the displayed interface to draw a line segment for counting objects crossing the line.\n3. After completing the two points, click the \"Complete Drawing\" button to enable bi-directional counting and statistics of objects crossing the line in the video.\nNote: The \"Detection Duration\" displayed on the interface indicates the length of video time that has been detected [related to detection speed], not the actual elapsed time.\n\n(2) Camera Detection Demonstration\n1. Click the open camera icon to activate the camera for real-time detection. Clicking this button again will close the camera.\n2. After opening the camera, click \"Draw Line Segment\" and use the left mouse button to click two points on the displayed interface to draw a line segment for counting objects crossing the line.\n3. After completing the two points, click the \"Complete Drawing\" button to enable bi-directional counting and statistics of objects crossing the line in the video.\nNote: The \"Detection Duration\" displayed on the interface indicates the length of video time that has been detected [related to detection speed], not the actual elapsed time.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the video detection function fully implemented?",
-      "description": "Review whether the code correctly implements video file selection, loading, and automatic detection. Check if the video playback controls work properly and if the detection results are displayed in real-time. Score 0 if the video detection is not implemented, 5 if basic video loading works but detection has issues, and 10 if video detection functions flawlessly with proper error handling.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the camera detection function properly implemented?",
-      "description": "Evaluate if the code successfully accesses the device camera, handles permissions correctly, and processes the camera feed for detection. Check whether the camera can be turned on/off as specified and if detection works in real-time. Deduct 5 points if camera permissions are not properly handled, and 3 points if there are performance issues with real-time detection. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the line segment drawing functionality implemented correctly?",
-      "description": "Check if users can draw a line segment by clicking two points on the interface, and if the 'Draw Line Segment' and 'Complete Drawing' buttons work as specified. Verify that the line remains visible after drawing and maintains its position during video playback. Deduct 5 points if the drawing mechanism is buggy, and 3 points if the visual feedback is unclear. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the object crossing detection and bi-directional counting implemented accurately?",
-      "description": "Verify if the code correctly detects and counts objects crossing the drawn line in both directions. Check the accuracy of the counting algorithm (intersection detection) and whether the statistics are updated in real-time. Score 0 if counting is not implemented, 5 if basic counting works but has accuracy issues, and 10 if bi-directional counting is fully functional with high precision.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid video files, camera access denial, browser compatibility issues, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Object type filtering 2. Heatmap visualization of crossing patterns 3. Exportable detection statistics with timestamps). 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 draw detection lines) 2. Function modules unrelated to video/camera detection (e.g., unnecessary settings pages) 3. Fancy effects that affect detection performance. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core detection 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 detection logic/UI/data processing layers), code reusability between video and camera detection modules, and performance optimization. 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 performance optimization for real-time detection. 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) Clear visual indicators for detection results and statistics. Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for unclear visualization of detection results. 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) Detection results appear without noticeable delay 2) Line drawing feedback is immediate and precise 3) Clear visual indicators when objects cross the line. Deduct 5 points for laggy detection visualization, 3 points for imprecise drawing feedback, and 5 points for unclear crossing indicators. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Automation",
-  "difficulty": "medium"
-}

package/library/utility_tools-automation/video-download-tool-with-batch-and-quality-options.json

@@ -1,68 +0,0 @@
-{
-  "index": 509,
-  "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. Develop a video download tool where users can input video URLs (such as YouTube), and the tool will automatically parse and provide different quality options for video download, supporting batch downloading and progress display.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the URL parsing and video metadata extraction fully implemented?",
-      "description": "Review whether the code accurately parses various video platform URLs (YouTube, Vimeo, etc.) and correctly extracts metadata including available quality options, video length, and format information. Score 0 if parsing is not implemented, 5 if only basic YouTube parsing works, and 10 if the system handles multiple platforms and extracts complete metadata.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the quality selection mechanism properly implemented?",
-      "description": "Check whether users can select from different quality options (resolution, bitrate, format) for each video. The interface should display size estimates for each option and preview thumbnails if possible. Deduct 3 points if only preset quality options are available, 5 points if quality comparison is missing, and 7 points if format conversion options are absent. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the batch download functionality effectively implemented?",
-      "description": "Evaluate whether the code allows users to queue multiple videos for download, with features like priority adjustment, pause/resume for individual downloads, and batch operations. Check if there's intelligent queue management for bandwidth optimization. Deduct 5 points if parallel download limits aren't configurable, and 3 points if download reordering is missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the progress display and notification system comprehensive?",
-      "description": "Review whether the progress tracking includes detailed information (download speed, ETA, file size), visual indicators (progress bars with percentage), and system notifications (completion alerts, error messages). Deduct 3 points for missing speed indicators, 3 points for inaccurate ETA calculations, and 5 points if there's no persistent progress tracking after browser refresh. 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 URLs, network interruptions, server-side restrictions, rate limiting, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Smart format detection based on device 2. Auto-categorization of downloaded content 3. Integration with media players for preview). 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 download methods 2. Function modules unrelated to video downloading (e.g., a built-in video editor) 3. Fancy effects that affect performance (e.g., excessive animations during downloads). 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 parsing/downloading/UI layers), unit test coverage, and error handling. 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 proper logging system for debugging purposes. 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 during download operations. Deduct 5 points for each operation without feedback, 3 points for jerky progress animations, and 5 points for hard-to-find download control buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Automation",
-  "difficulty": "easy"
-}

package/library/utility_tools-automation/vs2019-code-generation-tools-requirements.json

@@ -1,68 +0,0 @@
-{
-  "index": 1395,
-  "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 can be demonstrated. What tools can work with you that directly integrate with VS2019, where I describe requirements and it writes code for me?",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is there a comprehensive analysis of VS2019 compatible AI coding tools?",
-      "description": "Evaluate whether the response provides a thorough overview of available AI coding assistants that integrate with Visual Studio 2019. The analysis should cover both Microsoft's first-party tools and third-party extensions. Deduct 3 points if major tools are missing, 5 points if integration methods aren't explained. Full implementation scores 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is there a technical comparison of the capabilities of different AI coding tools?",
-      "description": "Check if the response compares the technical capabilities of different tools (language support, code generation capabilities, context understanding, etc.). A complete comparison should include feature matrices, supported programming languages, and limitations. Deduct 5 points if only surface-level comparison is provided without technical depth. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are practical installation and configuration instructions provided?",
-      "description": "Assess whether the response includes step-by-step instructions for installing and configuring these tools in VS2019, including screenshots of the installation process, environment requirements, and potential conflicts. Deduct 5 points if only general instructions are provided without VS2019-specific details. Full implementation scores 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are there concrete examples demonstrating the tools in action?",
-      "description": "Evaluate whether the response includes practical examples/screenshots showing how to use the tools to generate code from requirements in different scenarios (e.g., UI components, algorithms, database operations). Deduct 3 points for each major programming paradigm not covered. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether any sample code provided demonstrates error handling, input validation, and follows best practices for the respective languages. Code with strong robustness should handle edge cases and include appropriate comments explaining complex logic. Give 10 points for excellent robustness, 5 points for average implementation, and 0 points if no error handling is included.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the response highlights unique capabilities of the tools that might not be immediately obvious (e.g., refactoring suggestions, architecture planning, automated testing). Add 3 points for each practical innovative feature highlighted (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check for redundancy in the response: 1. Overlapping tool recommendations without differentiation 2. Explanation of features unrelated to VS2019 integration 3. Excessive theoretical explanations without practical application. Deduct 3 points for each redundancy found, and directly deduct 10 points if core information is obscured by redundant content.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the response have engineering quality?",
-      "description": "Review the organization of information, accuracy of technical details, and overall structure of the response. Deduct 5 points if information is poorly organized; deduct 5 points if technical specifications contain errors; deduct 5 points if the response lacks logical progression. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional documentation standards?",
-      "description": "Evaluate whether any screenshots and diagrams are clear, properly annotated, and follow professional documentation standards. Check for logical organization of visual elements, proper resolution, and highlighting of important UI elements. Deduct 3 points for each unclear visual element, 5 points for poor labeling, and 5 points for inconsistent visual style. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the practical workflow guidance provided?",
-      "description": "Judge whether the response provides a clear workflow for using these tools effectively: 1) Requirement formulation guidelines 2) Tool selection criteria based on project needs 3) Iterative refinement process with the AI. Deduct 5 points for missing workflow stages, 3 points for vague instructions, and 5 points for unrealistic expectations about tool capabilities. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Automation",
-  "difficulty": "medium"
-}

package/library/utility_tools-automation/vue-desktop-app-browser-plugin-settings.json

@@ -1,68 +0,0 @@
-{
-  "index": 310,
-  "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 display purposes. Please create a Vue desktop application with browser management, plugin management, and settings menu. When clicking on browser management, it should display a paginated view with 10 items per page, showing workid and operation columns. The workid is an auto-incrementing ID starting from 1. Operations include start and stop buttons. Clicking start will launch Chrome.exe from a specified path with startup parameters:\n\n```javascript\nconst args = [\n    `--lang=zh-CN`,\n    `--timezone=${timezone || 'Asia/Hong_Kong'}`,\n    `--fps=${workId}`,\n    // `--window-icon=${iconPath}`,\n];\nconst allExtensions = [...(pluginPaths || [])];\nif (allExtensions.length > 0) {\n    args.push('--load-extension=' + allExtensions.join(','));\n    args.push('--disable-extensions-except=' + allExtensions.join(','));\n}\n```\n(This is what I wrote in JavaScript)",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Vue desktop application structure correctly implemented?",
-      "description": "Review whether the code properly implements a Vue desktop application with the three required main components: browser management, plugin management, and settings menu. Check if Vue.js framework is correctly set up with proper component structure, routing, and state management. Score 0 if the core structure is missing, 5 if implemented but with architectural issues, and 10 if properly structured with component reusability and clean architecture.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the browser management functionality fully implemented?",
-      "description": "Verify if the browser management component correctly displays a paginated view with 10 items per page, showing workid and operation columns as required. Check if the auto-incrementing workid starting from 1 is properly implemented. Deduct 5 points if pagination is incorrect or missing, 3 points if workid implementation is flawed, and 3 points if the display layout is poorly structured. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are the start and stop operations correctly implemented in the browser management?",
-      "description": "Evaluate whether clicking the start button properly launches Chrome.exe with the specified parameters (language, timezone, fps, extensions) and whether the stop button correctly terminates the process. Check if the code handles process management properly. Deduct 5 points if Chrome launching fails with specified parameters, 3 points if process termination is not properly handled, and 3 points if error handling for these operations is missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the plugin management functionality properly implemented?",
-      "description": "Assess whether the plugin management section allows users to add, view, and manage Chrome extensions that will be used in the '--load-extension' and '--disable-extensions-except' parameters. Check if the UI allows browsing for extension paths and if the selected extensions are properly stored and used when launching Chrome. Deduct 5 points if extension path selection is missing, 3 points if validation is inadequate, and 3 points if the extension list management is poorly implemented. 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 Chrome paths, missing extensions, process launch failures, 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. Browser profile management 2. Extension marketplace integration 3. Performance monitoring dashboard for launched browsers). 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 launch browsers) 2. Function modules unrelated to browser management (e.g., built-in games) 3. Fancy effects that affect performance (e.g., unnecessary animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating UI components/business logic/process management layers), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast sliding, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Automation",
-  "difficulty": "medium"
-}

package/library/utility_tools-automation/vue-packet-capture-electron-app.json

@@ -1,68 +0,0 @@
-{
-  "index": 877,
-  "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. Rewrite a complete Vue packet capture project that can be packaged into an Electron desktop application.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the packet capturing functionality fully implemented?",
-      "description": "Review whether the code accurately implements the core packet capture functionality using appropriate libraries (like pcap, npcap, or libpcap bindings). Check if it can capture different protocols (TCP, UDP, HTTP, etc.), filter packets by protocol/IP/port, and display packet details. Score 0 if core capture functionality is missing, 5 if basic capturing works but with limited protocol support, and 10 if comprehensive protocol analysis is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the Vue frontend properly structured and integrated with Electron?",
-      "description": "Evaluate the Vue project structure, component organization, and proper integration with Electron. Check for proper use of Vue's reactivity system, component lifecycle management, and appropriate use of Vuex/Pinia for state management. Examine whether the build process correctly bundles the application for Electron. Deduct 5 points if Vue-Electron integration has security issues, and 3 points if the build process is incomplete. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are packet visualization and analysis features implemented?",
-      "description": "Check if the application provides visual representations of captured packets (charts, timelines, flow diagrams) and analysis tools (filters, search, statistics). Verify if packet details can be exported in standard formats (PCAP, CSV, JSON). Deduct 5 points if visualization is basic or missing, 3 points if analysis tools are limited. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there proper handling of system permissions and native OS integration?",
-      "description": "Assess whether the application correctly requests and manages elevated permissions required for packet capture across different operating systems. Check for proper error handling when permissions are denied, and verify appropriate use of native OS APIs through Electron. Deduct 5 points if permission handling is incomplete, and 3 points if the application fails on specific operating systems. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as permission denial, network interface changes, high packet volume, 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 protocol anomaly detection 2. Machine learning based traffic classification 3. Customizable dashboard with drag-and-drop widgets 4. Built-in packet replay functionality). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple packet filtering mechanisms) 2. Function modules unrelated to packet capture (e.g., a built-in media player) 3. Fancy effects that affect performance (e.g., excessive animations that slow down packet processing). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating capture logic/visualization/analysis layers), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast packet display updates, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Automation",
-  "difficulty": "medium"
-}

package/library/utility_tools-automation/vue3-webpack-complete-process.json

@@ -1,68 +0,0 @@
-{
-  "index": 1323,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Be sure to make the code you generate executable for demonstration. Vue3 webpack complete process",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Vue3 project initialization and webpack configuration fully implemented?",
-      "description": "Review whether the code accurately sets up a Vue3 project with webpack, including proper configuration files (webpack.config.js), development and production modes, and essential loaders. Score 0 if the basic webpack configuration is missing, 5 if only basic configuration is implemented, and 10 if it includes optimized configurations for both development and production environments.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the Vue3 core features properly integrated with webpack?",
-      "description": "Check whether the configuration properly handles Vue3's Composition API, Single File Components (.vue files), and script setup syntax. The webpack configuration should include vue-loader with proper options. Deduct 5 points if SFC handling is incorrectly configured, and 3 points if Composition API features aren't supported. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is asset handling and optimization properly implemented?",
-      "description": "Evaluate whether the webpack configuration includes proper loaders and plugins for different asset types (CSS, SCSS, images, fonts, etc.), along with optimization strategies like minification, code splitting, and tree shaking. Deduct 5 points if asset loaders are missing or misconfigured, and 3 points if no optimization techniques are implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the development environment properly configured?",
-      "description": "Check whether the code includes proper development tools like webpack-dev-server with hot module replacement, source maps for debugging, and environment variables management. Deduct 5 points if hot reloading isn't implemented, and 3 points if proper debugging tools are missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common build errors (such as import errors, syntax errors in Vue files, etc.) and provide friendly error messages or recovery mechanisms. Code with strong robustness should include proper error plugins and fallbacks, giving 10 points. If the robustness is average, give 5 points, and if no error handling is implemented, 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 development experience (e.g., 1. Build analytics visualization 2. Custom webpack plugins for Vue-specific optimizations 3. Automatic component documentation generation). 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 webpack plugins performing similar tasks 2. Unnecessary transpilation steps or polyfills 3. Over-engineered configurations that add complexity without benefits. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core build process is slowed down significantly by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular configuration design (separating webpack configs by environment), proper dependency management (dev vs. prod dependencies), and build process automation. Deduct 5 points if configurations are not modularized; deduct 5 points if there's excessive duplication between configs; deduct 5 points if the build process isn't properly scripted in package.json. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the project structure follow Vue3 best practices?",
-      "description": "Evaluate whether the project structure follows modern Vue3 standards: 1) Proper separation of components, composables, and views 2) Consistent naming conventions for files and directories 3) Clear organization of assets and styles. Deduct 3 points for unclear component organization, 5 points for mixing concerns (like API calls in components), and 5 points for inconsistent file structures. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the build performance and output optimized?",
-      "description": "Judge whether the build process is optimized for performance: 1) Proper code splitting and lazy loading 2) Cache optimization with contenthash 3) Minimized bundle size with tree shaking and proper external dependencies. Deduct 5 points for missing code splitting, 3 points for inefficient caching strategies, and 5 points for bloated bundle sizes without optimization. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Automation",
-  "difficulty": "medium"
-}