@getollie/cli 0.0.4 → 0.2.0

package/library/management_systems-frontend_backend_platforms/vehicle-travel-recording-app-development.json

@@ -1,68 +0,0 @@
-{
-  "index": 1226,
-  "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. I am a professional business driver, please help me develop an app to record vehicle travel.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core vehicle tracking functionality fully implemented?",
-      "description": "Evaluate whether the code includes accurate GPS location tracking, distance calculation algorithms, and trip recording mechanisms. Check if the implementation handles location updates efficiently (using proper intervals to balance accuracy and battery usage). Score 0 if core tracking is missing, 5 if basic location recording is implemented, and 10 if it includes advanced features like background tracking and offline functionality.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the trip management system comprehensive?",
-      "description": "Review whether the application provides complete trip lifecycle management including start/pause/resume/end operations, automatic trip detection, and manual trip editing capabilities. Deduct 5 points if trip categorization (business vs. personal) is missing, and 3 points if there's no ability to annotate or tag trips. Give 10 points if the trip management system is fully featured with validation checks.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are business-specific reporting features implemented?",
-      "description": "Check if the code includes business-specific reporting such as expense calculations, mileage summaries, and exportable reports in standard formats (PDF, CSV). Verify if tax-related calculations are supported (e.g., business vs. personal mileage separation). Deduct 5 points if export functionality is missing, and 3 points if the reports lack customization options. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the data persistence and synchronization mechanism reliable?",
-      "description": "Evaluate whether the app implements proper data storage (local database like SQLite/Realm), backup mechanisms, and cloud synchronization options. Check if data integrity is maintained through proper transaction handling and conflict resolution. Deduct 5 points if there's no automated backup system, and 3 points if cross-device synchronization is missing. Give 10 points for a complete implementation with data recovery options.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as GPS signal loss, network interruption, app backgrounding, 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. Automatic business destination recognition 2. Integration with expense management systems 3. Voice commands for hands-free operation while driving). 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 location tracking methods running simultaneously) 2. Function modules unrelated to business driving (e.g., a built-in music player) 3. Fancy effects that affect performance or distract while driving (e.g., complex animations during navigation). 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 location services/UI/data storage 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 standards for vehicle apps: 1) High-contrast display readable in varying light conditions 2) Proper layout with touch targets ≥ 48px for use while stationary 3) Simplified interface with minimal interaction required while driving. Deduct 3 points for each hard-to-read element, 5 points for distracting interface elements, and 5 points for designs requiring complex interactions while driving. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction suitable for use in a vehicle environment?",
-      "description": "Judge whether the app interactions are appropriate for a driving context: 1) Voice feedback for critical operations 2) Single-tap or voice command for essential functions 3) Automatic mode switching between driving/stationary states. Deduct 5 points for interactions requiring precise touch control while moving, 3 points for distracting animations or notifications, and 5 points for critical functions buried in menus. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "hard"
-}

package/library/management_systems-frontend_backend_platforms/vue-b-s-architecture-project-setup.json

@@ -1,68 +0,0 @@
-{
-  "index": 1076,
-  "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 purposes. Using viz_dashboard as the project name, help me set up a Vue B/S architecture project with a stable Vue 3 version. Please provide detailed steps for the solution.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Vue 3 project setup process fully implemented?",
-      "description": "Review whether the code accurately implements the Vue 3 project setup using proper tools (Vue CLI, Vite, etc.), includes the necessary configuration files, and follows the recommended project structure. Score 0 if the setup process is missing or incorrect, 5 if basic setup is provided but incomplete, and 10 if a comprehensive and well-documented setup process is provided with proper package.json configuration.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the B/S (Browser/Server) architecture properly established?",
-      "description": "Check whether the code sets up a clear separation between frontend (browser) and backend (server) components, establishes proper communication patterns between them, and implements the necessary API interfaces. Deduct 5 points if there's no clear definition of API endpoints, 3 points if authentication mechanisms aren't addressed, and 3 points if error handling for network requests is missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the Vue 3 implementation leveraging its key features?",
-      "description": "Evaluate whether the code correctly uses Vue 3's Composition API, properly implements reactive state management, and takes advantage of Vue 3-specific features (e.g., Teleport, Fragments, emits declaration). Deduct 5 points if the code uses Options API exclusively without explanation, 3 points if reactivity isn't properly implemented, and 3 points if component structure is inefficient. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the dashboard architecture suitable for visualization?",
-      "description": "Check whether the dashboard structure follows best practices for data visualization applications: proper layout system, component hierarchy that supports different chart types, and responsive design principles. Deduct 5 points if the dashboard layout doesn't support dynamic content positioning, 3 points if visualization libraries aren't properly integrated, and 3 points if the architecture doesn't support different screen sizes. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as network failures, API errors, malformed data, etc.) and provides friendly error prompts or recovery mechanisms. Code with strong robustness should 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. Dark mode with auto detection 2. Dashboard layout customization 3. Interactive data exploration tools). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple state management solutions) 2. Function modules unrelated to dashboard visualization (e.g., unnecessary external services) 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 component reusability, separation of concerns), TypeScript integration, code formatting tools, and build process configuration. Deduct 5 points if global state management is poorly implemented; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build and deployment process is not properly configured. 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 interactions, 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/vue-book-management-system-frontend-page.json

@@ -1,68 +0,0 @@
-{
-  "index": 1297,
-  "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 as much as possible. Create a front-end page for a book management system using Vue.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Does the Vue component architecture follow best practices?",
-      "description": "Evaluate whether the code follows Vue.js best practices with proper component hierarchy, single-responsibility components, and proper use of props/events. Check if components are reusable and properly named. Score 0 if basic Vue syntax is incorrect, 5 if components exist but with poor organization, and 10 if components follow all best practices with proper encapsulation.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the book data management system fully implemented?",
-      "description": "Review whether the code implements CRUD operations for books (Create, Read, Update, Delete) with proper form validation and error handling. Check if sorting, filtering, and search functionality are implemented. Score 0 if basic operations are missing, 5 if only basic listing and adding are implemented, and 10 if all operations are fully functional with validation.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is state management properly implemented?",
-      "description": "Assess whether the application uses appropriate state management techniques (Vuex store, Composition API, or Pinia) for handling book data, user interactions, and UI state. Check if state mutations follow proper patterns with actions/mutations or reactive methods. Deduct 5 points if global state is directly mutated, 3 points if reactivity issues exist. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is routing and navigation properly implemented?",
-      "description": "Evaluate if Vue Router is correctly implemented with appropriate route configuration, navigation guards, and page transitions. Check if route parameters are used for book details and URL state preservation. Deduct 5 points if navigation doesn't work correctly, 3 points if route guards are missing for protected areas. 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 book lists, form input errors, API 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. Book cover preview with zoom 2. Drag-and-drop organization of books 3. Reading progress tracking 4. Book recommendation engine). 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 data fetching mechanisms coexisting) 2. Function modules unrelated to book management (e.g., a built-in music player) 3. Fancy effects that affect performance (e.g., excessive animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review component organization, code splitting, proper use of Vue lifecycle hooks, and build optimizations. Check for consistent coding style, proper commenting, and use of TypeScript or PropTypes if applicable. Deduct 5 points if global component registration is overused; deduct 5 points if code duplication rate is too high (over 30%); deduct 5 points if the build process is not optimized. 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 of book 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/vue-elementui-express-survey-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 982,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate, professional responses. Make sure the code you generate is executable for demonstration purposes. Please design a survey system based on Vue + ElementUI + Express.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Vue front-end architecture properly implemented?",
-      "description": "Evaluate if the code follows Vue best practices with proper component structure, Vuex state management, Vue Router configuration, and lifecycle hooks usage. Check for single-file components with clear separation of template, script, and style. Score 0 if only basic Vue syntax is used without architecture, 5 if basic component structure exists but lacks proper state management, and 10 if a complete Vue architecture with proper data flow is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the ElementUI integration complete and appropriate?",
-      "description": "Assess whether ElementUI components are correctly imported and used following library guidelines. Check for proper form validation using ElementUI's built-in validators, responsive layouts using its grid system, and theme customization. Deduct 5 points for global import instead of on-demand loading (affecting performance), 3 points for inconsistent ElementUI styling overrides, and 3 points for not utilizing ElementUI's form validation capabilities. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the Express backend implementation comprehensive?",
-      "description": "Review the Express server implementation including middleware usage (cors, body-parser, etc.), RESTful API design, error handling middleware, and database integration. Check for proper route organization and controller separation. Deduct 5 points if authentication middleware is missing, 3 points if error handling is incomplete, and 5 points if API endpoints don't follow RESTful principles. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there a complete survey creation and response workflow?",
-      "description": "Evaluate whether the system implements a full survey lifecycle: creation, distribution, response collection, and result analysis. Check for features like different question types (multiple choice, rating scales, open-ended questions), skip logic, and survey analytics. Score 0 if only basic form creation exists, 5 if survey creation and collection are implemented but lack analytics, and 10 if the complete workflow including visualization of results is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as network errors, form validation failures, server unavailability, etc.) and provide friendly error prompts or recovery mechanisms. Check for input sanitization to prevent XSS attacks and proper handling of concurrent submissions. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Real-time collaborative survey editing 2. Survey result visualization with charts 3. Survey templates and branching logic 4. Export to multiple formats like PDF/Excel). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple form validation systems coexisting) 2. Function modules unrelated to surveys (e.g., a built-in file manager) 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 API calls/UI components/business logic), test coverage, and build process automation. Check for proper use of environment variables, code linting, and security 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 overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors beyond ElementUI's theme) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional form layouts with proper labels and help text. Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic form layouts. 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 feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance for multi-step forms. Deduct 5 points for each operation without loading states, 3 points for jarring transitions between survey pages, and 5 points for confusing navigation in multi-page surveys. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "medium"
-}

package/library/management_systems-frontend_backend_platforms/vue-hbuilder-admin-management-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 1477,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate, professional responses. Be sure to provide executable code whenever possible. Build a Vue-based admin management system through HBuilder.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Vue-based admin system foundation correctly established?",
-      "description": "Review whether the code properly initializes a Vue project using HBuilder, includes the Vue framework configuration (Vue 2 or Vue 3), and sets up the necessary project structure. Check if Vue Router and Vuex/Pinia are properly integrated. Score 0 if the Vue framework is not correctly initialized, 5 if basic Vue setup is present but with configuration issues, and 10 if the Vue framework is fully configured with proper module organization.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Does the code implement a complete authentication and authorization system?",
-      "description": "Evaluate if the authentication system includes login, logout, token management (JWT recommended), and role-based access control. Check if permissions are verified at both router navigation guards and component levels. Deduct 5 points if token refresh mechanism is missing, 3 points if no role-based access control exists, and 4 points if secure storage of credentials is not implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is there a comprehensive UI component system implementation?",
-      "description": "Check whether the code integrates a UI framework (Element UI, Ant Design Vue, etc.) and customizes components as needed. Examine if the components are properly organized with consistent props and emit patterns. Deduct 3 points if component reusability is poor, 4 points if UI framework is not utilized effectively, and 5 points if the component hierarchy is overly complex or flat. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the system implement proper API integration and data management?",
-      "description": "Assess whether the code uses centralized API service modules, includes proper error handling for network requests, and implements data caching strategies. Check if the system uses interceptors for request/response processing. Deduct 3 points if API calls are scattered throughout components, 4 points if there's no global error handling, and 5 points if no data loading states are managed. 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, state inconsistencies) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should include form validations, defensive programming patterns, and graceful degradation. Give 10 points for comprehensive error handling, 5 points for partial implementation, and 0 points if error handling is absent.",
-      "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. Dark/light theme switching with system preference detection 2. Dashboard with real-time data visualization 3. Multi-tab page management system). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Duplicate functionality across different components or services 2. Unnecessary third-party libraries for simple tasks 3. Over-engineered solutions that complicate maintenance. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core admin functionality is obscured by superfluous features.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (separation of concerns between components, services, and stores), code consistency (ESLint/Prettier integration), and build optimization. Deduct 5 points if global state is overused; deduct 3 points if naming conventions are inconsistent; deduct 4 points if the build process doesn't include optimization. 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 admin UI principles: 1) Consistent color scheme with brand identity 2) Clear visual hierarchy with proper whitespace 3) Responsive design for different screen sizes. Deduct 3 points for inconsistent spacing, 4 points for poor mobile adaptation, and 5 points for cluttered information architecture. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the user experience includes: 1) Loading states for asynchronous operations 2) Smooth transitions between routes and component states 3) Instant feedback for user actions. Deduct 3 points for missing loading indicators, 4 points for jarring page transitions, and 5 points for delayed user feedback after form submissions or actions. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "medium"
-}

package/library/management_systems-frontend_backend_platforms/vue-spring-boot-parking-management-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 973,
-  "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 purposes. Now, please help me create a parking management system based on Vue and Spring Boot.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the parking management system front-end fully implemented?",
-      "description": "Review whether the Vue code accurately implements essential parking management features: car entry/exit recording, parking space management, and payment processing. Score 0 if core functionality is missing, 5 if only basic features are implemented without proper state management, and 10 if all required features are implemented with proper Vue component structure and state management (Vuex/Pinia).",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the Spring Boot back-end API design comprehensive?",
-      "description": "Check if the API endpoints cover all necessary operations (CRUD for vehicles, parking spaces, payments, users), follows RESTful principles, includes appropriate validation, error handling, and documentation (Swagger/OpenAPI). Deduct 5 points if security mechanisms are missing (authentication/authorization), and 3 points if data validation is insufficient. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the database design appropriate for a parking management system?",
-      "description": "Evaluate whether the database schema includes necessary tables (users, vehicles, parking spaces, transactions, rates), with proper relationships, indexing on frequently queried fields, and appropriate data types. Check if proper ORM implementation is used (JPA/Hibernate). Deduct 5 points for missing entity relationships, and 3 points for improper constraint design. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there real-time monitoring and reporting functionality?",
-      "description": "Check if the system provides real-time dashboard for parking space availability, occupancy rates, revenue tracking, and historical data visualization. Assess whether WebSocket is used for real-time updates and if the reporting includes filterable/exportable reports. Deduct 5 points if real-time updates are missing, and 3 points if reporting capabilities are limited. 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 duplicate entry/exit records, payment failures, concurrent space allocation, 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. License plate recognition integration 2. Mobile app notifications for vehicle owners 3. Predictive analytics for peak hours 4. Integration with payment gateways). 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 register vehicles) 2. Function modules unrelated to parking management (e.g., a built-in chat system) 3. Fancy effects that affect performance (e.g., unnecessary animations on critical paths). 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 controllers/services/repositories in Spring Boot, and components/views/stores in Vue), 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"
-}

package/library/management_systems-frontend_backend_platforms/vue-tailwind-vite-admin-template.json

@@ -1,68 +0,0 @@
-{
-  "index": 851,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code whenever possible. Create an admin template using Vite, Vue, and Tailwind CSS.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Vite + Vue + Tailwind CSS tech stack properly implemented?",
-      "description": "Check if the project structure follows Vite best practices with proper configuration files (vite.config.js, tailwind.config.js, postcss.config.js). Verify that Vue 3 is correctly set up with Composition API or Options API. Tailwind CSS should be properly integrated with necessary plugins. Score 0 if core configuration is missing, 5 if basic setup exists but has configuration errors, and 10 if all configurations are optimally set with appropriate performance optimizations.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Does the admin template include essential layout components?",
-      "description": "Evaluate if the template includes fundamental admin layout components: responsive sidebar/navigation, header with user profile/notifications, main content area, footer, and breadcrumbs. Check for proper layout structuring with flexbox/grid. Deduct 2 points for each missing component. Award full points only if all components are responsive and properly integrated with Vue routing.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are authentication and authorization features implemented?",
-      "description": "Check for login/logout functionality, role-based access control, protected routes, and JWT/session management. Verify proper state management (Pinia or Vuex) for authentication. Award 3 points for basic login UI, 3 points for proper auth state management, 4 points for comprehensive role-based protections including route guards and API authentication. Deduct all points if authentication is completely missing.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the template include essential admin UI components and utilities?",
-      "description": "Verify the presence of reusable admin components like data tables, forms with validation, charts/graphs, modals/dialogs, alerts/toasts, cards, and dashboard widgets. Check if these components leverage Vue's component system effectively. Award 1 point for each well-implemented component (up to 10). Deduct 5 points if components aren't reusable or don't follow Vue best practices.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as API failures, form validation errors, responsive layout edge cases) and provide friendly error prompts or recovery mechanisms. Check for proper error boundaries in Vue components. 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. Dark/light theme toggle with system preference detection 2. Customizable dashboard with drag-and-drop widgets 3. Interactive data visualizations 4. Keyboard shortcuts for power users 5. Real-time notifications). 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 components (e.g., multiple button styles that serve the same purpose) 2. Unused utility functions/components 3. Overly complex animations that affect performance. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review component architecture (proper composition, reusable components), state management approach, code splitting for lazy loading routes, and build optimizations. Deduct 3 points if global state is overused; deduct 3 points if components exceed 300 lines; deduct 2 points if there's no code splitting; deduct 2 points if build assets aren't properly optimized. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the design follows modern admin UI principles: 1) Consistent color scheme using Tailwind's color system 2) Proper use of spacing utilities (p-x, m-y, gap-z) 3) Responsive design across all viewports 4) Accessible contrast ratios and focus states. Deduct 3 points for inconsistent spacing, 3 points for poor responsive behavior, 2 points for accessibility issues, and 2 points for poor typography hierarchy. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the UI interactions meet modern expectations: 1) Smooth transitions between routes 2) Loading states for async operations 3) Proper form feedback (validation, success/error) 4) Intuitive navigation patterns. Deduct 3 points for missing loading indicators, 3 points for jarring page transitions, 2 points for poor form interaction feedback, and 2 points for confusing navigation patterns. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "medium"
-}

package/library/management_systems-frontend_backend_platforms/vue2-h5-mobile-project-setup.json

@@ -1,68 +0,0 @@
-{
-  "index": 399,
-  "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. Please use Vue 2 to build a front-end H5 project named \"interview\" and configure it for mobile device adaptation.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is a complete Vue 2 project structure correctly set up?",
-      "description": "Verify if the project includes essential Vue 2 files and directories (main.js, App.vue, components folder, package.json with Vue 2 dependencies). Check if Vue CLI or webpack configuration is properly set up with appropriate loaders. Score 0 if no project structure exists, 5 if basic structure is present but incomplete, 10 if fully configured with proper separation of concerns and directory organization.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is mobile device adaptation properly implemented?",
-      "description": "Examine if the code includes viewport meta tags, media queries, flexible units (rem/vw/vh), and responsive design principles. Check for device orientation handling and touch event support. Verify implementation of at least one mobile adaptation solution (viewport.js, amfe-flexible, postcss-px-to-viewport). Deduct 5 points if only basic viewport meta tag is used without comprehensive adaptation, 3 points if touch events are missing. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the project named correctly with proper configuration?",
-      "description": "Check if the project is named 'interview' in package.json, manifest files, and build configuration. Verify that the build scripts, output paths, and deployment settings correctly reference this name. Deduct 5 points if the project name is inconsistent across files, 3 points if build configurations don't properly use the name. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are essential mobile H5 features implemented?",
-      "description": "Evaluate if the project includes typical H5 mobile features: pull-to-refresh, infinite scroll, mobile-specific UI components (such as swipe cards, bottom sheets, actionsheets), and smooth transitions. Check for handling of software keyboard issues and iOS/Android differences. Score 0 if no mobile features exist, 5 if basic features are present, 10 if comprehensive mobile optimization is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as network errors, API failures, different screen sizes, orientation changes, 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. Skeleton screens during loading 2. Custom animations for transitions 3. Offline capability with service workers). 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 HTTP request libraries) 2. Function modules unrelated to the mobile H5 context 3. Fancy effects that affect performance (e.g., excessive animations causing jank). 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 components/views/store), code splitting for performance, and build process optimization. Deduct 5 points if global state pollution is found or Vue best practices are not followed; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if no mobile-specific build optimizations are implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern mobile design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle, critical tap targets ≥ 44px) 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 layouts that cause horizontal scrolling. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to mobile user expectations: 1) Touch feedback delay ≤ 100ms 2) Transition animation duration controlled between 200-300ms 3) Clear visual feedback for all interactions. Deduct 5 points for each operation without feedback, 3 points for janky animations during transitions, and 5 points for non-standard mobile interaction patterns. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "easy"
-}