@getollie/cli 0.0.5 → 0.2.0

package/library/utility_tools-automation/google-extension-vue-devtools-vue2-vue3.json

@@ -1,68 +0,0 @@
-{
-  "index": 717,
-  "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. Help me write a Google extension: the requirement is similar to the Vue DevTools in the Google Store, and it should simultaneously support both Vue 2 and Vue 3.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Chrome extension architecture correctly implemented?",
-      "description": "Evaluate whether the extension follows Chrome extension best practices with proper manifest.json configuration (v3 preferred), background scripts, content scripts, and popup interfaces. Check for permission declarations, extension lifecycle management, and proper isolation between contexts. Score 0 if basic extension structure is missing, 5 if implementation is basic but functional, 10 if implementation is comprehensive and follows all Chrome extension guidelines.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Does the extension properly detect both Vue 2 and Vue 3 applications?",
-      "description": "Review the detection mechanism for identifying Vue instances in the page. Check if it can distinguish between Vue 2 and Vue 3, adapt to different mounting patterns, and handle both options API and composition API. Examine how it handles multiple Vue instances on the same page. Deduct 5 points if detection works for only one Vue version, 3 points if edge cases (like lazy-loaded components) aren't handled. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the component tree visualization fully implemented?",
-      "description": "Check if the extension properly builds and displays the component hierarchy tree with correct parent-child relationships. Verify if it updates in real-time when components mount/unmount, and shows component depth levels correctly. Assess whether the tree is searchable and filterable. Score 0 if visualization is absent, 5 if basic tree is implemented but lacks features, 10 if complete with all expected functionality.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are component inspection features comparable to Vue DevTools?",
-      "description": "Evaluate the component inspection functionality: props viewing/editing, data observation, computed properties calculation, methods listing, and event tracking. Check support for time-travel debugging and state snapshots. Verify hooks/lifecycle visualization for both Vue versions. Deduct 3 points for each major missing feature compared to official DevTools. 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 pages with multiple Vue instances, hydration mismatches, minified production builds, SSR applications, 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. Component rendering performance metrics 2. State change diff visualization 3. Component export/import 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 ways to inspect the same property) 2. Function modules unrelated to Vue debugging (e.g., general DOM inspection that duplicates Chrome DevTools) 3. Fancy effects that affect performance (e.g., excessive animations in the panel). 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 core logic/UI/communication 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": "hard"
-}

package/library/utility_tools-automation/image-based-search-program.json

@@ -1,68 +0,0 @@
-{
-  "index": 1343,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the code you generate is executable for demonstration. Help me create a small program for image-based search.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the image loading and processing functionality properly implemented?",
-      "description": "Evaluate if the code correctly handles image loading (from file upload or URL), preprocessing (resizing, normalization), and error handling for corrupt or invalid images. Score 0 if image handling is missing, 5 if basic loading works but lacks preprocessing, and 10 if it includes comprehensive image manipulation with proper error handling.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the image feature extraction algorithm well-implemented?",
-      "description": "Check whether the code implements proper feature extraction techniques (e.g., color histograms, SIFT, HOG features, or deep learning embeddings). Assess algorithm selection appropriateness for image search. Deduct 5 points if only basic pixel comparison is used, 3 points if advanced features are implemented but inefficiently. Give full 10 points for optimized, industry-standard feature extraction.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is there an efficient image matching/similarity calculation mechanism?",
-      "description": "Evaluate the implementation of similarity metrics (e.g., cosine similarity, Euclidean distance) and optimization techniques for fast comparison. Check if indexing is used for large datasets. Deduct 5 points if brute-force comparison is used on large datasets, 3 points if metrics are implemented but without optimization. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there a well-designed search results display and user interface?",
-      "description": "Assess if the search results are clearly displayed with relevant information (similarity score, metadata), pagination if needed, and sorting options. Check for interactive previews and result filtering capabilities. Deduct 5 points for basic list display without visual thumbnails, 3 points if results lack metadata or sorting. Give 10 points for comprehensive, user-friendly result presentation.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid images, network failures, memory constraints with large datasets, 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 visual feedback during search 2. Content-based filtering options 3. Interactive image editing before search). 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 image processing functions 2. Feature modules unrelated to image search (e.g., a built-in social media sharing system) 3. Computationally expensive visualizations that affect performance. 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 image processing/feature extraction/search/UI layers), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional image display techniques (proper thumbnails, responsive galleries). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for poor image rendering quality. 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) Search feedback delay ≤ 500ms or progress indicator for longer searches 2) Smooth transitions when displaying results 3) Clear visual guidance during the image upload and search process. Deduct 5 points for searches without progress indication, 3 points for jerky transitions between search states, and 5 points for unintuitive image upload interfaces. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Automation",
-  "difficulty": "easy"
-}

package/library/utility_tools-automation/implement-automatic-backup-tool.json

@@ -1,68 +0,0 @@
-{
-  "index": 650,
-  "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 when possible. Implement an automatic backup tool that allows users to select data they need to back up (such as notes, task lists, etc.), and regularly save the data to local or cloud storage, providing recovery and version management functions.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the backup source selection mechanism properly implemented?",
-      "description": "Evaluate whether the code implements a flexible selection mechanism that allows users to choose specific data types (notes, tasks, etc.) or files for backup, with proper file system permissions handling. Score 0 if selection functionality is missing, 5 if basic file selection is implemented, and 10 if the implementation includes advanced features like wildcards, exclusion rules, and metadata-based filtering.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the backup scheduling system fully functional?",
-      "description": "Check whether the tool implements configurable backup scheduling with options for frequency (hourly, daily, weekly), specific times, and event-triggered backups. Deduct 3 points if the scheduling is hardcoded, 5 points if it lacks persistence across system restarts, and 5 points if it doesn't handle missed backup windows. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the backup storage mechanism properly designed?",
-      "description": "Assess whether the tool provides both local and cloud storage options with proper authentication, encryption, and storage optimization. Check for incremental backup capability to save space and bandwidth. Deduct 5 points if only one storage type is supported, 3 points if data is not encrypted, and 3 points if no compression or deduplication is implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are version management and recovery features comprehensive?",
-      "description": "Evaluate whether the tool implements a clear version history, point-in-time recovery capabilities, and efficient version pruning mechanisms. Check for features like version browsing, comparison, and selective restoration. Deduct 5 points if only full restores are possible, 3 points if version metadata is incomplete, and 5 points if there's no conflict resolution for multi-device scenarios. 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, permission issues, storage limitations, corrupted backups, 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. AI-powered selective backup suggestions 2. Cross-device sync capabilities 3. Content-aware backup prioritization). 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 backup methods 2. Function modules unrelated to data backup/recovery (e.g., a built-in media player) 3. Fancy effects that affect performance (e.g., unnecessary animations during backup). 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 backup logic/UI/storage layers), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Backup progress indicators with accurate time estimation 2) Non-blocking UI during backup operations 3) Clear visual feedback for completed/failed backups. Deduct 5 points for operations without feedback, 3 points for UI freezes during backups, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Automation",
-  "difficulty": "hard"
-}

package/library/utility_tools-automation/implement-fabricjs-mobile-h5-application.json

@@ -1,68 +0,0 @@
-{
-  "index": 1635,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable and presentable when possible. Functional goal: Implement a mobile H5 application based on Fabric.js JSON data for template replacement. Users only need to upload images, text, prices, and other content, and use Fabric.js to generate images for user download. The application should include canvas controls such as layer adjustment, font color, etc.\n\nTechnology stack: Vue3 + wot-design-uni component library.\nSpecial requirements: Mobile adaptation, embedded in a mini program.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Fabric.js template replacement system fully implemented?",
-      "description": "Review whether the code accurately implements the Fabric.js template system with proper loading/parsing of JSON templates and handling of object replacements (images, text, prices). Score 0 if the core template replacement is not implemented, 5 if basic replacement works but has limitations, and 10 if the system handles all replacement types with proper validation and error handling.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the canvas editing controls comprehensive and functional?",
-      "description": "Evaluate the implementation of canvas controls including layer adjustment, font styling (color, size, family), object positioning, scaling, and rotation. Deduct 2 points for each missing essential control (layer management, text editing, image manipulation). The implementation should use Fabric.js APIs correctly and maintain object states properly. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the mobile adaptation properly implemented?",
-      "description": "Check whether the application is properly adapted for mobile devices with responsive canvas sizing, touch interactions (pinch zoom, drag, etc.), and appropriate UI scaling. Verify that the canvas maintains proper aspect ratios across different screen sizes. Deduct 5 points if the canvas is not responsive, 3 points if touch gestures are not properly handled. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the mini-program embedding integration fully functional?",
-      "description": "Assess the integration with mini-program environments, including proper handling of context, lifecycle hooks, and platform-specific APIs. Check if the application handles permissions correctly (file system access, image picking) and manages state persistence within the mini-program context. Deduct 5 points if platform-specific adaptations are missing, 3 points if there are compatibility issues. 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 JSON templates, failed image loading, network interruptions, memory constraints on mobile devices) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should 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 preview while editing 2. One-click social sharing with custom thumbnails 3. Smart object alignment guides). 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 image upload methods coexisting) 2. Function modules unrelated to the template editing (e.g., unnecessary animations) 3. Resource-heavy features that affect mobile performance. 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 Fabric.js canvas logic from Vue components), component reusability, and build process optimization for mini-program environments. Deduct 5 points if global state management is poorly implemented; deduct 5 points if the code doesn't follow Vue 3 composition API best practices; deduct 5 points if there's no performance optimization for mobile devices. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the UI follows the wot-design-uni design system consistently: 1) Proper component usage without custom overrides that break design consistency 2) Mobile-first layout with appropriate touch targets (minimum 44×44px) 3) Professional typography system respecting the component library's defaults. Deduct 3 points for each UI inconsistency, 5 points for poor information hierarchy, and 5 points for illegible text on mobile screens. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects are optimized for mobile: 1) Canvas rendering maintains 60fps during manipulation 2) Image loading and processing includes loading states and optimization 3) Clear visual indicators during export/download process. Deduct 5 points for each interaction with noticeable lag, 3 points for missing loading indicators, and 5 points for unresponsive UI during heavy operations like image processing. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Automation",
-  "difficulty": "medium"
-}

package/library/utility_tools-automation/implement-ssh-terminal-tauri-vue3-xterm.json

@@ -1,68 +0,0 @@
-{
-  "index": 709,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure the generated code is executable for demonstration. How can I use Xterm.js to implement a terminal for Vue and Gin projects—connecting to a remote server and controlling it? Please provide me with complete code (as fully functional as possible).",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Xterm.js integration with Vue.js correctly implemented?",
-      "description": "Check whether the Xterm.js terminal is properly initialized in a Vue component with essential options (cursorBlink, fontSize, theme configuration). Verify event handling setup for terminal input/output. Score 0 if terminal isn't functional, 5 if basic terminal display works but lacks essential options, and 10 if the terminal is fully configured with proper lifecycle management (mounted/destroyed hooks, resize handling).",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the WebSocket connection to the Gin backend properly implemented?",
-      "description": "Evaluate the WebSocket connection implementation between Vue frontend and Gin backend, including connection establishment, message handling, and error handling. Connection must include authentication mechanism and reconnection strategy. Deduct 5 points if authentication is missing, 3 points if reconnection strategy is incomplete, and 2 points if there's no connection status indicator. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the Gin backend properly handling terminal sessions?",
-      "description": "Review the Gin backend implementation for terminal sessions, including session creation/management, command execution, and output streaming. Check for TTY allocation, proper environment variables setting, and signal handling (SIGINT, SIGTERM). Deduct 5 points if process management is incomplete, 3 points if session persistence isn't implemented, and 5 points if security measures are inadequate. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the SSH/remote terminal connection properly implemented?",
-      "description": "Assess the implementation of SSH/remote terminal connection, including authentication methods (password, key-based), session management, and terminal resizing capabilities. Verify proper handling of different shell environments and terminal types. Deduct 5 points if authentication options are limited, 3 points if terminal resize isn't handled, and 5 points if connection state management is missing. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (network disconnection, authentication failures, server errors, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should effectively handle edge cases like connection timeouts, unexpected terminal exits, and concurrent users, 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. Terminal session recording/playback 2. Split terminal functionality 3. Command history with search 4. Syntax highlighting for common commands 5. Auto-completion). 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 connect to a server) 2. Function modules unrelated to terminal functionality (e.g., a built-in file manager when not needed) 3. Fancy effects that affect performance (e.g., excessive animations in the terminal UI). 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 (separating terminal logic/UI/network layers), clear component structure, code comments, and error handling. Deduct 5 points if global state management is misused; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no proper error logging system. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface design meet professional terminal standards?",
-      "description": "Evaluate whether the terminal interface follows professional design principles: 1) Proper color scheme with good contrast 2) Monospace font with appropriate size and line height 3) Clear cursor visibility and blinking options 4) Responsive design that adapts to container size. Deduct 3 points for poor text readability, 5 points for a cluttered interface with unnecessary elements, and 5 points for non-responsive terminal dimensions. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the terminal interaction smooth and responsive?",
-      "description": "Judge whether the terminal interaction conforms to expected behavior: 1) Input latency ≤ 100ms 2) Smooth scrolling without flickering 3) Proper handling of keyboard shortcuts and special keys (Ctrl+C, arrow keys, Tab). Deduct 5 points for noticeable input lag, 3 points for rendering issues during rapid output, and 5 points for incorrect handling of special keys or key combinations. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Hardware Management",
-  "difficulty": "hard"
-}

package/library/utility_tools-automation/javascript-search-autocomplete-chinese-pinyin-english.json

@@ -1,68 +0,0 @@
-{
-  "index": 896,
-  "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 whenever possible. Please use JavaScript to implement a search autocomplete system that can recognize Chinese characters, Pinyin, and English.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Chinese character recognition and search functionality fully implemented?",
-      "description": "Review whether the code accurately implements Chinese character matching, including full character matching, partial character matching, and radical-based search. Check if it supports traditional and simplified Chinese conversion, and handles polyphone characters correctly. Score 0 if basic Chinese recognition is missing, 5 if only simple character matching is implemented, and 10 if comprehensive Chinese character processing including stroke order and radical recognition is fully supported.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the Pinyin input recognition system comprehensively implemented?",
-      "description": "Evaluate whether the Pinyin recognition includes tone handling (with and without tone marks), fuzzy Pinyin matching (zh/z, ch/c, sh/s confusion), and initial letter abbreviation search. Check if it supports both full Pinyin and abbreviated Pinyin input modes. Deduct 5 points if tone-insensitive matching is missing, and 3 points if fuzzy matching for common Pinyin confusions is not handled. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the multilingual mixed search capability properly designed?",
-      "description": "Check whether the system can handle mixed input of Chinese, Pinyin, and English simultaneously within a single search query. Evaluate the accuracy of language detection and switching algorithms, and whether cross-language matching is supported (e.g., English keywords matching Chinese results). Deduct 5 points if language switching has noticeable delays, and 3 points if mixed input causes search conflicts. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the autocomplete suggestion algorithm optimized for performance?",
-      "description": "Review whether the autocomplete system implements efficient data structures like Trie trees or similar for fast prefix matching, includes debouncing mechanisms for user input, and provides ranked suggestions based on relevance and frequency. Check if caching strategies are implemented for common queries. Deduct 5 points if response time exceeds 200ms for typical queries, and 5 points if no input optimization techniques are used. Give 10 points if fully optimized.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid Unicode characters, mixed encoding input, network timeouts, malformed search queries, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should effectively handle edge cases like empty inputs, extremely long queries, and special characters, 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 search experience (e.g., 1. Voice input with speech-to-text for Chinese/English 2. Smart typo correction and suggestion 3. Semantic search with context understanding 4. Historical search pattern learning). 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 search algorithms (e.g., multiple Pinyin conversion libraries coexisting) 2. Function modules unrelated to search autocomplete (e.g., built-in translation services) 3. Fancy effects that affect search performance (e.g., heavy animations during typing). Deduct 3 points for each redundancy found, and directly deduct 10 points if core search 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 search logic/data processing/UI layers), unit test coverage for different language inputs, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if 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 design meet professional standards?",
-      "description": "Evaluate whether the search interface follows modern design principles: 1) Harmonious color matching with proper contrast ratios for text readability 2) Appropriate dropdown suggestion spacing (minimum 44px touch targets) 3) Professional typography supporting multilingual display (proper font fallbacks for Chinese characters). Deduct 3 points for each crowded visual element, 5 points for poor text legibility in suggestions, and 5 points for inconsistent multilingual text alignment. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the search interaction smooth and responsive?",
-      "description": "Judge whether the search experience meets usability standards: 1) Input response delay ≤ 100ms 2) Suggestion dropdown appears within 200ms 3) Smooth keyboard navigation (arrow keys, enter, escape) 4) Clear visual feedback for selection states. Deduct 5 points for each laggy interaction, 3 points for missing keyboard accessibility, and 5 points for unclear selection indicators. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Automation",
-  "difficulty": "medium"
-}

package/library/utility_tools-automation/mini-program-auto-extract-geo-coordinates-from-screenshots.json

@@ -1,68 +0,0 @@
-{
-  "index": 954,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you provide is executable for demonstration purposes. I am a programming novice. How can I create a mini-program that automatically extracts precise latitude and longitude coordinates from uploaded location screenshots? Please automatically generate the code for me and provide detailed step-by-step instructions.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the image processing and OCR functionality properly implemented?",
-      "description": "Evaluate whether the code includes robust image processing capabilities (like OpenCV) to handle various screenshot formats and OCR library integration (like Tesseract) to extract text from images. Check if preprocessing steps like image resizing, normalization, and noise reduction are included. Score 0 if image processing is absent, 5 if basic functionality exists but handles limited formats, and 10 if comprehensive processing with format validation is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the coordinate extraction logic comprehensive and accurate?",
-      "description": "Check whether the code can recognize different coordinate formats (decimal degrees, DMS, UTM) and extract them accurately using regex patterns or other text analysis methods. Verify if the implementation can handle different map service screenshots (Google Maps, Apple Maps, etc.). Deduct 5 points if only one coordinate format is supported, 3 points if extraction accuracy is below 90%. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the user interface intuitive and beginner-friendly?",
-      "description": "Assess whether the interface provides clear upload mechanisms, progress indicators, and result displays appropriate for a programming novice. Check if there are visual cues for successful/failed operations. Deduct 5 points if the interface requires coding knowledge to operate, 3 points if feedback on processing status is unclear. Give 10 points if the interface is completely self-explanatory.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are there validation and error handling mechanisms for coordinate extraction?",
-      "description": "Evaluate whether the code validates extracted coordinates (checking range: latitude -90 to 90, longitude -180 to 180) and provides meaningful error messages for images without coordinates or with unreadable text. Look for fallback mechanisms when primary extraction fails. Deduct 5 points if validation is absent, 3 points if error messages are generic or unhelpful. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as corrupted images, wrong file types, extraction 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. Automatic map service detection 2. Reverse geocoding to show address from coordinates 3. Batch processing multiple screenshots). 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 OCR engines doing the same job) 2. Function modules unrelated to coordinate extraction (e.g., a built-in image editor) 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/processing/validation logic), 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 dependencies are not properly managed. 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) Processing feedback delay ≤ 2 seconds for standard images 2) Clear progress indicators for longer operations 3) Intuitive drag-and-drop or file selection interfaces. Deduct 5 points for each operation without feedback, 3 points for processing times over 5 seconds without indicators, and 5 points for confusing upload or download mechanisms. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Automation",
-  "difficulty": "medium"
-}

package/library/utility_tools-automation/monitor-chext-transactions-mobile.json

@@ -1,68 +0,0 @@
-{
-  "index": 1422,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate, professional responses. Take care to ensure the code you produce is executable when displayed. Write a program that can monitor in real-time single transactions equal to 300,000 shares (3,000 lots) on the ChiNext (Growth Enterprise Market) board stocks on mobile phones, excluding ST stocks.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the real-time stock monitoring system properly implemented?",
-      "description": "Review whether the code accurately implements a real-time monitoring system that tracks ChiNext board stocks with transactions of exactly 300,000 shares (3,000 lots), with proper filtering for ST stocks. The implementation should include data retrieval, filtering logic, and appropriate triggers when conditions are met. Score 0 if core monitoring logic is missing, 5 if basic monitoring is implemented but with deficiencies, and 10 if all requirements are fully satisfied with efficient algorithms.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the data source connection and real-time updates properly handled?",
-      "description": "Check whether the implementation connects to a reliable stock market data feed (like an API from a financial data provider), handles connection management, implements proper polling or WebSocket for real-time updates, and includes error handling for connection issues. Deduct 5 points if data retrieval is not real-time or lacks reliability mechanisms, and 3 points if error handling for network issues is insufficient. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the ChiNext board filtering and ST stock exclusion properly implemented?",
-      "description": "Evaluate whether the code correctly identifies ChiNext board stocks (usually by stock code prefix or through API parameters) and properly filters out ST stocks. The implementation should account for changes in stock status and maintain an updated list. Deduct 5 points if the ChiNext filtering is inaccurate, and 5 points if ST stock exclusion logic is missing or flawed. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the 300,000 shares (3,000 lots) transaction detection accurate?",
-      "description": "Check if the code precisely detects single transactions equal to exactly 300,000 shares, not aggregated multiple smaller transactions. The implementation should distinguish between normal trading volume and the specific transaction size being monitored. Deduct 5 points if the detection cannot differentiate between single large transactions and accumulated volume, and 5 points if the volume calculation contains errors or ambiguities. 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 market data delays, API failures, irregular trading hours, trading halts, etc.) and provides friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Historical pattern analysis of 300,000-share transactions 2. Auto-correlation with news events when large transactions occur 3. Visual heatmaps of transaction frequency by stock). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple notification systems) 2. Function modules unrelated to stock monitoring (e.g., a built-in general news reader) 3. Fancy effects that affect performance (e.g., excessive animations that drain battery). 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 retrieval/processing/notification layers), unit test coverage, and mobile-specific optimizations for battery and data usage. 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 mobile-specific optimizations are missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the mobile interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern mobile design principles: 1) Harmonious color matching suitable for financial applications (no more than 3 primary colors) 2) Proper layout spacing for touch targets (at least 44x44pt) 3) Professional font system (body font size ≥ 16px for readability). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for poorly organized data presentation. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the mobile notification and alert system effective?",
-      "description": "Judge whether the alert system for detected transactions is properly implemented for mobile: 1) Immediate push notifications when transactions are detected 2) Configurable alert sounds/vibrations 3) Background operation capability with battery optimization. Deduct 5 points for notifications with >5 second delay, 3 points for lack of configuration options, and 5 points for excessive battery drain in background mode. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Automation",
-  "difficulty": "hard"
-}