npm - @getollie/cli - Versions diffs - 0.0.1 - Mend

@getollie/cli 0.0.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (1798) hide show

package/library/web_applications-web_visuals/online-editable-menu-image-exporter.json ADDED Viewed

@@ -0,0 +1,68 @@
+{
+  "index": 226,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Try to ensure that the generated code can be executed and displayed. Based on this HTML foundation, support online editing and exporting of menu images.\n\n<!DOCTYPE html>\n<html lang=\"zh-CN\">\n\n<head>\n    <meta charset=\"UTF-8\">\n    <title>Premium Home-style Restaurant Menu</title>\n    <style>\n        body {\n            font-family: 'Microsoft YaHei', sans-serif;\n            background-color: #f8f8f8;\n            padding: 30px;\n        }\n\n        .menu-card {\n            background: white;\n            border-radius: 12px;\n            box-shadow: 0 4px 15px rgba(0, 0, 0, 0.1);\n            padding: 25px;\n            max-width: 600px;\n            margin: 0 auto;\n        }\n\n        h1 {\n            text-align: center;\n            color: #c74a2a;\n            font-size: 28px;\n            margin-bottom: 25px;\n        }\n\n        .menu-table {\n            width: 100%;\n            border-collapse: collapse;\n            margin-bottom: 20px;\n        }\n\n        .menu-table th {\n            background-color: #f8f8f8;\n            font-weight: 600;\n            color: #333;\n            padding: 12px;\n        }\n\n        .menu-table td {\n            padding: 15px;\n            border-bottom: 1px solid #eee;\n            vertical-align: middle;\n        }\n\n        .combo-price {\n            text-align: right;\n            color: #c74a2a;\n            font-weight: bold;\n            width: 80px;\n        }\n\n        .additional {\n            background: #fff9f5;\n            padding: 15px;\n            border-radius: 8px;\n            margin-top: 25px;\n        }\n\n        .additional h3 {\n            color: #c74a2a;\n            margin: 0 0 12px 0;\n        }\n\n        .dish-item {\n            display: flex;\n            justify-content: space-between;\n            padding: 8px 0;\n            border-bottom: 1px dashed #ddd;\n        }\n\n        .price-tag {\n            color: #c74a2a;\n            font-size: 16px;\n        }\n    </style>\n</head>\n\n<body>\n    <div class=\"menu-card\">\n        <h1>Premium Home-style Restaurant</h1>\n        <p style=\"text-align: center; color: #666; margin-bottom: 25px;\">\n            March 28th Lunch Menu\n        </p>\n\n        <!-- Set Meal Combinations -->\n        <table class=\"menu-table\">\n            <thead>\n                <tr>\n                    <th>Set Meal Combinations</th>\n                    <th class=\"combo-price\">Price</th>\n                </tr>\n            </thead>\n            <tbody>\n                <tr>\n                    <td>Main Meat Dish + Small Meat Dish + Vegetable</td>\n                    <td class=\"combo-price\">¥16</td>\n                </tr>\n                <tr>\n                    <td>2 Main Meat Dishes + Small Meat Dish + Vegetable</td>\n                    <td class=\"combo-price\">¥22</td>\n                </tr>\n            </tbody>\n        </table>\n\n        <!-- Additional Options -->\n        <div class=\"additional\">\n            <h3>Additional Options</h3>\n            <ul>\n                <li>Main Meat Dish ¥8, Small Meat Dish ¥4, Vegetable ¥2</li>\n            </ul>\n        </div>\n\n    <hr></hr>\n\n        <table class=\"menu-table\">\n            <thead>\n                <tr>\n                    <th>Rice with Toppings</th>\n                    <th class=\"combo-price\">Price</th>\n                </tr>\n            </thead>\n            <tbody>\n                <tr>\n                    <td>Homestyle Stir-fried Pork</td>\n                    <td class=\"combo-price\">¥16</td>\n                </tr>\n                <tr>\n                    <td>Kung Pao Chicken</td>\n                    <td class=\"combo-price\">¥14</td>\n                </tr>\n            </tbody>\n        </table>\n    </div>\n</body>\n\n</html>",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is online menu editing functionality fully implemented?",
+      "description": "Review whether the code includes a complete editing system allowing users to modify menu items, prices, categories, and descriptions. Check for content validation, input field constraints, and real-time preview. Score 0 if no editing features exist, 5 if only basic text editing is supported, and 10 if comprehensive menu structure editing with validation is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the menu image export functionality properly implemented?",
+      "description": "Evaluate the export functionality for converting the menu to image format (PNG/JPEG/SVG). Check for proper rendering of all elements including special characters, custom fonts, and layout preservation. Score 0 if no export feature exists, 5 if basic screenshot functionality is available but with quality/formatting issues, and 10 if high-quality image export with customization options (resolution, format, crop area) is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the menu structure data model well-designed?",
+      "description": "Assess whether the code uses a structured data model (JSON/object) to represent menu items, categories, and pricing, enabling clean separation between data and presentation. Check if the model allows for dynamic updates and maintains data integrity. Deduct 5 points if global variables are overused; deduct 5 points if the data structure doesn't support menu hierarchy. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are interactive UI elements properly implemented for editing?",
+      "description": "Review the implementation of UI controls (buttons, form fields, dropdowns) for editing menu content. Check for consistent interaction patterns, visual feedback on actions, and clear edit/save states. Deduct 5 points for poor accessibility (no keyboard support, missing ARIA attributes); deduct 3 points if the interface lacks clear visual indication of editable elements. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid input data, image generation failures, 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 the experience (e.g., 1. Template gallery with different menu styles 2. QR code generation for digital menu sharing 3. Multilingual support 4. Print-optimized view). 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 export methods doing the same thing) 2. Function modules unrelated to menu editing/export (e.g., unnecessary animations) 3. Fancy effects that affect performance (e.g., heavy decorative elements that slow rendering). 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 menu data/view/controller layers), browser compatibility, 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 code doesn't handle different device screen sizes. 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 editing operations, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Web Visuals",
+  "difficulty": "hard"
+}

package/library/web_applications-web_visuals/online-network-topology-editor-antv-g6.json ADDED Viewed

@@ -0,0 +1,68 @@
+{
+  "index": 1277,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Pay attention to ensuring that the generated code is executable for demonstration. So, based on this web server and combining with AntV G6, develop an online network topology diagram editing tool.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core graph editing functionality properly implemented?",
+      "description": "Review whether the code correctly implements node creation, edge connection, selection, and basic editing operations using AntV G6. Check if the topology editing interface includes essential operations like add/delete/move nodes, connect/disconnect edges, and group/ungroup elements. Score 0 if the core editing functions are missing, 5 if only basic operations are implemented, and 10 if a comprehensive set of topology editing features is available.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the network topology data structure well-designed?",
+      "description": "Evaluate if the code implements an appropriate data structure for representing network topology (nodes, edges, groups, attributes). Check if the structure supports topology validation, cycle detection, and maintains referential integrity. Deduct 5 points if the data structure doesn't allow for custom node/edge properties, and 3 points if it doesn't handle hierarchical relationships. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is a proper server integration implemented for topology persistence?",
+      "description": "Check if the code includes proper API integration with the web server for saving, loading, and versioning topology diagrams. Verify if the implementation handles concurrent editing conflicts, provides auto-save functionality, and includes error recovery. Deduct 5 points if server synchronization is missing, and 3 points if there's no offline editing capability. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are advanced topology visualization features implemented?",
+      "description": "Assess whether the tool implements advanced visualization features like automatic layout algorithms, mini-map navigation, zoom/pan controls, and custom styling options. Check if it includes filtering/search capabilities for large topologies. Score 10 points for comprehensive visualization features with performance optimization, 5 points for basic functionality, and 0 if advanced features are missing.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid topology configurations, server connection failures, concurrent editing conflicts, 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 collaborative editing 2. Topology validation and error checking 3. Network simulation capabilities 4. AI-assisted layout suggestions). 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 node creation workflows) 2. Function modules unrelated to network topology editing (e.g., unnecessary analytics) 3. Fancy effects that affect performance (e.g., excessive animations or 3D 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 modular design (such as separating data model/view/controller layers), efficient use of AntV G6 API, proper event handling, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching for topology elements (distinguishable but not jarring) 2) Proper layout of toolbars and editing panels (following standard UX patterns) 3) Professional typography and iconography for network elements. Deduct 3 points for cluttered toolbars, 5 points for poor visual hierarchy, and 5 points for inconsistent node/edge styling. 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 node dragging with < 50ms latency 2) Smooth zooming and panning with proper acceleration/deceleration 3) Clear visual feedback during edge creation and connection. Deduct 5 points for laggy graph manipulation, 3 points for jumpy animations during layout changes, and 5 points for confusing interaction models. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Web Visuals",
+  "difficulty": "medium"
+}

package/library/web_applications-web_visuals/panoramic-photo-project-vue3-threejs.json ADDED Viewed

@@ -0,0 +1,68 @@
+{
+  "index": 881,
+  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable when possible. Create a panoramic photo project using the Vue3 and Three.js technology stack.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Three.js panoramic rendering core fully implemented?",
+      "description": "Review whether the code correctly implements panoramic image mapping using Three.js SphereGeometry or BoxGeometry, including proper texture loading, UV mapping, and camera controls for 360-degree viewing. Score 0 if basic panoramic display is not working, 5 if only static panoramic view is implemented, and 10 if full interactive panoramic rendering with proper geometry and materials is完整implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the Vue3 integration architecture properly designed?",
+      "description": "Check whether the Vue3 Composition API is correctly integrated with Three.js lifecycle, including proper reactive state management, component mounting/unmounting handling, and memory cleanup. Evaluate if ref/reactive are used appropriately for Three.js objects. Deduct 5 points if memory leaks are present, and 3 points if Vue reactivity conflicts with Three.js rendering loop. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are interactive controls and navigation mechanisms implemented?",
+      "description": "Evaluate whether mouse/touch controls for panoramic navigation are smooth and intuitive, including orbit controls, zoom functionality, and mobile device support. Check if control sensitivity is adjustable and if there are proper boundaries to prevent disorientation. Deduct 5 points if mobile touch controls are missing, and 3 points if zoom limits are not implemented. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the panoramic asset loading and optimization system complete?",
+      "description": "Check whether the code includes efficient image loading with progress indicators, supports multiple panoramic formats (equirectangular, cube maps), and implements proper error handling for failed loads. Evaluate if image preprocessing and compression are considered. Deduct 5 points if no loading states are shown, and 3 points if large images cause performance issues. Give 10 points if fully optimized with lazy loading and multiple format support.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as WebGL compatibility issues, image loading failures, browser resize events, device orientation changes, etc.) and provide friendly error prompts or fallback mechanisms. Code with strong robustness should effectively handle these edge cases, giving 10 points. If robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there innovative features that enhance the panoramic experience?",
+      "description": "Check whether the code includes advanced features that elevate the user experience (e.g., 1. Hotspot annotations with interactive tooltips 2. Multiple panoramic scene transitions 3. Mini-map navigation 4. VR mode compatibility 5. Auto-rotation with pause on interaction). Add 2-3 points for each well-implemented innovative feature (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features or unnecessary complexity?",
+      "description": "Strictly check three types of redundancy: 1. Redundant Three.js scene/renderer instances 2. Unnecessary Vue components that don't contribute to panoramic functionality 3. Over-engineered animations or effects that impact performance without adding value. Deduct 3 points for each redundancy found, and directly deduct 10 points if core panoramic functionality is compromised by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code demonstrate high engineering quality?",
+      "description": "Review modular architecture (separating Three.js logic, Vue components, and utility functions), TypeScript usage for better type safety, and proper build configuration. Deduct 5 points if global state pollution is found or if Three.js objects are not properly disposed; deduct 5 points if code organization is poor with high coupling; deduct 5 points if build process lacks optimization for 3D assets. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface design meet professional visual standards?",
+      "description": "Evaluate whether the UI overlay design follows modern principles: 1) Clean control interface that doesn't obstruct the panoramic view 2) Intuitive iconography for navigation controls 3) Proper contrast and visibility across different panoramic backgrounds 4) Responsive design for various screen sizes. Deduct 3 points for each poorly designed control element, 5 points for controls that interfere with panoramic viewing, and 5 points for poor mobile responsiveness. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Are the panoramic interactions smooth and performant?",
+      "description": "Judge whether the panoramic navigation meets performance standards: 1) Smooth 60fps rendering during navigation 2) Responsive controls with <50ms input delay 3) Smooth transitions between different viewing angles 4) Proper performance on mobile devices. Deduct 5 points for each noticeable frame drop during interaction, 3 points for laggy controls, and 5 points if mobile performance is significantly degraded. Full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Web Visuals",
+  "difficulty": "easy"
+}

package/library/web_applications-web_visuals/prize-drawing-webpage-with-admin-panel.json ADDED Viewed

@@ -0,0 +1,68 @@
+{
+  "index": 1626,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable and displayable. Help me create a prize drawing webpage with an admin panel that allows adjusting prize names and winning probabilities. The admin panel password is 123456789987654321. There should be a popup notification when a prize is won.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the prize drawing core mechanism properly implemented?",
+      "description": "Review whether the code accurately implements a weighted random selection algorithm based on configured probabilities. Check if the probability distribution is correctly calculated and if the random number generation is properly seeded. Score 0 if the core drawing mechanism is missing, 5 if basic random selection is implemented without weighting, and 10 if the weighted probability system is fully implemented with proper verification that actual results match the configured odds.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the admin panel functionality complete and secure?",
+      "description": "Evaluate whether the admin panel allows comprehensive prize management (adding, editing, deleting prizes and adjusting their probabilities). Check if the authentication mechanism is properly implemented with the specified password (123456789987654321). Deduct 5 points if the password is stored in plain text or visible in client-side code, 3 points if CSRF protection is missing, and 3 points if there's no session timeout. Give 10 points if the admin panel is fully functional and reasonably secure.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the prize notification system properly implemented?",
+      "description": "Check whether the popup notification appears when a prize is won, with appropriate animation and visibility. Evaluate if the notification includes all relevant prize details and is properly positioned. Deduct 5 points if the notification is not visually distinct, 3 points if it lacks animation, and 5 points if it disappears too quickly or doesn't have a dismissal option. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is data persistence implemented for configuration and results?",
+      "description": "Assess whether the application properly stores prize configurations and drawing history. Check if localStorage/sessionStorage is used for client-side persistence or if server-side storage is implemented. Verify if data is properly loaded when the page initializes. Deduct 5 points if prize configurations are lost on page refresh, 3 points if there's no drawing history, and 5 points if there's no export/backup functionality. 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 probability inputs, empty prize lists, concurrent admin operations, 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. Visual drawing animation with suspense 2. Confetti/celebration effects for winners 3. Statistics dashboard of historical draws). 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 functions (e.g., multiple prize drawing algorithms coexisting) 2. Function modules unrelated to prize drawing (e.g., unnecessary third-party widgets) 3. Fancy effects that affect performance (e.g., excessive animations that slow down the interface). 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 layers), code reusability, 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 5 points if there are no comments on complex logic. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows 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 jarring during animations, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Web Visuals",
+  "difficulty": "easy"
+}

package/library/web_applications-web_visuals/python-semantic-ui-webpage-creation.json ADDED Viewed

@@ -0,0 +1,68 @@
+{
+  "index": 969,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. You're a code expert. Please use your professional knowledge to generate accurate and expert responses. Be sure the code you generate is executable for demonstration. Create a simplified webpage using Python with Semantic UI.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Python web framework properly implemented?",
+      "description": "Evaluate whether the code correctly uses a Python web framework (Flask, Django, etc.) with proper routing, request handling, and serving static files. Check for middleware configuration, environment variable handling, and appropriate HTTP response codes. Score 0 if no framework is used, 5 if basic implementation is present but with flaws, 10 if properly implemented with error handling.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is Semantic UI correctly integrated?",
+      "description": "Check if Semantic UI CSS/JS files are properly linked (either via CDN or local installation), and whether the correct version is specified. Verify that Semantic UI components are used according to documentation standards with proper class names and nesting. Deduct 5 points if linked incorrectly, 3 points if outdated version used, and 2 points if JS initialization is missing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Does the webpage have a responsive design?",
+      "description": "Analyze whether the webpage uses Semantic UI's responsive grid system correctly, with proper breakpoints for different screen sizes. Check if the layout adjusts appropriately on mobile, tablet and desktop views. Deduct 5 points if no responsive grid is implemented, 3 points if elements overflow on small screens, and 2 points if mobile menu is missing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are Semantic UI components used effectively?",
+      "description": "Evaluate the appropriate use of Semantic UI components (menus, cards, buttons, forms, etc.) according to their intended purpose. Check for proper semantic markup with correct class hierarchies. Deduct 3 points for each improperly used component, 2 points for missing interactive behaviors, and 5 points if no Semantic UI-specific components are used. 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 form validation errors, missing data, server 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. Dynamic theme switching 2. Custom animations with Semantic UI transitions 3. Interactive data visualizations). 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 imports or libraries that aren't used 2. Over-engineered solutions for simple tasks 3. Excessive use of Semantic UI components where simpler HTML would suffice. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functionality is overcomplicated by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating routes/templates/static files), appropriate commenting, and adherence to Python best practices (PEP 8). Deduct 5 points for global variable abuse or non-idiomatic Python; deduct 5 points if the code structure is monolithic; deduct 5 points if there's no separation of concerns. 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 consistent principles) 3) Professional typography (appropriate font sizes and legibility). 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 transitions, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Web Visuals",
+  "difficulty": "easy"
+}

package/library/web_applications-web_visuals/react-ant-design-text-flipping-function.json ADDED Viewed

@@ -0,0 +1,68 @@
+{
+  "index": 1425,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the code you generate is executable and can be demonstrated. Please help me write a text flipping function using React and Ant Design UI.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the text flipping function core implementation complete?",
+      "description": "Examine whether the React component properly implements text flipping animation with appropriate state management. Check if it handles different text types (single/multi-line), allows configuration of flipping direction (horizontal/vertical), and maintains text readability during animation. Score 0 if core flipping functionality is missing, 5 for basic implementation, 10 if fully configurable with multiple animation options.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is Ant Design UI properly integrated?",
+      "description": "Verify that the implementation correctly uses Ant Design components following their API specifications rather than just basic HTML elements. Check if proper Ant Design theming is applied, component props are used correctly, and the solution follows Ant Design's design principles. Deduct 5 points if Ant Design is barely used, 3 points if used incorrectly or inconsistently. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the component flexible and customizable?",
+      "description": "Evaluate if the component accepts customization props for animation speed, timing functions, delay, text content, styles, and integration with other Ant Design components. Check if it exposes appropriate callback events (onFlipStart, onFlipComplete). Deduct 3 points for each missing essential customization option. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is accessibility properly implemented?",
+      "description": "Check if the text flipping animation is accessible - including proper ARIA attributes, keyboard navigability, respecting reduced motion preferences, and maintaining text contrast during animation. The component should work with screen readers and include proper focus management. Deduct 3 points for each accessibility issue found. 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 text, extremely long text, rapid state changes, etc.) and provide friendly error handling or 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. 3D perspective flipping effects 2. Ability to flip only portions of text or characters sequentially 3. Integration with React transitions/motion libraries like react-spring). 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 state management (e.g., duplicate state for the same functionality) 2. Unnecessary re-renders caused by implementation issues 3. Fancy effects that affect performance without adding value to the text flipping functionality. 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 component structure (separation of concerns, proper hooks usage), TypeScript/PropTypes usage, and code organization. Deduct 5 points if props are not properly typed or documented; deduct 5 points if there are useState/useEffect anti-patterns; deduct 5 points if the component structure violates React best practices. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the flipping animation follows modern design principles: 1) Smooth transitions with appropriate easing functions 2) Maintains visual hierarchy during animation 3) Follows Ant Design's aesthetic guidelines. Deduct 3 points for jarring or disruptive animations, 5 points for animations that make text difficult to read, and 5 points for designs that clash with Ant Design's visual language. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the animation performs well: 1) Animation runs at 60fps without frame drops 2) Transition duration is appropriate (300-500ms) 3) Animation doesn't cause layout shifts or reflows. Deduct 5 points for each noticeable performance issue, 3 points for animations that feel too fast or too slow, and 5 points for animations that cause visual glitches or browser rendering issues. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Web Visuals",
+  "difficulty": "easy"
+}

package/library/web_applications-web_visuals/react-antd-windows-desktop-menu-design.json ADDED Viewed

@@ -0,0 +1,68 @@
+{
+  "index": 1483,
+  "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. React+antd4 javascript simulating Windows desktop menu design.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Windows desktop menu structure accurately implemented?",
+      "description": "Review whether the code accurately implements the hierarchical structure of a Windows desktop menu, including Start menu, right-click context menus, taskbar interactions, and system tray functionality. Score 0 if none of these elements are implemented, 5 if only basic menu structure exists, and 10 if the implementation includes cascading menus, proper grouping, and visual separators matching Windows standards.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are the essential Windows menu interactions implemented?",
+      "description": "Check whether all core Windows menu interactions are implemented: click and hover behaviors, keyboard navigation support (Tab, arrows, shortcuts), and proper focus management. Deduct 3 points if keyboard accessibility is missing, 3 points if hover states are incorrect, and 3 points if focus behavior doesn't match Windows patterns. Full score requires implementing Esc key to close menus and proper event bubbling prevention.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the visual styling faithful to Windows design patterns?",
+      "description": "Evaluate whether the styling properly follows Windows desktop UI standards, including correct colors, borders, shadows, fonts (Segoe UI), and spacing. Look for accurate implementation of hover/focus/active states, highlighting of selected items, and proper icons. Deduct 5 points if the styling lacks key Windows visual cues, and 3 points if animations (like fade/slide effects) are missing or incorrect.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the implementation integrate React with Ant Design effectively?",
+      "description": "Assess the technical integration between React and Ant Design components. Check for proper use of Ant Design's Menu, Dropdown, and Popover components while maintaining Windows aesthetics. Review the component structure for logical hierarchy and reuse. Deduct 5 points if Ant Design components are significantly customized to mimic Windows style (contradicting library purpose), and 3 points if React hooks usage is suboptimal.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code handles edge cases such as dynamic menu content, window resizing, screen boundaries for submenus, empty menu states, and long menu item text. Code with strong robustness should prevent menu overflow outside viewport boundaries and handle high-contrast modes. Score 10 points if all edge cases are handled, 5 points if only basic error handling exists, and 0 points if no robustness considerations are present.",
+      "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. Live folder previews, 2. Recent files integration, 3. Custom theme support like Windows theme switching, 4. Drag and drop reordering of menu items). 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 menu opening mechanisms) 2. Function modules unrelated to Windows desktop experience (e.g., unnecessary animations) 3. Complex features that affect performance (e.g., excessive DOM nesting or unnecessary re-renders). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core Windows menu experience is compromised by extraneous code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating menu components/logic/styles), proper React patterns (hooks, context API usage, memoization), and component reusability. Deduct 5 points if global state management is poor or prop drilling is excessive; deduct 3 points if component responsibilities are poorly defined; deduct 3 points if performance optimizations like React.memo or useMemo are missing where needed. 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 Windows design principles: 1) Proper color palette matching Windows themes 2) Consistent padding and margins (8px grid system) 3) Appropriate font usage (Segoe UI or system-ui, proper sizing hierarchy). Deduct 3 points for each UI element that breaks Windows consistency, 5 points for significant visual discrepancies from Windows standards, 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 menu interactions feel native to Windows: 1) Opening/closing animations match Windows speed (200-250ms) 2) Click response feels immediate (≤100ms) 3) Submenu flyouts appear with appropriate timing and direction. Deduct 5 points for janky animations, 3 points for menu flickering during interactions, and 5 points for noticeable delays in menu response. Check if hovering behavior for cascading menus follows Windows patterns with appropriate timing. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Web Visuals",
+  "difficulty": "easy"
+}

package/library/web_applications-web_visuals/react-single-page-application-development.json ADDED Viewed

@@ -0,0 +1,68 @@
+{
+  "index": 1096,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code whenever possible. Use React to build a single-page application.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is a complete React single-page application structure implemented?",
+      "description": "Check if the code includes essential React application components: entry point (index.js/tsx), App component, routing system, and proper component hierarchy. Verify that create-react-app or another modern React setup is properly configured. Score 0 if only fragments are provided without a proper structure, 5 if basic structure exists but lacks organization, and 10 if a complete, well-organized SPA structure is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Does the application implement proper routing and navigation?",
+      "description": "Evaluate if React Router (or equivalent) is properly implemented with multiple routes, navigation components, and guards for protected routes if applicable. Check for URL parameter handling and proper history management. Deduct 3 points if only basic routing exists without nested routes, 5 points if there's no 404 handling, and 3 points if navigation state isn't preserved between rerenders. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is state management implemented effectively?",
+      "description": "Assess state management approach (useState, useReducer, Redux, Context API, etc.). Verify that global and component state are appropriately separated, and state updates don't cause unnecessary re-renders. Deduct 5 points for prop drilling beyond 3 levels, 3 points for inefficient state updates causing performance issues, and 5 points if no centralized state management is used when clearly needed. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are React hooks used correctly and optimally?",
+      "description": "Check for proper implementation of React hooks (useState, useEffect, useCallback, useMemo, useRef, etc.) and adherence to the Rules of Hooks. Watch for dependency arrays in useEffect and memoization hooks. Deduct 3 points for each hook rule violation, 5 points for memory leaks in useEffect, and 5 points for excessive re-renders due to improper hook usage. 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 API failures, invalid user inputs, loading states, etc.) and provide friendly error boundaries 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. Performance optimizations like virtualized lists 2. Accessibility features beyond basic ARIA 3. Progressive Web App capabilities). 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 state management solutions coexisting) 2. Function modules unrelated to core requirements 3. Fancy effects that affect performance (e.g., excessive animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review component structure (atomic design principles, reusability), code splitting implementation, and build process optimization. Deduct 5 points if components exceed 300 lines; deduct 3 points if prop types or TypeScript types are missing; deduct 5 points if no code splitting is implemented for larger bundles. Check for ESLint/Prettier configuration. 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) Consistent component styling (e.g., using styled-components, CSS modules, or a UI library) 2) Proper responsive design with media queries or fluid layouts 3) Professional typography system with proper hierarchy. Deduct 3 points for inconsistent styling between components, 5 points for non-responsive layouts, and 5 points for accessibility issues (contrast, focus indicators). 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) Loading states for asynchronous operations 2) Smooth transitions between routes with proper animations 3) Form validation with immediate feedback. Deduct 5 points for missing loading indicators, 3 points for jarring page transitions, and 5 points for delayed user feedback after actions. Check for optimization techniques like debouncing for search inputs. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Web Visuals",
+  "difficulty": "easy"
+}