@getollie/cli 0.0.5 → 0.2.1

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

@@ -1,68 +0,0 @@
-{
-  "index": 939,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Big Data Healthcare Project:\n\n## Interface Menu: API Rate Limiting Strategy\n\n### Functionality:\n**Rate Limiting Strategy Configuration**: Users can customize API rate limiting strategies through the following settings:\n- Duration Limit: Set time duration restrictions for API interface calls.\n- API Traffic Limit Count: Set call frequency limitations for API interfaces.\n- User Traffic Limit: Set call frequency limitations for each user.\n- Application Traffic Limit: Set call frequency limitations for each application.\n\n**Strategy Management**: Display all configured rate limiting strategies, supporting operations such as editing, deleting, viewing detailed information, etc.\n\n**Strategy Monitoring**: Monitor the implementation of rate limiting strategies, display records of non-compliant calls.\n\nBased on the above functional description, implement a new strategy form and data list of existing strategies using ant-design-vue 1.7.8.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Rate Limiting Strategy Configuration form fully implemented?",
-      "description": "Examine whether the form correctly implements all required configuration fields (Duration Limit, API Traffic Limit Count, User Traffic Limit, Application Traffic Limit) using ant-design-vue components. Check for proper form validation, field descriptions, tooltips, and intuitive input controls. Score 0 if core fields are missing, 5 if basic fields exist but lack validation, and 10 if all fields are properly implemented with complete validation logic.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the Strategy Management data list properly implemented?",
-      "description": "Verify that the data list displays all configured rate limiting strategies with appropriate columns. Check for the implementation of edit, delete, and detail view operations. The table should include pagination, sorting capabilities, and filtering options. Deduct 3 points if any CRUD operation is missing, 3 points if pagination is not implemented, and 2 points if sorting/filtering is absent. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the Strategy Monitoring visualization implemented?",
-      "description": "Evaluate whether the monitoring interface displays records of non-compliant calls effectively. Look for visual indicators (charts, graphs, status indicators) showing rate limit violations. Assess whether time-series data is presented and if filtering by API/user/application is available. Award 10 points for comprehensive monitoring with visualizations, 5 points for basic tabular data without visualizations, and 0 points if monitoring is not implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the ant-design-vue 1.7.8 component library properly utilized?",
-      "description": "Check if the implementation correctly uses ant-design-vue 1.7.8 components and follows the library's design patterns and best practices. Verify that appropriate components are used for each UI element (Form, Table, Modal, Card, etc.) and that they are configured properly. Deduct 3 points for each misused component or implementation that doesn't follow ant-design-vue conventions. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as form validation errors, network failures, empty data states, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Real-time rate limit visualization 2. Threshold recommendation based on historical data 3. One-click template application for common API types). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple form validation logics coexisting) 2. Function modules unrelated to rate limiting (e.g., unnecessary user profile features) 3. Fancy effects that affect performance (e.g., excessive animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating UI components/services/state management), code reusability, and maintainability. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no clear separation of concerns. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (consistent with ant-design-vue's design system) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional form and table layout (aligned labels, consistent input sizes). Deduct 3 points for each crowded visual element, 5 points for inconsistent styling that breaks ant-design visual guidelines, and 5 points for chaotic form or table layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Form submission and response feedback ≤ 300ms 2) Smooth transitions between strategy list and detail views 3) Clear loading states during data fetching. Deduct 5 points for operations without feedback, 3 points for jarring transitions between views, and 5 points for confusing user flows when creating or editing strategies. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "easy"
-}

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

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

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

@@ -1,68 +0,0 @@
-{
-  "index": 1442,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable for demonstration. Write an ATM user interface that implements complete functionality including user login, deposits and withdrawals, balance inquiries, receipt printing, etc., using front-end technologies.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the login and authentication system fully implemented?",
-      "description": "Review whether the code properly implements user authentication with proper input validation, secure handling of credentials, and session management. Check if there are measures against brute force attacks (like account lockout) and if proper error messages are displayed without revealing sensitive information. Score 0 if authentication is missing, 5 if basic authentication is implemented without security measures, and 10 if comprehensive secure authentication is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the core ATM operations (deposit, withdrawal, balance inquiry) fully functional?",
-      "description": "Evaluate whether all core banking operations work correctly. Verify that deposits and withdrawals properly update the account balance with validation checks (e.g., preventing negative balances, checking for valid input amounts). Check if balance inquiries accurately display current balances. Deduct 3 points for each core operation that's missing or dysfunctional, and 2 points for each operation with validation issues. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the receipt generation and printing functionality implemented?",
-      "description": "Check if the system properly formats transaction receipts with all required information (transaction type, amount, timestamp, remaining balance, transaction ID). Verify if there are options to print, email, or decline receipts. Assess whether the print formatting would work on actual receipt paper dimensions. Score 0 if receipts are missing, 5 if basic receipt information is available but lacks formatting or printing options, and 10 if comprehensive receipt functionality is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there proper transaction history and account management?",
-      "description": "Review whether the interface allows users to view transaction history with filtering options, manage account settings, change PIN/password, or configure preferences. Check if transactions are properly recorded with timestamps and unique identifiers. Deduct 3 points if transaction history is missing, 3 points if account management features are absent, and 2 points if history data is incomplete. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as incorrect PIN entries, insufficient funds, network failure, service timeouts, card reading errors, etc.) and provide friendly error prompts or recovery mechanisms. Check if the system has proper timeout functionality for security. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Biometric authentication options 2. Quick withdrawal presets 3. Dark mode/accessibility features 4. Interactive voice guidance 5. Currency conversion calculator). Add 2 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple ways to check balance) 2. Function modules unrelated to banking (e.g., games or entertainment features) 3. Fancy effects that affect performance or usability (e.g., excessive animations that slow down transactions). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating UI/business logic/data layers), input validation, security measures, and code organization. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if security best practices are not followed (e.g., storing sensitive data in localStorage). The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern ATM interface principles: 1) Clear visual hierarchy with important functions prominently displayed 2) Consistent and appropriately sized touch targets (at least 44×44px) 3) High contrast for readability in various lighting conditions 4) Clear typography with legible font sizes (at least 16px). Deduct 3 points for each usability issue, 5 points for poor contrast or readability problems, and 5 points for inconsistent layouts between screens. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and user-friendly?",
-      "description": "Judge whether the interface conforms to ATM usability standards: 1) Clear timeouts with warnings before session expiration 2) Logical flow between screens with proper back/cancel options 3) Loading indicators for processes that take time 4) Confirmation screens for critical actions like withdrawals. Deduct 5 points for missing timeout functionality, 3 points for lack of confirmation screens, and 5 points for confusing navigation or workflow. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "easy"
-}

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

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

package/library/management_systems-frontend_backend_platforms/backend-interface-tea-culture.json

@@ -1,68 +0,0 @@
-{
-  "index": 345,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate, professional responses. Be sure to provide executable code in your demonstrations. Create a simple backend interface based on tea culture.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the backend API architecture fully implemented?",
-      "description": "Review whether the code accurately implements a RESTful or GraphQL API structure with proper routing, controller logic, and HTTP method handling specific to tea culture domains. Score 0 if no API endpoints are implemented, 5 if basic CRUD operations are present but lack proper organization, and 10 if the architecture follows best practices with clear separation of concerns and tea-specific domain modeling.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the tea culture domain model properly designed?",
-      "description": "Evaluate if the data models properly represent tea culture concepts (tea types, origins, brewing methods, etc.) with appropriate relationships and attributes. Check for proper schema design with validation rules. Deduct 5 points if critical tea attributes are missing, 3 points if relationship modeling is flawed. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the database integration implemented correctly?",
-      "description": "Check whether the code includes database connection setup, proper ORM/query builder usage, and data persistence mechanisms. Assess if tea-related queries are optimized and if database transactions are used where appropriate. Deduct 5 points for hardcoded credentials, 3 points for missing indexing on frequently queried tea properties. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are API authentication and security measures implemented?",
-      "description": "Evaluate if the backend implements proper authentication/authorization mechanisms (JWT, OAuth, etc.), input validation, and protection against common vulnerabilities (SQL injection, XSS, etc.). Deduct 5 points if authentication is missing, 3 points if input sanitization is inadequate, and 5 points if no rate limiting is implemented. 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 invalid inputs, database connection failures, authentication errors, etc.) and provide appropriate error responses with status codes. Code with strong robustness should include try-catch blocks, input validation, and graceful error handling, 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. Tea recommendation algorithm 2. Brewing timer calculations based on tea type 3. Seasonal tea availability). 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 tea culture (e.g., general blog functionality) 3. Over-engineered components that add complexity without value. 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 controller/service/data access layers), test coverage, and deployment configurations. Deduct 5 points if global state is mismanaged; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no error logging mechanism. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Is the API documentation comprehensive and clear?",
-      "description": "Evaluate whether the API is well-documented using standards like OpenAPI/Swagger, with clear endpoint descriptions, request/response examples specific to tea culture domains. Deduct 3 points for missing parameter descriptions, 5 points for lack of response schemas, and 5 points for no usage examples. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the API performance optimized?",
-      "description": "Judge whether performance considerations are implemented: 1) Response caching for tea catalog data 2) Query optimization for tea searches 3) Pagination for large result sets. Deduct 5 points for missing caching strategy, 3 points for unoptimized database queries, and 5 points for returning excessive data in responses. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "hard"
-}

package/library/management_systems-frontend_backend_platforms/backend-transfer-record-processing-page.json

@@ -1,68 +0,0 @@
-{
-  "index": 1784,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to make the generated code executable for demonstration purposes. Help me create a backend processing page for a transfer record. The transfer is from Changsha Bank, account name \"Changsha Funding Service Center\", account number 6282*************** to China Agricultural Bank, recipient name \"Li Jianwei\", account number 6228***************, transfer amount 44,000 yuan, transfer time March 7, 2025, 15:30:01, arrival time 1-2 business days, with the note \"Student subsidy\".",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the transfer record display fully implemented?",
-      "description": "Review whether the code accurately displays all required transaction details (sender bank, sender name, sender account, recipient bank, recipient name, recipient account, amount, transfer time, expected arrival time, and note). Score 0 if critical information is missing, 5 if basic display is implemented but lacks formatting, and 10 if all details are properly formatted (e.g., currency formatted as '¥44,000.00', account numbers partially masked).",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the backend processing logic properly implemented?",
-      "description": "Check if the code includes proper backend processing logic for transfer records, including data validation, transaction record creation, and handling state transitions. Deduct 5 points if input validation is missing, 3 points if transaction state management is incomplete, and 2 points if logging mechanism is insufficient. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is there a proper receipt/confirmation generation feature?",
-      "description": "Evaluate whether the code implements functionality to generate a transfer receipt or confirmation that can be viewed, printed, or downloaded. Check for features like PDF generation, print-friendly formatting, or save-to-file options. Score 0 if completely missing, 5 if basic receipt is available but lacks formatting, and 10 if a professional receipt with all transaction details and bank identifiers is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is sensitive data properly handled and protected?",
-      "description": "Assess how the code handles sensitive financial information. Check for proper masking of account numbers (showing only last 4 digits), secure storage practices, and protection against data exposure. Deduct 5 points if account numbers are fully exposed, 3 points if masking is inconsistent, and 3 points if there's no distinction between public and sensitive data. 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 failed transfers, network errors, data inconsistencies) 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 transfer status tracking 2. Integration with popular messaging apps for notifications 3. QR code generation for the receipt). 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 validation logics for the same field) 2. Function modules unrelated to transfer records (e.g., a built-in calculator) 3. Fancy effects that affect performance (e.g., unnecessary animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating data/view/controller layers), unit test coverage, and error handling. 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 error handling is inadequate. 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 financial application design principles: 1) Clean, trust-inspiring color scheme (preferably using bank brand colors) 2) Proper layout spacing with clear visual hierarchy 3) Professional typography (readable font sizes, proper emphasis on important financial information). Deduct 3 points for each crowded visual element, 5 points for unprofessional color combinations, and 5 points for chaotic information architecture. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the user interactions are appropriate for a financial application: 1) Confirmation dialogs before critical actions 2) Clear loading states during processing 3) Success/failure notifications with appropriate next steps. Deduct 5 points for missing confirmation on important actions, 3 points for lack of loading indicators, and 5 points for unclear transaction outcome feedback. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "medium"
-}

package/library/management_systems-frontend_backend_platforms/base-station-maintenance-system-ui-with-navbar.json

@@ -1,68 +0,0 @@
-{
-  "index": 1054,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable for demonstration purposes. Create a front-end UI interface for a base station maintenance system, with a top navigation bar that includes base station information and alarm information.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the top navigation bar properly implemented?",
-      "description": "Check whether the navigation bar is properly positioned at the top of the page, with clearly visible menu items for base station information and alarm information. The bar should be responsive, maintain visibility during scrolling, and use appropriate contrast for readability. Deduct 3 points if the navigation is not fixed to the top, 5 points if menu items are not clearly visible, and 5 points if it's not responsive across different screen sizes. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the base station information section comprehensively implemented?",
-      "description": "Evaluate whether the code accurately implements the base station information display, including essential data fields (station ID, location, status, equipment list, maintenance history). Check for proper data formatting, sorting capabilities, and filtering options. Score 0 if the section is missing, 5 if only basic information is displayed without interaction features, and 10 if comprehensive information with advanced filtering/sorting is implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the alarm information system functional?",
-      "description": "Review if the alarm information section includes critical elements: alarm severity indicators (color-coding), timestamp display, alarm categorization, and acknowledgment mechanisms. Verify whether visual/audio indicators for critical alarms are implemented. Deduct 5 points if severity indicators are missing, 3 points if acknowledgment functionality is absent, and 3 points if there's no alarm history view. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there a dashboard or visualization component for monitoring?",
-      "description": "Check whether the interface includes data visualization components like status charts, alarm trend graphs, or geographic maps showing base station distribution. Evaluate if the visualizations are interactive and provide meaningful insights. Deduct 5 points if visualizations are static only, 5 points if key metrics are missing, and 3 points if legends/tooltips are not implemented. 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 data loading failures, empty states, 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. Real-time alert notifications 2. Dark/light theme toggle 3. Customizable dashboard layouts 4. Interactive equipment diagrams). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple ways to display the same information) 2. Function modules unrelated to base station maintenance (e.g., unrelated analytics) 3. Fancy effects that affect performance (e.g., excessive animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating UI components/data services/state management), component reusability, and build process optimization. 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 separation of concerns between UI and business logic. 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 for alarm states. Deduct 5 points for each operation without feedback, 3 points for laggy transitions between interface sections, and 5 points for hard-to-find critical alarm information. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "easy"
-}

package/library/management_systems-frontend_backend_platforms/basic-settings-page-shadcn-ui-nextjs.json

@@ -1,68 +0,0 @@
-{
-  "index": 1219,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and expert responses. Be sure to ensure that any code you generate is executable for demonstration. Create a basic settings page for me based on shadcn UI in Next.js.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the shadcn UI integration properly implemented?",
-      "description": "Verify that shadcn UI components are correctly imported and used according to the documentation. Check if the necessary installation steps (via CLI or manual setup) are completed. Score 0 if shadcn UI is not used, 5 if components are imported but with configuration errors, and 10 for proper implementation with correct theming configuration.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the settings page structure appropriate for Next.js architecture?",
-      "description": "Assess whether the code follows Next.js best practices: proper file structure (app/ or pages/ directory), correct usage of client/server components, and appropriate routing. Check if Server Components and Client Components are segregated correctly with 'use client' directives where needed. Deduct 5 points if the implementation doesn't follow Next.js 13+ conventions, and 3 points if metadata or layout files are missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Does the settings page include essential configuration sections?",
-      "description": "Evaluate if the settings page includes standard sections like Profile, Account, Appearance, Notifications, and Security. Each section should have appropriate form controls matching their purpose (e.g., toggles for notifications, color pickers for themes). Score 2 points for each well-implemented section, with a maximum of 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is form state management properly implemented?",
-      "description": "Check if the code uses appropriate form state management (React Hook Form, Formik, or native form controls) with proper validation. Verify that form submissions handle loading states and error handling. Score 0 if there's no form state management, 5 if basic implementation exists but lacks validation or error handling, and 10 if comprehensive implementation with validation, error states, and proper submission handling is present.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as form validation errors, network failures during submission, unexpected input values, 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. Live preview of settings changes 2. User preference persistence with localStorage/cookies 3. Keyboard shortcut navigation between settings sections). 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 controls (e.g., multiple theme switchers) 2. Function modules unrelated to settings (e.g., a built-in calculator) 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 settings functionality is interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating UI components/logic/state management), component reusability, and code organization. Deduct 5 points if global state is used inappropriately; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no separation of concerns. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Consistent use of shadcn UI's design language 2) Proper layout spacing and component hierarchy 3) Professional typographic system with appropriate heading sizes and readable body text. Deduct 3 points for each inconsistent UI element, 5 points for poorly structured navigation, 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) Immediate feedback on form interactions 2) Smooth transitions between settings sections 3) Clear visual indicators for active states. Deduct 5 points for each operation without feedback, 3 points for jarring transitions, and 5 points for confusing navigation mechanisms. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "easy"
-}