@getollie/cli 0.0.4 → 0.2.0

package/library/utility_tools-calculation_tools/network-diagnostic-tool-visual-ping-bandwidth.json

@@ -1,68 +0,0 @@
-{
-  "index": 542,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Try to ensure that the generated code is executable for demonstration.\n\n======== ROLE ========\nYou are an experienced code expert. I am providing you with a software development requirement description. Based on these project requirements, please generate the project code. Strictly follow the rules to help users generate complete project code with simple, easy-to-understand language and thorough comments, without outputting anything else.\n\n======== OUTPUT RULES ========\n1. Always generate complete, runnable project code; ensure the project is fully executable\n2. Make sure all code files you output are complete, don't omit any code\n3. Carefully review and check all code before final output, evaluating its executability. If the code cannot run or contains errors, regenerate it\n4. If the requirements include external API access or user data (images, videos, audio, etc.), please provide mock data\n\n======== PROJECT REQUIREMENTS ========\nDevelop a network diagnostic tool with: 1. Visual Ping route tracing 2. Bandwidth test progress circle 3. Result generation and report sharing 4. Historical record comparison feature 5. Abnormal node map location",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Visual Ping route tracing functionality fully implemented?",
-      "description": "Review whether the code accurately implements a visual ping route tracer with node-by-node path visualization, hop latency metrics, and packet loss indication. Check if the visualization includes an interactive traceroute map showing the network path with proper node representation and connection lines.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the Bandwidth test progress circle properly implemented?",
-      "description": "Evaluate the implementation of the bandwidth test progress circle, checking for proper animation, accurate percentage representation, and real-time updating. The component should visually represent download/upload speeds with a circular progress indicator that fills as the test proceeds.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are the Result generation and report sharing features complete?",
-      "description": "Check whether the code includes functionality to generate comprehensive diagnostic reports with timestamp, ISP information, and network metrics. Verify if sharing options (direct link, PDF export, social media integration) are implemented and functioning correctly.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the Historical record comparison feature implemented effectively?",
-      "description": "Assess whether the code implements functionality to store, retrieve, and compare historical diagnostic results. Check if the comparative visualization effectively highlights differences between tests, showing performance trends over time.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common network diagnostic scenarios (intermittent connections, timeouts, packet loss) and provide helpful error messaging. Check for proper exception handling, retry mechanisms, and graceful degradation when services are unavailable.",
-      "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 diagnostic experience (e.g., 1. Network health scoring system 2. Predictive performance alerts 3. ISP comparison in your area 4. Interactive topology visualization).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Duplicate network testing methods with overlapping results 2. Functionality unrelated to network diagnostics 3. Performance-intensive visualizations that slow down the core functionality.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (separation of network testing logic, data processing, and visualization layers), test coverage for core functions, and build process automation. Check for proper error handling specific to network operations.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the diagnostic tool's UI follows modern dashboard design principles: 1) Clean layout with proper information hierarchy 2) Consistent color scheme for status indicators (red for errors, yellow for warnings, green for normal) 3) Proper data visualization for network metrics with appropriate charts.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the diagnostic tool provides responsive feedback during network operations: 1) Real-time updates during ongoing tests 2) Smooth transitions between test phases 3) Clear progress indicators for long-running operations.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Calculation Tools",
-  "difficulty": "hard"
-}

package/library/utility_tools-calculation_tools/pension-calculator-social-security-personal-contribution.json

@@ -1,68 +0,0 @@
-{
-  "index": 916,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be careful to ensure the code you generate is executable for demonstration. Help me design a pension calculator that can calculate how much retirement pension one can receive based on local social security and personal contribution circumstances.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the pension calculation logic comprehensive and accurate?",
-      "description": "Evaluate whether the code correctly implements all essential pension calculation formulas, including base salary calculation, years of contribution, contribution rates, and inflation adjustments. Score 0 if calculations are missing or incorrect, 5 if basic calculations are present but lack adjustments for different scenarios, and 10 if the implementation handles multiple pension calculation methods with proper documentation of formulas used.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Does the calculator handle various contribution scenarios?",
-      "description": "Check if the calculator accommodates different contribution patterns (regular vs. irregular contributions), career breaks, varying contribution rates over time, and different retirement ages. Deduct 3 points if only constant contribution rates are supported, 3 points if it cannot handle contribution gaps, and 4 points if retirement age flexibility is not implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are regional/national pension system variations supported?",
-      "description": "Assess whether the code includes configurable parameters for different pension systems, tax treatments, and benefit structures across regions. Score 0 if only one fixed system is implemented, 5 if limited parameterization exists, and 10 if the calculator can be easily configured for multiple national/regional pension systems with different rules and formulas.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there future value projection with economic factors?",
-      "description": "Evaluate if the calculator incorporates economic variables like inflation rates, investment returns for personal contributions, and adjustments for cost of living. Deduct 4 points if inflation is not considered, 3 points if investment growth is simplified/missing, and 3 points if there's no sensitivity analysis for different economic 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 negative values, extremely high values, missing inputs, non-numeric inputs, etc.) and provide friendly error prompts or validation 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. Multiple visualization methods for comparing different scenarios 2. Tax optimization suggestions 3. Integration with retirement lifestyle cost calculators). 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 methods 2. Function modules unrelated to pension calculation (e.g., general financial calculators) 3. Unnecessary 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 calculation logic/view/data validation layers), unit test coverage, and documentation quality. 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 explaining complex pension formulas. 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 labels and appropriate validation messages. Deduct 3 points for each crowded input section, 5 points for confusing result displays, and 5 points for poor information hierarchy. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and user-friendly?",
-      "description": "Judge whether the calculator provides an intuitive user experience: 1) Real-time calculation updates without page refresh 2) Clear visualization of how input changes affect pension outcomes 3) Mobile responsiveness for different screen sizes. Deduct 5 points for delayed calculation feedback, 3 points for confusing input mechanisms, and 5 points if results are not displayed in an easily understandable format (e.g., both graphical and numerical). The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Calculation Tools",
-  "difficulty": "hard"
-}

package/library/utility_tools-calculation_tools/production-calculation-calculator-software.json

@@ -1,68 +0,0 @@
-{
-  "index": 1548,
-  "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. Help me create a usable production calculation calculator packaged as software.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the basic calculation functionality implemented correctly?",
-      "description": "Evaluate whether the calculator includes essential production calculation features: input validation, formula parsing, unit conversion, and result formatting. Score 0 if basic arithmetic operations are missing, 5 if only simple calculations are supported, and 10 if comprehensive production formulas (including rate calculations, efficiency metrics, etc.) are implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the software properly packaged for distribution?",
-      "description": "Check if the code includes proper packaging mechanisms (executable generation, installer creation, dependency bundling). Verify if environment-specific configurations are handled, and if cross-platform compatibility is considered where appropriate. Deduct 5 points if the packaging process is manual, 3 points if dependency management is incomplete. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Does the calculator include industry-specific production formulas?",
-      "description": "Assess whether the calculator incorporates specialized production calculations relevant to manufacturing industries (yield calculations, throughput estimations, cycle time computations, etc.). Deduct 5 points if only generic calculations are available without industry context. Score 10 if comprehensive industry-specific formulas are included with appropriate documentation.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there data persistence and export functionality?",
-      "description": "Evaluate if the calculator can save calculation history, user preferences, and custom formulas. Check for export capabilities to common formats (CSV, PDF, etc.) and integration with other systems. Deduct 5 points if saving is limited to session only, and 3 points if export options are restrictive. 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 inputs, division by zero, memory limitations, 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 visualization of calculation trends 2. Template system for common production scenarios 3. Integration with material databases). 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 methods 2. Function modules unrelated to production calculations (e.g., unnecessary multimedia components) 3. Fancy effects that affect performance (e.g., excessive animations in a calculation tool). 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/UI/data persistence 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) Calculation response time ≤ 100ms 2) Input field navigation and transition smoothness 3) Clear visual feedback for calculation processes. Deduct 5 points for each operation without feedback, 3 points for noticeable lag during complex calculations, and 5 points for unintuitive UI interactions that impede workflow. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Calculation Tools",
-  "difficulty": "easy"
-}

package/library/utility_tools-calculation_tools/programmer-calculator.json

@@ -1,68 +0,0 @@
-{
-  "index": 1487,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is functional and can be displayed. Using markdown, provide me a calculator for programmers, with the generated HTML consisting of div and script components for each function.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the basic calculator functionality fully implemented?",
-      "description": "Verify if the code implements all essential calculator operations (addition, subtraction, multiplication, division, modulo) correctly. Check if it handles operand precedence properly and supports parentheses for expression grouping. Score 0 if core calculation logic is missing, 5 if basic operations work but with edge case errors, and 10 if calculations are mathematically accurate in all scenarios.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are programmer-specific functions included?",
-      "description": "Evaluate whether the calculator includes functions essential for programmers: binary/hexadecimal/octal conversions, bitwise operations (AND, OR, XOR, NOT, shifts), logic operations, and possibly scientific functions. Deduct 2 points for each key programmer function missing. Award full points only if the calculator supports multiple number bases and complete set of bitwise operations.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the memory and history functionality implemented?",
-      "description": "Check if the calculator maintains operation history, allows result recall, and includes memory functions (M+, M-, MR, MC). Verify if users can copy results to clipboard and recall previous calculations. Deduct 3 points if history tracking is missing, 3 points if memory operations are absent, and 2 points if clipboard integration is not implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the calculator handle different number systems properly?",
-      "description": "Assess whether the calculator allows seamless switching between decimal, binary, octal, and hexadecimal systems. Verify if it properly displays bit representation, handles signed vs. unsigned integers, and allows bit-length selection (8/16/32/64-bit). Deduct 5 points if conversion between bases has errors, and 5 points if bit manipulation operations don't respect selected bit length.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as division by zero, invalid inputs, overflow/underflow conditions) and provide friendly error prompts. Code with strong robustness should prevent calculation errors through input validation and handle edge cases gracefully. Give 10 points if fully robust, 5 points if some edge cases are unhandled, and 0 points if major calculation errors occur frequently.",
-      "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. Expression syntax highlighting 2. Auto-parentheses balancing 3. Real-time conversion between number systems 4. Customizable keyboard shortcuts). 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 perform the same calculation) 2. Function modules unrelated to a programmer's calculator (e.g., unnecessary graphics) 3. Fancy effects 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 UI/calculation logic/state management), code organization, and maintainability. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high; deduct 5 points if there's inadequate error handling or poor code structure. 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 professional calculator design principles: 1) Clear visual hierarchy between number pad and special functions 2) Proper button spacing and sizing for usability 3) Effective use of color to distinguish function groups 4) Clear display area with appropriate font size and contrast. Deduct 3 points for each hard-to-read element, 5 points for inconsistent button styling, and 3 points for poor layout organization. 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) Clear indication of active mode/base 3) Responsive layout for different screen sizes. Deduct 3 points for each button that lacks visual feedback, 5 points for confusing operation state indicators, and 5 points if the calculator doesn't work properly on mobile devices. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Calculation Tools",
-  "difficulty": "medium"
-}

package/library/utility_tools-calculation_tools/random-number-wheel-1-to-200.json

@@ -1,68 +0,0 @@
-{
-  "index": 1816,
-  "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. Create a random number wheel from 1 to 200.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the wheel interface properly implemented?",
-      "description": "Check whether the code creates a visually clear wheel with numbers 1-200 displayed in a circular arrangement. Numbers should be legible, with appropriate font size and spacing. Score 0 if no visual wheel is created, 5 if the wheel exists but numbers are hard to read, and 10 if the wheel is visually well-designed with clear number placement.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the random number selection mechanism properly implemented?",
-      "description": "Evaluate whether the code uses a proper random number generation method (Math.random or similar appropriate function) that ensures each number from 1-200 has an equal probability of being selected. Check if the randomness is correctly applied to the wheel's spinning mechanism. Score 0 if randomness is not implemented, 5 if basic randomness exists but with bias, and 10 if truly random selection is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the spinning animation smooth and realistic?",
-      "description": "Review the wheel's spinning animation - it should gradually slow down to simulate physics (easing function), have appropriate duration (3-7 seconds), and provide a clear indication of the final selected number. Deduct 5 points if the animation is jerky, 3 points if there's no deceleration effect, and 3 points if the final selection isn't clearly highlighted.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there user interaction for triggering the wheel spin?",
-      "description": "Check if there's a clear mechanism (button, click event, etc.) for users to trigger the wheel spin. The interaction should include appropriate visual feedback (button state change, cursor change) and prevent multiple spins while animation is in progress. Score 0 if no interaction exists, 5 if basic interaction exists but lacks feedback, and 10 if interaction is intuitive with proper feedback.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as rapid multiple clicks, browser resizing, script errors) 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. Sound effects during spinning 2. Confetti/visual effects when landing on a number 3. History of previous spins 4. Customizable speed/appearance). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple methods to trigger spinning) 2. Function modules unrelated to the wheel (e.g., unnecessary analytics) 3. Fancy effects that affect performance (e.g., excessive animations that slow down the page). 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 wheel logic/view/animation), code organization, 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; deduct 5 points if there's no separation of concerns between UI and logic. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic wheel 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) Wheel animation performance (60fps without frame drops) 3) Clear visual indication of result. Deduct 5 points for each operation without feedback, 3 points for stuttering animation, and 5 points for unclear result indication. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Calculation Tools",
-  "difficulty": "medium"
-}

package/library/utility_tools-calculation_tools/retirement-calculator-html.json

@@ -1,68 +0,0 @@
-{
-  "index": 1774,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the generated code is executable for demonstration. Create a retirement calculator in HTML format.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the retirement calculator core functionality properly implemented?",
-      "description": "Evaluate whether the calculator accurately computes retirement savings based on standard financial formulas (including compound interest calculation, inflation adjustment, and withdrawal rate projections). Check if it accounts for key variables: initial savings, monthly contribution, expected return rate, inflation rate, retirement age, and life expectancy. Score 0 if basic calculations are missing, 5 if only simple projections are implemented, and 10 if comprehensive financial modeling is included with accurate formulas.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Does the calculator include input validation and constraints?",
-      "description": "Check whether the form implements proper input validation (numeric constraints, reasonable ranges for percentages/ages, prevention of negative values, etc.). Verify if the code provides immediate feedback on invalid inputs and handles edge cases (extremely high return rates, unrealistic age inputs). Deduct 5 points if basic validation is missing, 3 points if validation exists but error messages are unclear. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is there a visual representation of retirement projections?",
-      "description": "Assess whether the calculator includes data visualization components (charts/graphs) that illustrate retirement savings growth over time, showing accumulation and withdrawal phases. Check if the visualization is interactive, allowing users to see how changing variables affects outcomes. Award 10 points for comprehensive, interactive visualizations, 5 points for basic static charts, and 0 points if visual representation is entirely missing.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are additional financial planning features included?",
-      "description": "Evaluate whether the calculator goes beyond basic calculations to include features like different withdrawal strategies comparison, Social Security integration, tax implications modeling, or scenario comparison tools. Deduct 3 points for each major financial planning aspect missing that would be expected in a comprehensive retirement calculator. Full score is 10 points for a feature-complete financial planning tool.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as non-numeric inputs, extreme values, browser compatibility issues, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Monte Carlo simulation for market variability 2. Automated savings goal recommendations 3. Dynamic retirement age adjustment based on savings rate). 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 calculations (e.g., multiple formulas calculating the same metric) 2. Function modules unrelated to retirement planning (e.g., a built-in currency converter) 3. Fancy effects that affect performance (e.g., excessive animations that slow 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/input handling), code organization, and maintainability. Deduct 5 points if global variable 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 clear separation between HTML structure, CSS styling, and JavaScript functionality. 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 suitable for financial applications (professional, trustworthy palette) 2) Proper layout spacing with clear form organization and logical flow 3) Professional font system with adequate sizing for financial data readability. Deduct 3 points for cluttered input fields, 5 points for poor visual hierarchy of results, and 5 points for chaotic arrangement of controls. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the calculator provides immediate feedback on input changes: 1) Instant recalculation when inputs change 2) Smooth transitions when displaying results 3) Clear visual cues for important financial thresholds or goals. Deduct 5 points if calculations require manual triggering with no auto-update, 3 points for laggy updates when changing variables, and 5 points for confusing input-to-result relationships. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Calculation Tools",
-  "difficulty": "easy"
-}

package/library/utility_tools-calculation_tools/uniapp-android-camera-tree-dbh-measurement.json

@@ -1,68 +0,0 @@
-{
-  "index": 1651,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable for demonstration. Please use HBuilder to develop a uniapp that calls the Android device camera to measure tree diameter at breast height (DBH), with the following requirements: 1. The interface should be visually appealing and appropriate for the forestry industry; 2. After opening the interface, the device camera should automatically start, displaying the image in the photo area; 3. Add two vertical thin red lines in the photo area as reference lines for tree boundaries, which can be moved manually; 4. When clicking the measurement button, take a photo of the tree while calculating and displaying the DBH measurement result.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the camera functionality fully implemented?",
-      "description": "Review whether the code accurately implements camera integration through uniapp APIs, including automatic camera startup, real-time preview display, and photo capture functionality. Check if camera permissions are properly requested and handled. Score 0 if camera doesn't work, 5 if only basic capture is implemented, and 10 if all camera features including preview, capture, and permission handling are fully functional.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the movable reference lines properly implemented?",
-      "description": "Evaluate whether the two vertical red reference lines are correctly overlaid on the camera preview, can be moved manually through touch gestures, and maintain proper positioning during camera operations. Check if the lines have appropriate visual styling (thin, red, clearly visible). Deduct 5 points if lines are not movable, 3 points if touch interaction is unresponsive, and 5 points if lines disappear during camera operations. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the DBH measurement algorithm accurate and reliable?",
-      "description": "Check whether the measurement calculation uses proper scaling algorithms based on reference objects or camera parameters to convert pixel distance to real-world measurements. Evaluate if the algorithm accounts for distance, camera angle, and provides reasonable DBH values. Deduct 5 points if no scaling mechanism exists, 3 points if measurements are consistently inaccurate, and 5 points if the algorithm doesn't handle edge cases. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the forestry-themed interface design professionally implemented?",
-      "description": "Assess whether the interface design appropriately reflects forestry industry aesthetics with nature-inspired color schemes, professional measurement tool styling, and industry-appropriate iconography. Check if the interface includes proper measurement units display, clear result presentation, and forestry-specific visual elements. Deduct 5 points if the design looks generic, 3 points if forestry context is missing, and 5 points if the interface appears unprofessional. 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 camera access denial, device orientation changes, measurement calculation errors, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should effectively handle camera failures, permission issues, and measurement edge cases, 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 enhance measurement accuracy?",
-      "description": "Check whether the code includes advanced features that improve measurement precision (e.g., 1. Auto-detection of tree edges 2. Multiple measurement averaging 3. Calibration using known reference objects 4. Measurement history with GPS location). Add 3 points for each practical innovative feature that enhances measurement functionality (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 photo capture methods) 2. Function modules unrelated to tree measurement (e.g., built-in photo filters) 3. Excessive visual effects that impact performance (e.g., complex animations during measurement). Deduct 3 points for each redundancy found, and directly deduct 10 points if core measurement 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 camera logic/measurement algorithms/UI components), proper uniapp project structure, and code organization. Deduct 5 points if global state pollution is found or component architecture is poor; deduct 5 points if code duplication rate is too high (over 30%); deduct 5 points if uniapp best practices are not followed. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional forestry application standards?",
-      "description": "Evaluate whether the design follows forestry application principles: 1) Nature-appropriate color palette (greens, browns, earth tones) 2) Clear measurement display with proper units and precision 3) Professional tool-like interface with good contrast for outdoor use. Deduct 3 points for each unclear measurement display, 5 points for inappropriate color choices that don't suit forestry context, and 5 points for poor readability in bright outdoor conditions. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the touch interaction smooth and measurement-focused?",
-      "description": "Judge whether the interactions are optimized for field measurement use: 1) Reference line dragging responds within 100ms 2) Measurement button provides immediate visual feedback 3) Results display clearly with appropriate precision 4) Interface remains stable during device movement. Deduct 5 points for each unresponsive interaction, 3 points for laggy reference line movement, and 5 points for unclear measurement result presentation. Full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Calculation Tools",
-  "difficulty": "easy"
-}

package/library/utility_tools-calculation_tools/uniapp-mortgage-calculator-app-code.json

@@ -1,68 +0,0 @@
-{
-  "index": 793,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Pay attention to ensuring that the generated code is executable for demonstration. UniApp: Mortgage calculator app code, then guide me step by step on how to turn the code into an APP.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the mortgage calculator functionality fully implemented?",
-      "description": "Evaluate whether the code accurately implements core mortgage calculation formulas (principal, interest rate, loan term, monthly payment, total payment, total interest). Check for support of both equal principal and equal installment methods. Score 0 if calculations are missing, 5 if only basic calculations exist, and 10 if comprehensive mortgage calculation features are implemented with validation of input ranges (e.g., interest rate bounds, maximum loan periods).",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Does the UniApp code follow proper framework structure and conventions?",
-      "description": "Check if the code follows UniApp's recommended project structure with proper separation of pages, components, and services. Verify the implementation of the App.vue, manifest.json, pages.json files. Deduct 5 points if the basic configuration files are missing or incomplete, 3 points if component reusability isn't considered, and 2 points if platform-specific adaptations are absent. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the step-by-step app compilation guide comprehensive?",
-      "description": "Assess whether clear instructions are provided for: 1) Setting up the development environment (HBuilderX), 2) Configuring project settings, 3) Testing in simulator, and 4) Building for different platforms (iOS/Android/H5). Deduct 3 points for each major step omitted, and 2 points if platform-specific considerations (certificates, signatures) are missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the implementation include data persistence and state management?",
-      "description": "Evaluate whether the app implements history saving, settings persistence, and proper state management. Check for the use of storage APIs, Vuex/Pinia for state management, and handling of computation history. Deduct 5 points if no data persistence exists, 3 points if the state management is poorly implemented, and 2 points if user preferences aren't saved. 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 inputs, calculation edge cases, network interruptions when saving data). Code with strong robustness should validate all user inputs, provide clear error messages, and implement fail-safe mechanisms. 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 app includes surprise features that enhance the experience (e.g., 1. Different loan type comparisons 2. Visualizations of payment schedules 3. Integration with local bank interest rates). 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. Duplicate calculation methods or overlapping functionality 2. Features unrelated to mortgage calculation (e.g., unnecessary mini-games or unrelated tools) 3. Overly complex UI elements that harm usability. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core mortgage calculation is obscured by unnecessary features.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (separation of UI/logic/data layers), code reusability, and build process configuration. Deduct 5 points if global state is mismanaged; deduct 5 points if code duplication rate is high (similar calculation logic repeated); deduct 5 points if the build and deployment process isn't properly configured in manifest.json. 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 modern mobile design principles: 1) Consistent color scheme suitable for financial apps 2) Proper spacing and layout (following system guidelines) 3) Readable typography system (minimum 14px text). Examine screenshots for: Deduct 3 points for crowded input fields, 5 points for inappropriate color combinations in financial contexts, and 5 points for poor information hierarchy. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and responsive?",
-      "description": "Judge whether the app provides immediate feedback: 1) Calculation results appear within 100ms 2) Form transitions are smooth with appropriate animations 3) Clear visual indicators for interactive elements. From screenshots, deduct 5 points for any calculation without loading states, 3 points for jarring transitions between views, and 5 points for confusing navigation patterns. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Calculation Tools",
-  "difficulty": "easy"
-}