@getollie/cli 0.0.1

package/library/web_applications-education_learning/anesthesia-record-form-web-code.json

@@ -0,0 +1,68 @@
+{
+  "index": 1381,
+  "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 display. Help me write a web code for an anesthesia record form, then verify if the web code can run properly. If not, modify it again until it's perfect.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the basic structure of the anesthesia record form implemented?",
+      "description": "Review whether the HTML structure properly includes all essential sections of an anesthesia record form: patient information, pre-anesthesia assessment, intraoperative monitoring, medications administration, fluid management, and post-anesthesia care. Score 0 if core sections are missing, 5 if basic structure exists but lacks medical specificity, and 10 if the form comprehensively covers all standard anesthesia documentation requirements.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are the data input fields appropriate for clinical use?",
+      "description": "Evaluate whether the form includes the correct types of input fields for different medical data (e.g., dropdowns for ASA classification, numeric fields with proper ranges for vital signs, date/time pickers for procedures). Check if field validation implements medical constraints (e.g., systolic BP range 60-250 mmHg). Deduct 3 points for each critical medical field using inappropriate input types, and 5 points if validation is missing for critical values. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Does the form implement real-time vital signs charting?",
+      "description": "Check if the code includes a visual charting system for vital signs (HR, BP, SpO2, EtCO2, temperature) that can be updated in real-time. Evaluate if the charting uses appropriate visualization (line graphs for trends, color coding for out-of-range values). Deduct 5 points if charts are static, 3 points if they lack proper scaling, and 5 points if they don't support real-time updates. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is there functionality for medication tracking and calculations?",
+      "description": "Review whether the code implements medication tracking with timestamps, dose calculations based on patient weight, and cumulative dose monitoring. Check for drug interaction warnings and automated BMI/dosage calculations. Deduct 3 points if timestamps aren't automatic, 5 points if weight-based calculations are missing, and 5 points if there's no cumulative dose tracking. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid data entry, connection issues during form submission, or browser compatibility issues) 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 clinical workflow (e.g., 1. Voice input for hands-free documentation 2. Automated alerts for concerning vital sign trends 3. Integration with mock EMR systems 4. Offline functionality with data synchronization). 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 data entry fields for the same information 2. Functionality not typically needed in anesthesia documentation (e.g., complex animation effects) 3. Performance-heavy features that could slow down critical documentation during surgery. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core medical documentation 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 medical data models/view/form validation), test coverage for critical calculations, and responsive design for different clinical environments. Deduct 5 points if global variables store critical patient data without proper encapsulation; deduct 5 points if medical calculations lack validation; deduct 5 points if the form breaks on mobile devices that might be used in medical settings. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet clinical design standards?",
+      "description": "Evaluate whether the design follows medical interface principles: 1) Clear visual hierarchy prioritizing critical patient data 2) Appropriate color schemes that highlight abnormal values and use accepted clinical color conventions (e.g., red for hypotension) 3) Readable typography under varied lighting conditions (operating room vs. recovery). Deduct 3 points for poor information hierarchy, 5 points for non-standard clinical color usage, and 5 points for text that would be illegible in medical settings. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the form optimized for clinical workflow?",
+      "description": "Judge whether the interface supports efficient clinical documentation: 1) Quick access to common medications and procedures 2) Keyboard shortcuts for frequent actions 3) Logical tab order following the anesthesia workflow 4) Auto-saving to prevent data loss. Deduct 5 points for workflow that contradicts clinical practice, 3 points for excessive clicks required for common tasks, and 5 points for designs that would distract from patient care. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Education/Learning",
+  "difficulty": "hard"
+}

package/library/web_applications-education_learning/apple-iphone-generations-intro.json

@@ -0,0 +1,68 @@
+{
+  "index": 1292,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable when possible. Please help me create a website that can be directly opened to display introductions to various generations of Apple iPhones.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the iPhone generation display structure complete?",
+      "description": "Review whether the HTML/CSS structure accurately implements a comprehensive timeline or grid of iPhone generations, from the original iPhone to the latest models. Check if each iPhone has its own section/card with consistent layout. Score 0 if missing multiple generations, 5 if only major generations are included, and 10 if all generations including variants (e.g., Pro, Max, Plus models) are properly represented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the iPhone data presentation comprehensive?",
+      "description": "Evaluate whether each iPhone model includes essential information: release date, key specifications (processor, display, camera features), pricing (original/historical), and distinctive features that defined that generation. Deduct 2 points for each major information category missing, and 1 point for incomplete technical specifications. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is visual representation of iPhone models implemented?",
+      "description": "Check if the website includes visual elements representing each iPhone generation (images, illustrations, or 3D models). Images should be properly sized, optimized, and responsive. Assess whether alt text is provided for accessibility. Deduct 5 points if visuals are missing for multiple models, 3 points if images are of poor quality or not responsive, and 2 points if alt text is missing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is comparison functionality between iPhone models available?",
+      "description": "Evaluate whether the website allows users to compare different iPhone generations side-by-side (through tables, interactive elements, or visual comparisons). Check for filtering options by features, year, or specifications. Award 10 points for comprehensive comparison tools, 5 points for basic comparison capabilities, and 0 if comparison functionality is absent.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as missing images, variable screen sizes, older browsers, etc.) and provide fallback solutions. Code with strong robustness should implement responsive design principles, polyfills for older browsers, and graceful error handling. Give 10 points for comprehensive robustness, 5 points for average implementation, and 0 points if critical fallbacks are missing.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprising features that enhance the experience (e.g., 1. Interactive 3D iPhone models 2. Evolution timeline visualization 3. Color-accurate iPhone rendering 4. Audio demonstrations of features). Add 2.5 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple ways to view the same information) 2. Function modules unrelated to iPhone information (e.g., unrelated product categories) 3. Fancy effects that affect performance (e.g., excessive animations or unnecessary parallax effects). 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 the code's organization (separation of HTML/CSS/JS), naming conventions, appropriate use of semantic HTML elements, and code optimization (minified assets, lazy loading for images). Deduct 3 points for non-semantic markup, 3 points for inefficient or unorganized code, 2 points for poor naming conventions, and 2 points if performance optimization is missing. 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 Apple's design principles: 1) Clean, minimalist aesthetic with appropriate white space 2) Typography that mirrors Apple's San Francisco font or equivalent 3) Color scheme that complements Apple's brand identity. Deduct 3 points for cluttered layouts, 4 points for non-Apple-like design elements, and 3 points for inconsistent styling across the site. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the website implements smooth transitions and interactions: 1) Page loading and transitions under 300ms 2) Smooth scrolling between sections 3) Intuitive navigation with clear information hierarchy. Deduct 3 points for jerky animations, 4 points for confusing navigation patterns, and 3 points for unresponsive interface elements. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Education/Learning",
+  "difficulty": "easy"
+}

package/library/web_applications-education_learning/automotive-chip-industry-subdivisions-html-code.json

@@ -0,0 +1,68 @@
+{
+  "index": 1365,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure that the code you generate can be executed for display. Summarize the subdivisions of the automotive chip industry and generate HTML code.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the automotive chip industry subdivision analysis comprehensive?",
+      "description": "Evaluate whether the content covers major automotive chip categories (e.g., MCU, SoC, ADAS processors, power management ICs, sensors). Check if the analysis includes key applications, technological trends, and market positioning of different chip types. Score 0 if only basic definitions are provided, 5 if common subdivisions are listed but lack depth, and 10 if comprehensive coverage with technical specifications and market contexts is included.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Does the HTML structure properly organize the industry subdivision content?",
+      "description": "Review if the HTML structure uses appropriate semantic elements (e.g., section, article, header) to organize the content hierarchically. Check if the document structure reflects the logical relationship between different chip categories and their applications. Deduct 5 points if the HTML lacks proper sectioning elements, 3 points if heading levels (h1-h6) are improperly nested, and 2 points if there's no clear content organization. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Does the visualization include appropriate data representation?",
+      "description": "Assess if the code implements visual elements (charts, diagrams, or tables) to represent market share, technical comparisons, or industry relationships. Evaluate if the chosen visualization methods effectively communicate complex chip industry information. Deduct 5 points if no visualization is included, 3 points if visualizations are present but don't add meaningful insight, and 2 points if the visualizations contain inaccurate data. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the implementation responsive and cross-browser compatible?",
+      "description": "Check if the HTML code includes responsive design principles (media queries, flexible layouts, viewport meta tags) to ensure the content displays correctly across different screen sizes. Verify CSS prefixing or feature detection for cross-browser compatibility. Deduct 5 points if responsive design is absent, 3 points if it's partially implemented but breaks at certain viewports, and 2 points if browser-specific issues aren't addressed. 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 missing data, image loading failures, script errors) and provides fallback options. Code with strong robustness should include error handling for API calls and graceful degradation. Give 10 points for comprehensive error handling, 5 points for basic error checks, and 0 points if no exception handling is implemented.",
+      "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. Interactive drill-down capabilities for chip categories 2. Animated transitions between industry segments 3. Comparison tools for different chip specifications). 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 visualization functions 2. Content elements unrelated to automotive chips 3. Fancy effects that affect performance (e.g., unnecessary animations, excessive DOM manipulation). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core information is obscured by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating content/presentation/behavior), code reusability, and maintainability. Deduct 5 points if inline styles are heavily used instead of external CSS; deduct 5 points if the code contains duplicated functionality or hardcoded values; deduct 5 points if JavaScript is not properly organized or lacks comments. 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": "Web Applications-Education/Learning",
+  "difficulty": "easy"
+}

package/library/web_applications-education_learning/blazor-binary-dat-file-parsing.json

@@ -0,0 +1,68 @@
+{
+  "index": 888,
+  "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. For a Blazor project, after uploading a binary dat file, parse the data sequentially according to a fixed data type protocol.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the file upload mechanism properly implemented in Blazor?",
+      "description": "Evaluate whether the implementation uses Blazor's InputFile component correctly, handles large file uploads appropriately (streaming for files >2MB), and provides progress feedback to users. Check if the component prevents multiple simultaneous uploads that could cause race conditions. Deduct 5 points if there's no file size validation, 3 points if progress indication is missing, and 2 points if file type filtering for .dat files is absent. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the binary data parsing logic correctly implemented?",
+      "description": "Review whether the code correctly implements binary data reading using appropriate methods (BinaryReader, Memory<byte>, Span<byte>), properly handles endianness issues, and correctly interprets the binary format according to the specified protocol. Check for buffer management and memory efficiency. Deduct 5 points if endianness is not explicitly handled, 3 points if unsafe parsing that could lead to memory corruption is used, and 5 points if the data structure protocol is not clearly defined or followed. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is error handling robust for binary parsing edge cases?",
+      "description": "Assess whether the code handles parsing exceptions gracefully, including unexpected EOF, corrupted data, or incorrect format versions. Check if validation is performed before parsing begins. Deduct 3 points if general exception handling is missing, 5 points if specific binary format validation is absent, and 5 points if parsing errors don't provide meaningful feedback to users about the nature of the error. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the parsed data visualized effectively in the UI?",
+      "description": "Examine how parsed data is presented to users - whether through tables, charts, or other appropriate visualizations based on the data type. Check if complex data structures are presented in a hierarchical manner. Deduct 3 points if raw data is displayed without formatting, 5 points if there's no contextual organization of related fields, and 5 points if large datasets aren't paginated or virtualized for performance. 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 files, parsing errors, memory limitations, UI thread blocking during parsing) 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 parsing with progress visualization 2. Schema-based binary format definition UI 3. Export capabilities to common formats like CSV/JSON 4. Data integrity validation with checksums). 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 implementations of similar parsing functions 2. Function modules unrelated to binary parsing (e.g., unnecessary analytics) 3. Expensive UI operations that affect parsing performance. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core parsing functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating parsing logic/UI components/data models), unit test coverage for parsing edge cases, and adherence to Blazor component lifecycle best practices. Deduct 5 points if global state pollution is found; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no separation between parsing logic and 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 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) UI remains responsive during binary parsing (background threading/progress updates) 2) Transition animations for data visualization are controlled between 300-500ms 3) Clear visual guidance during file selection and parsing phases. Deduct 5 points for UI freezing during parsing operations, 3 points for abrupt data presentation without transitions, and 5 points for lack of clear parsing status indicators. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Education/Learning",
+  "difficulty": "hard"
+}

package/library/web_applications-education_learning/bootstrap-4-dynamic-table-ajax-backend.json

@@ -0,0 +1,68 @@
+{
+  "index": 1259,
+  "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 purposes. Write a table with dynamically loaded headers and data using Bootstrap 4, where clicking a button adds a row, clicking the submit button retrieves the table data, and saves it to the backend through Ajax.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the table with dynamic headers fully implemented?",
+      "description": "Check whether the code correctly implements a table with dynamic header creation functionality. Headers should be properly rendered using Bootstrap 4 table styling. Score 0 if there's no table implementation, 5 if a static table is implemented, and 10 if headers can be dynamically defined/loaded.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the row addition functionality properly implemented?",
+      "description": "Evaluate whether clicking a button successfully adds a new row to the table. Check if the added rows maintain proper structure matching the headers, include appropriate input fields, and preserve proper Bootstrap styling. Deduct 5 points if rows are added but don't align with headers, 3 points if styling is inconsistent. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the data retrieval and submission functionality working?",
+      "description": "Verify if clicking the submit button correctly retrieves all table data (properly formatted as an object/array), and if the Ajax call to the backend is implemented with appropriate error handling. Check for proper data validation before submission. Score 0 if no submission functionality exists, 5 if data is collected but Ajax is missing/incomplete, and 10 if everything is properly implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are data formatting and validation handled properly?",
+      "description": "Check whether the code includes input validation, data type conversion (for number fields), and proper error messaging for invalid inputs. Review if empty cells are handled appropriately during submission. Deduct 5 points for missing validation, 3 points for missing error feedback to users, and 2 points for improper data type handling. 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 empty tables, network errors during Ajax submission, malformed data, 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. Drag-and-drop row reordering 2. In-cell editing with validation 3. Column sorting functionality 4. Export to CSV/Excel). 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 add rows) 2. Function modules unrelated to table management (e.g., unnecessary animations) 3. Fancy effects that affect performance (e.g., excessive DOM manipulations). 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/business logic/data handling layers), code reusability, and proper event handling. Deduct 5 points if global variable pollution is found; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if event listeners aren't properly managed (potential memory leaks). 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 Bootstrap 4 principles: 1) Consistent use of Bootstrap classes 2) Proper spacing and margins (following Bootstrap's spacing system) 3) Responsive design implementation. Deduct 3 points for inconsistent styling, 5 points for non-responsive implementation, and 5 points for incorrect use of Bootstrap grid system or components. 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 user expectations: 1) Immediate feedback when adding rows 2) Clear loading indicators during Ajax operations 3) Smooth transitions and animations (if used). Deduct 5 points for operations without feedback, 3 points for jarring UI updates, and 5 points for confusing action flows or buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Education/Learning",
+  "difficulty": "easy"
+}

package/library/web_applications-education_learning/botanical-garden-interface.json

@@ -0,0 +1,68 @@
+{
+  "index": 1120,
+  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Be sure to ensure the generated code is executable for display.\n\n<view class=\"container\">\n  <image src=\"../images/wificonfigbackground.jpg\" class=\"background-image\"></image>\n  <view class=\"content\">\n    <!-- Top title -->\n    <view class=\"header\">\n      <text class=\"title\">Wi-Fi Scan</text>\n    </view>\n    <view class=\"header\">\n      <text class=\"subtitle\">Select any Wi-Fi to connect</text>\n    </view>\n\n    <!-- Wi-Fi list -->\n    <scroll-view class=\"wifi-list\" scroll-y=\"true\" style=\"height: 400rpx;\">\n      <view wx:for=\"{{wifiList}}\" wx:key=\"ssid\" class=\"wifi-item\" bindtap=\"connectWifi\" data-ssid=\"{{item.ssid}}\">\n        <text class=\"wifi-ssid\">{{item.ssid}}</text>\n        <text class=\"wifi-signal\">Signal strength: {{item.rssi}} dBm</text>\n      </view>\n    </scroll-view>\n\n    <!-- Refresh button -->\n    <button bindtap=\"scanWifi\">Refresh Wi-Fi List</button>\n\n     <!-- Return to Wi-Fi configuration -->\n     <button bindtap=\"navigateToWificonfig\">Return to Wi-Fi Configuration</button>\n  </view>\n</view>   .container {\n    display: flex;\n    justify-content: center;\n    align-items: center;\n    height: 100vh;\n    background-color: #f0f8f0;\n  }\n  \n  .background-image {\n    position: absolute;\n    top: 10rpx;\n    right: 0rpx;\n    width: 500rpx;\n    height: 500rpx;\n    background-color: transparent;\n    mix-blend-mode: multiply;\n  }\n  \n  .content {\n    width: 90%;\n    max-width: 600rpx;\n    background-color: rgba(255, 255, 255, 0.2);\n    padding: 40rpx;\n    border-radius: 20rpx;\n    box-shadow: 0 10rpx 30rpx rgba(0, 0, 0, 0.1);\n    display: flex;\n    flex-direction: column;\n    align-items: center;\n    margin-top: 450rpx;\n  }\n  \n  .header {\n    text-align: center;\n    margin-bottom: 30rpx;\n  }\n  \n  .title {\n    font-size: 68rpx;\n    font-weight: bold;\n    color: #4CAF50;\n    margin-bottom: 10rpx;\n  }\n  \n  .subtitle {\n    font-size: 32rpx;\n    color: #81C784;\n  }\n  \n  .wifi-list {\n    width: 100%;\n    margin-top: 5rpx;\n  }\n  \n  .wifi-item {\n    padding: 10rpx;\n    border-bottom: 2rpx solid #ddd;\n    align-items: center; /* horizontal centering */\n    justify-content: center; /* vertical centering */\n    text-align: center; /* text centering */\n    margin-bottom: 20rpx; /* spacing with next item */\n  }\n  \n  .wifi-ssid {\n    font-size: 32rpx;\n    color: #333;\n    margin-bottom: 10rpx; /* spacing between SSID and signal strength */\n  }\n  \n  .wifi-signal {\n    font-size: 28rpx;\n    color: #666;\n  }\n\n    /* Login button */\n    button {\n        padding: 17px 20px;\n        border-radius: 50px;\n        cursor: pointer;\n        border: 0;\n        background-color: #8BC34A; /* base color: green */\n        box-shadow: rgb(0 0 0 / 5%) 0 0 8px;\n        letter-spacing: 1.5px;\n        text-transform: uppercase;\n        font-size: 15px;\n        transition: all 0.5s ease;\n        margin-bottom: 20rpx; /* increased spacing between buttons */\n      }\n      \n      button:hover {\n        letter-spacing: 3px;\n        background-color: #689F38; /* hover color: dark green */\n        color: hsl(0, 0%, 100%); /* text color: white */\n        box-shadow: rgb(104 159 56 / 50%) 0px 7px 29px 0px; /* shadow color: dark green */\n      }\n      \n      button:active {\n        letter-spacing: 3px;\n        background-color: #33691E; /* click color: deeper green */\n        color: hsl(0, 0%, 100%); /* text color: white */\n        box-shadow: rgb(51 105 30 / 50%) 0px 0px 0px 0px; /* shadow color: deeper green */\n        transform: translateY(10px);\n        transition: 100ms;\n      }\n   Develop a WeChat Mini Program for a botanical garden, following this style to help me create a botanical garden interface",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Mini Program interface for the botanical garden completely implemented?",
+      "description": "Review whether the code implements a botanical garden interface following the style shown in the example code. Check if it includes necessary elements such as plant listings, garden maps, information displays, and relevant botanical garden features.Score 0 if the core botanical garden elements are missing, 5 if only basic elements are implemented, and 10 if a comprehensive botanical garden interface is created with proper categorization and display of plant information.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the Wi-Fi connectivity functionality adapted for botanical garden usage?",
+      "description": "Evaluate whether the Wi-Fi connectivity features from the sample code are appropriately adapted to serve botanical garden visitors (such as connecting to garden hotspots, location-based plant information, or interactive garden tours).Deduct 5 points if the Wi-Fi functionality is merely copied without adaptation to botanical context. Deduct 3 points if the connection process lacks garden-specific features. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are botanical garden specific features implemented?",
+      "description": "Check if the code includes features specific to a botanical garden experience: plant identification/catalog, tour scheduling, educational content, seasonal highlights, or event information.Deduct 5 points if fewer than three botanical-specific features are implemented. Deduct 3 points if features exist but lack depth or proper implementation. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the navigation system intuitive for garden visitors?",
+      "description": "Assess whether the navigation system would help visitors effectively explore the garden with features like map integration, location markers, guided tours, search functionality, and path recommendations.Deduct 5 points if the navigation lacks spatial orientation features. Deduct 3 points if the user flow is confusing or requires more than 3 taps to reach key features. Give 10 points if navigation is intuitive and garden-oriented.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as missing images, offline usage in garden areas with poor connectivity, location services 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 enhance the botanical garden experience?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. AR plant identification 2. Seasonal bloom notifications 3. Interactive plant care guides 4. Community photo sharing of plants).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 map views with the same purpose) 2. Function modules unrelated to botanical gardens (e.g., unnecessary gaming elements) 3. Fancy effects that affect performance (e.g., heavy animations that would drain battery during garden visits).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 botanical data/view/location services layers), component reusability, and WeChat Mini Program best practices.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 Mini Program API usage is incorrect or outdated. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional botanical garden design standards?",
+      "description": "Evaluate whether the design follows nature-inspired design principles: 1) Natural color palette (greens, earth tones, with subtle accent colors) 2) Proper spacing that creates visual breathing room 3) Typography that prioritizes readability outdoors (minimum 16px font size, high contrast). Check if plant imagery is high quality and accurately displayed.Deduct 3 points for each cluttered visual element, 5 points for unnatural color combinations, and 5 points for poor image quality of plant specimens. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction suitable for outdoor garden usage?",
+      "description": "Judge whether the app is designed for real-world garden use: 1) Large touch targets for outdoor usage (≥ 44px) 2) High contrast display readable in sunlight 3) Battery-efficient interactions 4) Offline functionality for areas with poor connectivity.Deduct 5 points for interactions that would be difficult in outdoor settings, 3 points for battery-intensive features without warnings, and 5 points for features that absolutely require connectivity without alternatives. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Education/Learning",
+  "difficulty": "easy"
+}

package/library/web_applications-education_learning/brachistochrone-curve-frontend-demonstration.json

@@ -0,0 +1,68 @@
+{
+  "index": 465,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code for demonstration whenever possible. What is the brachistochrone curve? Please create a frontend program to demonstrate this concept to children.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the brachistochrone curve concept accurately explained?",
+      "description": "Check if the response provides a clear, accurate explanation of the brachistochrone curve (cycloid shape), its mathematical properties, and its historical significance (Johann Bernoulli's problem). The explanation should be scientifically correct while being accessible to children. Deduct 5 points if the explanation contains mathematical errors, 3 points if key properties are missing, and 2 points if historical context is absent. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the visualization of the brachistochrone curve properly implemented?",
+      "description": "Evaluate if the code correctly renders a cycloid curve using proper mathematical formulas. Check if the visualization demonstrates that a ball rolling down this curve reaches the bottom faster than other paths. The implementation must use parametric equations for the cycloid (x = r(t - sin(t)), y = r(1 - cos(t))). Deduct 5 points if the curve is incorrectly drawn, 5 points if the physics simulation is inaccurate. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is there an interactive comparison between different paths?",
+      "description": "Check if the program allows comparison between at least three different paths (straight line, curved line, and brachistochrone). The simulation should clearly demonstrate that the brachistochrone path is the fastest despite appearing longer. Assess whether users can trigger the comparison simulation and if timing measurements are shown. Deduct 5 points if only two paths are compared, 5 points if no timing comparison is implemented. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the physics simulation accurate and educational?",
+      "description": "Verify that the physics engine correctly simulates gravity, acceleration, and motion. Check if the simulation properly accounts for conservation of energy and if the motion appears natural. The implementation should include acceleration calculations based on path slope. Deduct 5 points for unrealistic movement, 3 points for incorrect acceleration behavior, and 2 points if energy conservation is violated. 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 window resizing, different screen sizes, browser compatibility issues, etc.) and provide graceful degradation. Code with strong robustness should be able to effectively handle 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 learning experience (e.g., 1. Interactive parameter adjustment 2. Real-time path editing 3. Age-appropriate explanations with animations). 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 physics engines coexisting) 2. Function modules unrelated to the brachistochrone concept 3. Fancy effects that affect performance (e.g., excessive particle effects). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core educational 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 physics/rendering/UI layers), code readability, and appropriate commenting for educational purposes. 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 code lacks meaningful comments for understanding. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet child-friendly design standards?",
+      "description": "Evaluate whether the design is appropriate for children: 1) Age-appropriate color scheme with high contrast 2) Larger interactive elements suitable for younger users 3) Clear visual instructions with minimal text dependency. Deduct 3 points for each small, hard-to-click element, 5 points for text-heavy explanations unsuitable for children, and 5 points for visually confusing layouts. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and engaging for children?",
+      "description": "Judge whether the interactive elements are designed for children's cognitive abilities: 1) Immediate visual feedback for interactions 2) Simplified controls with clear cause-effect relationships 3) Engaging animations that reinforce the concept being taught. Deduct 5 points for each complex interaction requiring advanced motor skills, 3 points for delayed feedback that might confuse children, and 5 points for interactions that don't contribute to understanding the brachistochrone concept. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Education/Learning",
+  "difficulty": "medium"
+}

package/library/web_applications-education_learning/calligraphy-stroke-practice-page.json

@@ -0,0 +1,68 @@
+{
+  "index": 1242,
+  "question": "You are a coding expert. Please use your professional knowledge to generate accurate, professional responses. Make sure the code you generate is executable for demonstration. Design a page that can print calligraphy stroke practice content.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the calligraphy stroke practice system fully implemented?",
+      "description": "Evaluate whether the code implements core calligraphy features including stroke display, character grid systems, stroke sequence demonstration, and stroke-by-stroke practice capability. Score 0 if no stroke rendering exists, 5 if only static character display is implemented, and 10 if complete interactive stroke practice with animation guidance is included.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the printing functionality properly implemented?",
+      "description": "Check if the code includes proper CSS @media print rules, print-optimized layouts, page breaks control, and print preview functionality. Deduct 3 points if the print layout breaks, 5 points if there's no print-specific styling, and 2 points if the printed output differs significantly from the screen display. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the calligraphy character customization feature implemented?",
+      "description": "Review whether users can customize the calligraphy content (character selection, style selection, grid size, stroke thickness, etc.). Score 10 for comprehensive customization options with preview capability, 5 for basic customization without preview, and 3 if only preset templates are available with minimal adjustments.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the system provide proper practice guidance mechanisms?",
+      "description": "Assess if the system includes features like stroke order visualization, proper spacing guides, writing direction indicators, and possibly animation demonstrations. Deduct 5 points if stroke order is missing, 3 points if guide lines aren't customizable, and 2 points if there's no visual feedback mechanism for practice. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code handles common edge cases (such as browser compatibility issues, device orientation changes, print errors, unsupported character inputs, etc.) and provides friendly error messages or fallbacks. Code with strong robustness should effectively handle these situations, 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": "Look for surprise features that enhance the experience (e.g., 1. Brush pressure simulation with pointer events 2. Animated stroke demonstrations with timing control 3. Progress tracking system for practice 4. Handwriting recognition for feedback). 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 functionality implemented in multiple ways 2. Features unrelated to calligraphy practice or printing 3. Decorative elements that hinder the primary learning function. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core calligraphy practice functions are obscured by unnecessary features.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review the modular design (separation of rendering engine, character data, user interface, and print functionality), reusability of components, and performance optimization for both screen and print media. Deduct 5 points if global variables are overused; deduct 5 points if the code isn't organized into logical components; deduct 5 points if print rendering performance isn't optimized. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards for calligraphy practice?",
+      "description": "Evaluate whether the design follows calligraphy practice principles: 1) Clear contrast between strokes and background 2) Proper grid spacing that follows traditional practice sheet proportions 3) Professional typography with appropriate spacing between characters. Deduct 3 points for poor stroke visibility, 5 points for improper grid sizing that makes practice difficult, and 5 points for cluttered interface elements that distract from practice. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the print output optimized for actual practice use?",
+      "description": "Judge whether the printed output is practical for real calligraphy practice: 1) Ink-saving design options 2) Appropriate stroke density and visibility on paper 3) Page format optimization for standard paper sizes. Deduct 5 points if the print output wastes excessive ink, 3 points if the printed stroke guides are too faint or too dark for practical use, and 5 points if the layout doesn't properly account for paper margins or standard sizes. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Education/Learning",
+  "difficulty": "medium"
+}