@getollie/cli 0.0.4 → 0.2.0

package/library/utility_tools-calculation_tools/used-car-value-assessment-template-uniapp-frontend.json

@@ -1,68 +0,0 @@
-{
-  "index": 1355,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code whenever possible. Used car value assessment template for uniapp frontend.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is a complete car value assessment form implemented?",
-      "description": "Check whether the code implements a comprehensive form for collecting essential car data (make, model, year, mileage, condition). The form should include proper validation with real-time feedback. Score 0 if the core form is missing, 5 if basic fields are implemented but lack validation, and 10 if a complete form with validation and field dependencies (e.g., model options changing based on selected make) is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the car value calculation algorithm implemented correctly?",
-      "description": "Evaluate whether the code includes a reasonable valuation algorithm that considers multiple factors (age depreciation, mileage impact, condition multipliers, market trends). Deduct 5 points if only basic linear depreciation is used. Deduct 3 points if market adjustments are missing. The algorithm should be well-commented and account for edge cases (very old/new cars, extremely low/high mileage). Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are uniapp-specific components and APIs utilized properly?",
-      "description": "Review whether the implementation properly utilizes uniapp components and APIs (uni-form, uni-picker, uni-popup) instead of generic HTML elements. Check for proper cross-platform adaptations and lifecycle hooks. Deduct 5 points if platform-specific code is not properly conditioned. Deduct 3 points if uniapp's built-in navigation isn't utilized. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is data persistence and state management implemented?",
-      "description": "Check if the code implements proper data persistence (uni.setStorage/getStorage) for saving assessment history and user preferences. Evaluate whether a state management solution is used for complex state (Vuex/Pinia). Deduct 5 points if offline mode isn't supported, 3 points if there's no way to retrieve previous assessments. 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 interruption, invalid input, API 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. Camera integration for car damage detection 2. VIN scanner for automatic car identification 3. Market comparison visualization). 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 validation systems) 2. Function modules unrelated to car assessment (e.g., unnecessary social sharing features) 3. Fancy effects that affect performance (e.g., heavy animations on value display). 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/API services), unit test coverage, and build process 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 configuration for different environments (development/production). 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 mobile design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (responsive to different device sizes) 3) Professional font system (readable font sizes, clear hierarchy). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic form 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 mobile interaction standards: 1) Form submission feedback ≤ 100ms 2) Smooth transitions between steps in the assessment process 3) Clear visual cues for required fields and validation errors. Deduct 5 points for each operation without feedback, 3 points for jarring transitions between assessment stages, and 5 points for hard-to-access primary functions. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Calculation Tools",
-  "difficulty": "easy"
-}

package/library/utility_tools-calculation_tools/vite-vue-bazi-calculator-gregorian-lunar.json

@@ -1,68 +0,0 @@
-{
-  "index": 712,
-  "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. Create a project for calculating Bazi (Chinese Eight Characters) using Vite+Vue, where users can input either Gregorian or Lunar calendar year, month, day, and hour.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Bazi calculation core algorithm correctly implemented?",
-      "description": "Review whether the code correctly implements the Chinese calendar conversion and Bazi calculation logic. Check if it accurately derives the Year, Month, Day, and Hour pillars with their respective Heavenly Stems and Earthly Branches. Score 0 if the core calculation is incorrect, 5 if only basic conversion is implemented without considering special cases (leap months), and 10 if all aspects including special cases are handled correctly.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Does the application correctly handle both Gregorian and Lunar calendar inputs?",
-      "description": "Evaluate whether the application can accurately convert between Gregorian and Lunar calendars. Check if leap months in the Lunar calendar are properly handled, and if the conversion maintains date integrity across both calendar systems. Deduct 5 points if leap month handling is missing, 3 points if time zone considerations are absent. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the input validation system comprehensive and user-friendly?",
-      "description": "Check whether the code implements comprehensive validation for user inputs (year range limitations, valid date checks). Error messages should be clear and helpful. Deduct 3 points if validation only occurs after form submission rather than real-time, 3 points if error messages are generic/unclear, and 5 points if critical validation is missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the application present the Bazi results in a traditional and visually appropriate format?",
-      "description": "Evaluate whether the Bazi results are presented in the traditional vertical column format or another culturally appropriate arrangement. Check if the Five Elements associations are correctly displayed for each pillar. Deduct 5 points if the display format doesn't follow cultural conventions, 3 points if Five Elements are missing or incorrect. 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 out-of-range dates, invalid inputs, edge cases around midnight or lunar calendar boundaries) 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. Visual representation of the Five Elements balance 2. Compatibility analysis between different Bazi charts 3. Auspicious timing recommendations based on the chart). 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 calendar conversion algorithms 2. Function modules unrelated to Bazi calculation (e.g., unrelated fortune telling features) 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 calculation logic/view/data layers), unit test coverage for the calendar conversion algorithms, 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 properly configured for Vite+Vue. 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 both modern design principles and traditional Chinese aesthetic elements: 1) Harmonious color matching (traditional Chinese color schemes) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Appropriate typography (readability of Chinese characters prioritized). Deduct 3 points for each crowded visual element, 5 points for a jarring color combination, and 5 points for poor Chinese character rendering. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance when switching between calendar systems. Deduct 5 points for each operation without feedback, 3 points for visual after-images during transitions, and 5 points for hard-to-find calendar toggle functions. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Calculation Tools",
-  "difficulty": "hard"
-}

package/library/utility_tools-calculation_tools/webpage-geographic-to-gauss-coordinates-cgcs2000.json

@@ -1,68 +0,0 @@
-{
-  "index": 1749,
-  "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. Help me create a webpage that converts geographic coordinates in degrees to Gauss coordinates, referencing China's CGCS2000 system.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the coordinate conversion system accurately implemented?",
-      "description": "Review whether the JavaScript code correctly implements the mathematical formulas for converting geographic coordinates (latitude, longitude) to Gauss-Krüger projection coordinates in the CGCS2000 system. Check the implementation of key formulas including meridian arc length calculation, curvature radius calculation, and the specific transformation constants for CGCS2000. Score 0 if core conversion formulas are missing, 5 if basic conversion is implemented but with mathematical errors, and 10 if the conversion fully conforms to the CGCS2000 national standard.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the specific parameters of the CGCS2000 system correctly configured?",
-      "description": "Evaluate whether the code correctly specifies CGCS2000 parameters including semi-major axis (a=6378137m), flattening (f=1/298.257222101), central meridian selection logic, and projection zone handling (3° or 6° zones). Deduct 2 points for each incorrect parameter, 5 points if the ellipsoid parameters are wrong, and 3 points if zone calculation is improperly handled. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the input validation and error handling complete?",
-      "description": "Check whether the code validates input coordinates (latitude: -90° to 90°, longitude: -180° to 180°), handles edge cases like polar regions, and provides clear error messages. Deduct 3 points for missing boundary checks, 5 points if invalid inputs crash the application, and 2 points if error messages are unclear. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the implementation include reverse conversion (Gauss to geographic coordinates)?",
-      "description": "Evaluate whether the code includes the inverse transformation from Gauss coordinates back to geographic coordinates, allowing for bidirectional conversion. Check the implementation of the iterative algorithm typically needed for this reverse process. Score 0 if reverse conversion is not implemented, 5 if it's implemented but with significant precision issues, and 10 if it correctly implements the reverse calculation with proper convergence criteria.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (invalid coordinates, non-numeric inputs, extreme values, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should prevent calculation errors and handle edge cases effectively. Give 10 points for comprehensive error handling, 5 points for basic validation, and 0 points if no exception handling exists.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes useful additional features that enhance functionality (e.g., 1. Visualization of the converted points on a map, 2. Batch conversion capability for multiple coordinates, 3. Supporting different projection zones/central meridians, 4. History of recent conversions). 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 calculation functions, 2. Function modules unrelated to coordinate conversion (e.g., unnecessary animation effects), 3. Computationally expensive features that affect performance. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core conversion 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 calculation logic from UI), code organization, documentation quality, and maintainability. Deduct 5 points if global variables are excessively used; deduct 5 points if the code lacks comments explaining the mathematical formulas; deduct 5 points if floating-point precision issues are not addressed. 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 form design with clear input/output sections. Deduct 3 points for each poorly arranged form element, 5 points for confusing input/output areas, and 5 points for illegible text or poor contrast. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the user interaction intuitive and responsive?",
-      "description": "Judge whether the interface provides clear guidance on input format requirements, immediate feedback on conversion results, and appropriate precision display options. Deduct 5 points if coordinate input format is unclear, 3 points if conversion requires multiple unnecessary clicks, and 5 points if results are displayed without proper formatting or units. Check that conversion happens within 100ms of user input completion. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Calculation Tools",
-  "difficulty": "easy"
-}

package/library/utility_tools-calculation_tools/wechat-mini-program-calculator-code.json

@@ -1,68 +0,0 @@
-{
-  "index": 1184,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code where possible. WeChat Mini Program practical calculator code",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the basic calculator functionality fully implemented?",
-      "description": "Review whether the calculator correctly implements all basic arithmetic operations (addition, subtraction, multiplication, division) with proper precedence handling. Score 0 if the core calculation logic is missing, 5 if only basic operations work but have errors with complex expressions, and 10 if all operations including parentheses and order of operations are correctly handled.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are advanced calculator features included?",
-      "description": "Check whether the code includes scientific calculator functions (e.g., trigonometric functions, logarithms, powers, roots) and memory functions (MC, MR, M+, M-). Deduct 3 points if scientific functions are missing, 2 points if memory functions are absent, and 5 points if both are missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the WeChat Mini Program architecture properly implemented?",
-      "description": "Evaluate whether the code follows WeChat Mini Program best practices with proper separation of app.js, page js files, WXML templates, and WXSS styles. Check for correct use of Page() and App() constructors, lifecycle hooks, and the global getApp() when needed. Deduct 5 points if the architecture doesn't follow Mini Program conventions and 5 points if the page rendering lifecycle is not handled correctly. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the calculator handle computation history and state persistence?",
-      "description": "Assess whether the calculator saves computation history, allows review of previous calculations, and persists state across Mini Program restarts using wx.setStorageSync/wx.getStorageSync. Deduct 3 points if history is not implemented, 4 points if persistence across sessions is missing, and 3 points if there's no way to clear history. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common calculator edge cases (division by zero, overflow/underflow, extremely large numbers, precision issues with floating-point operations) and provides friendly error prompts. Code with strong robustness should validate all user inputs and gracefully handle all 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. Voice input for calculations 2. Currency/unit conversion 3. Customizable themes or layouts 4. Formula visualization). 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 calculation engines) 2. Function modules unrelated to a calculator (e.g., a built-in game) 3. Fancy effects that affect performance (e.g., excessive animations that slow down calculations). 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 calculation logic/view/utilities), error handling strategies, and code organization. Deduct 5 points if global state is poorly managed; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no clear separation of concerns between UI and business logic. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the calculator UI follows WeChat design guidelines: 1) Harmonious color matching matching with WeChat's aesthetic 2) Proper button sizing and spacing (easy touch targets ≥ 44pt) 3) Professional typography with clear number display (result font size ≥ 18px). Deduct 3 points for cluttered button layout, 5 points for poor contrast that affects readability, and 5 points for inconsistent button sizes or awkward alignments. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the calculator provides appropriate feedback: 1) Button press visual feedback ≤ 100ms 2) Calculation results appear instantly 3) Clear haptic feedback for key operations using wx.vibrateShort(). Deduct 5 points for operations without feedback, 3 points for delayed calculation results, and 5 points for lack of visual indication of the current operation. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Calculation Tools",
-  "difficulty": "easy"
-}

package/library/utility_tools-daily_office_tasks/add-lunar-holidays-perpetual-calendar.json

@@ -1,68 +0,0 @@
-{
-  "index": 1656,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable and functional. Add lunar holidays and integrate them to create a perpetual calendar code.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the perpetual calendar core functionality fully implemented?",
-      "description": "Review whether the code accurately implements a perpetual calendar system that displays dates correctly across all years (past and future). Check that it properly handles leap years, month lengths, and weekday calculations. Score 0 if the core calendar logic is incorrect, 5 if basic functionality works but with edge case errors, and 10 if the calendar works flawlessly for any arbitrary date.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the lunar holiday integration complete and accurate?",
-      "description": "Evaluate the implementation of lunar holiday calculations. The code should accurately convert between Gregorian and lunar calendars and correctly identify lunar holidays. Verify the accuracy of the lunar date algorithm across different years. Deduct 5 points if the lunar calendar conversion has inaccuracies, 3 points if only major lunar holidays are included, and 2 points if regional lunar holidays are missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are the solar (Gregorian) holidays properly implemented?",
-      "description": "Check whether the code includes major international and regional solar holidays, with proper handling of holidays that fall on specific weekdays (like 'First Monday of September'). Verify that the code handles holidays that change dates annually. Deduct 3 points if only fixed-date holidays are supported, 2 points if movable holidays are missing, and 5 points if holiday categorization is absent. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there a comprehensive date navigation and search system?",
-      "description": "Assess the calendar's navigation capabilities, including the ability to jump between years/months, search for specific dates or holidays, and bookmark significant dates. Verify that users can easily find dates of interest through intuitive controls. Deduct 5 points if year/month navigation is cumbersome, 3 points if holiday search functionality is missing, and 2 points if there's no direct date input option. 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 dates, out-of-range years, unsupported locales, 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. Multi-cultural calendar systems integration 2. Historical event integration for significant dates 3. Personalized reminder system for recurring events). 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 date calculation algorithms 2. Function modules unrelated to calendar functionality (e.g., non-date-related widgets) 3. Unnecessarily complex 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 calendar logic/view/data layers), unit test coverage for date calculations, and appropriate data structures for holiday storage. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no separation between the calendar engine and the UI. 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 calendar design principles: 1) Clear visual hierarchy between months, weeks, and days 2) Proper differentiation of weekdays, weekends, and holidays 3) Professional color-coding system for different types of holidays. Deduct 3 points for cluttered date displays, 5 points for poor holiday highlighting, and 5 points for inconsistent date cell sizing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the calendar interactions conform to user expectations: 1) Month/year switching transitions under 300ms 2) Immediate visual feedback when selecting dates 3) Smooth hover states for interactive elements. Deduct 5 points for laggy month transitions, 3 points for delayed holiday information display, and 5 points for unresponsive date selection. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Daily Office Tasks",
-  "difficulty": "hard"
-}

package/library/utility_tools-daily_office_tasks/ant-design-vue-excel-import-export-table.json

@@ -1,68 +0,0 @@
-{
-  "index": 262,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Make sure that the generated code is executable for demonstration purposes. Please write an import and export function with Ant Design Vue, requiring that when the import button is clicked, data from an Excel file will be imported into an <a-table> data table.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the import and export functionality fully implemented?",
-      "description": "Check if the code implements both import and export functions. Import should correctly parse Excel data and populate the table; export should generate a downloadable Excel file from table data. Score 0 if neither function works, 5 if only one direction works correctly, and 10 if bidirectional functionality is complete with proper file handling.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the Excel parsing implementation correct and robust?",
-      "description": "Evaluate if the code uses proper libraries (like SheetJS/xlsx) to handle Excel files. Check if it handles different Excel formats (.xls, .xlsx), sheet selection, handles headers correctly, and supports various data types (text, numbers, dates). Deduct 3 points if only basic data types are supported, 5 points if it fails with large files (>1MB), and 3 points if encoding issues aren't handled.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the Ant Design <a-table> integration properly implemented?",
-      "description": "Check if the table component is correctly initialized with dynamic columns based on imported data, if pagination works, if sorting/filtering is preserved during import/export, and if the table UI updates properly after import. Deduct 5 points if column mapping is hardcoded, 3 points if the table doesn't visually refresh after import, and 5 points if no loading state is displayed during operations.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there appropriate user feedback during the import/export process?",
-      "description": "Verify if the code includes loading indicators, progress feedback, success/error notifications, and validation results display. Check if the user is warned about data loss when replacing existing table data. Deduct 5 points if no progress indication exists for large files, 3 points if error messages are generic/unhelpful, and 5 points if validation failures are not clearly highlighted.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid file formats, incomplete data, empty files, special characters in data) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Preview before import 2. Column mapping UI 3. Data validation with highlighting 4. Template download option). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant libraries for the same purpose (e.g., multiple Excel parsing libraries) 2. Function modules unrelated to import/export (e.g., unnecessary filters) 3. Overly complex implementations that could be simplified. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating UI/logic/service layers), error handling patterns, and reusability. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there are no comments for complex logic. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows Ant Design principles: 1) Consistent with Ant Design styles 2) Proper button placement and hierarchy 3) Clear visual feedback for states (idle, loading, success, error). Deduct 3 points for each UI element that breaks from Ant Design guidelines, 5 points for inconsistent visual style, and 5 points for poor information hierarchy. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Clear indication when file selection is in progress 2) Smooth transition when data loads into table 3) Appropriate animation for success/error states. Deduct 5 points for each operation without feedback, 3 points for jarring transitions between states, and 5 points if the import/export buttons are not disabled during processing to prevent multiple submissions. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Daily Office Tasks",
-  "difficulty": "hard"
-}

package/library/utility_tools-daily_office_tasks/app-with-work-items-tasks-pomodoro-timer.json

@@ -1,68 +0,0 @@
-{
-  "index": 773,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code whenever possible. I want to create an APP that includes work item categorization, task lists, and a Pomodoro timer. What APP integration platform should I use, and can you provide the complete programming code?",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the work item categorization system properly implemented?",
-      "description": "Evaluate whether the code implements a comprehensive categorization system that allows for hierarchical organization (projects > categories > tasks), tag-based filtering, and priority assignment. Check if it includes data validation for category creation/editing and proper handling of category deletion (including orphaned tasks). Score 0 if categorization is absent, 5 if basic categorization exists, and 10 if advanced features like custom fields or category-based analytics are implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the task list functionality complete and intuitive?",
-      "description": "Examine the task list implementation for core features like task creation, editing, deletion, status tracking, due dates, reminders, and sorting/filtering options. Check if the code handles task dependencies, recurring tasks, and progress tracking. Deduct 5 points if basic CRUD operations are missing, and 3 points if there's no offline data persistence. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the Pomodoro timer properly implemented with standard features?",
-      "description": "Review the Pomodoro timer code for accurate time tracking, configurable work/break intervals, audio notifications, and session counting. Check if it handles background execution and device sleep modes correctly. Deduct 5 points if timer continues running in background without proper notifications, 3 points if customization options are limited, and 5 points if there's no session history. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the integration between components seamless and logical?",
-      "description": "Assess how well the three main components (categorization, task lists, and Pomodoro timer) are integrated. Check if tasks can be associated with timer sessions, if completed pomodoros update task progress, and if the categorization system affects task visibility. Deduct 5 points if components operate in isolation, 3 points if data sharing between components requires manual user intervention. 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 incorrect input data, network interruption, app backgrounding, 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-based task prioritization 2. Visual productivity analytics 3. Social accountability features 4. Voice command support). 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 timer implementations) 2. Function modules unrelated to productivity management 3. Fancy effects that affect performance (e.g., excessive animations that slow down task entry). 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 business logic/UI/data persistence layers), 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-Daily Office Tasks",
-  "difficulty": "medium"
-}

package/library/utility_tools-daily_office_tasks/baby-event-event-recorder.json

@@ -1,68 +0,0 @@
-{
-  "index": 1335,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate, professional responses. Be sure the code you generate is executable when presented. Please create a small program that can record baby feeding times, diaper change times, and other similar events.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core baby event tracking functionality fully implemented?",
-      "description": "Review whether the code accurately implements recording of feeding times (including type, duration, amount), diaper changes (including type, severity), and other critical baby care events. Score 0 if the core data entry logic is missing, 5 if only basic event logging is implemented without details, and 10 if comprehensive event tracking with timestamps and detailed parameters is fully included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the data persistence mechanism properly implemented?",
-      "description": "Evaluate whether the application properly stores event data locally or through a backend service. Check for proper data structuring, consistent storage approach (localStorage, IndexedDB, file system, or database), and data retrieval mechanisms. Deduct 5 points if there's no data persistence, 3 points if data is poorly structured or prone to corruption. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Does the application provide adequate data visualization and reporting?",
-      "description": "Check whether the application offers meaningful ways to visualize baby care data (charts, timelines, etc.) and provides reports or summaries of trends. Evaluate if data can be filtered by date ranges and event types. Deduct 5 points if visualization is missing, 3 points if visualizations are present but not useful for parental decision-making. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the multi-caregiver functionality and notification system implemented?",
-      "description": "Assess whether the application supports multiple caregivers (user accounts or profiles) and implements notifications or reminders for scheduled care events. Check for synchronization between caregivers if applicable. Deduct 5 points if multi-caregiver support is missing, and 3 points if notification functionality is absent. 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 input data, network issues if applicable, interrupted operations) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should effectively handle input validation, data type checking, and 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-based insights on baby patterns 2. Integration with smart baby monitors 3. Customizable event categories and fields). 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 log the same event type) 2. Function modules unrelated to baby care tracking (e.g., a built-in general calendar) 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 data/view/controller layers), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast interactions, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Daily Office Tasks",
-  "difficulty": "easy"
-}