@getollie/cli 0.0.4 → 0.2.0

package/library/web_applications-other/real-estate-vr-showcase.json

@@ -1,68 +0,0 @@
-{
-  "index": 533,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code when possible. Create a real estate showcase website with virtual reality (VR) functionality. The homepage should feature a full-screen video background with a transparent navigation bar at the top. The property listing page should use a card layout, with each card displaying brief information and a 360° panorama preview icon when hovered over. Clicking on a property card takes users to a detail page, where the top section displays a property photo carousel with thumbnail navigation and gesture-based swiping. Add a 3D floor plan viewer that allows users to switch between different floors and room views. Implement a VR house tour feature where users can virtually navigate through rooms using VR glasses or their phone's gyroscope. Add a property comparison tool that can simultaneously compare multiple properties' features and prices.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the homepage with full-screen video background and transparent navigation properly implemented?",
-      "description": "Review whether the code correctly implements a full-screen video background with autoplay, appropriate compression for performance, and fallback content. The navigation bar should have proper transparency effects with readable text that remains visible against varying video backgrounds. Score 0 if none implemented, 5 if basic implementation with flaws (e.g., poor mobile responsiveness, performance issues with video), 10 if flawlessly implemented with responsive design and performance optimization.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the property listing page with card layout and 360° preview functionality properly implemented?",
-      "description": "Check if the property cards display essential information (price, location, bedrooms, bathrooms) in an organized layout. Each card should show a 360° panorama icon on hover, with proper transitions. Score 0 if card layout is missing, 5 if cards exist but lack hover effects or have poor responsive design, and 10 if cards are fully functional with smooth hover transitions and optimized loading of preview thumbnails.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the property detail page with photo carousel and thumbnail navigation effectively implemented?",
-      "description": "Evaluate the implementation of the photo carousel with gestures for swiping on mobile and tablet devices. Check if thumbnail navigation properly syncs with the main carousel view. Score 0 if carousel is absent, 5 if basic carousel exists but lacks gesture support or thumbnail navigation, and 10 if fully implemented with smooth transitions, preloading of adjacent images, and proper touch/mouse event handling.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are the 3D floor plan viewer and VR house tour features properly implemented?",
-      "description": "Assess whether the 3D floor plan viewer can switch between different floors and room views as specified. The VR tour should work with both VR glasses and phone gyroscopes. Score 0 if features are missing, 5 if implemented but with limited functionality (e.g., only works on certain devices, poor performance), and 10 if fully implemented with optimized 3D rendering, appropriate textures, and smooth navigation controls.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as missing property data, slow network connections, browser compatibility issues, device orientation changes) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. AI-powered property recommendations 2. Augmented reality measurement tools for room dimensions 3. Virtual furniture placement to visualize spaces). 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 viewers with overlapping purposes) 2. Function modules unrelated to real estate showcase (e.g., unnecessary social media feeds) 3. Fancy effects that affect performance (e.g., excessive particle animations in background). 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, data fetching, and 3D/VR rendering services), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern real estate website principles: 1) Harmonious color matching that reflects luxury/comfort (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) VR navigation responds within 100ms to prevent motion sickness 2) 3D floor plan interactions feel natural with appropriate weight/physics 3) Clear visual cues for interactive elements vs. static content. Deduct 5 points for each operation without feedback, 3 points for jitter or frame drops during VR navigation, and 5 points for disorienting transitions between views. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Online Shopping",
-  "difficulty": "medium"
-}

package/library/web_applications-other/vue-spring-movie-seat-selection.json

@@ -1,68 +0,0 @@
-{
-  "index": 237,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable for demonstration.\n\n<template>\n  <div id=\"app\">\n    <!-- Global navigation bar -->\n    <nav class=\"navbar\">\n      <div class=\"container\">\n        <!-- Logo on the left -->\n        <router-link to=\"/movielist\" class=\"logo\">Movie Ticket Booking System</router-link>\n\n        <!-- Login and registration links on the right -->\n        <div class=\"auth-links\">\n          <router-link to=\"/login\" class=\"auth-link\">Login</router-link>\n          <router-link to=\"/register\" class=\"auth-link\">Register</router-link>\n        </div>\n      </div>\n    </nav>\n\n    <!-- Main content area -->\n    <main class=\"main-content\">\n      <router-view></router-view> <!-- Dynamically render route components -->\n    </main>\n\n    <!-- Global footer -->\n    <footer class=\"footer\">\n      <div class=\"container\">\n        <p>&copy; 2023 Movie Ticket Booking System. All rights reserved.</p>\n      </div>\n    </footer>\n  </div>\n</template>\n\n<script>\nexport default {\n  name: 'App',\n};\n</script>\n\n<style>\n/* Global styles */\nbody {\n  margin: 0;\n  font-family: Arial, sans-serif;\n}\n\n#app {\n  display: flex;\n  flex-direction: column;\n  min-height: 100vh;\n}\n\n.navbar {\n  background-color: #333;\n  color: white;\n  padding: 10px 0;\n  position: sticky; /* Fixed navigation bar */\n  top: 0; /* Fixed at the top */\n  z-index: 1000; /* Ensure navigation bar is on top layer */\n}\n\n.navbar .container {\n  display: flex;\n  justify-content: space-between; /* Left and right alignment */\n  align-items: center;\n  max-width: 1200px;\n  margin: 0 auto;\n  padding: 0 20px;\n}\n\n.navbar .logo {\n  color: white;\n  text-decoration: none;\n  font-size: 20px;\n  font-weight: bold;\n}\n\n.auth-links {\n  display: flex;\n  gap: 15px; /* Space between login and register links */\n}\n\n.auth-link {\n  color: white;\n  text-decoration: none;\n  font-size: 14px;\n}\n\n.auth-link:hover {\n  text-decoration: underline;\n}\n\n.main-content {\n  flex: 1;\n  padding: 20px;\n  max-width: 1200px;\n  margin: 0 auto;\n}\n\n.footer {\n  background-color: #333;\n  color: white;\n  text-align: center;\n  padding: 5px 0;\n  position: sticky; /* Fixed navigation bar */\n  bottom: 0; /* Fixed at the bottom */\n  z-index: 1000; /* Ensure navigation bar is on top layer */\n}\n</style>\n\nThis is the frontend homepage. The schedules table structure is:\nCREATE TABLE `schedules` (\n  `schedule_id` int NOT NULL AUTO_INCREMENT,\n  `movie_id` int NULL DEFAULT NULL,\n  `movie_name` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL,\n  `hall_id` int NULL DEFAULT NULL,\n  `hall_name` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL,\n  `start_time` datetime NULL DEFAULT NULL,\n  `end_time` datetime NULL DEFAULT NULL,\n  `price` decimal(38, 2) NOT NULL,\n  PRIMARY KEY (`schedule_id`) USING BTREE,\n  INDEX `movie_id`(`movie_id` ASC) USING BTREE,\n  INDEX `hall_id`(`hall_id` ASC) USING BTREE,\n  CONSTRAINT `schedules_ibfk_1` FOREIGN KEY (`movie_id`) REFERENCES `movies` (`movie_id`) ON DELETE RESTRICT ON UPDATE RESTRICT,\n  CONSTRAINT `schedules_ibfk_2` FOREIGN KEY (`hall_id`) REFERENCES `halls` (`hall_id`) ON DELETE RESTRICT ON UPDATE RESTRICT\n)\n\nThe halls table structure is:\nDROP TABLE IF EXISTS `halls`;\nCREATE TABLE `halls` (\n  `hall_id` int NOT NULL AUTO_INCREMENT,\n  `name` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL,\n  `seat_count` int NOT NULL,\n  `layout` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL,\n  `equipment` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL,\n  PRIMARY KEY (`hall_id`) USING BTREE\n)\n\nThe seats table structure is:\nDROP TABLE IF EXISTS `seats`;\nCREATE TABLE `seats` (\n  `seat_id` int NOT NULL AUTO_INCREMENT,\n  `hall_id` int NULL DEFAULT NULL,\n  `row_number` int NULL DEFAULT NULL,\n  `column_letter` int NULL DEFAULT NULL,\n  `is_available` tinyint(1) NULL DEFAULT 1,\n  PRIMARY KEY (`seat_id`) USING BTREE,\n  INDEX `hall_id`(`hall_id` ASC) USING BTREE,\n  CONSTRAINT `seats_ibfk_1` FOREIGN KEY (`hall_id`) REFERENCES `halls` (`hall_id`) ON DELETE RESTRICT ON UPDATE RESTRICT\n)\n\nPlease provide the implementation code for movie screening selection and seat selection, using Vue 3 for frontend and Spring Boot for backend implementation.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the movie screening selection feature fully implemented?",
-      "description": "Review whether the code provides a comprehensive movie screening selection interface with appropriate filters (by date, time, genre), clear display of available screenings with essential details (movie title, hall, start time, end time, price), and proper integration with the backend API. The component should handle loading states and errors gracefully.Score 0 if the feature is completely missing, 5 if only basic listing is implemented without filtering, and 10 if all functionality including advanced filtering, pagination, and sorting is properly implemented with proper state management.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the seat selection functionality complete and intuitive?",
-      "description": "Evaluate the seat selection interface for visual representation of the theater layout, clear indication of available/unavailable seats, ability to select/deselect seats, and real-time feedback. Check if the implementation retrieves seat data from the backend correctly and validates selected seats against the database before proceeding to checkout.Score 0 if seat selection is not implemented, 5 if basic functionality exists but lacks visual representation or validation, and 10 if the feature offers an intuitive theater layout view with color-coded seats, responsive selection, and proper backend validation.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are the Spring Boot backend endpoints properly implemented for the required functionality?",
-      "description": "Check if the backend provides all necessary REST endpoints for retrieving schedules, hall information, seat availability, and processing seat reservations. Verify that the endpoints implement proper error handling, input validation, and follow RESTful design principles. The API should handle concurrent seat selection scenarios correctly.Score 0 if backend endpoints are missing, 5 if basic endpoints exist but lack proper validation or concurrency handling, and 10 if all required endpoints are implemented with comprehensive error handling, validation, and transaction management.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there proper integration between Vue 3 frontend and Spring Boot backend?",
-      "description": "Assess how well the Vue 3 components interact with Spring Boot endpoints. Check for proper API calls using Axios or Fetch, appropriate handling of responses and errors, and consistent data structures between frontend and backend. Verify that the integration handles authentication for protected endpoints if applicable.Score 0 if integration is missing, 5 if basic integration exists but with inconsistent error handling or data structures, and 10 if the integration is seamless with proper loading states, error handling, and consistent data formats.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as network failures, concurrent seat bookings, invalid user inputs) and provide friendly error prompts or recovery mechanisms. Check if proper validations are in place for all user inputs and if the system can handle edge cases gracefully.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 seat availability updates 2. Interactive seat price visualization 3. Recommended seating based on group size 4. Virtual theater view with screen perspective).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 select seats) 2. Function modules unrelated to movie booking (e.g., unnecessary social features) 3. Fancy effects that affect performance (e.g., excessive animations that slow down the booking process).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 presentation/business logic/data access layers), component reusability, state management approach, and build process automation. Examine the code structure, naming conventions, and adherence to Vue 3 and Spring Boot best practices.Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the 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 seat selection and screening interfaces follow modern design principles: 1) Harmonious color matching that clearly indicates seat availability status 2) Proper layout spacing that makes the theater layout easy to understand 3) Professional typography with clear labeling of rows, columns, and screen position.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) Immediate feedback when selecting/deselecting seats 2) Smooth transitions when filtering movie screenings 3) Clear visual cues for selected seats and pricing updates. Pay special attention to how the system handles concurrent selections by different users.Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast interactions, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Online Shopping",
-  "difficulty": "easy"
-}

package/library/web_applications-other/web-30-minute-countdown-timer.json

@@ -1,68 +0,0 @@
-{
-  "index": 412,
-  "question": "You are a coding expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable for demonstration purposes. Please create a 30-minute countdown timer webpage and output it in HTML format.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core countdown timer functionality fully implemented?",
-      "description": "Review whether the code accurately implements a 30-minute countdown timer with proper time calculations. Check for accurate second-by-second countdown, correct time formatting (MM:SS), and proper termination when reaching zero. Score 0 if the timer doesn't work at all, 5 if it has minor time calculation errors, and 10 if it precisely counts down from 30 minutes to zero.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are essential timer controls implemented?",
-      "description": "Evaluate whether the timer includes necessary control functions such as start, pause, resume, and reset. Each function should work correctly without glitches. Deduct 3 points if any single control is missing, and 5 points if controls are present but malfunction. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is visual feedback provided during countdown?",
-      "description": "Check whether the timer provides visual feedback during the countdown process. This could include changing colors as time decreases, progress indicators, or visual cues when reaching specific time thresholds (e.g., last 5 minutes, last minute). Deduct 5 points if no visual feedback exists beyond the numbers changing, give 5 points for basic visual feedback, and 10 points for comprehensive visual indicators that enhance user awareness of time progression.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there audio/visual notification when the timer ends?",
-      "description": "Evaluate whether the timer provides clear indication when it reaches zero. This should include visual alerts (color change, animation) and ideally audio notification. Give 3 points for basic visual indication, 7 points for enhanced visual effects, and 10 full points if both visual and audio notifications are implemented professionally.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as rapid button clicking, browser tab switching/background processing, or page refresh) and provide 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. Customizable time presets 2. Theme switching 3. Session counting or history 4. Pomodoro-style functionality). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple timer engines running simultaneously) 2. Function modules unrelated to a countdown timer (e.g., a built-in calculator) 3. Fancy effects that affect performance (e.g., excessive animations that slow down the page). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating timer logic/view/control layers), code organization, and maintainability. Deduct 5 points if global variables are excessively used or if the code structure is chaotic; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no error handling or if the code is poorly commented. 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 (timer digits clearly visible from distance, appropriate contrast). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for poor readability of the timer digits. 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) Button click feedback delay ≤ 100ms 2) Smooth second/minute transitions 3) Clear visual focus on the current time remaining. Deduct 5 points for each operation without feedback, 3 points for jerky time transitions, and 5 points for hard-to-find control buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Utility Tools-Calculation Tools",
-  "difficulty": "easy"
-}

package/library/web_applications-other/wechat-mini-program-self-service-car-wash.json

@@ -1,68 +0,0 @@
-{
-  "index": 1498,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Ensure that the code you generate is executable for demonstration purposes. Design a WeChat Mini Program page for a self-service car wash that has a beautiful interface and is suitable for commercial use.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core business logic of the self-service car wash fully implemented?",
-      "description": "Review whether the code accurately implements the complete car wash service flow through WeChat Mini Program framework, including service selection (basic wash/premium wash/wax service), time slot booking, payment integration, and real-time status tracking. Score 0 if core business logic is missing, 5 if only basic service selection is implemented, and 10 if complete commercial workflow including WeChat Pay integration is fully functional.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the WeChat Mini Program native functionality properly utilized?",
-      "description": "Check whether the implementation leverages WeChat Mini Program's native capabilities including location services (wx.getLocation), camera for QR code scanning (wx.scanCode), real-time messaging (WebSocket), and proper lifecycle management (onLoad/onShow/onHide). Deduct 5 points if location-based services are not implemented, 3 points if QR code scanning is missing, and 2 points if WeChat sharing functionality is absent. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the data persistence and state management architecture properly designed?",
-      "description": "Evaluate whether the mini program implements proper data flow management using WeChat's storage APIs (wx.setStorageSync/wx.getStorageSync), handles network requests with proper error handling, and maintains consistent state across page navigations. Check if user session management and order history persistence are implemented. Deduct 5 points if data consistency issues exist, 3 points if offline capability is missing. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the commercial-grade user experience workflow complete?",
-      "description": "Check whether the code includes complete commercial features such as user registration/login, service history tracking, membership system, promotional coupon management, and customer feedback mechanism. Evaluate if the booking confirmation process includes proper validation and confirmation steps. Deduct 5 points if payment flow is incomplete, 3 points if user account management is missing, 2 points if no feedback mechanism exists. Give 10 points if fully commercial-ready.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as network failures, WeChat API errors, payment interruptions, invalid user inputs, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should include proper error boundaries, fallback UI states, and graceful degradation. Give 10 points for comprehensive error handling, 5 points for basic error handling, and 0 points if no exception handling exists.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that enhance commercial value?",
-      "description": "Check whether the code includes value-added features that enhance user experience (e.g., 1. AR car wash preview using camera 2. AI-powered service recommendations based on car type 3. Real-time queue monitoring with estimated wait times 4. Social sharing of wash completion with before/after photos). 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 payment processing logics) 2. Function modules unrelated to car wash services (e.g., built-in games or social features) 3. Excessive animations that affect Mini Program performance limits. Deduct 3 points for each redundancy found, and directly deduct 10 points if core business functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design following WeChat Mini Program best practices (proper page/component separation, utils organization), code reusability, and adherence to WeChat Mini Program development standards. Deduct 5 points if global state pollution is found or improper use of Mini Program lifecycle; deduct 5 points if code duplication rate is too high (over 30%); deduct 5 points if not following WeChat Mini Program coding standards. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface design meet commercial Mini Program standards?",
-      "description": "Evaluate whether the UI design follows WeChat Design Guidelines and commercial standards: 1) Consistent with WeChat's visual language and color schemes 2) Proper use of WeChat UI components (weui) 3) Professional branding elements suitable for car wash business 4) Clear visual hierarchy with proper spacing (following 8px grid system) 5) Readable typography (minimum 28rpx font size). Deduct 3 points for each non-compliant visual element, 5 points for poor color harmony, and 5 points for unprofessional commercial appearance. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the interaction design smooth and Mini Program compliant?",
-      "description": "Judge whether the interactions conform to WeChat Mini Program UX standards: 1) Touch feedback within 100ms following WeChat guidelines 2) Page transitions using proper Mini Program navigation APIs 3) Loading states with WeChat-style indicators 4) Proper use of Mini Program gestures and interactions 5) Accessibility considerations for diverse users. Deduct 5 points for each interaction not following WeChat standards, 3 points for performance issues during navigation, and 5 points for non-intuitive user flow. Full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Online Shopping",
-  "difficulty": "hard"
-}

package/library/web_applications-web_visuals/3d-map-amap-vue3-custom-building-blocks-mvt-polyhedrons.json

@@ -1,68 +0,0 @@
-{
-  "index": 1696,
-  "question": "You are a code expert. Please utilize your professional knowledge to generate accurate and professional responses. Be sure to ensure that the code you generate is executable for demonstration. Develop a 3D map using Amap API with Vue 3, draw custom building blocks, and use MVT polyhedrons.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Amap API integration correctly implemented?",
-      "description": "Review whether the code properly initializes the Amap instance with appropriate API keys, correctly loads the required plugins, and handles map lifecycle events. Check if the map container is properly configured with correct dimensions and initial view settings (center coordinates, zoom level). Score 0 if the map fails to initialize, 5 if basic initialization works but missing error handling, and 10 if fully implemented with proper error handling and loading states.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are custom building blocks properly implemented?",
-      "description": "Evaluate whether custom building geometries are correctly constructed using Amap's polygon/polyline APIs or custom WebGL rendering. Check if the buildings have proper height extrusion, accurate geographic positioning, and appropriate texturing. Deduct 5 points if buildings lack proper height data, 3 points if texture mapping is incorrect, and 2 points if building footprints don't match geographic data. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the MVT (Mapbox Vector Tiles) polyhedron rendering implemented correctly?",
-      "description": "Check if the code properly loads and renders MVT data, correctly interprets vector tile protocols, and efficiently renders polyhedrons based on tile data. Verify tile loading optimization techniques like caching and level-of-detail management. Deduct 5 points if rendering artifacts occur at tile edges, 3 points if tile loading is inefficient, and 5 points if the MVT protocol implementation is incorrect. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is Vue 3 integration properly implemented with reactive map components?",
-      "description": "Assess whether the code uses Vue 3's Composition API effectively for map component state management, properly handles component lifecycle with map instance creation/destruction, and implements reactive data binding between UI controls and map state. Deduct 5 points for improper component lifecycle management, 3 points for non-reactive map controls, and 5 points for memory leaks in component cleanup. 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 loading failures, network interruptions, invalid geographic data, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should implement proper try-catch blocks around API calls, handle promise rejections, and provide fallback rendering. Give 10 points for comprehensive error handling, 5 points for basic error handling, and 0 points if no error handling exists.",
-      "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. Custom shader effects for buildings 2. Dynamic time-of-day lighting 3. Interactive building selection with information panels). 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 map initialization or multiple conflicting map instances 2. Unnecessary libraries that increase bundle size without adding functionality 3. Overuse of 3D effects that hinder performance or usability. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core map functionality is compromised by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating map configuration/layer management/data fetching logic), reusable component structure, and build process optimization. Deduct 5 points if global state management is poorly implemented; deduct 5 points if there's significant code duplication across components; deduct 5 points if the component hierarchy doesn't follow Vue 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 map visualization follows modern cartographic design principles: 1) Balanced visual hierarchy between basemap and custom elements 2) Appropriate color schemes that maintain readability of map features 3) Proper labeling and symbology that scales with zoom levels. Deduct 3 points for cluttered map elements, 5 points for poor color contrast affecting readability, and 5 points for inconsistent styling between map elements. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the map interactions meet performance standards: 1) Map pan/zoom responds within 60ms 2) Building selection/hover feedback within 100ms 3) Smooth frame rate (>30fps) during 3D navigation. Deduct 5 points for jerky camera movements, 3 points for delayed tile loading causing visual gaps, and 5 points for unresponsive UI controls during map rendering. Verify if level-of-detail adjustments occur smoothly during zoom operations. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Web Visuals",
-  "difficulty": "medium"
-}

package/library/web_applications-web_visuals/ai-park-innovation-platform.json

@@ -1,68 +0,0 @@
-{
-  "index": 878,
-  "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 demonstrable when possible. Help me create a webpage for \"AI Park Innovation\" - an AI platform specifically for generating industrial designs, featuring a dedicated information plaza, model integration interface, and generation interface. The page should be simple yet impressive, with the words \"AI Park Innovation\" appearing on each page.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the main webpage structure properly implemented?",
-      "description": "Evaluate if the HTML structure follows semantic principles with proper sectioning (header, main, footer), responsive layout, and correct navigation between the three key sections (information plaza, model integration interface, and generation interface). Check if the title 'AI Park Innovation' appears consistently on each page. Score 0 if basic structure is missing, 5 if structure exists but with improper hierarchy, and 10 if perfectly structured with proper semantic HTML5 tags and responsive design principles.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the information plaza functionality complete?",
-      "description": "Review whether the information plaza includes essential components like news feed, featured designs, user highlights, and information filtering/searching. Check if dynamic content loading is implemented, if pagination or infinite scrolling works, and if the content display adapts to different screen sizes. Deduct 3 points if filtering is missing, 4 points if dynamic loading isn't implemented, and 3 points if responsiveness fails on mobile devices. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the model integration interface functional and intuitive?",
-      "description": "Assess the model integration interface for its ability to upload/select AI models, configure parameters, and display integration status. Verify if the interface includes model compatibility checking, parameter validation, and visual feedback during integration processes. Deduct 5 points if there's no error handling for model uploads, 3 points if parameter configuration is confusing, and 2 points if visual feedback during processes is missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the AI design generation interface well-implemented?",
-      "description": "Evaluate the design generation interface for input mechanisms (text prompts, reference images, parameter settings), generation state management, and result visualization. Check if it includes progress indicators, cancellation options, and history tracking. Deduct 4 points if there's no visual preview or progress indication, 3 points if the interface lacks parameter fine-tuning, and 3 points if history/saved designs aren't accessible. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid inputs, network failures, image loading 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 AI design preview 2. Collaborative design capabilities 3. AR visualization of generated designs). 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 uploaders) 2. Function modules unrelated to industrial design generation (e.g., social networking functions) 3. Fancy effects that affect performance (e.g., excessive animations that slow down core 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 modular design (such as separating UI/API/state management), component reusability, and build process optimization. Deduct 5 points if global state pollution is found or modern frontend frameworks aren't leveraged; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build/bundling process is inefficient. 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 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": "medium"
-}

package/library/web_applications-web_visuals/alarm-data-overview-module.json

@@ -1,68 +0,0 @@
-{
-  "index": 958,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable for demonstration when possible.\n\n2. Today's Alarm Data Overview Module\n- Statistical analysis of total alarms by time dimension\n- Alarm type distribution (bar chart/pie chart)\n- Processing status proportion (donut chart)\n- Alarm heat map of key areas\n\nPlease help me design the frontend component layout for the above features, and write a complete HTML example page for mobile version.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the statistical analysis of total alarms by time dimension properly implemented?",
-      "description": "Check if the code implements a time-based visualization (line chart, bar chart, etc.) showing alarm frequency over different time periods. The implementation should include time filtering options (daily, weekly, monthly), proper time axis formatting, and data aggregation logic. Score 0 if missing, 5 if basic implementation without filtering, 10 if complete with interactive time range selection.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the alarm type distribution visualization correctly implemented?",
-      "description": "Evaluate whether the bar chart or pie chart accurately represents alarm type distribution with proper legends, labels, and percentage values. Check if the visualization is responsive and handles various data scenarios (many categories, single dominant category). Deduct 5 points if legends are missing or unclear, 3 points if percentage calculation is incorrect. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the processing status proportion (donut chart) properly visualized?",
-      "description": "Check if the donut chart correctly displays alarm processing statuses (e.g., pending, in progress, resolved) with clear color coding, labels, and center statistics. The chart should be interactive allowing users to select status segments for filtering. Deduct 3 points if center statistics are missing, 5 points if interaction is not implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the alarm heat map for key areas effectively implemented?",
-      "description": "Review if the heat map properly visualizes alarm concentration in different areas using appropriate color gradients, legends, and location markers. The heat map should be responsive to different screen sizes and provide zoom/pan capabilities. Deduct 5 points if the color gradient is hard to interpret, 3 points if area labeling is unclear, 5 points if the map is not interactive. 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 datasets, network errors, rendering on different screen sizes, etc.) and provide friendly error prompts or fallback displays. 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 data updates with animation 2. Cross-chart filtering capabilities 3. Custom alert thresholds with visual indicators). 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 visualizations (e.g., multiple charts showing the same data) 2. Function modules unrelated to alarm data overview 3. Fancy effects that affect performance (e.g., excessive animations or 3D effects that slow down 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 chart components, data processing, and layout), code reuse for similar chart types, and responsive design implementation. Deduct 5 points if global variables are excessively used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if responsive design breakpoints are poorly implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards for mobile?",
-      "description": "Evaluate whether the mobile design follows modern principles: 1) Touch-friendly element size (min 44px tap targets) 2) Proper layout spacing for small screens (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 16px for mobile readability). Deduct 3 points for elements that are too small to tap accurately, 5 points for horizontal scrolling on standard mobile screens, 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 for touch?",
-      "description": "Judge whether the mobile interaction conforms to touch interaction standards: 1) Fast touch response (≤ 100ms) 2) Proper touch gestures for map navigation/chart interaction 3) Clear visual feedback for tapped states. Deduct 5 points for interactions requiring precise cursor control, 3 points for missing touch feedback, and 5 points for overlapping touch targets. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Web Visuals",
-  "difficulty": "easy"
-}

package/library/web_applications-web_visuals/birthday-card-with-oldies-music.json

@@ -1,68 +0,0 @@
-{
-  "index": 337,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable for demonstration. Help me create a birthday card frontend program for my 85-year-old mother who was a teacher, accompanied by classic Western oldies music.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the birthday card visual design age-appropriate and teacher-themed?",
-      "description": "Review whether the code implements a visually appealing birthday card with teacher-themed elements (books, apples, classroom motifs, etc.) and age-appropriate design for an 85-year-old recipient. Check for large, readable fonts (minimum 18px), high contrast colors, and meaningful educational symbols. Score 0 if no thematic elements are present, 5 if basic birthday card layout exists, and 10 if fully themed with teacher-specific decorations and age-appropriate considerations.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the classic Western oldies music integration properly implemented?",
-      "description": "Check whether the HTML5 audio implementation includes proper music controls, autoplay handling (with user interaction compliance), and features classic Western oldies tracks suitable for an 85-year-old. Verify volume controls, play/pause functionality, and track selection. Deduct 5 points if music doesn't autoplay after user interaction, 3 points if volume controls are missing, and 5 points if music selection isn't age-appropriate. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are interactive birthday card animations and effects well-designed?",
-      "description": "Evaluate whether the card includes engaging but gentle animations suitable for elderly users - such as falling confetti, blooming flowers, or gentle fade-in effects for birthday messages. Animations should be smooth, not overwhelming, and enhance the emotional impact. Deduct 5 points if animations are too fast or jarring, 3 points if no interactive elements exist, and 5 points if effects don't match the celebratory theme. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the personalized message system and content delivery implemented?",
-      "description": "Check whether the code includes a personalized birthday message system with heartfelt content appropriate for a retired teacher. Verify if messages appear progressively, include teaching appreciation themes, and have options for customization. Deduct 5 points if messages are generic, 3 points if no progressive reveal mechanism exists, and 5 points if content doesn't reflect the teacher profession. Give 10 points if fully personalized with teaching-related appreciation messages.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as audio loading failures, browser compatibility issues, slow network connections, 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 any innovative features that enhance emotional connection?",
-      "description": "Check whether the code includes thoughtful features that enhance the emotional experience (e.g., 1. Photo slideshow integration 2. Voice message recording capability 3. Memory timeline of teaching career 4. Interactive guest book for family messages). 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 audio players) 2. Function modules unrelated to birthday celebration (e.g., games or complex navigation) 3. Overly flashy effects that might overwhelm elderly users (e.g., rapid blinking animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if core birthday card 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 audio/visual/interaction layers), clean HTML structure, and organized CSS/JavaScript. Deduct 5 points if global state pollution is found or no design patterns are used; deduct 5 points if code duplication rate is too high (over 30%); deduct 5 points if files are not properly organized. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet accessibility and aesthetic standards for elderly users?",
-      "description": "Evaluate whether the design follows accessibility principles for elderly users: 1) High contrast color combinations with warm, nostalgic tones 2) Large, clear typography (minimum 18px, preferably 20px+) 3) Generous spacing and large clickable areas 4) Consistent visual hierarchy. Deduct 3 points for each small or hard-to-read element, 5 points for poor color contrast, and 5 points for cluttered layout. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the user interaction gentle and intuitive for elderly users?",
-      "description": "Judge whether interactions are designed for elderly users: 1) Large, clearly labeled buttons with hover effects 2) Gentle, slow-paced animations (500-800ms duration) 3) Clear visual feedback for all interactions 4) Simple, intuitive navigation flow. Deduct 5 points for each small or unclear interactive element, 3 points for too-fast animations, and 5 points for confusing navigation. Full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Web Visuals",
-  "difficulty": "easy"
-}