@getollie/cli 0.0.4 → 0.2.0

package/library/web_applications-education_learning/lisao-webpage-dynamic-video-audio-narration.json

@@ -1,68 +0,0 @@
-{
-  "index": 1542,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Ensure that any code you provide is executable for demonstration. This is an illustration from the Chinese literature lesson on \"Lisao\" (The Lament). I need you to create a webpage based on this image with the following requirements:\n- Transform the image into a dynamic video, adding details from the text\n- Generate a synchronized audio narration file that plays with the video, with the narration content providing supplementary knowledge about \"Lisao\" not covered in the lesson",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the webpage structure properly implemented with HTML5 standards?",
-      "description": "Evaluate whether the HTML structure follows semantic markup principles with proper use of <header>, <main>, <section>, <footer> tags. Check for responsive design implementation with appropriate meta viewport tags and CSS media queries. Score 0 if basic HTML structure is missing, 5 if basic structure exists but lacks semantic elements, 10 if fully compliant with HTML5 standards including accessible attributes.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the dynamic video transformation successfully implemented?",
-      "description": "Review whether the code effectively transforms the static image into a dynamic video with animated elements. Check if it uses canvas manipulation, SVG animations, or HTML5 video elements with proper layering. Score 0 if no animation exists, 5 if basic animation is implemented but lacks smoothness or detail, 10 if the animation is fluid with multiple animated elements that accurately represent scenes from 'Lisao'.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are the details from the text appropriately incorporated into the visual elements?",
-      "description": "Examine whether specific textual details from 'Lisao' are visually represented in the animations. Check for symbolic elements (like herbs, mythical creatures, or celestial journeys mentioned in the poem), accurate historical context visualization, and visual storytelling elements. Deduct 3 points for each major textual element missing, and 5 points if the visuals contradict the poem's content. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the audio narration properly synchronized with the visual content?",
-      "description": "Evaluate the implementation of audio-visual synchronization. Check if the code includes timestamp markers for synchronization points, event listeners for coordinating audio with visual elements, and proper preloading of audio resources. Score 0 if no synchronization exists, 5 if basic synchronization is implemented but with noticeable lag, 10 if perfect synchronization with visual cues matching narration content.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as browser compatibility issues, network interruption during audio/video loading, user interaction errors, 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. Interactive elements allowing users to trigger specific poem scenes 2. Parallax scrolling effects tied to poem progression 3. Cultural context tooltips appearing alongside narration). 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 animation systems overlapping) 2. Function modules unrelated to the poem presentation (e.g., unrelated social media widgets) 3. Fancy effects that affect performance (e.g., excessive particle effects causing lag). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core presentation is interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating animation/audio/UI layers), file organization, and performance optimization. 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 no performance considerations (like image optimization or lazy loading) are implemented. 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 classical Chinese aesthetic principles while maintaining modern usability: 1) Harmonious color palette reflecting the poem's tone 2) Proper layout balancing text and visuals with adequate negative space 3) Typography that honors traditional Chinese calligraphy while remaining readable. Deduct 3 points for each visually jarring element, 5 points for inappropriate modern elements that clash with the classical theme, and 5 points for poor readability. 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) Transitions between poem sections feel natural and contemplative 2) Animation timing reflects the emotional pacing of the poem 3) Clear visual guidance for user navigation and interaction. Deduct 5 points for jarring transitions, 3 points for animations that run too quickly to appreciate, and 5 points for confusing navigation or lack of user control options (pause/play/rewind). The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Education/Learning",
-  "difficulty": "medium"
-}

package/library/web_applications-education_learning/literature-retrieval-frontend-design.json

@@ -1,68 +0,0 @@
-{
-  "index": 1220,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Take care to ensure that any code you generate is executable for demonstration purposes. Design a frontend page similar to literature retrieval systems, referencing third-party open source projects.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the literature retrieval search functionality fully implemented?",
-      "description": "Check if the code includes a comprehensive search system with advanced filters (author, title, date range, keywords), fuzzy matching, and result sorting capabilities. Review whether proper query string handling and search parameter validation are implemented. Score 0 if there's no search functionality, 5 if only basic keyword search exists, and 10 if advanced search with filters and sorting is fully implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the search results display system properly designed?",
-      "description": "Evaluate whether the results are displayed in a clean, organized format with proper pagination (10-20 items per page), sorting controls, and citation details. Check if each result includes essential bibliographic information (title, authors, publication, year, DOI/URL). Deduct 3 points if pagination is missing, 3 points if sorting options are absent, and 4 points if the results lack proper formatting for academic citations. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is there a detailed view for individual literature entries?",
-      "description": "Check if users can view detailed information about a specific publication, including abstract, full citation, author details, and related papers. Assess whether the code provides options to export citations in multiple formats (BibTeX, RIS, EndNote). Deduct 5 points if detailed view is missing, 3 points if citation export functionality is absent. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there a user account system with save/bookmark functionality?",
-      "description": "Review whether the implementation includes user profiles with the ability to save searches, create bibliographies, and bookmark papers. Check for reading history tracking and organization of saved papers into collections/folders. Score 0 if no user system exists, 5 if basic bookmarking is available, and 10 if comprehensive user profiles with organized collections are implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as empty search results, server errors, malformed queries) and provide friendly error prompts or recovery mechanisms. Check for input validation, error boundary components, and graceful fallbacks. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Visual citation network graphs 2. AI-powered paper recommendations 3. Browser extensions for one-click citation 4. Annotation tools for PDFs). 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 search forms with overlapping functionality) 2. Function modules unrelated to literature retrieval (e.g., a built-in chat system) 3. Fancy effects that affect performance (e.g., excessive animations or 3D visualizations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating UI components, API services, and state management), component reusability, and build process automation. Examine code organization, naming conventions, 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 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 academic interface principles: 1) Clean, distraction-free reading experience 2) Proper typography for academic content (serif fonts for body text, adequate line spacing) 3) Consistent visual hierarchy with clear content separation. Deduct 3 points for cluttered layouts, 5 points for poor readability (small font sizes, insufficient contrast), and 5 points for inconsistent design patterns across pages. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Search response time appears immediate (loading indicators for searches >300ms) 2) Smooth transitions between search results and detailed views 3) Intuitive interactions for filtering and refining searches. Deduct 5 points for laggy search experiences, 3 points for jarring page transitions, and 5 points for confusing navigation patterns. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Education/Learning",
-  "difficulty": "medium"
-}

package/library/web_applications-education_learning/lunar-calendar-moon-phase-webpage.json

@@ -1,68 +0,0 @@
-{
-  "index": 234,
-  "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 display. Create a webpage showing the moon's phase changes from the first to the thirtieth day of the lunar calendar.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the lunar phase simulation scientifically accurate?",
-      "description": "Check whether the code correctly represents the lunar phases according to astronomical principles (waxing crescent, first quarter, waxing gibbous, full moon, waning gibbous, third quarter, waning crescent, new moon). Review whether the calculation takes into account the 29.53-day lunar cycle rather than simply using a 30-day calendar. Score 0 if phases are incorrect, 5 if basic phases are present but with inaccuracies, and 10 if astronomically accurate with proper illumination angles.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the day-by-day phase transition visualization implemented?",
-      "description": "Evaluate whether the code provides a clear visual representation for all 30 days of the lunar calendar, with proper transitions between phases. Check if the illumination percentage matches the day number in the lunar cycle. Deduct 5 points if transitions are abrupt, 3 points if illumination angles are inconsistent, and 2 points if the shape of the moon is distorted. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is there an interactive component allowing users to navigate between different days?",
-      "description": "Check whether users can interact with the visualization to select specific lunar days or navigate through the cycle (such as sliders, clickable days, or animation controls). Score 0 if no interaction exists, 5 if basic navigation is implemented but clunky, and 10 if smooth, intuitive navigation with immediate visual feedback is provided.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is additional contextual information about lunar phases provided?",
-      "description": "Assess whether the code includes educational elements about each lunar phase (names, characteristics, cultural significance, or astronomical explanations). Score 0 if no information is provided, 5 if basic labels are present, and 10 if comprehensive information that enhances user understanding is integrated seamlessly with the visualization.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as out-of-bounds input, browser compatibility issues, user operation errors, 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 comparisons with current lunar phase 2. Realistic lunar surface textures with shadows 3. Regional visibility indicators based on geography). 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 calculations or rendering logic that could be optimized 2. Function modules unrelated to lunar phases (e.g., unnecessary weather information) 3. Fancy effects that affect performance (e.g., excessive animations that distract from the lunar phase visualization). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core visualization is obscured by redundant elements.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating astronomical calculations/visualization/user interface layers), code reusability, and implementation efficiency. 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 animation performance is poor (below 30 fps). 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 (appropriate night sky or space theme without being garish) 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 distracting color scheme that diminishes the moon visualization, 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/selection feedback delay ≤ 100ms 2) Phase transition animations controlled between 300-500ms for smooth blending 3) Clear visual cues for current day selection. Deduct 5 points for each operation without feedback, 3 points for jerky animations during phase transitions, and 5 points for confusing navigation between lunar days. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Education/Learning",
-  "difficulty": "hard"
-}

package/library/web_applications-education_learning/major-historical-disasters-on-this-day.json

@@ -1,68 +0,0 @@
-{
-  "index": 1108,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure that the code you generate is executable for demonstration. Write a tool that can view \"major disasters that happened on this day in history\", in HTML format, for mobile devices.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core functionality of displaying 'major disasters on this day in history' implemented?",
-      "description": "Check whether the code properly fetches and displays historical disaster data for the current date. It should include the date handling logic, data retrieval mechanism, and proper rendering. Score 0 if the core functionality is missing, 5 if basic implementation exists but with limitations, and 10 if it comprehensively shows disasters with proper date formatting and details.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is there an appropriate data source or API integration?",
-      "description": "Evaluate whether the implementation uses a reliable data source or API to fetch historical disaster information. Check if the API calls are properly structured with error handling, rate limiting consideration, and fallback mechanisms. Deduct 5 points if no proper data source is used (e.g., hardcoded sample data), and 3 points if the API integration lacks error handling. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the mobile-specific design properly implemented?",
-      "description": "Assess whether the implementation follows mobile-first design principles, including responsive layouts, appropriate touch targets (minimum 44x44px), mobile-friendly navigation, and proper viewport settings. Check for media queries handling different screen sizes. Deduct 5 points if the interface is not optimized for mobile viewing, and 3 points if touch interactions are not properly implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the implementation include date navigation or filtering capabilities?",
-      "description": "Check if users can navigate through different dates or filter disasters by type/severity/location. Evaluate if the date selection is intuitive (calendar picker, swipe gestures, etc.) and whether filter options are properly implemented. Deduct 5 points if date navigation is absent, and 3 points if the filtering system is limited or unintuitive. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as network failures, API errors, invalid dates, empty result sets, 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. Interactive timeline visualization 2. Disaster location mapping 3. Related historical context information 4. Categorization by disaster type with visual indicators). 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 date pickers) 2. Function modules unrelated to historical disasters (e.g., weather forecasts) 3. Fancy effects that affect performance (e.g., unnecessary animations or high-resolution images). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating data fetching/processing/rendering), code maintainability, and performance optimization. Deduct 5 points if global variables are overused; deduct 5 points if the code has high complexity or poor organization; deduct 5 points if performance optimizations are missing (e.g., no caching of previously viewed dates). The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern mobile design principles: 1) Harmonious color matching (appropriate for the serious subject matter) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional typography (readable font sizes ≥ 16px, sufficient contrast). Deduct 3 points for each cluttered section, 5 points for inappropriate color schemes (e.g., festive colors for disaster content), and 5 points for poor information hierarchy. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to mobile interaction patterns: 1) Touch feedback delay ≤ 100ms 2) Smooth scrolling through disaster entries 3) Intuitive gestures for date navigation if implemented. Deduct 5 points for laggy scrolling, 3 points for delayed touch responses, and 5 points for unintuitive interaction patterns. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Education/Learning",
-  "difficulty": "easy"
-}

package/library/web_applications-education_learning/material-testing-specifications-data.json

@@ -1,68 +0,0 @@
-{
-  "index": 300,
-  "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.\n\nlet base_data = [\n  {\n    // testing_project field\n    label: \"Test Project\",\n    search: null,\n    tensile_strength: \"Tensile Strength\",\n    elongation_at_break: \"Elongation at Break\",\n    flexural_strength: \"Flexural Strength\",\n    flexural_modulus: \"Flexural Modulus\",\n    izod_impact_strength: \"Izod Impact Strength\",\n    heat_deflection_temp: \"Heat Deflection Temperature\",\n    dielectric_strength: \"Dielectric Strength\",\n    volume_resistivity: \"Volume Resistivity\",\n    density: \"Density\",\n    melt_flow_rate: \"Melt Flow Rate\",\n    molding_shrinkage: \"Molding Shrinkage\",\n    flammability_1_5mm: \"1.5mm Flammability Rating\",\n    flammability_3_0mm: \"3.0mm Flammability Rating\",\n    yellow_card: \"Yellow Card Number\",\n    rti_elec: \"RTI (Elec)\",\n    rti_imp: \"RTI (Imp)\",\n    rti_str: \"RTI (Str)\",\n    hwi: \"HWI\",\n    hai: \"HAI\",\n    cti: \"CTI\",\n    outdoor_performance: \"Outdoor Performance\",\n    ball_pressure_temp: \"Ball Pressure Temperature\",\n    rohs: \"RoHS\",\n    reach_svhc: \"REACH, SVHC\",\n    quotation: \"Quotation\",\n    remarks: \"Remarks\"\n  },\n  {\n    // testing_standards field\n    label: \"Testing Standards\",\n    search: null,\n    tensile_strength: \"ASTM D638\",\n    elongation_at_break: \"ASTM D638\",\n    flexural_strength: \"ASTM D790\",\n    flexural_modulus: \"ASTM D790\",\n    izod_impact_strength: \"ASTM D256\",\n    heat_deflection_temp: \"ASTM D648\",\n    dielectric_strength: \"ASTM D149\",\n    volume_resistivity: \"ASTM D257\",\n    density: \"ASTM D792\",\n    melt_flow_rate: \"ASTM D1238\",\n    molding_shrinkage: \"ASTM D955\",\n    flammability_1_5mm: \"UL-94\",\n    flammability_3_0mm: \"UL-94\",\n    yellow_card: \"/\",\n    rti_elec: \"UL 746B\",\n    rti_imp: \"UL 746B\",\n    rti_str: \"UL 746B\",\n    hwi: \"UL 746B\",\n    hai: \"UL 746B\",\n    cti: \"UL 746B\",\n    outdoor_performance: \"UL 746B\",\n    ball_pressure_temp: \"IEC 60695-10-2\",\n    rohs: \"/\",\n    reach_svhc: \"/\",\n    quotation: \"\",\n    remarks: \"\"\n  },\n  {\n    // testing_conditions field\n    label: \"Testing Conditions\",\n    search: null,\n    tensile_strength: \"50mm/min\",\n    elongation_at_break: \"50mm/min\",\n    flexural_strength: \"2mm/min\",\n    flexural_modulus: \"2mm/min\",\n    izod_impact_strength: \"3.2mm, 23℃\",\n    heat_deflection_temp: \"1.82MPa, 6.4mm\",\n    dielectric_strength: \"1.6mm\",\n    volume_resistivity: \"/\",\n    density: \"23℃\",\n    melt_flow_rate: \"230℃, 2.16kg\",\n    molding_shrinkage: \"23℃\",\n    flammability_1_5mm: \"1.5mm\",\n    flammability_3_0mm: \"3.0mm\",\n    yellow_card: \"/\",\n    rti_elec: \"1.5mm\",\n    rti_imp: \"1.5mm\",\n    rti_str: \"1.5mm\",\n    hwi: \"1.5mm\",\n    hai: \"1.5mm\",\n    cti: \"1.5mm\",\n    outdoor_performance: \"/\",\n    ball_pressure_temp: \"3.0mm\",\n    rohs: \"/\",\n    reach_svhc: \"/\",\n    quotation: \"\",\n    remarks: \"\"\n  },\n  {\n    // unit field\n    label: \"Unit\",\n    search: null,\n    tensile_strength: \"Mpa\",\n    elongation_at_break: \"Tensile Strength\",\n    flexural_strength: \"Mpa\",\n    flexural_modulus: \"Mpa\",\n    izod_impact_strength: \"J/m2\",\n    heat_deflection_temp: \"℃\",\n    dielectric_strength: \"kV/mm\",\n    volume_resistivity: \"Ω·cm\",\n    density: \"g/cm3\",\n    melt_flow_rate: \"g/10min\",\n    molding_shrinkage: \"%\",\n    flammability_1_5mm: \"/\",\n    flammability_3_0mm: \"/\",\n    yellow_card: \"/\",\n    rti_elec: \"℃\",\n    rti_imp: \"℃\",\n    rti_str: \"℃\",\n    hwi: \"℃\",\n    hai: \"℃\",\n    cti: \"℃\",\n    outdoor_performance: \"/\",\n    ball_pressure_temp: \"℃\",\n    rohs: \"/\",\n    reach_svhc: \"/\",\n    quotation: \"\",\n    remarks: \"\"\n  },\n  {\n    // range field\n    label: \"Specifications\",\n    search: null,\n    tensile_strength: \"≥13\",\n    elongation_at_break: \"Tensile Strength\",\n    flexural_strength: \"≥15\",\n    flexural_modulus: \"≥800\",\n    izod_impact_strength: \"≥300\",\n    heat_deflection_temp: \"≥70\",\n    dielectric_strength: \"≥14\",\n    volume_resistivity: \"≥1E+14\",\n    density: \"0.80 - 1.25\",\n    melt_flow_rate: \"≥1.0\",\n    molding_shrinkage: \"≤1.8\",\n    flammability_1_5mm: \"V-0\",\n    flammability_3_0mm: \"5VA\",\n    yellow_card: \"/\",\n    rti_elec: \"≥80\",\n    rti_imp: \"≥80\",\n    rti_str: \"≥80\",\n    hwi: \"≤4\",\n    hai: \"≤3\",\n    cti: \"≤3\",\n    outdoor_performance: \"/\",\n    ball_pressure_temp: \"/\",\n    rohs: \"PASS\",\n    reach_svhc: \"PASS\",\n    quotation: \"\",\n    remarks: \"\"\n  }\n]\n\nWrite a multi-line fixed header based on this, using Element UI syntax, where each object corresponds to a row in the header.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Element UI table header structure correctly implemented?",
-      "description": "Verify that the table header uses proper Element UI syntax with el-table and el-table-column components. The header structure should support the multi-line fixed header requirement with correct row spans and column spans. Each object in base_data should correspond to a row in the header.Deduct 5 points if the table structure is not using Element UI components, 5 points if fixed header functionality is not implemented, and 5 points if multi-line header configuration is incorrect. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Does the implementation correctly map all data from base_data to the table?",
-      "description": "Check whether all fields from the base_data array (including testing_project, testing_standards, testing_conditions, unit, and range specifications) are properly displayed in the table header. The implementation should handle all 23+ fields without omissions.Deduct 2 points for each missing field. Deduct 5 points if data mapping is inconsistent or illogical. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is proper alignment and styling applied to the table headers?",
-      "description": "Evaluate whether the table headers use appropriate alignment (text-align), padding, and styling to ensure readability. Headers should have consistent appearance with proper text wrapping for long content.Deduct 3 points for inconsistent text alignment, 3 points for improper padding or spacing, and 4 points if long text handling causes layout issues. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the implementation include proper fixed header functionality?",
-      "description": "Check if the table implements proper fixed header functionality when scrolling, ensuring that header remains visible while scrolling through data rows. Verify that the header-with-body alignment is maintained during horizontal scrolling.Deduct 5 points if fixed header functionality is not implemented, 3 points if header-body alignment issues occur during scrolling, and 2 points if there are performance issues with large datasets. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle potential issues such as missing data fields, null values, or empty strings. Check for error handling when data structure changes or when special characters appear in the data.Evaluate whether the code can handle common abnormal situations (such as null/undefined values, empty strings, etc.) and provide fallback 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. Column filtering/sorting 2. Responsive design for different screen sizes 3. Tooltip explanations for technical terms 4. Export functionality 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 style the same element) 2. Function modules unrelated to the data display (e.g., unnecessary animations) 3. Fancy effects that affect performance (e.g., excessive DOM operations).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 component/style/logic), code reusability, and maintainability. Check if the implementation follows Vue/Element UI best practices.Deduct 5 points if global state pollution is found or component design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if proper Vue lifecycle hooks are not utilized. 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 with Element UI theme 2) Proper layout spacing and header heights 3) Consistent typography (font sizes, weights, etc.).Deduct 3 points for each crowded visual element, 5 points for inconsistent styling with Element UI standards, and 5 points for chaotic alignment of header content. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the table provides good user interaction: 1) Smooth scrolling performance 2) Responsive to screen resizing 3) Clear visual feedback for user interactions like sorting or filtering.Deduct 5 points for laggy scrolling performance with large datasets, 3 points for lack of responsive design considerations, and 5 points for missing user interaction feedback. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Education/Learning",
-  "difficulty": "easy"
-}

package/library/web_applications-education_learning/math-prize-wheel-for-students.json

@@ -1,68 +0,0 @@
-{
-  "index": 1817,
-  "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.\n\nI am a middle school math teacher who wants to reward students with excellent grades. Please help me create a prize wheel webpage with the following prizes: $5 cash, $10 cash, $20 cash, $50 cash, Study Master Time Manager, Error Correction Printer + Math Meme Tape, \"Genshin Impact\" Character Pencil Case + Function Coordinate Notebook + Draft Paper, Probability Question Mystery Box Pen, Honor of Kings Q-version Heroes + Sarcastic Quote Stickers. The webpage should have a cute style background that includes elements middle school students enjoy, with animation effects when the wheel spins.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the prize wheel core functionality fully implemented?",
-      "description": "Review whether the code accurately implements a spinning wheel mechanism through HTML5 Canvas/SVG and JavaScript, with proper physics-based deceleration and random/weighted result selection. Check if it includes prize highlighting when landing, and validation that prevents manipulation. Score 0 if the core spinning functionality is not implemented, 5 if basic spinning exists but lacks physics, and 10 if it includes realistic inertia, proper randomization, and anti-cheat mechanisms.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are all the specified prizes properly represented on the wheel?",
-      "description": "Evaluate whether all 9 required prizes ($5 cash, $10 cash, $20 cash, $50 cash, Study Master Time Manager, Error Correction Printer + Math Meme Tape, 'Genshin Impact' Character Pencil Case + Function Coordinate Notebook + Draft Paper, Probability Question Mystery Box Pen, Honor of Kings Q-version Heroes + Sarcastic Quote Stickers) are included on the wheel with equal or intentionally weighted probabilities. Deduct 1 point for each missing prize or if prizes are not clearly readable when the wheel is stationary. Full points require visually distinct prize segments with proper spacing.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the animation effect for the wheel spin implemented effectively?",
-      "description": "Check if the wheel animation includes smooth rotation transitions, proper easing functions (initial acceleration and gradual deceleration), audio feedback, and visual indicators during spinning. Score 3 points for basic rotation, 3 additional points for proper easing physics, 2 points for spinning sound effects, and 2 points for visual feedback (like sparkling effects or dynamic highlights). Ensure the animation runs at consistently smooth framerates (minimum 30 FPS).",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the implementation include a cute style background with middle school student appeal?",
-      "description": "Evaluate whether the background incorporates age-appropriate design elements that appeal to middle school students (gaming references, math symbols, colorful patterns, etc.). Background should be relevant to both prize themes (games like Genshin Impact/Honor of Kings and educational items) without overwhelming the main prize wheel. Deduct 5 points if the background is generic/stock, 3 points if it's too childish or too mature, and 3 points if it competes with or obscures the wheel functionality.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as rapid repeated clicks, browser resizing, touch vs. mouse interactions, 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. Confetti explosion for high-value prizes 2. Prize history tracking 3. Teacher controls for probability adjustment 4. Animated characters reacting to prizes 5. Math formula animations). Add 2 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 animation systems) 2. Function modules unrelated to the prize wheel (e.g., unrelated games) 3. Fancy effects that affect performance (e.g., excessive particle systems that cause lag). 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 layers), 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 (over 30%); deduct 3 points if variable naming is inconsistent or unclear. Check for browser compatibility across at least Chrome, Firefox and Safari. 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 with appropriate complementary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 16px, appropriately playful yet readable fonts). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic 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) Spin button feedback delay ≤ 100ms 2) Wheel rotation animation should be fluid (60fps if possible) 3) Clear visual and audio guidance when a prize is won. Deduct 5 points for laggy spinning animations, 3 points for missing winner announcement effects, and 5 points for unresponsive or hard-to-find spin button. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Education/Learning",
-  "difficulty": "medium"
-}

package/library/web_applications-education_learning/merge-sort-visualization.json

@@ -1,68 +0,0 @@
-{
-  "index": 1020,
-  "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 purposes. Visualization of merge sort.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the merge sort algorithm correctly implemented?",
-      "description": "Check if the algorithm follows the correct divide-and-conquer approach with proper splitting and merging steps. Verify that the time complexity is O(n log n) and space complexity is O(n). Deduct 5 points if the core algorithm has logical errors, 3 points if edge cases are not handled (empty arrays, single elements), and 2 points if unnecessary operations affect performance. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Does the visualization clearly show each step of the merge sort process?",
-      "description": "Evaluate whether the visualization distinctly represents each phase: dividing the array, comparing elements, and merging the subarrays. There should be clear visual differentiation between unsorted elements, elements being compared, and sorted subarrays. Give 0 points if the core visualization logic is missing, 5 points if only basic steps are shown, and 10 points if all merge sort phases are comprehensively visualized.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the animation of the sorting process smooth and informative?",
-      "description": "Review whether the animation flows at an appropriate pace with controls for speed adjustment. Check if transitions between steps are smooth (not abrupt) and if key comparison and swap operations are highlighted. Deduct 5 points if animations are jerky or inconsistent, 3 points if speed controls are missing, and 2 points if transitions lack clarity. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the visualization include informative metrics and educational elements?",
-      "description": "Check if the implementation displays relevant metrics such as comparison count, array access count, current recursion depth, and time/space complexity explanations. Educational tooltips or explanatory text should help users understand the algorithm's operation. Deduct 3 points for each missing key metric, and award full 10 points only if comprehensive educational elements are included.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid input types, extremely large arrays, browser compatibility issues, etc.) and provide friendly error prompts or graceful degradation. 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 array generation options with different distributions 2. Side-by-side comparison with other sorting algorithms 3. Interactive mode allowing users to perform merge steps manually). 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. Function modules unrelated to merge sort or algorithm visualization 3. Fancy effects that affect performance without adding educational value. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core visualization is interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating algorithm logic/visualization/UI controls), code reusability, and performance optimization. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the visualization stutters on arrays larger than 100 elements. 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 (logical color coding for different states) 2) Proper layout spacing (clear separation between controls and visualization area) 3) Professional font system (legible labels and explanatory text). Deduct 3 points for each crowded visual element, 5 points for confusing color schemes that don't aid understanding, and 5 points for poor arrangement of visualization 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 human perception characteristics: 1) Responsive controls with immediate visual feedback 2) Appropriate animation timing that balances educational clarity with engaging pace 3) Clear visual indication of the current state of the algorithm. Deduct 5 points for laggy animations, 3 points for confusing transitions between steps, and 5 points for controls that don't clearly indicate their function. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Education/Learning",
-  "difficulty": "medium"
-}

package/library/web_applications-education_learning/mobile-fish-recognition-webpage-tabs.json

@@ -1,68 +0,0 @@
-{
-  "index": 1750,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate, professional responses. Be sure to create executable code for demonstration purposes whenever possible. I need to create a fish recognition webpage that is optimized only for mobile devices. It should include three bottom tabs: Recognition, Records, and Personal Center. Please provide appropriate HTML code.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the fish recognition feature fully implemented?",
-      "description": "Review whether the code effectively implements the fish recognition functionality through appropriate HTML, CSS, and JavaScript. Check for proper image upload capabilities, camera access for taking fish photos, and integration with recognition API or algorithm. Score 0 if no recognition elements are present, 5 if basic image upload is implemented but without processing logic, and 10 if complete end-to-end recognition with visual feedback is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the tab navigation system properly implemented for mobile?",
-      "description": "Check whether the three-tab system (Recognition, Records, Personal Center) is properly implemented with appropriate mobile touch interactions, active state indicators, and smooth transitions between tabs. The tabs should be positioned at the bottom as specified, with proper sizing for mobile touch targets (minimum 44x44px). Deduct 5 points if tabs don't maintain state across content changes, 3 points if transition animations are missing, and 2 points if active states are not visually distinct. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the records/history management properly designed?",
-      "description": "Evaluate if the Records tab properly displays previous recognition results with timestamps, images, and identification details. Check for implementation of data persistence (localStorage, IndexedDB, or server-side storage), sorting/filtering capabilities, and the ability to view detailed information for each record. Deduct 5 points if no persistence mechanism exists, 3 points if sorting/filtering is absent, and 2 points if detailed view functionality is missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the personal center functionality properly implemented?",
-      "description": "Assess whether the Personal Center tab includes essential user management features such as profile settings, preferences, login/logout functionality, and possibly achievements or statistics related to fish recognition history. Verify if user data is properly managed and persisted. Deduct 3 points if profile customization is missing, 4 points if authentication features are absent, and 3 points if there's no integration with the recognition history. 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 image upload failures, recognition API errors, offline usage, or unexpected user inputs) 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. AR fish identification overlay 2. Social sharing with animated previews 3. Gamification elements for frequent recognition). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple image processing methods coexisting) 2. Function modules unrelated to fish recognition (e.g., a built-in game) 3. Fancy effects that affect mobile performance (e.g., heavy animations on low-end devices). 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 recognition logic/view/data layers), responsive design implementation, and mobile optimization techniques. 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 performance optimization for mobile devices is missing (e.g., no image compression before upload). The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional mobile design standards?",
-      "description": "Evaluate whether the overall design follows modern mobile design principles: 1) Touch-friendly elements (minimum tap target size of 44x44px) 2) Proper layout spacing for mobile (safe areas accounting for notches and home indicators) 3) Mobile-optimized typography (readable font sizes, minimum 16px for body text). Deduct 3 points for non-touch-friendly elements, 5 points for layouts that extend into unsafe areas, and 5 points for text that requires zooming to read. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the mobile interaction smooth and optimized?",
-      "description": "Judge whether the mobile interactions are optimized for touch devices: 1) Fast tap response ≤ 100ms 2) Proper keyboard handling for form inputs 3) Support for mobile gestures (swipe between tabs, pinch-zoom for fish images). Deduct 5 points for each operation without feedback, 3 points for keyboard issues that obscure the interface, and 5 points for missing essential mobile gestures. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Education/Learning",
-  "difficulty": "hard"
-}