@getollie/cli 0.0.1

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

@@ -0,0 +1,68 @@
+{
+  "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

@@ -0,0 +1,68 @@
+{
+  "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

@@ -0,0 +1,68 @@
+{
+  "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

@@ -0,0 +1,68 @@
+{
+  "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"
+}

package/library/management_systems-frontend_backend_platforms/vue2-mobile-desktop-system-page.json

@@ -0,0 +1,68 @@
+{
+  "index": 798,
+  "question": "You are a code expert. Please utilize your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable for demonstration. Write a system page similar to a mobile phone desktop using Vue 2.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the mobile phone desktop UI layout properly implemented?",
+      "description": "Evaluate if the code implements a grid-based app icon layout with proper spacing and alignment. Check if the UI includes status bar elements (time, battery, signal), app icons with labels, and a dock/favorites bar at the bottom. Score 0 if no desktop layout is present, 5 points for basic grid layout, 10 points for complete desktop metaphor including status bar and dock.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are core mobile desktop interactions implemented?",
+      "description": "Review if the code implements interactions like app launching (click to open), long-press for edit mode (app rearrangement, deletion, or widgets), swipe gestures for page navigation, and possibly a notification dropdown. Deduct 3 points if long-press functionality is missing, 3 points if swipe navigation is absent, and 4 points if there's no visual feedback on interactions. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is proper component architecture used following Vue 2 best practices?",
+      "description": "Check if the code properly utilizes Vue 2 component structure with single-file components (.vue files), props validation, emit events for child-parent communication, and computed properties/watchers where appropriate. Evaluate the use of Vue lifecycle hooks. Deduct 3 points for global state without proper management, 3 points for prop drilling beyond 2 levels, and 4 points for not leveraging Vue reactivity system. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the state management approach appropriate for the application?",
+      "description": "Evaluate whether the code uses an appropriate state management approach (local component state, prop passing, or Vuex) based on the complexity. For a desktop system, app data, current page, and UI state should be properly managed. Deduct 5 points if there's no centralized state for app data, 3 points if page state isn't preserved during navigation, and 2 points if UI states aren't reactive. 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 app data, icon loading failures, unexpected user interactions) and provide appropriate fallbacks or error handling. Code with strong robustness should validate inputs, handle edge cases, and provide meaningful error messages or recovery mechanisms, giving 10 points. If the robustness is average, give 5 points, and if no error handling exists, 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. App folder creation and management 2. Widget support with live data 3. Custom themes or wallpaper support). 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 open apps) 2. Function modules unrelated to mobile desktop (e.g., built-in games unrelated to the launcher) 3. Fancy effects that affect performance (e.g., excessive animations or transitions). 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 from logic), reusable components, code organization, and Vue style guide adherence. Deduct 3 points for inline styles instead of properly scoped CSS, 3 points if code duplication rate is high (over 30%), 2 points if naming conventions are inconsistent, and 2 points if component responsibilities are unclear or mixed. 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 UI principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows consistent principles) 3) Professional typography (readable font sizes, proper contrast). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for inconsistent icon styles or sizes. 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 UX expectations: 1) Touch feedback delay ≤ 100ms 2) Transition animations controlled between 200-350ms 3) Clear visual cues for interactive elements. Deduct 3 points for each interaction without feedback, 3 points for janky animations, 2 points for inconsistent transition effects, and 2 points for non-optimized rendering performance (e.g., not using v-once for static content). Full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "easy"
+}

package/library/management_systems-frontend_backend_platforms/vue3-dynamic-menu-vuex-state-management.json

@@ -0,0 +1,68 @@
+{
+  "index": 1194,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Ensure that the code you produce is executable when possible. Please provide a complete program for implementing dynamic menu additions based on different users in Vue 3, using Vuex for state management.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Vue 3 component architecture properly implemented?",
+      "description": "Review whether the code properly leverages Vue 3 Composition API or Options API, with clear separation of concerns between components. Check for proper component hierarchy, reusability patterns, and usage of Vue 3 specific features (e.g., teleport, fragments, multiple v-model). Score 0 if Vue 3 specific syntax is not used correctly, 5 if basic implementation is present but lacks optimization, 10 if implementation follows Vue 3 best practices with proper component design.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the Vuex state management correctly implemented for dynamic menu handling?",
+      "description": "Evaluate the Vuex store implementation, focusing on proper state organization, mutations, actions, and getters for menu management. Check if the store correctly handles user permissions and menu configurations. Deduct 5 points if the store structure doesn't follow Vuex best practices, 3 points if actions/mutations are inconsistently used. Ensure proper namespacing for menu-related store modules. Full score requires proper reactivity implementation and optimized state access.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Does the code implement role-based access control for dynamic menus?",
+      "description": "Check whether the implementation includes proper user role detection and permission verification mechanisms. Evaluate if the solution handles different user types (admin/regular users) with corresponding menu structures. Score 0 if permissions are hardcoded, 5 if basic role checking exists but lacks granularity, 10 if a complete RBAC system is implemented with proper menu filtering based on user permissions.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is there an efficient menu data structure design?",
+      "description": "Review the menu data structure for flexibility, performance, and maintainability. Check if it supports nested menus (multi-level), dynamic additions/removals, and menu item properties (icons, badges, etc.). Deduct 5 points if the structure doesn't support nesting beyond 2 levels, 3 points if it lacks metadata support for menu items. Full score requires an optimized structure that balances performance with flexibility.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as missing user permissions, partial menu data, network failure during menu loading, etc.) and provide friendly error handling or fallback mechanisms. Code with strong robustness should handle edge cases effectively, 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. Menu animations with configurable transitions 2. Intelligent menu collapse based on screen size 3. User-customizable menu ordering/favorites). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant state management (e.g., duplicating menu state in component and Vuex) 2. Function modules unrelated to dynamic menus (e.g., extensive authentication systems) 3. Unnecessary re-renders due to poor state design. 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 (separation of menu logic/UI/state management), type safety (TypeScript usage or JSDoc annotations), and testability. 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 consideration for testing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the menu design follows modern UI principles: 1) Consistent spacing between menu items (8px rule) 2) Proper visual hierarchy for nested menus 3) Appropriate use of icons and typography (menu text should be at least 14px). Deduct 3 points for inconsistent spacing, 5 points for poor visual hierarchy, and 5 points for improper icon/text alignment. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the menu interactions are performant and user-friendly: 1) Menu expansion/collapse animations between 200-300ms 2) Responsive to viewport changes 3) Clear visual feedback for active/hover states. Deduct 5 points for jerky menu transitions, 3 points for poor responsive behavior, and 5 points for missing visual indicators for the current menu item. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "easy"
+}

package/library/management_systems-frontend_backend_platforms/vue3-electron-sqlite-knex-pinia-project.json

@@ -0,0 +1,68 @@
+{
+  "index": 1246,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the code you generate is executable for demonstration. This involves coding with the common structure of a Vue 3 project using Electron combined with better-sqlite3 and knex, also utilizing Pinia.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Vue 3 core architecture correctly implemented?",
+      "description": "Review whether the code accurately implements Vue 3 composition API features, including setup(), reactive state management, computed properties, and lifecycle hooks. Evaluate the proper use of ref(), reactive(), computed(), and watch(). Score 0 if Vue 3 specific features are not utilized, 5 if basic implementation exists but with optimization issues, and 10 if all Vue 3 best practices are followed with proper component organization.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is Electron integration properly configured and implemented?",
+      "description": "Check if the Electron main and renderer processes are correctly set up with proper IPC communication between them. Evaluate security considerations like contextIsolation and nodeIntegration settings. Verify that file system access, native dialogs, and window management are correctly implemented. Deduct 5 points if process separation is poor, 3 points if security best practices are ignored, and 2 points if native OS integration is missing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is SQLite database integration with better-sqlite3 and knex properly implemented?",
+      "description": "Evaluate whether database connections, migrations, and queries are properly implemented using better-sqlite3 and knex. Check for transaction support, proper error handling, and connection pool management. Assess if query builders are used instead of raw SQL where appropriate. Deduct 5 points if no migrations exist, 3 points if transactions are not used for critical operations, and 5 points if SQL injection vulnerabilities exist. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is Pinia state management effectively implemented?",
+      "description": "Analyze if Pinia stores are properly structured with state, getters, and actions. Check for proper store modularization, composition, and persistence handling. Evaluate if stores interact correctly with Vue components and avoid anti-patterns. Deduct 3 points if store composition is missing, 5 points if state mutations occur outside actions, and 5 points if stores are overly complex or redundant. 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 database connection failures, IPC errors, file system permission issues, etc.) and provide 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. Cross-platform file drag-and-drop support 2. Automatic database backup and version control 3. Live data synchronization between multiple app instances). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple state management solutions coexisting) 2. Function modules unrelated to the core application (e.g., unused libraries) 3. Fancy effects that affect performance (e.g., excessive animations or transitions). 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 components/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 or lacks proper configuration for Electron. 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) Database operations don't block the UI thread 3) Clear visual loading states during async operations. Deduct 5 points for each operation without feedback, 3 points for UI freezes during database operations, and 5 points for missing transitions between major view changes. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "medium"
+}

package/library/management_systems-frontend_backend_platforms/vue3-element-plus-project-generation.json

@@ -0,0 +1,68 @@
+{
+  "index": 1685,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate, professional responses. Be sure to provide executable code examples when possible. https://www.sowoll.com/#/dashboard Connect to generate a Vue3 + Vue3 + Element Plus project",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Vue3 project setup correctly implemented?",
+      "description": "Check if the code includes proper Vue3 initialization using createApp, proper configuration of Vue Router, and correct loading of Element Plus. Verify that the package.json includes the correct dependencies (vue@^3.x, element-plus, vue-router@^4.x), and that vite.config.js or vue.config.js is properly set up. Score 0 if Vue3 is not correctly configured, 5 if basic setup exists but is incomplete, and 10 if full configuration with proper imports, plugin registration, and environment variables is present.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is Element Plus properly integrated and configured?",
+      "description": "Evaluate whether Element Plus components are properly imported (either globally or on-demand with auto imports), theme customization is implemented, and icon libraries are correctly set up. Check if CSS imports for Element Plus are correctly placed in main.js or index.html. Deduct 5 points if the importing strategy leads to bundle bloat, 3 points if theme configuration is missing, and 2 points if icon setup is incorrect. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the dashboard layout properly implemented?",
+      "description": "Review whether the dashboard layout uses appropriate Element Plus components (such as el-container, el-header, el-aside, el-main) and proper responsive design. Check if the sidebar menu is collapsible and if the layout adapts to different screen sizes. Score 0 if no dashboard layout is implemented, 5 if basic layout exists but lacks responsiveness, and 10 if a fully responsive, well-structured dashboard with proper navigation components is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is proper state management implemented for the dashboard?",
+      "description": "Assess whether the code implements proper state management with Vue3's Composition API (ref, reactive), Pinia, or Vuex. Check for separation of concerns between views and state, and verify that dashboard data is properly reactive. Deduct 5 points if global state is mismanaged, 3 points if props/emits are improperly used, and 5 points if reactivity isn't properly leveraged. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as API failures, loading states, form validation errors) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should include try/catch blocks, error boundaries, and loading indicators. Give 10 points for comprehensive error handling and input validation, 5 points if basic error handling exists, and 0 points if exceptions are not handled at all.",
+      "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 2. Custom dashboard layout saving 3. Interactive data visualizations 4. Keyboard shortcuts for common operations). 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 component registrations or imports 2. Feature modules unrelated to the dashboard context 3. Heavy animations or effects 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 composition (single-responsibility components), file structure organization, code style consistency, and build process configuration. Deduct 5 points if component coupling is too high; deduct 5 points if naming conventions are inconsistent; deduct 5 points if no ESLint/Prettier configuration is present. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern design principles: 1) Consistent use of Element Plus design language 2) Proper whitespace and component spacing 3) Professional typography with consistent font hierarchy. Deduct 3 points for each inconsistent UI element, 5 points for misaligned components, and 5 points for inconsistent use of Element Plus styling. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the interactions conform to best practices: 1) Appropriate loading indicators for async operations 2) Smooth transitions between routes 3) Feedback for user actions within 100ms. Deduct 5 points for missing loading states during data fetching, 3 points for abrupt page transitions, and 5 points for unresponsive UI during heavy operations. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "medium"
+}