@getollie/cli 0.0.4 → 0.2.0

package/library/management_systems-frontend_backend_platforms/tencent-cloud-operations-management-mini-program.json

@@ -1,68 +0,0 @@
-{
-  "index": 751,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate, professional responses. Be sure to ensure that the generated code is executable for demonstration. How to use Tencent Cloud components to develop a technical operations management application/WeChat mini program that includes: 1. Daily inspections: inspection personnel upload inspection images, fill in inspection notes, and submit to reviewers for approval; 2. Operations support: operations staff report daily maintenance activities and submit to reviewers for approval; 3. Report queries: reviewers can check inspection and operations situations, including frequency and content.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the daily inspection module fully implemented?",
-      "description": "Evaluate whether the code accurately implements the daily inspection workflow, including image upload, note entry, and approval mechanisms using Tencent Cloud components. Check if the code implements TCB (Tencent CloudBase) for data storage, image compression and storage in COS (Cloud Object Storage), and secure user authentication. Score 0 if the core functionality is missing, 5 if basic functionality is implemented but lacking cloud integration, and 10 if fully implemented with proper Tencent Cloud services.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the operations support module correctly implemented?",
-      "description": "Review the implementation of the operations support system, including daily maintenance activity reporting and the approval workflow. Verify that it uses Tencent Cloud Serverless functions for backend logic and proper database schema design for maintenance records. The implementation should include status tracking and notifications. Deduct 5 points if the approval workflow is incomplete, 3 points if notification mechanisms are missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the report query system properly designed?",
-      "description": "Assess whether the reporting system enables reviewers to effectively query and analyze both inspection and operations data. Check if it implements Tencent Cloud's data visualization components, supports filtering by date ranges, personnel, and status. Verify if it includes statistical analysis functions and exportable reports. Deduct 5 points if filtering capabilities are limited, 3 points if visualization is inadequate, and 5 points if export functionality is missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the WeChat Mini Program integration properly implemented?",
-      "description": "Evaluate the WeChat Mini Program implementation, focusing on integration with Tencent Cloud services and WeChat's native capabilities. Check for proper use of WeChat login, cloud functions connection, offline data caching, and push notification integration. The code should follow WeChat Mini Program development best practices. Deduct 5 points for improper authentication flow, 3 points for missing offline capabilities, and 5 points for security vulnerabilities in cloud API calls. 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 interruption, image upload failures, form validation 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. AI-powered image analysis for inspection verification 2. Automated report generation with insights 3. Location-based task assignment). 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 approval workflows coexisting) 2. Function modules unrelated to operations management (e.g., a built-in game feature) 3. Fancy effects that affect performance (e.g., unnecessary animations on critical paths). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating business logic/view/network 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/test-case-management-platform.json

@@ -1,68 +0,0 @@
-{
-  "index": 313,
-  "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. Build a modern test case management platform with these core functions: user system, case management system, and case statistics system. Implement features for adding, modifying, and importing test cases via Excel. Execute test cases and generate execution statistics. Frontend tech stack: Vue.js + Bootstrap, etc. Backend tech stack: Django + Django REST framework, etc. Database: SQLite3, etc. Based on these requirements, what questions and suggestions do you have?",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the test case management system architecture properly implemented?",
-      "description": "Review whether the code implements a clear separation of concerns with proper frontend-backend architecture. The frontend should use Vue.js component structure with proper state management, and the backend should follow Django's MVT pattern with REST API endpoints. Score 0 if the architecture is missing or fundamentally flawed, 5 if basic structure exists with some issues, and 10 if the architecture is comprehensive with proper separation of concerns.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the user system fully functional?",
-      "description": "Evaluate the implementation of user registration, authentication, authorization, and role management. Check for JWT/session-based authentication, role-based access control, proper password hashing, and account management features. Deduct 3 points if password security is inadequate, 3 points if role-based permissions are missing, and 4 points if authentication tokens aren't properly managed. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the case management system comprehensive?",
-      "description": "Assess the implementation of CRUD operations for test cases, including proper data models with relationships, validation logic, and versioning. Check for features like test case categorization, search/filtering, and bulk operations. Deduct 3 points if the data model lacks necessary fields, 3 points if validation is inadequate, and 4 points if searching/filtering capabilities are missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are the Excel import/export features properly implemented?",
-      "description": "Review the implementation of Excel import/export functionality for test cases. Check for proper file format validation, template handling, error reporting during import, and data integrity checks. Evaluate the UX flow for imports/exports. Deduct 3 points for missing validation, 3 points for inadequate error handling, 2 points for poor UX, and 2 points for missing template functionality. 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, network issues, database failures, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should include proper exception handling, input validation, and defensive programming. Give 10 points for comprehensive error handling, 5 points for average robustness, and 0 points if exceptions aren't 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. Real-time collaboration on test cases 2. Test case dependency visualization 3. Automated test execution scheduling 4. AI-assisted test case generation). 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 export data) 2. Function modules unrelated to test case management (e.g., a built-in chat system) 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 business logic/view/API layers), unit test coverage, and build process automation. Examine frontend component reusability and backend API documentation. Deduct 3 points if global state management is poorly implemented; deduct 3 points if the code duplication rate is too high (over 30%); deduct 2 points if the build process is not automated; deduct 2 points if API documentation is missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the UI follows modern design principles: 1) Harmonious color matching with Bootstrap theme customization 2) Proper layout spacing and responsive design 3) Professional typography and consistent design language. Deduct 3 points for inconsistent design elements, 3 points for non-responsive layouts, and 4 points for poor information hierarchy and navigation structure. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the statistical dashboard comprehensive and insightful?",
-      "description": "Judge the quality of the statistical system implementation: 1) Variety of metrics and KPIs (test coverage, pass/fail rates, execution times) 2) Visual data representations (charts, graphs) 3) Filtering and time-range selection 4) Export capabilities. Deduct 3 points for missing key metrics, 3 points for poor visualization choices, 2 points for limited filtering options, and 2 points for missing export functionality. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "medium"
-}

package/library/management_systems-frontend_backend_platforms/test-execution-dynamic-forms-homepage-module-ttf-icons.json

@@ -1,68 +0,0 @@
-{
-  "index": 1260,
-  "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 display. Tasks completed:\n1. Test execution - added multiple query options to the operating condition execution interface;\n2. Added dynamic form controls;\n3. Test records - added multiple query options to the operating condition execution interface;\n4. Added homepage module;\n5. Improved the TTF icon library",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Are the multiple query options for operating condition execution interface fully implemented?",
-      "description": "Review whether the code accurately implements the query form with proper validation, filtering logic, and state management. Check if the advanced filtering options allow for complex combinations and flexible parameter adjustments. Score 0 if query functionality is missing, 5 if only basic filtering is implemented, and 10 if it includes advanced features like fuzzy search, range filters, and parameter persistence.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the dynamic form control system properly implemented?",
-      "description": "Evaluate the implementation of dynamic form controls including validation logic, error handling, and state management. Check if the controls support conditional visibility, dependent validation, and value interpolation. Deduct 3 points if controls lack accessibility features, 3 points if validation logic is inconsistent, and 4 points if state management causes memory leaks. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are the test records query options correctly integrated with the execution interface?",
-      "description": "Examine whether the test records query interface is properly connected to the execution system, with appropriate data flow between components. Verify that search results update reactively and maintain consistency with filter states. Deduct 5 points if the query results don't synchronize correctly with execution context, and 3 points if pagination or sorting logic has edge cases. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the homepage module comprehensive and well-integrated?",
-      "description": "Assess the homepage module for completeness, featuring dashboard elements, navigation system, and proper integration with other system modules. Check for responsive design implementation and information architecture. Deduct 5 points if key metrics are missing, 3 points for poor navigation design, and 2 points for inadequate responsive behavior. 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 interruption, empty states, concurrent operations, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Smart query suggestions based on usage patterns 2. Visualization of test result trends 3. Keyboard shortcut system for power users). 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 filtering mechanisms coexisting) 2. Function modules unrelated to the test system (e.g., unnecessary 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 logic/view/data 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). Examine the TTF icon library implementation for consistency, proper sizing and alignment. 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/ticket-management-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 1375,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Try to ensure the generated code is executable. Below are SQL scripts generated based on the entity classes you provided. These scripts will create corresponding database tables, and define field types, primary keys, comments, and other information.\n\n### 1. `chat_record` table\n```sql\nCREATE TABLE `chat_record` (\n  `id` INT(11) NOT NULL AUTO_INCREMENT COMMENT 'Primary Key ID',\n  `from_user_id` INT(11) NOT NULL COMMENT 'Sender',\n  `to_user_id` INT(11) NOT NULL COMMENT 'Recipient',\n  `status` INT(11) NOT NULL COMMENT '0 Unread 1 Read',\n  `content` VARCHAR(255) NOT NULL COMMENT 'Message content',\n  `create_time` DATETIME NOT NULL COMMENT 'Creation time',\n  PRIMARY KEY (`id`)\n) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='Chat records table';\n```\n\n### 2. `sys_notice` table\n```sql\nCREATE TABLE `sys_notice` (\n  `id` INT(11) NOT NULL AUTO_INCREMENT COMMENT 'Notice ID',\n  `notice_title` VARCHAR(255) NOT NULL COMMENT 'Notice title',\n  `notice_type` INT(11) NOT NULL COMMENT 'Notice type (1 notification 2 announcement)',\n  `notice_content` TEXT NOT NULL COMMENT 'Notice content',\n  `status` INT(11) NOT NULL COMMENT 'Notice status (0 active 1 closed)',\n  `create_time` DATETIME NOT NULL COMMENT 'Creation time',\n  `update_time` DATETIME NOT NULL COMMENT 'Update time',\n  PRIMARY KEY (`id`)\n) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='Notifications and announcements table';\n```\n\n### 3. `sys_user` table\n```sql\nCREATE TABLE `sys_user` (\n  `id` INT(11) NOT NULL AUTO_INCREMENT COMMENT 'Primary Key ID',\n  `nickname` VARCHAR(255) NOT NULL COMMENT 'Nickname',\n  `avatar` VARCHAR(255) NOT NULL COMMENT 'Avatar',\n  `password` VARCHAR(255) NOT NULL COMMENT 'Password',\n  `mobile` VARCHAR(20) NOT NULL COMMENT 'Phone number',\n  `email` VARCHAR(255) NOT NULL COMMENT 'Email',\n  `role_id` INT(11) NOT NULL COMMENT 'Role',\n  `dept_id` INT(11) NOT NULL COMMENT 'Department ID',\n  `update_time` DATETIME NOT NULL COMMENT 'Modification time',\n  `create_time` DATETIME NOT NULL COMMENT 'Creation time',\n  `locked` INT(11) NOT NULL COMMENT '1 valid 2 invalid',\n  `deleted` INT(11) NOT NULL COMMENT 'Logical deletion 0 normal 1 deleted',\n  `confirm_password` VARCHAR(255) NOT NULL COMMENT 'Confirm password',\n  PRIMARY KEY (`id`)\n) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='Backend admin user table';\n```\n\n### 4. `ticket` table\n```sql\nCREATE TABLE `ticket` (\n  `id` INT(11) NOT NULL AUTO_INCREMENT COMMENT 'Primary Key ID',\n  `train_number` INT(11) NOT NULL COMMENT 'Train number',\n  `pass_station` VARCHAR(255) NOT NULL COMMENT 'Via stations',\n  `train_number_type` INT(11) NOT NULL COMMENT 'Train type 1 High-speed 2 EMU 3 Direct 4 Express 5 Other',\n  `ticket_number` INT(11) NOT NULL COMMENT 'Number of tickets',\n  `seat_type` INT(11) NOT NULL COMMENT 'Seat type 1 Soft seat 2 Hard seat 3 Sleeper',\n  `status` INT(11) NOT NULL COMMENT '1 Online 2 Offline',\n  `starting_point` VARCHAR(255) NOT NULL COMMENT 'Departure point',\n  `ending_point` VARCHAR(255) NOT NULL COMMENT 'Destination',\n  `price` INT(11) NOT NULL COMMENT 'Price',\n  `starting_time` DATETIME NOT NULL COMMENT 'Departure time',\n  `arriving_time` DATETIME NOT NULL COMMENT 'Arrival time',\n  `create_time` DATETIME NOT NULL COMMENT 'Creation time',\n  `update_time` DATETIME NOT NULL COMMENT 'Update time',\n  PRIMARY KEY (`id`)\n) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='Ticket table';\n```\n\n### 5. `ticket_order` table\n```sql\nCREATE TABLE `ticket_order` (\n  `id` INT(11) NOT NULL AUTO_INCREMENT COMMENT 'Primary Key ID',\n  `order_id` VARCHAR(255) NOT NULL COMMENT 'Order ID',\n  `user_id` INT(11) NOT NULL COMMENT 'User ID',\n  `ticket_id` INT(11) NOT NULL COMMENT 'Ticket ID',\n  `username` VARCHAR(255) NOT NULL COMMENT 'Username',\n  `id_card` VARCHAR(255) NOT NULL COMMENT 'ID card number',\n  `create_time` DATETIME NOT NULL COMMENT 'Creation time',\n  `update_time` DATETIME NOT NULL COMMENT 'Update time',\n  PRIMARY KEY (`id`)\n) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='Ticket order table';\n```\n\n### 6. `user` table\n```sql\nCREATE TABLE `user` (\n  `id` INT(11) NOT NULL AUTO_INCREMENT COMMENT 'Primary Key ID',\n  `nickname` VARCHAR(255) NOT NULL COMMENT 'Nickname',\n  `password` VARCHAR(255) NOT NULL COMMENT 'Password',\n  `avatar` VARCHAR(255) NOT NULL COMMENT 'Avatar',\n  `gender` INT(11) NOT NULL COMMENT 'Gender',\n  `mobile` VARCHAR(20) NOT NULL COMMENT 'Phone number',\n  `status` INT(11) NOT NULL COMMENT 'Status 1 Normal 2 Banned',\n  `create_time` DATETIME NOT NULL COMMENT 'Creation time',\n  `update_time` DATETIME NOT NULL COMMENT 'Update time',\n  PRIMARY KEY (`id`)\n) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='User table';\n```\n\n### Notes:\n1. **Field types**: Adjust field types according to actual needs, such as the length of `VARCHAR` or the range of `INT`.\n2. **Character set**: Default to `utf8mb4` to support more characters (such as emoji).\n3. **Engine**: Default to `InnoDB` engine, supporting transactions and foreign keys.\n4. **Comments**: Table name and field comments can be adjusted according to actual requirements.\n\nPlease help me generate a ticket management system based on the above table information, using Spring Boot, MyBatis, and templates for the frontend pages.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the database schema design logically sound?",
-      "description": "Review whether the database tables follow normalization principles, have appropriate data types, constraints, and relationships. Check for primary/foreign key definitions, indexes for performance optimization, and proper cascading rules for referential integrity.Deduct 5 points for each missing index on frequently queried fields; 10 points if foreign key constraints are not implemented correctly between related tables (e.g., ticket_order.ticket_id → ticket.id); 5 points for inappropriate data types (e.g., using VARCHAR for numeric values); 3 points for each missing constraint that could lead to data integrity issues. The full score is 15 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the Spring Boot project structure properly organized?",
-      "description": "Evaluate if the code follows the standard Spring Boot project structure with clear separation of concerns (Controller, Service, Repository layers). Check for proper package organization, configuration management, and dependency injection patterns.Give full 10 points if the project follows strict layered architecture patterns with proper separation of concerns. Deduct 3 points if controllers contain business logic; 3 points if service layer is bypassed; 2 points if repositories are accessed directly from controllers; 5 points if dependency injection is not used appropriately. Score 0 if the basic MVC pattern is not followed.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the MyBatis integration complete and efficient?",
-      "description": "Check if MyBatis mappers, XML files, and annotations are correctly implemented. Assess if complex queries use efficient SQL, pagination is implemented, and if proper result mapping is configured.Award 10 points for a complete implementation with XML mappers or annotations, properly configured datasource, and transaction management. Deduct 3 points for missing pagination; 3 points for N+1 query issues; 2 points for inefficient SQL queries; 5 points if dynamic SQL is not used where appropriate. Score 0 if basic CRUD operations are not functional.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the ticket management system's core functionality implemented?",
-      "description": "Review if the system includes essential features: ticket creation/modification, searching/filtering, booking process, order management, and user authentication. Check if business rules like seat availability validation and booking constraints are implemented.Full 15 points for implementing all core ticket management features including search, booking, payment workflow, and order management. Deduct 3 points for each missing major feature; 5 points if ticket availability checking is not implemented; 5 points if the booking process is incomplete; 2 points for each business rule violation. Score 0 if the basic ticket CRUD operations are not functional.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code handles exceptions properly, includes input validation, implements transaction management correctly, and provides appropriate error handling and logging.Evaluate whether the code can handle common abnormal situations (such as invalid inputs, duplicate bookings, concurrent modifications) 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 seat availability visualization 2. Smart recommendation system 3. Automated notification system for ticket status changes 4. Trip planning assistant).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 booking methods coexisting) 2. Function modules unrelated to ticket management (e.g., a built-in game) 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, code reuse patterns, exception handling strategy, unit test coverage, and build process automation. Check for code comments and documentation.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; deduct 3 points if documentation is insufficient. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the ticket management UI follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing 3) Professional font system (body font size ≥ 14px, line height over 1.5 times) 4) Clear information hierarchy for ticket listings and details.Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. Deduct 3 points if ticket information is not clearly presented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the ticket booking flow and management operations conform to user expectations: 1) Responsive feedback for ticket search/booking operations 2) Clear visual indicators for seat availability 3) Intuitive navigation between ticket search, booking, and order management.Deduct 5 points for each operation without feedback, 3 points for slow response times during ticket searches, and 5 points for hard-to-find key booking functions. Deduct 3 points if the booking process requires unnecessary steps. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "medium"
-}

package/library/management_systems-frontend_backend_platforms/trading-system-component-framework.json

@@ -1,68 +0,0 @@
-{
-  "index": 1160,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the generated code is executable for demonstration whenever possible. Provide a complete trading system component framework.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core trading functionality fully implemented?",
-      "description": "Review whether the code accurately implements essential trading operations (buy/sell orders, order types, order book management). Check if trade matching logic, price determination, and execution flow are correctly implemented. Score 0 if core trading logic is missing, 5 if basic order placement exists but lacks matching engine, and 10 if the system includes comprehensive order management with various order types (market, limit, stop, etc.).",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the trading system architecture properly designed?",
-      "description": "Evaluate the overall system architecture, including separation of concerns, component interactions, and scalability considerations. Check if the design follows recognized patterns like event-driven architecture or microservices. Deduct 5 points if components are tightly coupled, 3 points if there's no clear separation between core trading logic and presentation layer, and 3 points if the design doesn't account for high throughput scenarios. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the risk management system implemented?",
-      "description": "Check for implementation of essential risk controls including position limits, exposure calculations, margin requirements, and circuit breakers. Deduct 3 points if there's no pre-trade risk validation, 3 points if margin calculation is missing, and 5 points if there are no circuit breakers or timeout mechanisms for extreme market conditions. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are market data handling and order book visualization properly implemented?",
-      "description": "Assess the market data processing pipeline and order book visualization components. Check if the system can efficiently process market data updates, maintain an accurate order book, and present it visually. Deduct 5 points if real-time updates aren't supported, 3 points if depth visualization is missing or poorly implemented, and 3 points if there's no historical data view. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as network errors, invalid orders, market data interruptions, etc.) and provide friendly error handling or recovery mechanisms. Check if edge cases like partial fills, order cancellations during matching, and race conditions are properly handled. Give 10 points for comprehensive error handling, 5 points for average robustness, and 0 points if exceptions are unhandled.",
-      "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 trading experience (e.g., 1. Real-time portfolio performance analytics 2. Market sentiment indicators integration 3. Automated trading strategy builder with backtesting). 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 order validation mechanisms) 2. Function modules unrelated to trading (e.g., built-in social media features) 3. Fancy visualizations that affect performance (e.g., unnecessary 3D charts). 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 trading logic/market data/UI layers), test coverage for critical components, 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 trading platform standards?",
-      "description": "Evaluate whether the design follows modern trading platform principles: 1) Professional color scheme (dark mode with accent colors) 2) Clean, information-dense layout with proper spacing 3) Clear visual hierarchy for important trading data. Deduct 3 points for cluttered trading screens, 5 points for poor data visualization choices, and 5 points for non-responsive layouts that waste screen space. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the trading interaction experience optimized?",
-      "description": "Judge whether the trading interactions conform to user expectations: 1) Order entry speed ≤ 100ms 2) Real-time updates without user-initiated refreshes 3) Clear confirmations for critical actions. Deduct 5 points for slow order entry, 3 points for laggy market data updates, and 5 points for confusing trade confirmation workflows. Check if keyboard shortcuts for power users are implemented. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "hard"
-}

package/library/management_systems-frontend_backend_platforms/tutoring-center-management-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 832,
-  "question": "You are a coding expert. Please use your professional knowledge to generate accurate and professional responses. Make sure that the code you generate is executable for demonstration purposes. Help me write a system code for a tutoring center that includes an attendance system, a work progress tracking system, a system for organizing incorrect answers and notes, and a section for teacher comments and specialized feedback.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the attendance system fully implemented?",
-      "description": "Review whether the code implements a comprehensive attendance tracking system including check-in/check-out functionality, absence tracking, tardiness recording, and attendance reporting. Check if it has user authentication to prevent fraudulent check-ins. Score 0 if attendance tracking is missing, 5 if basic attendance is implemented without validation, and 10 if it includes all features with proper authentication and reporting capabilities.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the work progress tracking system properly designed?",
-      "description": "Evaluate whether the system tracks student progress effectively with features like milestone tracking, assignment completion status, time spent on tasks, and progress visualization. Check if it includes progress metrics and comparison against goals. Deduct 3 points if it lacks visual progress indicators, 4 points if historical data tracking is missing, and 5 points if it doesn't support custom progress goals. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the incorrect answers and notes organization system comprehensive?",
-      "description": "Check if the system properly categorizes and stores incorrect answers with associated notes, includes tagging or classification by topic/difficulty, and provides effective search/retrieval mechanisms. Verify if it supports various media types for explanations (text, images, audio). Deduct 5 points if categorization is missing, 3 points if search functionality is inadequate, and 5 points if it doesn't connect errors to learning resources. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the teacher feedback and comments system sufficiently detailed?",
-      "description": "Assess whether the system allows teachers to provide structured feedback, includes templated and customized comment options, supports attachment of resources, and offers a mechanism for tracking feedback implementation. Check if students can respond to feedback creating a dialogue. Deduct 3 points if feedback templates are missing, 4 points if there's no way to track if students reviewed feedback, and 4 points if the system doesn't support multimedia feedback. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code handles common edge cases (invalid inputs, duplicate entries, concurrent access, etc.) and provides appropriate error handling with user-friendly messages. Check for data validation, transaction handling for database operations, and defense against common security vulnerabilities. Deduct 3 points for each unhandled critical error scenario, 5 points if input validation is inconsistent or weak, and 5 points if there's no graceful error recovery. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes unexpected valuable features such as: 1) AI-powered personalized learning path suggestions based on error patterns, 2) Gamification elements to improve student engagement, 3) Automated progress insights and recommendation engine, 4) Integration with external learning resources, 5) Mobile-friendly interfaces with notifications. Add 2 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1) Multiple implementations of similar functionality (e.g., different attendance tracking methods that serve the same purpose), 2) Features unrelated to tutoring center management (e.g., complex social networking capabilities), 3) Overengineered components that add complexity without proportional value. Deduct 3 points for each redundancy found, and directly deduct 10 points if redundant code interferes with core functionality.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review the architecture (MVC/MVVM patterns), code organization, naming conventions, and test coverage. Check for proper separation of concerns, dependency injection, and database abstraction. Evaluate documentation quality and maintainability. Deduct 3 points for poor naming conventions, 3 points for excessive coupling between components, 3 points for inadequate documentation, and 4 points if testing is absent. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the UI follows modern design principles: 1) Consistent color scheme with appropriate contrast ratios, 2) Intuitive navigation and information hierarchy, 3) Responsive design that works across devices, 4) Accessibility compliance. Deduct 3 points for inconsistent styling, 3 points for poor information architecture, 2 points for non-responsive elements, and 3 points for accessibility failures. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the system provides appropriate feedback for user actions, maintains state consistency during operations, and offers intuitive workflows. Check if form submissions show loading states, operations have confirmation dialogs when appropriate, and users receive clear notifications about system status changes. Deduct 3 points for delayed feedback (>300ms), 3 points for confusing navigation flows, 2 points for missing confirmation on critical actions, and 3 points for inadequate error state handling. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "hard"
-}

package/library/management_systems-frontend_backend_platforms/ui-interface-design-code-generation.json

@@ -1,68 +0,0 @@
-{
-  "index": 1185,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure that the code you generate is executable whenever possible. I'll show you a UI interface design, and could you write the corresponding code for it?",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the UI implementation faithful to the design specification?",
-      "description": "Evaluate whether the implementation matches the provided design with pixel-perfect accuracy. Check for proper colors, spacing, fonts, and overall visual fidelity. Score 0 if the implementation looks completely different from the design, 5 if there are several noticeable inconsistencies, and 10 if it's nearly identical to the design specification.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the HTML structure semantic and accessible?",
-      "description": "Examine the HTML structure for proper semantics (using appropriate tags like nav, header, section, etc.), ARIA attributes where necessary, and keyboard navigability. Check for proper heading hierarchy, alt text for images, and form label associations. Deduct 3 points for each major accessibility issue found (missing alt text, non-semantic divs for clickable elements, etc.). The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the CSS implementation clean, maintainable and responsive?",
-      "description": "Check if the CSS uses a methodology (BEM, SMACSS, etc.), avoids !important, implements responsive breakpoints properly, and uses relative units where appropriate. Check for browser compatibility and if media queries are used effectively. Deduct 3 points for excessive CSS duplication, 3 points for non-responsive implementation, and 4 points for browser incompatibility issues. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the interactive functionality fully implemented?",
-      "description": "Verify that all interactive elements work as expected: buttons trigger appropriate actions, forms validate input, dropdown menus open/close, modal dialogs function correctly, etc. Check for proper event handling and state management. Score 0 if interactive elements are purely decorative, 5 if basic functionality works but with issues, 10 if all interactions are fully functional.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as empty states, error handling, input validation, edge cases) 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. Subtle micro-interactions 2. Performance optimizations like lazy loading 3. Additional visual feedback for user actions). 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 2. Function modules unrelated to the UI design 3. Fancy effects that affect performance (e.g., unnecessary animations or transitions). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as component-based structure), code organization, variable/function naming, and code reusability. Deduct 5 points if global CSS/JS pollutes namespace, deduct 5 points if the code duplication rate is too high (over 30%), deduct 5 points if code is not properly organized into files/folders. 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/urban-homestay-brand-management.json

@@ -1,68 +0,0 @@
-{
-  "index": 1786,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Try to ensure that the generated code is executable for display. I am now starting a business to create an urban homestay brand, with properties distributed across different neighborhoods, each with a different style. The investment amount is 300,000, with 3 staff members responsible for platform OTA operations, housekeeper customer service, and soft furnishing design, etc. Based on the above ideas and content, please help me generate a piece of HTML code. I don't understand how to write code, but need management that meets smart and intelligent urban homestay management!",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the urban homestay management system's core functionality implemented?",
-      "description": "Review whether the HTML code implements essential management features including property listing management, reservation tracking, occupancy calendar, and financial reporting. Score 0 if none of the core functions are implemented, 5 if only basic listing display is present, and 10 if a complete management dashboard with all key metrics is included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the OTA (Online Travel Agency) integration functionality implemented?",
-      "description": "Check whether the code includes integration with OTA platforms (like Airbnb, Booking.com, etc.) through API connectors or embedded widgets. Verify if it allows synchronized calendar management across platforms and centralized booking management. Deduct 5 points if there's no real-time synchronization mechanism, and 3 points if listing information can't be updated across multiple platforms simultaneously. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the customer service and housekeeping management system implemented?",
-      "description": "Evaluate whether the code includes features for managing housekeeping schedules, cleaning status tracking, maintenance requests, and guest communication tools. Check if the system allows for task assignment to the 3 staff members mentioned. Deduct 5 points if there's no notification system for urgent issues, and 3 points if cleaning verification protocols are missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the property style management and visualization implemented?",
-      "description": "Assess whether the code includes functionality to showcase different property styles across neighborhoods, including visual representation through image galleries, style categorization, and furnishing inventory management. Check if the system supports the soft furnishing design staff member's work with design templates or mockup tools. Deduct 5 points if there's no visual representation of properties, and 3 points if style categories can't be filtered or searched. 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 incomplete form submissions, network interruptions, data validation 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. AI-powered pricing optimization 2. Smart home integration for remote property management 3. Guest experience personalization tools). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple calendar views showing the same data) 2. Function modules unrelated to homestay management (e.g., a built-in game for guests) 3. Fancy effects that affect performance (e.g., unnecessary animations on critical management pages). 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), component reusability, and responsive design implementation. Deduct 5 points if global variable pollution is found; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the interface doesn't adapt to different screen sizes. 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 that reflects the homestay brand identity 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 dashboard layouts. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance for critical management tasks. Deduct 5 points for each operation without feedback, 3 points for laggy dashboard refreshes, 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"
-}