@getollie/cli 0.0.1

package/library/management_systems-frontend_backend_platforms/ancient-chinese-natural-science-platform.json

@@ -0,0 +1,68 @@
+{
+  "index": 1275,
+  "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. Create a project with a theme of \"Ancient Chinese Natural Science Appreciation Platform,\" which should include a backend management system, login system, and content collected by crawling Baidu. The directory should be categorized using a Chinese map image style.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Ancient Chinese Natural Science Appreciation Platform fully implemented?",
+      "description": "Evaluate whether the code implements a complete platform structure with frontend visualization, content display, and navigation functionality. Check if the platform has clear sections for different scientific achievements categorized by periods, fields, or figures. Score 0 if only basic HTML structure exists, 5 if there's a functional but basic platform, and 10 if the platform is comprehensive with rich content organization and display features.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the Chinese map image-style directory categorization implemented effectively?",
+      "description": "Assess whether the code implements an interactive Chinese map visualization that serves as the main navigation directory. Check if regions are properly mapped to content categories, with clear visual distinction, hover effects, and proper geographical accuracy. Deduct 5 points if the map is static/non-interactive, 3 points if regional divisions are inaccurate, and 3 points if content categories don't logically align with geographical regions. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the backend management system properly implemented?",
+      "description": "Review the backend code for content management functionality, including CRUD operations for scientific content, user management, and system settings. Check for proper API design, database schema, and admin dashboard implementation. Deduct 5 points if content management features are missing, 3 points if there's no user role system, and 3 points if there's no content approval workflow. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the login system secure and complete?",
+      "description": "Examine the authentication implementation for security best practices, including password hashing, session management, CSRF protection, and user role authorization. Review if there are features for registration, password recovery, and account management. Deduct 5 points for missing encryption/hashing, 3 points for lack of session timeout handling, and 5 points for no input validation. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as network failures, invalid inputs, unauthorized access attempts, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should include proper error handling, input validation, and defensive programming techniques, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Interactive timeline visualization of scientific developments 2. AR/VR demonstrations of ancient inventions 3. Side-by-side comparison of ancient and modern scientific principles). 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 content management systems) 2. Function modules unrelated to ancient Chinese science (e.g., modern Western science sections) 3. Fancy effects that affect performance (e.g., excessive animations on educational content). 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), unit test coverage, and build process automation. Evaluate the web crawler implementation for efficiency and respect for target site policies. 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 both modern and traditional Chinese aesthetic principles: 1) Harmonious color matching (using traditional Chinese color palettes) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (appropriate use of Chinese calligraphy fonts for headings, readable fonts for content). Deduct 3 points for each crowded visual element, 5 points for inappropriate color combinations, 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 when navigating the map interface. Assess the performance impact of crawled content display and map rendering. Deduct 5 points for each operation without feedback, 3 points for visual after-images during map navigation, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "hard"
+}

package/library/management_systems-frontend_backend_platforms/android-car-ivi-launcher.json

@@ -0,0 +1,68 @@
+{
+  "index": 845,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code for demonstration when possible. Create a powerful and beautiful Android Launcher for a 1920x720 resolution car IVI display screen, and generate the code.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the car launcher UI properly optimized for 1920x720 resolution?",
+      "description": "Check if the layout is explicitly designed for 1920x720 resolution with appropriate density considerations. All UI elements should be correctly sized for this specific wide-format display. Examine if the code includes specific configuration for landscape orientation and handles the wider aspect ratio (8:3) properly. Deduct 5 points if the layout doesn't adapt well to this resolution, and 10 points if elements are cut off or distorted. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the launcher optimized for in-vehicle usage patterns?",
+      "description": "Review whether the code implements car-specific UI considerations: 1) Large tap targets (at least 56dp for critical functions) 2) Glanceability with minimal driver distraction 3) Quick access to navigation, media, and communication functions in the primary viewing area. Deduct 5 points if touch targets are too small for driving conditions, and 5 points if critical functions require more than 2 taps. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the launcher responsive to different driving contexts?",
+      "description": "Evaluate if the code implements context awareness: 1) Day/night mode switching based on ambient light sensors 2) Driving mode that simplifies UI when vehicle is in motion 3) Integration with vehicle state APIs. Score 3 points for each implemented context adaptation feature. Deduct all 10 points if the launcher lacks any driving context awareness features.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the launcher provide proper integration with Android Auto or vehicle systems?",
+      "description": "Check if the code includes appropriate system integration: 1) Hooks for Android Auto compatibility 2) Vehicle telemetry data display (speed, fuel level) 3) HVAC controls integration. Score 3 points for each well-implemented integration point. If the launcher is completely isolated from vehicle systems with no integration paths, score 0 points. 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 system resource constraints, unexpected app crashes, transient connectivity loss, etc.) and provide graceful degradation. Check for error handling in background services and UI rendering code. 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 car experience (e.g., 1. Voice command integration 2. Customizable quick action panels 3. Contextual suggestions based on time/location). 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. Unnecessary animations that might distract drivers 2. Duplicate app launching methods that confuse users 3. Heavy visual elements that impact performance on automotive hardware. Deduct 3 points for each redundancy found, and directly deduct 10 points if safety-critical functions are obstructed by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review architecture design (such as MVVM pattern adoption, separation of UI/business logic), memory management for limited automotive hardware, and power efficiency considerations. Deduct 5 points if global state pollution is found; deduct 5 points if the code causes memory leaks; deduct 5 points if wake locks are abused. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional automotive design standards?",
+      "description": "Evaluate whether the overall design follows modern automotive UI principles: 1) Limited color palette with high contrast for visibility 2) Clear visual hierarchy prioritizing essential driving information 3) Consistent iconography sized appropriately for glanceable interactions. Deduct 3 points for each distracting visual element, 5 points for text smaller than 18sp, and 5 points for low-contrast color schemes that impact visibility in variable lighting. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction optimized for in-vehicle use?",
+      "description": "Judge whether the interactions conform to driver safety considerations: 1) Touch feedback delay ≤ 100ms 2) Minimal animations during driving 3) Voice feedback for critical interactions. Deduct 5 points for each distracting animation, 5 points for gesture controls requiring fine motor skills, and 5 points for interaction flows requiring more than 2 seconds of visual attention. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "medium"
+}

package/library/management_systems-frontend_backend_platforms/angular-security-management-decision-support.json

@@ -0,0 +1,68 @@
+{
+  "index": 1059,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable and ready for demonstration. Implement the following functionality using Angular 15:\n\nSecurity Management and Decision Support: Provide comprehensive data analysis to assist decision-makers in conducting security assessments and developing appropriate emergency response plans.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the security data analysis framework properly implemented?",
+      "description": "Evaluate whether the code implements a comprehensive Angular 15 data analysis framework with proper security data models, services for data retrieval/processing, and visualization components. Check if the implementation includes data normalization techniques, risk scoring algorithms, and statistical analysis utilities for security metrics. Score 0 if core analysis capabilities are missing, 5 if basic analysis is present but lacks depth, and 10 if the framework offers comprehensive security analytics with multiple analysis methodologies.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the decision support system functionality complete?",
+      "description": "Assess whether the code implements decision support capabilities including recommendation generation based on security data, scenario modeling, and comparison of potential response options. Verify that the system incorporates weighted decision matrices, risk-benefit analysis tools, and predictive modeling. Deduct 5 points if the recommendation engine is missing or primitive, 3 points if scenario modeling is absent. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are the security assessment visualization components effective?",
+      "description": "Check if the code includes visualization components (charts, heatmaps, network graphs) that effectively communicate security status and risk levels. Angular components should use modern visualization libraries (e.g., D3.js, Chart.js, ngx-charts) with proper Angular integration through directives/components. Evaluate if visualizations are interactive, support drill-down capabilities, and offer multiple viewing options. Deduct 5 points if visualizations are static, 3 points if they lack interactivity. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the emergency response planning functionality implemented?",
+      "description": "Review whether the code implements emergency response planning features including template management, workflow orchestration, resource allocation modeling, and plan versioning. Check if the implementation supports collaborative editing, approval workflows, and integration with notification systems. Deduct 5 points if plan versioning is missing, 3 points if the system lacks collaborative features. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code handles security-specific edge cases (data breaches during analysis, incomplete security data, conflicting risk assessments) with proper error boundaries and fallback mechanisms. Assess error handling for API failures, authentication issues, and data corruption scenarios. Code with strong robustness should provide detailed error logs, graceful degradation, and secure fallback options, 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 security management (e.g., 1. AI-powered threat prediction models 2. Automated security posture benchmarking against industry standards 3. Real-time threat intelligence integration with visualization 4. Geospatial security incident mapping). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Duplicate security analysis functions using different approaches 2. Excessive data transformation layers without clear purpose 3. Overly complex visualizations that don't contribute to decision-making clarity. Deduct 3 points for each redundancy found, and directly deduct 10 points if core security analysis is obscured by unnecessary features.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review Angular-specific best practices: proper use of NgRx or services for state management, lazy-loaded modules, proper dependency injection, and adherence to OnPush change detection strategy where appropriate. Check for unit tests with Jasmine/Karma, end-to-end tests with Protractor/Cypress, and proper TypeScript typing. Deduct 5 points if global state management is chaotic; deduct 5 points if the code lacks proper module organization; deduct 5 points if TypeScript 'any' type is overused. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the Angular components follow Material Design or enterprise UI guidelines with: 1) Consistent color theming using Angular Material theming system 2) Proper responsive grid layout using Angular Flex-Layout or CSS Grid 3) Accessibility compliance with ARIA attributes and keyboard navigation. Deduct 3 points for inconsistent component styling, 5 points for poor information hierarchy, and 5 points for inaccessible UI elements. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the Angular application demonstrates: 1) Optimized change detection to prevent UI freezing 2) Proper loading states with skeleton screens/spinners 3) Smooth transitions between security dashboard views using Angular animations. Deduct 5 points for UI jank during data operations, 3 points for abrupt view transitions without proper animations, and 5 points for lack of real-time feedback during security analysis operations. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "hard"
+}

package/library/management_systems-frontend_backend_platforms/animal-information-management-app.json

@@ -0,0 +1,68 @@
+{
+  "index": 696,
+  "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. How would you design a program or app to conveniently input, save, and search animal information?",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the animal information data model properly designed?",
+      "description": "Evaluate whether the code implements a comprehensive data model for animal information (properties like species, age, habitat, conservation status, etc.). Check if appropriate data types are used, if relationships between entities are properly defined, and if there's support for taxonomic hierarchy. Score 10 if the model is comprehensive with validation rules, 5 if basic but functional, 0 if severely lacking essential fields.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the input mechanism user-friendly and comprehensive?",
+      "description": "Check if the code provides intuitive interfaces for data entry with field validation, auto-completion, and guided input. Assess if it handles different input types (text, numbers, images) and supports both quick entry and detailed information. Deduct 3 points if validation is missing, 3 points if the interface is cluttered, and 4 points if it lacks appropriate input controls for different data types.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the data persistence layer properly implemented?",
+      "description": "Evaluate the data storage implementation (database, file system, cloud storage). Check if CRUD operations are complete, if there's proper error handling for storage failures, and if the solution includes data backup/recovery mechanisms. Award full 10 points if it includes transaction handling and data migration capabilities, 5 points if basic persistence works but lacks robustness, 0 if data isn't reliably saved.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the search functionality efficient and versatile?",
+      "description": "Assess the search implementation for features like full-text search, filters, advanced search options, and performance optimization for large datasets. Check if it handles partial matches, phonetic similarity, and taxonomic relationships. Score 10 if it includes indexed search with multiple parameters and performance considerations, 5 if basic search works but with limitations, 0 if search capability is missing or non-functional.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid input, storage failures, network issues, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. AI-powered species identification from images 2. Geolocation tracking for wildlife sightings 3. Data visualization for population trends). 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 storage systems without clear purpose) 2. Function modules unrelated to animal information management 3. Fancy effects that affect performance (e.g., unnecessary 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 modular design (such as separating data/business logic/presentation layers), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) 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 scrolling through animal lists, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "easy"
+}

package/library/management_systems-frontend_backend_platforms/api-rate-limiting-strategy-config.json

@@ -0,0 +1,68 @@
+{
+  "index": 939,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Big Data Healthcare Project:\n\n## Interface Menu: API Rate Limiting Strategy\n\n### Functionality:\n**Rate Limiting Strategy Configuration**: Users can customize API rate limiting strategies through the following settings:\n- Duration Limit: Set time duration restrictions for API interface calls.\n- API Traffic Limit Count: Set call frequency limitations for API interfaces.\n- User Traffic Limit: Set call frequency limitations for each user.\n- Application Traffic Limit: Set call frequency limitations for each application.\n\n**Strategy Management**: Display all configured rate limiting strategies, supporting operations such as editing, deleting, viewing detailed information, etc.\n\n**Strategy Monitoring**: Monitor the implementation of rate limiting strategies, display records of non-compliant calls.\n\nBased on the above functional description, implement a new strategy form and data list of existing strategies using ant-design-vue 1.7.8.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Rate Limiting Strategy Configuration form fully implemented?",
+      "description": "Examine whether the form correctly implements all required configuration fields (Duration Limit, API Traffic Limit Count, User Traffic Limit, Application Traffic Limit) using ant-design-vue components. Check for proper form validation, field descriptions, tooltips, and intuitive input controls. Score 0 if core fields are missing, 5 if basic fields exist but lack validation, and 10 if all fields are properly implemented with complete validation logic.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the Strategy Management data list properly implemented?",
+      "description": "Verify that the data list displays all configured rate limiting strategies with appropriate columns. Check for the implementation of edit, delete, and detail view operations. The table should include pagination, sorting capabilities, and filtering options. Deduct 3 points if any CRUD operation is missing, 3 points if pagination is not implemented, and 2 points if sorting/filtering is absent. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the Strategy Monitoring visualization implemented?",
+      "description": "Evaluate whether the monitoring interface displays records of non-compliant calls effectively. Look for visual indicators (charts, graphs, status indicators) showing rate limit violations. Assess whether time-series data is presented and if filtering by API/user/application is available. Award 10 points for comprehensive monitoring with visualizations, 5 points for basic tabular data without visualizations, and 0 points if monitoring is not implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the ant-design-vue 1.7.8 component library properly utilized?",
+      "description": "Check if the implementation correctly uses ant-design-vue 1.7.8 components and follows the library's design patterns and best practices. Verify that appropriate components are used for each UI element (Form, Table, Modal, Card, etc.) and that they are configured properly. Deduct 3 points for each misused component or implementation that doesn't follow ant-design-vue conventions. 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, network failures, empty data states, 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 rate limit visualization 2. Threshold recommendation based on historical data 3. One-click template application for common API types). 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 form validation logics coexisting) 2. Function modules unrelated to rate limiting (e.g., unnecessary user profile features) 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 modular design (such as separating UI components/services/state management), 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's no clear 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 (consistent with ant-design-vue's design system) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional form and table layout (aligned labels, consistent input sizes). Deduct 3 points for each crowded visual element, 5 points for inconsistent styling that breaks ant-design visual guidelines, and 5 points for chaotic form or table 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) Form submission and response feedback ≤ 300ms 2) Smooth transitions between strategy list and detail views 3) Clear loading states during data fetching. Deduct 5 points for operations without feedback, 3 points for jarring transitions between views, and 5 points for confusing user flows when creating or editing strategies. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "easy"
+}

package/library/management_systems-frontend_backend_platforms/asset-management-system-vue-bootstrap.json

@@ -0,0 +1,68 @@
+{
+  "index": 906,
+  "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 displayable. Use Bootstrap, Vue.js, or a combination of both to build an asset management system.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the asset management core functionality fully implemented?",
+      "description": "Review whether the code accurately implements comprehensive asset management features including asset creation, editing, deletion, categorization, and search functionality. Check if asset metadata management (name, description, tags, creation date, file size, etc.) is properly handled. Score 0 if core CRUD operations are missing, 5 if only basic operations are implemented, and 10 if full asset lifecycle management with advanced filtering and bulk operations are included.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the data management and persistence layer properly architected?",
+      "description": "Evaluate whether the system implements proper data persistence with appropriate storage solutions (localStorage, IndexedDB, or backend API integration). Check if data validation, error handling for data operations, and state management (Vuex/Pinia) are correctly implemented. Deduct 5 points if data validation is insufficient, 3 points if no backup/recovery mechanism exists. Full score requires robust data integrity and proper state synchronization.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the component architecture well-structured and reusable?",
+      "description": "Assess whether Vue.js components follow proper composition patterns with clear separation of concerns. Check if components are properly structured with props/events, utilize composition API effectively, and implement proper component lifecycle management. Deduct 5 points if components are tightly coupled, 3 points if props validation is missing. Requires modular, maintainable component hierarchy with proper data flow.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the user workflow and navigation system intuitive and complete?",
+      "description": "Evaluate whether the system provides logical user workflows for asset management tasks. Check if navigation is intuitive with proper routing (Vue Router), breadcrumbs, and user guidance. Assessment includes workflow efficiency, task completion paths, and user onboarding elements. Deduct 5 points if navigation is confusing, 3 points if no loading states or progress indicators exist. Full score requires seamless user experience with clear action paths.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust and handles edge cases effectively?",
+      "description": "Evaluate whether the code can handle common abnormal situations (network failures, invalid file uploads, permission errors, large dataset rendering, etc.) and provides meaningful error messages and recovery mechanisms. Robust code should gracefully handle edge cases with proper error boundaries and fallback UI states. Give 10 points if fully implemented, 5 points if partially handled, 0 points if no exception handling exists.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there innovative features that enhance user productivity?",
+      "description": "Check whether the code includes valuable productivity features such as: 1) Advanced search with filters and sorting 2) Batch operations and bulk editing 3) Asset preview and thumbnail generation 4) Export/import functionality 5) Dashboard analytics or reporting. Add 2-3 points for each well-implemented innovative feature that genuinely improves user experience (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant or unnecessary implementations?",
+      "description": "Strictly identify three types of redundancy: 1) Duplicate functionality implementations (multiple similar components doing the same task) 2) Features unrelated to asset management (unnecessary third-party integrations) 3) Over-engineered solutions that complicate simple tasks. Deduct 3 points for each redundancy found, and deduct 10 points if redundant code significantly impacts core functionality performance.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code demonstrate professional engineering standards?",
+      "description": "Review code organization, Vue.js best practices implementation, proper use of Bootstrap utilities, component composition patterns, and build configuration. Check for proper linting, consistent coding style, appropriate use of TypeScript (if used), and proper dependency management. Deduct 5 points for poor code organization, 3 points for inconsistent naming conventions, 2 points for missing development tooling setup.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the UI design meet modern web application standards?",
+      "description": "Evaluate visual design quality using Bootstrap components effectively: 1) Consistent color scheme and proper contrast ratios 2) Responsive grid layout that works across devices 3) Proper typography hierarchy and spacing (following Bootstrap's spacing utilities) 4) Effective use of Bootstrap components without over-customization. Deduct 3 points for inconsistent spacing, 5 points for poor responsive behavior, 5 points for accessibility violations or poor color choices.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Are interactions smooth with proper feedback and performance?",
+      "description": "Assess interaction quality and performance: 1) Vue.js transitions and animations are smooth (300-500ms duration) 2) Immediate visual feedback for user actions 3) Proper loading states and skeleton screens 4) Efficient rendering for large asset lists (virtual scrolling if needed) 5) Responsive touch interactions. Deduct 5 points for laggy interactions, 3 points for missing loading indicators, 5 points for poor performance with large datasets.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "hard"
+}

package/library/management_systems-frontend_backend_platforms/atm-user-interface-frontend.json

@@ -0,0 +1,68 @@
+{
+  "index": 1442,
+  "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. Write an ATM user interface that implements complete functionality including user login, deposits and withdrawals, balance inquiries, receipt printing, etc., using front-end technologies.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the login and authentication system fully implemented?",
+      "description": "Review whether the code properly implements user authentication with proper input validation, secure handling of credentials, and session management. Check if there are measures against brute force attacks (like account lockout) and if proper error messages are displayed without revealing sensitive information. Score 0 if authentication is missing, 5 if basic authentication is implemented without security measures, and 10 if comprehensive secure authentication is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are the core ATM operations (deposit, withdrawal, balance inquiry) fully functional?",
+      "description": "Evaluate whether all core banking operations work correctly. Verify that deposits and withdrawals properly update the account balance with validation checks (e.g., preventing negative balances, checking for valid input amounts). Check if balance inquiries accurately display current balances. Deduct 3 points for each core operation that's missing or dysfunctional, and 2 points for each operation with validation issues. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the receipt generation and printing functionality implemented?",
+      "description": "Check if the system properly formats transaction receipts with all required information (transaction type, amount, timestamp, remaining balance, transaction ID). Verify if there are options to print, email, or decline receipts. Assess whether the print formatting would work on actual receipt paper dimensions. Score 0 if receipts are missing, 5 if basic receipt information is available but lacks formatting or printing options, and 10 if comprehensive receipt functionality is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is there proper transaction history and account management?",
+      "description": "Review whether the interface allows users to view transaction history with filtering options, manage account settings, change PIN/password, or configure preferences. Check if transactions are properly recorded with timestamps and unique identifiers. Deduct 3 points if transaction history is missing, 3 points if account management features are absent, and 2 points if history data is incomplete. 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 incorrect PIN entries, insufficient funds, network failure, service timeouts, card reading errors, etc.) and provide friendly error prompts or recovery mechanisms. Check if the system has proper timeout functionality for security. 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. Biometric authentication options 2. Quick withdrawal presets 3. Dark mode/accessibility features 4. Interactive voice guidance 5. Currency conversion calculator). Add 2 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple ways to check balance) 2. Function modules unrelated to banking (e.g., games or entertainment features) 3. Fancy effects that affect performance or usability (e.g., excessive animations that slow down transactions). 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), input validation, security measures, and code organization. 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 security best practices are not followed (e.g., storing sensitive data in localStorage). 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 ATM interface principles: 1) Clear visual hierarchy with important functions prominently displayed 2) Consistent and appropriately sized touch targets (at least 44×44px) 3) High contrast for readability in various lighting conditions 4) Clear typography with legible font sizes (at least 16px). Deduct 3 points for each usability issue, 5 points for poor contrast or readability problems, and 5 points for inconsistent layouts between screens. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and user-friendly?",
+      "description": "Judge whether the interface conforms to ATM usability standards: 1) Clear timeouts with warnings before session expiration 2) Logical flow between screens with proper back/cancel options 3) Loading indicators for processes that take time 4) Confirmation screens for critical actions like withdrawals. Deduct 5 points for missing timeout functionality, 3 points for lack of confirmation screens, and 5 points for confusing navigation or workflow. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "easy"
+}

package/library/management_systems-frontend_backend_platforms/automatic-course-scheduling-and-statistics.json

@@ -0,0 +1,68 @@
+{
+  "index": 895,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Take care to ensure that the code you generate is executable for demonstration purposes. You are an academic affairs administrator, and you need to design an automatic course scheduling software and a class hour statistics software similar to the Crystal Course Scheduling Software. Please provide complete code and methods for packaging the code.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core course scheduling algorithm fully implemented?",
+      "description": "Evaluate whether the code implements a complete scheduling algorithm that handles constraints like teacher availability, classroom capacity, course conflicts, and time slots. Check if it uses optimization techniques (genetic algorithms, constraint satisfaction, simulated annealing, etc.). Score 0 if no algorithm is implemented, 5 if a basic greedy algorithm is used, and 10 if an advanced optimization algorithm with multiple constraint handling is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Does the system provide comprehensive class hour statistics functionality?",
+      "description": "Review whether the code includes detailed statistics tracking for teacher workload, classroom utilization, course distribution across time slots, and department allocation. Verify that it can generate reports by department, teacher, classroom, or time period. Deduct 5 points if only basic counting is implemented without analytics, and 3 points if export functionality is missing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the data model properly designed for educational institution requirements?",
+      "description": "Examine if the data structure design includes entities for courses, teachers, students, classrooms, departments, time slots, and semesters with appropriate relationships. Check if academic constraints like prerequisites, co-requisites, and credit limits are modeled. Deduct 5 points for missing essential relationships, 3 points for improper normalization, and 5 points for ignoring academic policy constraints. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are conflict detection and resolution mechanisms implemented?",
+      "description": "Verify that the code includes validation for teacher scheduling conflicts, room double-booking, student course overlaps, and academic rule violations. Check if it provides automatic conflict resolution or clear user notifications with resolution suggestions. Deduct 5 points if conflicts are not detected, 3 points if detected but not resolved, and 2 points if resolution is manual only. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as missing data, invalid input, database connection failures, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. AI-powered scheduling recommendations 2. Calendar synchronization with external systems 3. Interactive visualization of schedule conflicts). 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 scheduling engines running in parallel) 2. Function modules unrelated to scheduling (e.g., a built-in messaging system) 3. Fancy effects that affect performance (e.g., excessive animations in the UI). 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 business logic/UI/data access layers), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast sliding, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "hard"
+}