@getollie/cli 0.0.4 → 0.2.0

package/library/management_systems-frontend_backend_platforms/educational-management-system-teaching-lab-experiments.json

@@ -1,68 +0,0 @@
-{
-  "index": 1453,
-  "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. Using educational management as an example, help me write a comprehensive system that includes teaching courses, laboratory courses, and experiments. In this educational management system, laboratory courses are part of the teaching management, laboratory courses contain experiments, teachers create experiment-related information, and students learn through experiments.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core educational management system fully implemented?",
-      "description": "Review whether the code accurately implements the fundamental educational management system components including course management (creation, updating, deletion), teacher/student registration, enrollment functionality, and grade tracking. Score 0 if no core functionality is implemented, 5 if only basic CRUD operations are available, and 10 if a complete system with role-based permissions and workflow is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the laboratory course management subsystem properly integrated?",
-      "description": "Evaluate whether laboratory courses are properly implemented as a specialized type of course with appropriate inheritance/composition relationships to the main course structure. Check if lab courses have distinct properties (equipment requirements, capacity limits, safety protocols) while maintaining core course attributes. Deduct 5 points if labs are implemented as completely separate entities without proper integration, and 3 points if lab-specific attributes are missing. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the experiment management functionality comprehensive?",
-      "description": "Check whether experiments within laboratory courses have complete lifecycle management including creation by teachers, assignment to students, submission by students, evaluation, and feedback mechanisms. Verify if experiments have appropriate metadata (time estimates, difficulty levels, prerequisites, learning objectives). Deduct 5 points if the experiment submission workflow is incomplete, and 3 points if metadata or learning analytics are missing. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the teacher-student interaction model properly designed?",
-      "description": "Assess whether the system successfully models teacher-student relationships across regular courses and laboratory experiments. Check if teachers can create, assign, track, and evaluate student experiment participation, and if students can view assignments, submit work, receive feedback, and track progress. Deduct 5 points if the notification system for new assignments/submissions is missing, and 3 points if the feedback mechanism is one-directional. 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 enrollments, scheduling conflicts, submission after deadlines, 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 educational experience (e.g., 1. AI-assisted grading system 2. Interactive virtual laboratory simulations 3. Learning analytics dashboard with performance predictions). 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 user management systems coexisting) 2. Function modules unrelated to educational management (e.g., a built-in social network) 3. Fancy effects that affect performance (e.g., unnecessary animations in critical workflows). 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/view/data access layers), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast sliding, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "hard"
-}

package/library/management_systems-frontend_backend_platforms/electricity-consumption-data-management-vue-upgrade.json

@@ -1,68 +0,0 @@
-{
-  "index": 1125,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the generated code is executable when possible. Provide functionality for manual entry of historical electricity consumption data for various company yards in 2022 and 2023. Input information includes electricity consumption category, equipment code, equipment name, energy consumption, workload, unit consumption, electricity consumption month, and other information. The functionality should include adding, modifying, editing, deleting, importing, and exporting yard electricity consumption data.\n\nThe frontend needs to be upgraded from Vue 2.0 to Vue 3.0, and the functionality migrated to the Yuheng development framework. Adjust functional components and styles to adapt to the new framework, and switch the usage methods of common entity classes and utility classes to ensure comprehensive adjustment and adaptation of code functionality.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the electricity consumption data entry functionality fully implemented?",
-      "description": "Review whether the code implements all required data fields (electricity consumption category, equipment code, equipment name, energy consumption, workload, unit consumption, electricity consumption month, etc.) with appropriate validation. Check for field type enforcement, range validation, and required field handling. Score 0 if core data structures are missing, 5 if basic fields are implemented but lack validation, and 10 if complete with comprehensive validation.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are all CRUD operations properly implemented for yard electricity consumption data?",
-      "description": "Evaluate whether the code properly implements adding, modifying, editing, deleting operations with appropriate state management. Check for optimistic updates, proper error handling during operations, and confirmation dialogs for destructive actions. Deduct 2 points for each missing operation, 3 points if operations don't update the UI appropriately, and 3 points if there's no validation feedback. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the data import/export functionality properly implemented?",
-      "description": "Check for robust import/export capabilities including file format support (CSV, Excel), validation of imported data, progress indicators for large datasets, and error reporting. Verify that exported files contain complete and accurate data. Deduct 3 points if import validation is missing, 3 points if export formatting options are limited, and 5 points if large file handling isn't optimized. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Has the Vue 2.0 to Vue 3.0 migration been properly executed?",
-      "description": "Evaluate whether the code successfully migrates from Vue 2.0 to 3.0, including: replacing the Options API with Composition API where appropriate, converting event bus patterns to provide/inject or state management, updating lifecycle hooks, and proper handling of reactive state. Deduct 5 points if deprecated Vue 2 syntax is still used, 3 points if reactivity isn't properly implemented with Vue 3 methods, and 5 points if there are console errors related to API incompatibilities. 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 errors, invalid user input, API failures) 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. Smart data entry suggestions based on historical patterns 2. Interactive data visualization for consumption trends 3. Automated data anomaly detection). 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 validation logic coexisting) 2. Function modules unrelated to electricity consumption tracking (e.g., unnecessary animations or widgets) 3. Performance-impacting features that don't add value to the core functionality. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating data models/view components/service layers), unit test coverage, and build process adaptation to the Yuheng framework. 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 integration with the Yuheng development framework is incomplete. 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 form design (consistent field widths, clear grouping of related fields). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic form layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Form submission feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual feedback for data operation success/failure. Deduct 5 points for each operation without feedback, 3 points for UI freezing during data processing, and 5 points for confusing navigation patterns. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "easy"
-}

package/library/management_systems-frontend_backend_platforms/electricity-consumption-vue3-upgrade.json

@@ -1,68 +0,0 @@
-{
-  "index": 1380,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Ensure that the code you generate is executable. Provide functionality for manual data entry of electricity consumption original data for various companies in 2022 and 2023. Data entry items include electricity consumption category, equipment code, equipment name, energy consumption amount, workload, unit consumption, electricity consumption month, and other information. Features include adding, modifying, editing, deleting, importing, and exporting electricity consumption data.\n\nBased on manually entered or imported electricity consumption data, automatically calculate the per-container energy consumption for standard containers and natural containers for equipment in the corresponding month.\n\nUpgrade the front-end from Vue 2.0 to Vue 3.0, and migrate the functionality to the Yuheng development framework. Adjust function components and styles to adapt to the new framework, and switch the usage methods of common entity classes and utility classes to ensure comprehensive adjustment and adaptation of code functionality.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "1. Is the electricity consumption data entry functionality fully implemented?",
-      "description": "Review whether the code accurately implements all required data entry fields (electricity consumption category, equipment code, equipment name, energy consumption amount, workload, unit consumption, electricity consumption month, etc.) with proper validation. Check if the form layout is responsive and user-friendly.Score 0 if core data entry fields are missing, 5 if basic fields are implemented without validation, and 10 if all fields are implemented with proper validation, formatting, and user guidance.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "2. Are all CRUD operations properly implemented for electricity consumption data?",
-      "description": "Evaluate the implementation of adding, modifying, editing, deleting, importing, and exporting electricity consumption data. Check for proper state management, error handling, and user feedback during these operations.Deduct 2 points for each missing operation. Deduct 1 point for each operation lacking proper error handling or user feedback. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "3. Is the automatic calculation of per-container energy consumption correctly implemented?",
-      "description": "Check if the code correctly calculates the per-container energy consumption for both standard containers and natural containers based on the entered data. Verify calculation logic, formula implementation, and dynamic updates when source data changes.Deduct 5 points if either standard container or natural container calculations are missing or incorrect. Deduct 3 points if calculations don't update dynamically. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "4. Has the migration from Vue 2.0 to Vue 3.0 been properly executed?",
-      "description": "Evaluate whether the code correctly implements Vue 3 Composition API instead of Options API, replaces Vue 2 specific features with Vue 3 equivalents, and properly handles migration of global plugins and components. Check for the use of script setup, Teleport, Fragments and other Vue 3 features.Deduct 3 points if reactive state management isn't using Vue 3 patterns, 3 points if lifecycle hooks aren't properly migrated, 2 points if template syntax isn't updated, and 2 points if Vue 3 specific features aren't leveraged. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "5. Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid data input, network interruption, empty data sets, etc.) and provide friendly error prompts or recovery mechanisms.Code with strong robustness should be able to effectively handle 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": "6. Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Real-time data visualization 2. Smart data validation and suggestions 3. Keyboard shortcuts for power users 4. Batch processing operations).Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "7. Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple data validation methods) 2. Function modules unrelated to electricity consumption data management 3. Fancy effects that affect performance (e.g., unnecessary animations).Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "8. Does the code have engineering quality?",
-      "description": "Review modular design (such as separating data management/UI components/business logic), unit test coverage, and adherence to Yuheng development framework standards. Check for proper TypeScript usage, component reusability, and maintainable code structure.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 Yuheng framework standards aren't followed. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "9. 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": "10. 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 for electricity data entry flows.Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast form navigation, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "easy"
-}

package/library/management_systems-frontend_backend_platforms/electricity-price-model-configuration.json

@@ -1,68 +0,0 @@
-{
-  "index": 1537,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure that the generated code is executable for demonstration. Based on this information, could you help me create a product prototype for an \"Electricity Price Model Configuration Module\"? Either provide an image directly or give me an HTML file that I can open in my browser myself.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the electricity price model configuration interface fully implemented?",
-      "description": "Review whether the code accurately implements configurable electricity pricing models through HTML/JavaScript, including time-of-use (TOU) pricing, tiered pricing, demand charges, and seasonal rate adjustments. Check if the interface allows users to set multiple rate periods, define price thresholds, and configure complex pricing structures. Score 0 if no pricing model configuration is implemented, 5 if only basic single-rate configuration exists, and 10 if comprehensive multi-tier pricing models with time-based variations are fully supported.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the dynamic price calculation and preview functionality implemented?",
-      "description": "Evaluate whether the system provides real-time calculation of electricity costs based on configured parameters, with live preview of pricing impact. Check if the code includes validation for price configuration conflicts, automatic calculation of blended rates, and graphical representation of price structures. Deduct 5 points if calculation logic is missing or incorrect, and 3 points if no visual feedback is provided for price changes. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the configuration data management and persistence mechanism designed?",
-      "description": "Check whether the prototype includes proper data structure for storing pricing configurations, supports import/export of pricing templates, and provides version control for different pricing schemes. Evaluate if the system can handle multiple utility rate schedules and allows for easy switching between configurations. Deduct 5 points if no data persistence is implemented, and 3 points if configuration templates cannot be saved or loaded. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the pricing model validation and testing framework constructed?",
-      "description": "Review whether the code includes comprehensive validation for pricing model consistency, conflict detection between overlapping rate periods, and scenario testing capabilities. Check if the system provides simulation tools to test pricing models against sample usage data and generates accuracy reports. Deduct 5 points if no validation logic exists, and 3 points if edge cases in pricing periods are not handled. Give 10 points if fully implemented with comprehensive testing scenarios.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid price inputs, overlapping time periods, negative rates, extreme values, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should effectively validate all user inputs, handle edge cases gracefully, and prevent system crashes from malformed data, 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 user experience (e.g., 1. Interactive pricing calendar with drag-and-drop rate setting 2. Smart pricing recommendations based on usage patterns 3. Real-time cost impact visualization 4. Pricing model comparison 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 price calculation engines coexisting) 2. Function modules unrelated to electricity pricing (e.g., weather widgets or unrelated utilities) 3. Fancy effects that affect usability (e.g., excessive animations during price configuration). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core pricing configuration 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 pricing logic/UI components/data models), code organization, and maintainability. Deduct 5 points if global state pollution is found or proper separation of concerns is not implemented; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the code structure is not scalable for adding new pricing models. 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 enterprise application design principles: 1) Professional color scheme suitable for utility management interfaces (no more than 3 primary colors) 2) Clear information hierarchy with proper spacing (element spacing follows the 8px multiple principle) 3) Professional typography system (body font size ≥ 14px, line height over 1.5 times) 4) Intuitive form layouts for complex pricing data. Deduct 3 points for each crowded visual element, 5 points for unprofessional color combinations, and 5 points for confusing data presentation layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and intuitive for configuration tasks?",
-      "description": "Judge whether the interface interactions are optimized for complex configuration tasks: 1) Form input feedback delay ≤ 100ms 2) Smooth transitions when switching between pricing models (300-500ms) 3) Clear visual indicators for active configuration sections 4) Intuitive navigation between different pricing parameters. Deduct 5 points for each configuration action without proper feedback, 3 points for confusing navigation flow, and 5 points for hard-to-locate critical configuration options. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "medium"
-}

package/library/management_systems-frontend_backend_platforms/electron-apple-books-like-bookshelf-app.json

@@ -1,68 +0,0 @@
-{
-  "index": 800,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure that any code you generate is executable and demonstrable. Develop a complete bookshelf application using Electron that has an interface similar to Apple Books, with capabilities for adding, deleting, modifying, and searching.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Apple Books-like interface design fully implemented?",
-      "description": "Review whether the code accurately replicates Apple Books' visual design through HTML/CSS/JavaScript, including the grid/list view toggle, book cover display with proper shadows and rounded corners, and smooth transitions between views. Check if the interface includes the characteristic typography, color scheme (light/dark mode support), and layout proportions matching Apple Books. Score 0 if basic UI structure is missing, 5 if only basic layout is implemented without proper styling, and 10 if the interface closely matches Apple Books' aesthetic standards.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the CRUD operations (add, delete, modify, search) fully functional?",
-      "description": "Evaluate whether all four core operations are properly implemented: 1) Add books with metadata input forms and file import capabilities 2) Delete books with confirmation dialogs and proper cleanup 3) Modify book information with inline editing or modal forms 4) Search functionality with real-time filtering and advanced search options. Check if data persistence is handled correctly using Electron's file system or database integration. Deduct 3 points for each missing operation, and 2 points if operations lack proper validation or error handling. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the Electron application architecture properly structured?",
-      "description": "Check whether the Electron app follows best practices with proper main/renderer process separation, secure IPC communication, and appropriate context isolation. Evaluate if the app includes proper window management, menu integration, and platform-specific features. Verify that security measures are in place (nodeIntegration disabled, contextIsolation enabled). Deduct 5 points if security vulnerabilities exist, 3 points if IPC communication is not properly structured, and 2 points if platform integration is missing. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the data management and persistence system robust?",
-      "description": "Assess whether the application includes a comprehensive data management system for book storage, metadata handling, and file organization. Check if the system supports various book formats, maintains data integrity, includes backup/restore functionality, and handles large libraries efficiently. Evaluate if the database schema (SQLite/JSON) is well-designed with proper indexing for search performance. Deduct 5 points if no persistent storage is implemented, 3 points if data integrity mechanisms are missing, and 2 points if performance optimization is lacking. 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 corrupted book files, disk space issues, invalid metadata, network errors for online features, 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 user experience (e.g., 1. Reading progress tracking with visual indicators 2. Smart book recommendations based on reading history 3. Export/import library functionality 4. Book preview with flip animation 5. Reading statistics dashboard). 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 search mechanisms coexisting) 2. Function modules unrelated to bookshelf management (e.g., built-in games or unrelated utilities) 3. Excessive animations or effects that impact performance (e.g., complex 3D transitions). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core bookshelf functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (separating UI components, data layer, and Electron-specific modules), proper error handling, and build process automation. Check for proper TypeScript usage if applicable, ESLint configuration, and packaging scripts. Deduct 5 points if global state pollution is found or proper architecture patterns are not used; deduct 3 points if code duplication rate is high (over 25%); deduct 2 points if build/packaging 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 consistent with Apple's design language 2) Proper layout spacing with consistent margins and padding 3) Professional typography system with appropriate font sizes and hierarchy 4) Responsive grid layout for different window sizes. Deduct 3 points for each visually inconsistent element, 5 points for poor color harmony that doesn't match Apple Books aesthetic, and 3 points for improper spacing or alignment issues. 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 Apple's Human Interface Guidelines: 1) Hover states and click feedback with proper timing 2) Smooth transitions between grid and list views 3) Fluid animations for book operations (add/delete/modify) 4) Responsive scrolling and loading states 5) Proper focus management for keyboard navigation. Deduct 4 points for each missing interaction feedback, 3 points for janky animations or performance issues, and 3 points for poor accessibility support. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "hard"
-}

package/library/management_systems-frontend_backend_platforms/electron-vue-typescript-epub-reader-desktop-app.json

@@ -1,68 +0,0 @@
-{
-  "index": 711,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the generated code is executable for demonstration. Create an epub reader desktop application using electron+vue3+vite+typescript",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the EPUB parsing and rendering functionality fully implemented?",
-      "description": "Verify if the code correctly implements EPUB parsing (extracting content, metadata, TOC from .epub files) and renders HTML/CSS content from EPUB files. Score 0 if core parsing is missing, 5 if basic content display works but with formatting issues, and 10 if it properly handles EPUB 2.0/3.0 standards including complex layouts, embedded fonts, and media overlays.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the e-reader navigation system complete and user-friendly?",
-      "description": "Check if the application implements essential navigation features: table of contents navigation, page turning animations, bookmarking system, search function, and reading progress tracking. Deduct 2 points for each missing core navigation feature. Score 10 only if the navigation is both complete and intuitive with keyboard shortcuts, touch gestures, and visual indicators.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the Electron integration properly implemented with Vue3 and Vite?",
-      "description": "Evaluate whether the code properly implements Electron's main and renderer processes with appropriate IPC communication. Check if the TypeScript types are correctly defined for Electron API interactions. Deduct 5 points if process separation is incorrect, 3 points if TypeScript interfaces are missing/incorrect, and 3 points if Vite configuration doesn't handle Electron's development and production builds properly.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the EPUB library management system robust and feature-complete?",
-      "description": "Assess if the application includes a library management system with metadata extraction, cover display, sorting/filtering options, and file system integration for importing and organizing EPUB files. Score 0 if no library management exists, 5 if basic listing is available, and 10 if it includes advanced features like collection management, reading history, and metadata editing.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as corrupt EPUB files, missing permissions, concurrent file operations, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Night reading mode with blue light filter 2. Text-to-speech integration 3. Note-taking and highlighting with cloud sync 4. Dictionary/translation integration). 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 layout engines) 2. Function modules unrelated to e-reading (e.g., a built-in game) 3. Fancy effects that affect performance (e.g., excessive animations that slow down page turning). 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 TypeScript usage quality (proper interfaces/types, no any types), component architecture (proper separation of concerns, reusable components), state management patterns, and build process automation. Deduct 5 points if TypeScript is used incorrectly or inconsistently; deduct 3 points if components are tightly coupled; deduct 3 points if state management is chaotic; deduct 2 points if the build process is not optimized for both development and production. 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 desktop application design principles: 1) Consistent theme with proper light/dark mode support 2) Proper use of whitespace and content hierarchy 3) Professional typography system with appropriate font scaling for readability. Deduct 3 points for inconsistent UI elements, 3 points for poor readability settings, and 4 points for lack of responsive design for different screen sizes. 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 desktop application standards: 1) Fast startup time (under 3 seconds) 2) Smooth page turns without flickering 3) Responsive UI even with large EPUB files 4) Proper loading indicators for background operations. Deduct 3 points for laggy scrolling/page turning, 3 points for UI freezes during file operations, and 4 points for noticeable rendering issues when changing display settings. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "hard"
-}

package/library/management_systems-frontend_backend_platforms/electron-vue2-network-requests.json

@@ -1,68 +0,0 @@
-{
-  "index": 248,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code examples when possible. Electron+Vue2.0 local application sending network requests",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Electron setup properly configured for Vue 2.0 integration?",
-      "description": "Review whether the project structure correctly integrates Vue 2.0 within Electron with proper main and renderer process separation. Check if background.js (main process) and Vue app initialization are correctly linked. Score 0 if no proper integration exists, 5 if basic setup is implemented but with architectural flaws, and 10 if the integration follows Electron best practices with clear process separation.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are network requests implemented with appropriate libraries and error handling?",
-      "description": "Evaluate the network request implementation (Axios, Fetch API, or Electron's net module). Check for proper timeout configurations, retry mechanisms, and comprehensive error handling. Deduct 3 points if CORS handling is missing for external APIs, 3 points if no request/response interceptors are implemented, and 5 points if error states aren't properly managed. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is there proper main and renderer process communication for network operations?",
-      "description": "Check if the application uses appropriate IPC channels (ipcMain/ipcRenderer) for network-related operations that should be in the main process. Evaluate if proper security measures are in place when handling external data. Deduct 5 points if all network requests are made directly from the renderer process without security considerations, and 3 points if IPC communication lacks error handling. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are offline capabilities and connection management implemented?",
-      "description": "Review whether the code handles network connectivity issues, includes offline detection, and implements data caching mechanisms. Check for online/offline event listeners and graceful degradation strategies. Deduct 5 points if no offline detection exists, 3 points if request queueing for offline mode is missing, and 3 points if no visual indicators for connection status are provided. 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, malformed responses, certificate issues, network timeouts, 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. Smart request throttling/batching 2. Background synchronization with system tray notifications 3. Visual network activity monitor). 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. Multiple HTTP client implementations coexisting without clear purpose 2. Unnecessary polling when WebSockets would be more appropriate 3. Excessive logging that impacts 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 modular design (such as separating API services/business logic/UI components), unit test coverage for network operations, and proper environment configuration for development vs production. 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 no environment-based API configuration exists. 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) Loading states for network operations appear within 300ms 2) Progress indicators for long-running requests 3) Smooth transitions for data updates after requests complete. Deduct 5 points for each operation without loading feedback, 3 points for jumpy layouts during data loading/updating, and 5 points for blocked UI during network operations. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "medium"
-}

package/library/management_systems-frontend_backend_platforms/electronic-fence-management-vue3-autonavi.json

@@ -1,68 +0,0 @@
-{
-  "index": 714,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that any code you generate is executable. I want to develop several screens using the AutoNavi (Gaode) API with VUE3.\n\nFirst screen: Electronic Fence Management\nThe screen layout should be half data display area and half map. When I click on an electronic fence data entry, the map area should simultaneously display the electronic fence style. The screen should support adding, deleting, modifying, and querying electronic fences, and also allow customization directly on the map.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Electronic Fence Implementation",
-      "description": "Check if the code implements a complete electronic fence system with AutoNavi's API in Vue3, including polygon, circle, and rectangle fence types with visual representations. Score 0 if no fence drawing is implemented, 5 if only basic shapes without editing capabilities, and 10 if all fence types are implemented with full editing functionality.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Map and Data Area Integration",
-      "description": "Evaluate the implementation of the half-data, half-map layout, checking whether the split view is properly responsive and maintains appropriate proportions across different screen sizes. Ensure synchronization between data entries and map visualization is working correctly (clicking a fence in the list highlights it on the map). Deduct 5 points if synchronization has noticeable lag (>200ms), 3 points if the layout breaks on certain screen sizes. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "CRUD Operations for Electronic Fences",
-      "description": "Verify that all create, read, update, and delete operations for electronic fences are properly implemented. Each operation should update both the data display and map visualization. Check for client-side validation of fence parameters and proper error handling. Deduct 3 points for each missing operation, 3 points for improper validation. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Map-based Fence Customization",
-      "description": "Examine whether direct fence manipulation on the map is supported (drawing new fences, resizing, moving vertices, etc.). Check if the editing interface is intuitive with proper mouse interaction feedback. Deduct 5 points if vertex editing is not supported, 3 points if fence creation requires complex steps, and 3 points if there's no visual feedback during editing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Code Robustness",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as API failures, invalid coordinate inputs, concurrent edits, 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": "Innovative Features",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Batch import/export of fence data 2. Fence conflict detection 3. History tracking of fence changes 4. Heat map visualization of fence interactions). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Feature Redundancy",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple ways to edit the same fence property) 2. Function modules unrelated to fence management (e.g., unnecessary weather overlays) 3. Fancy effects that affect map 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": "Engineering Quality",
-      "description": "Review Vue3 component architecture, state management approach, code reusability, and proper use of Vue's Composition API. Deduct 5 points if global state is mismanaged; deduct 3 points if components are too tightly coupled; deduct 5 points if API integration is not properly abstracted; deduct 3 points if Vue3 best practices are not followed. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Interface Design Quality",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing for both map and data areas 3) Professional typography system (consistent font hierarchy). Deduct 3 points for cluttered list displays, 5 points for poor contrast between map and UI elements, and 5 points for inconsistent styling between data area and map controls. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Interaction Fluidity",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Immediate visual feedback when selecting fences 2) Smooth animations for fence creation/editing (300-500ms) 3) Clear visual indicators for active/selected fences. Deduct 5 points for laggy map interactions, 3 points for jarring transitions between data and map updates, and 5 points for confusing fence selection states. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "medium"
-}