@getollie/cli 0.0.5 → 0.2.1

package/library/management_systems-frontend_backend_platforms/qiankun-react-micro-app-manual-load.json

@@ -1,68 +0,0 @@
-{
-  "index": 433,
-  "question": "You are a code expert, please utilize your professional knowledge to generate accurate and professional responses. Make sure the code you provide is executable for demonstration. You are a frontend expert, proficient in various micro-frontend architectures.\n\nUsing the qiankun framework, with all child applications manually loaded using loadMicroApp, write a simple React DEMO.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the qiankun framework properly initialized?",
-      "description": "Check if the main application correctly initializes qiankun with proper configuration (prefetch strategy, sandbox options, etc.). Verify that the initialization includes error handling for micro-app registration failures. Score 0 if qiankun is not initialized at all, 5 if basic initialization exists but lacks configuration options, and 10 if fully configured with error handling.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the micro-app loading mechanism correctly implemented using loadMicroApp?",
-      "description": "Verify that loadMicroApp is correctly used instead of registerMicroApps/start pattern. Check if the manual loading includes proper lifecycle management (mount, unmount, update) with appropriate error handling. Deduct 5 points if loadMicroApp is incorrectly used, 3 points if lifecycle events are not properly managed. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are the container elements for micro-apps properly managed?",
-      "description": "Examine if the React main application correctly creates and manages DOM container elements for each micro-app. Check if containers are created, referenced, and cleaned up appropriately to prevent memory leaks. Deduct 5 points for missing cleanup on unmount, 3 points for inefficient container management. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there proper data/state communication between main app and micro-apps?",
-      "description": "Evaluate if the demo implements proper communication mechanisms between the main app and micro-apps (props passing, custom events, shared state, etc.). Check if the communication is bidirectional and handles edge cases like undefined values. Deduct 5 points if communication is one-way only, 3 points if error handling is missing. 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 micro-app loading failures, network interruption, missing dependencies, 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. Dynamic micro-app loading based on user permissions 2. Performance monitoring for micro-apps 3. Preloading strategy for frequently used micro-apps). 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 micro-app loaders coexisting) 2. Function modules unrelated to micro-frontend architecture (e.g., unnecessary third-party libraries) 3. Fancy effects that affect performance (e.g., excessive animations during micro-app 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 config/loader/router 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) Micro-app loading and rendering delay ≤ 300ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual loading states during micro-app switches. Deduct 5 points for each micro-app transition without loading indicator, 3 points for jarring or flickering transitions, and 5 points for slow micro-app rendering (>1s). The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "hard"
-}

package/library/management_systems-frontend_backend_platforms/qt-interface-for-solidworks-ansys-data.json

@@ -1,68 +0,0 @@
-{
-  "index": 269,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate, professional responses. Be sure to ensure that the code you generate is executable for demonstration purposes. How can I implement a UI interface using QT that can call SolidWorks models and Ansys data? The functionality to implement is using QT to enable calls to SolidWorks and Ansys.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Qt-SolidWorks integration properly implemented?",
-      "description": "Review whether the code correctly implements the COM interface or SolidWorks API to communicate with SolidWorks models. Check for proper initialization, error handling during connection, and clean release of COM objects. Score 0 if no integration is implemented, 5 if basic model loading works but with limitations, and 10 if full model manipulation (loading, viewing, modifying) is properly implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the Qt-Ansys data integration functionality complete?",
-      "description": "Evaluate whether the code implements proper ways to access and manipulate Ansys data, either through Direct API, scripting interfaces (Python/APDL), or file-based communication. Check if it handles different data types (FEA results, thermal analysis, etc.). Deduct 5 points if only read-only operations are supported, and 3 points if the integration lacks error recovery mechanisms. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the data exchange mechanism between applications robust?",
-      "description": "Assess how data is exchanged between Qt, SolidWorks, and Ansys. Look for proper data format conversions, synchronization mechanisms, and handling of large datasets. A complete implementation should include progress indicators for long operations and graceful error handling when data transfer fails. Deduct 5 points if data synchronization is one-way only, 3 points if there's no data validation. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the UI provide comprehensive visualization of engineering data?",
-      "description": "Check if the Qt interface provides proper visualization components for SolidWorks models and Ansys results (stress contours, deformation plots, etc.). Review if the implementation uses appropriate Qt visualization libraries (like Qt3D, VTK integration, or custom OpenGL widgets). Deduct 5 points if visualization is static only, 3 points if interactive elements are missing. 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 application crashes, API version mismatches, memory limitations, 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. Real-time parameter sensitivity analysis 2. Automated report generation from simulation results 3. Gesture-based 3D model manipulation). 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 file loading mechanisms) 2. Function modules unrelated to engineering analysis (e.g., built-in social media sharing) 3. Fancy effects that affect performance (e.g., unnecessary animations during critical calculations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating UI/business logic/external API calls), unit test coverage, and error logging mechanisms. 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 proper dependency management for the external tools. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional engineering software standards?",
-      "description": "Evaluate whether the UI design follows engineering software conventions: 1) Properly organized toolbars and ribbons for common operations 2) Clear visual hierarchy for model browsers and property panels 3) Consistent use of engineering terminology and iconography. Deduct 3 points for cluttered workspaces, 5 points for non-standard engineering visualization coloring schemes, and 5 points for poor layout of critical data. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the performance optimization adequate for engineering workflows?",
-      "description": "Judge whether the implementation handles large engineering datasets efficiently: 1) Background processing for time-consuming operations 2) Appropriate level-of-detail rendering for complex models 3) Efficient memory management when dealing with large simulation results. Deduct 5 points for UI freezes during calculations, 3 points for excessive memory consumption, and 5 points for lack of caching mechanisms for frequently accessed data. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "hard"
-}

package/library/management_systems-frontend_backend_platforms/qt-palantir-style-web-ui-project.json

@@ -1,68 +0,0 @@
-{
-  "index": 266,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Ensure that the code you generate is executable for demonstration. Create a UI project using QT based on Palantir's style with web interface development as the foundation. This project should include Palantir's main elements and facilitate easy modification of styles, language switching between Chinese and English, etc. How can this be implemented? Please provide specific and complete code.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Qt UI framework properly set up with web interface integration?",
-      "description": "Evaluate whether the code properly establishes a Qt framework with web capabilities (WebEngineView or equivalent). Check if the bridge between Qt C++ and web components is correctly implemented with proper data binding. Score 0 if there's no integration between Qt and web, 5 if basic integration exists but with limitations, and 10 if there's seamless two-way communication between Qt and web components.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Does the implementation replicate Palantir's distinctive UI style accurately?",
-      "description": "Verify if the code implements key Palantir UI characteristics: dark theme with accent colors (typically blue/teal), data-dense interfaces, card-based components, and distinctive typography. Score based on completeness: 0 points if no Palantir styling is present, 5 points if basic styling elements are included, 10 points if the UI closely resembles Palantir's professional interface with attention to shadows, borders, and spacing.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the style modification system flexible and comprehensive?",
-      "description": "Evaluate if the code includes a robust theming system that allows dynamic style changes. Check for separation of style definitions (CSS/SCSS or Qt style sheets), theme manager implementation, and runtime style switching capability. Deduct 5 points if styles are hardcoded, 3 points if theme changes require application restart. The full score is 10 points for a fully abstracted theming system with hot-swappable styles.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the language switching functionality properly implemented?",
-      "description": "Check if internationalization is correctly implemented with a translation management system supporting at least Chinese and English. The implementation should include translation files/resources, dynamic text replacement mechanism, and proper handling of text expansion/contraction between languages. Deduct 5 points if translations are hardcoded, 3 points if language changes require application restart, and 2 points if right-to-left language support is missing. 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 resource loading failures, network interruption, user operation errors, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Animated transitions between views 2. Data visualization components 3. Gesture-based interactions). 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 theme management systems) 2. Function modules unrelated to UI framework (e.g., unnecessary data processing logic) 3. Fancy effects that affect performance (e.g., excessive animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating UI/logic/data layers), class organization, and build process setup. 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 properly configured with QMake/CMake. 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 Palantir's palette) 2) Proper layout spacing (element spacing follows consistent principles) 3) Professional font system (appropriate sizing hierarchy, consistent font families). Deduct 3 points for each crowded visual element, 5 points for inconsistent color schemes, 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 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": "medium"
-}

package/library/management_systems-frontend_backend_platforms/react-antd-admin-template.json

@@ -1,68 +0,0 @@
-{
-  "index": 1300,
-  "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 can be executed and displayed. Help me create a backend management template using React 18, Ant Design, Design Pro, and Redux.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the React 18 framework architecture properly implemented?",
-      "description": "Review whether the code correctly utilizes React 18's new features including Concurrent Features, Automatic Batching, and Suspense for data fetching. Check if the project structure follows modern React patterns with proper component composition and hooks usage. Score 0 if using outdated React patterns, 5 if basic React 18 setup without new features, and 10 if fully leveraging React 18's capabilities including Concurrent Rendering and new APIs.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is Ant Design integration comprehensive and theme-consistent?",
-      "description": "Evaluate whether Ant Design components are properly integrated with consistent theming, proper ConfigProvider setup, and customized design tokens. Check if the implementation includes responsive design, proper form validation, and accessibility features. Deduct 5 points if default styling is used without customization, 3 points if responsive breakpoints are not handled properly. Full score requires complete theme customization and component optimization.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is Ant Design Pro template structure and routing implemented correctly?",
-      "description": "Check whether the code implements proper ProLayout, route configuration with menu generation, and authentication guards. Evaluate if breadcrumb navigation, multi-tab support, and permission-based menu rendering are included. Deduct 5 points if basic layout structure is missing, 3 points if route guards are not implemented. Full score requires complete admin template features including settings drawer and layout customization.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is Redux state management architecture robust and scalable?",
-      "description": "Assess whether Redux implementation follows modern patterns with Redux Toolkit, proper slice organization, and async thunk handling. Check if middleware setup includes proper debugging tools, persistence layer, and normalized state structure. Deduct 5 points if using legacy Redux patterns, 3 points if state normalization is poor. Full score requires RTK Query integration, proper error handling, and optimistic updates.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust and error-resilient?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as API failures, network interruption, invalid user inputs, route errors, etc.) and provide friendly error boundaries and recovery mechanisms. Code with strong robustness should include proper loading states, error boundaries, and graceful degradation, giving 10 points. If the robustness is average, give 5 points, and if no error handling is implemented, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there innovative backend management features that enhance productivity?",
-      "description": "Check whether the code includes valuable features that improve admin efficiency (e.g., 1. Advanced data table with virtual scrolling 2. Real-time dashboard with WebSocket updates 3. Drag-and-drop form builder 4. Advanced search with filters 5. Bulk operations with progress tracking). Add 2 points for each well-implemented innovative feature (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant or unnecessary implementations?",
-      "description": "Strictly check three types of redundancy: 1. Duplicate component implementations (e.g., multiple table components with similar functionality) 2. Unused dependencies or features unrelated to backend management 3. Over-engineered solutions that complicate simple tasks. Deduct 3 points for each redundancy found, and directly deduct 10 points if core admin functionalities are hindered by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code demonstrate high engineering standards?",
-      "description": "Review modular architecture (proper separation of components, services, and utilities), TypeScript usage, testing implementation, and build optimization. Deduct 5 points if TypeScript types are poorly defined or any type is overused; deduct 5 points if no testing strategy is implemented; deduct 5 points if build optimization and code splitting are not configured. Full score requires comprehensive engineering practices.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface design meet professional admin dashboard standards?",
-      "description": "Evaluate whether the design follows modern admin interface principles: 1) Consistent color scheme with proper contrast ratios 2) Logical information hierarchy and spacing (following 8px grid system) 3) Professional typography with readable font sizes (≥14px for body text, proper line heights). Deduct 3 points for each cluttered interface section, 5 points for poor color contrast or accessibility issues, and 5 points for inconsistent spacing or typography. Full score requires polished, professional appearance.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Are interactions smooth with appropriate feedback mechanisms?",
-      "description": "Judge whether the user interactions provide appropriate feedback: 1) Button clicks and form submissions have immediate visual feedback ≤100ms 2) Loading states and transitions are smooth (300-500ms duration) 3) Navigation and state changes provide clear visual cues. Deduct 5 points for each interaction without proper feedback, 3 points for jerky animations or transitions, and 5 points for unclear navigation flow. Full score requires seamless, intuitive user experience.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "medium"
-}

package/library/management_systems-frontend_backend_platforms/react-company-portal-website.json

@@ -1,68 +0,0 @@
-{
-  "index": 320,
-  "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. Build a company portal website using React.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core React component architecture properly implemented?",
-      "description": "Evaluate if the code follows React best practices with proper component hierarchy, separation of concerns, and state management. Check for functional components with hooks rather than class components, proper prop drilling or context usage, and implementation of reusable components. Score 0 if React fundamentals are missing, 5 if basic components exist but lack organization, and 10 if components are well-structured with clear responsibilities.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is routing functionality implemented effectively?",
-      "description": "Check if React Router (or equivalent) is properly configured with nested routes, route parameters, protected routes for admin sections, and proper navigation handling. Verify if there's a 404 page and that history navigation works correctly. Deduct 5 points if only basic routing is implemented without nested routes, 3 points if navigation state isn't preserved, and 2 points if there's no route protection for sensitive areas.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are key company portal pages and sections included?",
-      "description": "Verify the implementation of essential company portal sections: Homepage with company overview, About/Team page, Services/Products section, Contact form, News/Blog section, and Career opportunities. Each missing critical section deducts 2 points. Score 10 if all essential sections are present with proper content structure and information hierarchy.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there state management for complex data flows?",
-      "description": "Evaluate whether appropriate state management solutions (Context API, Redux, Zustand, etc.) are implemented for global state. Check if data fetching is handled with proper loading/error states and if caching strategies are used. Deduct 5 points if global state is handled improperly, 3 points if there's no loading/error handling, and 2 points if no data persistence strategy exists.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as API failures, slow connections, invalid user inputs) and provide friendly error boundaries or fallback UIs. Code with strong robustness should implement form validation, handle API timeouts gracefully, and prevent common React pitfalls like infinite render loops. Give 10 points if edge cases are thoroughly handled, 5 points if basic error handling exists, and 0 points if no error handling is implemented.",
-      "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. Personalized dashboard for logged-in users 3. Interactive company timeline 4. Multilingual 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. Duplicate implementations of similar functionalities 2. Unnecessary third-party packages for simple tasks 3. Over-engineered solutions for basic requirements. Deduct 3 points for each redundancy found, and directly deduct 10 points if core performance is compromised by excessive features.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review code organization (proper folder structure, component naming conventions), testing implementation, and build configuration. Deduct 5 points if component organization is chaotic; deduct 3 points if there are no tests; deduct 2 points if there's no proper build optimization. Check for TypeScript usage or PropTypes for type checking, deducting 3 points if neither is used. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface design meet professional standards?",
-      "description": "Evaluate whether the UI implementation follows modern design principles: 1) Consistent component styling with a theme system 2) Responsive design for all screen sizes 3) Accessible UI elements with proper ARIA attributes 4) Consistent spacing and typography system. Deduct 3 points for inconsistent styling, 3 points for non-responsive layouts, and 4 points for accessibility issues. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the user interaction smooth and intuitive?",
-      "description": "Judge whether interactions provide appropriate feedback: 1) Form submission states clearly indicated 2) Navigation transitions are smooth 3) Interactive elements have hover/focus states 4) Loading states prevent UI jumping. Deduct 3 points for each missing feedback mechanism, 2 points for jarring transitions, and 5 points for confusing navigation patterns. Check if interactions work on both mouse and keyboard navigation, deducting 5 points for keyboard accessibility issues. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "hard"
-}

package/library/management_systems-frontend_backend_platforms/react-material-design-marketing-automation-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 1055,
-  "question": "You are a code expert, please use your professional knowledge to provide accurate, professional responses. Make sure the code generated is executable when possible. Develop a marketing automation system using React technology and Material Design that provides the following functions:\n1. User management\n2. Message template management, where during editing, an AI assistant helps generate marketing text messages/SMS copy",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the React application structure properly implemented with best practices?",
-      "description": "Evaluate whether the code follows React best practices including: proper component structure (presentational vs container components), appropriate use of hooks (useState, useEffect, useContext), implementation of React Router for navigation, and correct state management (Context API or Redux). Deduct 3 points if components are not properly modularized, 3 points for incorrect hook usage, and 4 points for poor state management. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the Material Design implementation correct and comprehensive?",
-      "description": "Check if the application correctly implements Material Design principles using either Material-UI (MUI) or another Material Design library. Verify proper use of components (Button, Card, Dialog, etc.), consistent theming, responsive layouts, and adherence to Material Design specifications. Award 10 points for complete implementation with custom theming, 5 points for basic implementation with standard components only, and 0 points if Material Design principles are not followed.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the user management system fully functional?",
-      "description": "Assess if the user management system includes essential CRUD operations, role-based access control, profile management, and secure authentication. Check for form validation, error handling, and proper data persistence. Award 10 points for a comprehensive system with all features, deduct 3 points for missing role management, 3 points for inadequate form validation, and 2 points for poor error handling.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the message template management system with AI integration properly implemented?",
-      "description": "Evaluate the template management system including: CRUD operations for templates, categorization, preview functionality, and most importantly, AI-assisted content generation. Check if the AI integration uses proper API calls, handles response states (loading/error/success), and allows user editing of AI suggestions. Award 10 points for full implementation, 5 points if AI integration is basic, and 0 points if AI assistance is missing.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as network errors, form validation failures, API 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. Real-time collaboration on templates 2. A/B testing capabilities for messages 3. Analytics dashboard for message performance). 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 authentication systems) 2. Function modules unrelated to marketing automation (e.g., a built-in game) 3. Fancy effects that affect performance (e.g., excessive animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating UI/business logic/API 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 (following Material Design color system) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional typography 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": "easy"
-}

package/library/management_systems-frontend_backend_platforms/real-time-interface-monitor-agent-status-planning-learning.json

@@ -1,68 +0,0 @@
-{
-  "index": 1198,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and expert responses. Pay attention to ensure that the code you generate is executable for demonstration. Please also add a real-time interface that can monitor the agent's operational status, consciousness state, planning, learning categories, and learning progress, then generate the complete code.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the AI agent core architecture fully implemented?",
-      "description": "Review whether the code accurately implements a complete agent system including perception, decision-making, action execution, and learning modules. Check if the agent has proper state management, goal setting, and task execution capabilities. Score 0 if core agent logic is missing, 5 if only basic state machine is implemented, and 10 if full autonomous agent architecture with modular design is included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the real-time monitoring interface comprehensively designed?",
-      "description": "Evaluate whether the monitoring dashboard includes all required components: operational status display, consciousness state visualization, planning process tracking, learning category breakdown, and progress indicators. Interface must update in real-time with WebSocket or similar technology. Deduct 5 points if any core monitoring component is missing, 3 points if real-time updates lag over 500ms. Full score requires live data streaming and interactive controls.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are the agent's consciousness state and planning mechanisms properly visualized?",
-      "description": "Check whether the code provides clear visualization of the agent's internal decision-making process, including current goals, active plans, decision trees, and reasoning chains. Must include visual representations like flowcharts, state diagrams, or mind maps. Deduct 5 points if consciousness state is only text-based, 3 points if planning visualization lacks interactivity. Requires dynamic updates showing thought processes in real-time.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the learning system with progress tracking fully functional?",
-      "description": "Evaluate whether the agent implements actual learning algorithms (reinforcement learning, neural networks, or adaptive algorithms) with categorized learning modules and measurable progress metrics. Must include learning rate visualization, skill acquisition tracking, and performance improvement graphs. Deduct 5 points if learning is simulated rather than functional, 3 points if progress metrics are not quantifiable or visualized.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as agent state corruption, monitoring interface disconnection, learning algorithm convergence failures, invalid user inputs, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should include error boundaries, graceful degradation, and automatic recovery. Give 10 points if fully robust, 5 points if average robustness, and 0 points if no exception handling.",
-      "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 agent monitoring experience (e.g., 1. 3D visualization of agent's neural network 2. Voice narration of agent's thoughts 3. Predictive analytics of agent behavior 4. Interactive agent training controls 5. Multi-agent comparison dashboards). 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 monitoring functions (e.g., multiple progress bars for same metric) 2. Feature modules unrelated to agent monitoring (e.g., built-in games or social features) 3. Excessive visual effects that impact performance (e.g., complex 3D animations that slow down real-time updates). Deduct 3 points for each redundancy found, and directly deduct 10 points if core monitoring functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (separating agent logic/monitoring interface/data processing layers), proper state management, and scalable architecture. Check for design patterns usage, code organization, and maintainability. Deduct 5 points if global state pollution is found or poor separation of concerns; deduct 5 points if code duplication rate exceeds 30%; deduct 5 points if no proper error logging or debugging capabilities. Full score requires clean architecture and professional coding standards.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional dashboard design standards?",
-      "description": "Evaluate whether the monitoring dashboard follows modern UI/UX principles: 1) Information hierarchy with clear visual grouping 2) Consistent color coding for different agent states 3) Proper data visualization techniques (charts, graphs, indicators) 4) Responsive layout that works on different screen sizes. Deduct 3 points for each cluttered section, 5 points for poor color choices that harm readability, and 5 points for inconsistent visual design patterns.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the real-time interaction smooth and intuitive?",
-      "description": "Judge whether the monitoring interface provides seamless real-time experience: 1) Data updates without screen flickering 2) Smooth transitions between different monitoring views 3) Responsive controls for interacting with agent 4) Clear feedback for user actions 5) Intuitive navigation between monitoring sections. Deduct 5 points for each laggy interaction, 3 points for confusing navigation, and 5 points for poor visual feedback on user actions.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "medium"
-}

package/library/management_systems-frontend_backend_platforms/real-time-job-recruitment-software.json

@@ -1,68 +0,0 @@
-{
-  "index": 830,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate, professional responses. Make sure the code you generate is executable for demonstration purposes. Build a page recruitment software where job positions are updated in real-time.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the real-time job position update system fully implemented?",
-      "description": "Review whether the code implements WebSocket or Server-Sent Events for real-time job position updates. Check if the system handles new job postings, position modifications, and removals properly. Score 0 if real-time functionality is not implemented, 5 if basic polling is used instead of true real-time solutions, and 10 if a complete real-time system with proper event handling is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the job listing display and filtering functionality complete?",
-      "description": "Evaluate whether the code provides comprehensive job listing features including sorting (by date, relevance, salary), filtering (by industry, location, experience level, etc.), and pagination. Deduct 3 points if sorting options are limited, 3 points if filtering is basic or missing key filters, and 4 points if pagination is absent or poorly implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the job search functionality effectively implemented?",
-      "description": "Check if the search feature includes full-text search, keyword highlighting, autocomplete suggestions, and search history. Assess if the search algorithm handles typos and provides relevant results. Deduct 3 points if autocomplete is missing, 3 points if the search doesn't handle partial matches or typos, and 4 points if search results aren't properly ranked by relevance. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there a complete user account and job application system?",
-      "description": "Review whether the code includes user registration/login, profile management, resume upload/management, application tracking, and saved job functionality. Deduct 3 points if authentication is basic or insecure, 3 points if profile/resume management is limited, and 4 points if the application tracking system is incomplete. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as network interruptions, server errors, invalid inputs, etc.) and provide friendly error prompts or recovery mechanisms. Check for proper input validation, error boundary implementation, and offline capabilities. Give 10 points for comprehensive error handling, 5 points for average robustness, and 0 points if exceptions are not handled.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. AI-powered job matching 2. Interactive salary comparison tools 3. Company culture insights visualization 4. Interview preparation resources). 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 notification systems) 2. Function modules unrelated to recruitment (e.g., a news feed unrelated to jobs) 3. Fancy effects that affect performance (e.g., excessive animations that slow page loading). 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/UI/service layers), component reusability, state management implementation, and build process optimization. Deduct 3 points if global state management is poorly implemented, 3 points if code reusability is low with high duplication, and 4 points if the build process lacks optimization for performance. 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 recruitment platform principles: 1) Clean, professional color scheme appropriate for job searching 2) Consistent spacing and alignment throughout 3) Typography hierarchy that enhances readability of job listings. Deduct 3 points for cluttered job cards, 3 points for inconsistent button styles/behaviors, and 4 points for poor information hierarchy that makes scanning jobs difficult. 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) New job notifications appear without disrupting user flow 2) Job application process feels seamless with appropriate feedback 3) Filtering/sorting actions update results with minimal perceived delay. Deduct 3 points for jarring transitions between pages, 3 points for lack of loading states during data fetching, and 4 points for unresponsive interface elements during real-time updates. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "hard"
-}