@getollie/cli 0.0.5 → 0.2.0

package/library/management_systems-frontend_backend_platforms/cloud-hospital-system-design.json

@@ -1,68 +0,0 @@
-{
-  "index": 1557,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable for demonstration purposes. Create a cloud hospital system design with functionality, and generate the related code using HTML, CSS, and JavaScript.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core hospital management system functionality implemented?",
-      "description": "Review whether the code accurately implements essential hospital system features such as patient registration, appointment scheduling, doctor availability, medical records management, and billing. Score 0 if core functionality is missing, 5 if only basic features are implemented, and 10 if a comprehensive system with role-based access control (patient, doctor, admin) is included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the cloud-based architecture properly designed?",
-      "description": "Evaluate whether the implementation includes proper cloud design patterns such as data synchronization, offline functionality, real-time updates, and secure data storage. Check for REST API integration points or mock services for backend communication. Deduct 5 points if there's no clear separation between frontend and backend concerns, and 3 points if data persistence strategy is missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the patient-doctor interaction workflow fully implemented?",
-      "description": "Assess whether the system properly handles the complete patient journey from registration to consultation to follow-up. Check for implementation of appointment scheduling, virtual consultation interfaces, prescription management, and medical history access. Deduct 5 points for missing key workflow elements, 3 points for illogical user flows. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the healthcare data visualization and reporting implemented?",
-      "description": "Review if the system includes visualizations for medical data (charts for patient vitals, health trends), administrative dashboards, and reporting capabilities. Score 0 if visualization is missing, 5 if basic charts are present, and 10 if comprehensive, interactive dashboards with filtering and export functionality are implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (invalid form submissions, network errors, authentication failures, etc.) and provide friendly error messages or recovery mechanisms. Code with strong robustness should be able to effectively handle edge cases and prevent data corruption, 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 symptom checker 2. Real-time translation for international patients 3. Integrated telehealth video system 4. Smart health reminders). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple user registration flows) 2. Function modules unrelated to healthcare (e.g., a built-in game for waiting room) 3. Fancy effects that affect performance (e.g., unnecessary animations on critical healthcare information). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (separation of concerns between patient, doctor, and admin modules), code organization, reusable components, and proper event handling. Deduct 5 points if global state management is chaotic or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if form validation and security practices are poor. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional healthcare design standards?",
-      "description": "Evaluate whether the design follows healthcare UI/UX principles: 1) Accessible color scheme with sufficient contrast ratios 2) Clean, organized layout with clear information hierarchy 3) Properly sized typography for medical information (body font size ≥ 14px, critical information ≥ 16px). Deduct 3 points for cluttered interfaces, 5 points for poor information prioritization, and 5 points for accessibility issues. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and appropriate for a healthcare context?",
-      "description": "Judge whether the interactions consider healthcare user needs: 1) Critical alerts with appropriate urgency 2) Simple navigation for elderly or impaired users 3) Clear confirmation for important actions like appointment booking or medication requests. Deduct 5 points for confusing navigation, 3 points for distracting animations during critical tasks, and 5 points for requiring excessive clicks for common healthcare tasks. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "medium"
-}

package/library/management_systems-frontend_backend_platforms/coal-company-erp-system-html.json

@@ -1,68 +0,0 @@
-{
-  "index": 1350,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable for demonstration. Create HTML code for a coal company's ERP system with an elegant interface, complete components, visualization elements, and comprehensive professional functionalities.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the ERP system architecture properly structured?",
-      "description": "Examine whether the HTML code implements a proper SPA (Single Page Application) architecture with clear module separation (HR, Finance, Inventory, Production, etc.) and navigation framework. Check for clean component hierarchy with parent-child relationships. Score 0 if there's no clear architecture, 5 if basic module separation exists but lacks proper navigation, and 10 if the architecture follows industry standards with proper routing and state management.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Does the interface include essential coal industry ERP components?",
-      "description": "Verify that the HTML includes coal-specific components: resource tracking dashboards, mine production monitoring, coal quality analysis charts, equipment maintenance schedules, and regulatory compliance tools. Each missing critical component costs 2 points. Deduct 5 points if key visualizations (production trend graphs, equipment utilization charts) are absent. Award full 10 points only if all core coal industry modules are present and functionally connected.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are data visualization elements implemented effectively?",
-      "description": "Evaluate the quality of data visualization elements: coal production graphs, inventory level charts, financial dashboards, and operational KPIs. Check whether the visualizations use appropriate chart types for different data categories (bar charts for production comparison, line charts for trends, heat maps for resource allocation). Deduct 3 points if visualizations aren't interactive, 2 points if they use inappropriate chart types, and 2 points if they lack legends or tooltips. Full score requires responsive visualizations with proper data encoding.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there an integrated dashboard for operational oversight?",
-      "description": "Assess whether the ERP system includes a comprehensive dashboard that aggregates critical metrics (coal extraction rates, equipment downtime, inventory levels, workforce allocation, safety incidents) for executive decision-making. The dashboard should include real-time alerts, filterable data views, and customizable displays. Deduct 5 points if the dashboard lacks data integration across departments, 3 points if it doesn't support filtering/customization, and 2 points if it lacks export functionality. Full score requires a complete executive dashboard with drill-down capabilities.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as data loading failures, form validation errors, offline operation, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should implement form validation, data sanitization, graceful error handling, and fallback UI states. Award 10 points for comprehensive error handling, 5 points for basic validation only, and 0 points if exceptions aren't managed at all.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. AI-powered coal demand prediction 2. Real-time equipment maintenance alerts with augmented reality integration 3. Environmental impact visualization dashboard 4. Interactive mine mapping). 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 dashboard widgets showing the same data) 2. Function modules unrelated to coal industry ERP (e.g., built-in games or entertainment features) 3. Fancy effects that affect performance (e.g., unnecessary 3D animations or auto-playing videos). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating data models/views/controllers), component reusability, code maintainability, and accessibility standards. Check for semantic HTML usage, ARIA attributes for accessibility, proper CSS organization (preferably using CSS modules or a framework), and clean JavaScript with minimal global variables. Deduct 5 points for accessibility failures, 3 points for non-semantic markup, and 2 points for poor code organization. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern enterprise UI principles: 1) Consistent color scheme appropriate for industrial applications (primarily neutral colors with strategic accent colors) 2) Clear visual hierarchy with proper whitespace utilization 3) Professional typography system (readable fonts at appropriate sizes) 4) Uniform UI components following a design system. Deduct 3 points for inconsistent styling, 5 points for poor information hierarchy, and 2 points for cluttered layouts. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the interactive elements provide appropriate feedback: 1) Loading states for async operations 2) Clear button states (hover, active, disabled) 3) Smooth transitions between views 4) Appropriate form validation feedback 5) Responsive design for different screen sizes. Deduct 3 points for missing loading indicators, 2 points for abrupt transitions, 3 points for poor mobile adaptation, and 2 points for inadequate interactive feedback. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "medium"
-}

package/library/management_systems-frontend_backend_platforms/commercial-property-rental-management-system-contract.json

@@ -1,68 +0,0 @@
-{
-  "index": 298,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the code you generate is executable for demonstration. Create a commercial property rental management system, including contract functionality, with each menu item represented as a separate webpage that links together.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core property management functionality fully implemented?",
-      "description": "Review whether the code accurately implements CRUD operations for properties, tenants, and landlords. Check if property listing details include essential information (location, size, price, availability). Score 0 if the core property management is not implemented, 5 if only basic listing is available, and 10 if comprehensive property management with search filters and sorting capabilities is included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the contract management system complete?",
-      "description": "Evaluate whether the contract module includes creation, signing, renewal, termination, and amendment workflows. Check for essential contract fields (parties involved, property details, rent amount, payment schedule, term length, special clauses). Deduct 3 points if digital signature capabilities are missing, 3 points if contract versioning is not implemented, and 2 points if contract templates are not available. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the financial transaction module properly integrated?",
-      "description": "Check if the system handles rent collection, payment tracking, invoicing, and financial reporting. Verify integration with contract terms for automatic payment calculations and rental increments. Deduct 3 points if reporting functionality is missing, 3 points if payment history is not tracked, and 2 points if there's no notification system for due/overdue payments. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the navigation and menu system properly implemented across pages?",
-      "description": "Evaluate the implementation of separate webpages for each menu item with proper navigation links between them. Check that URLs are structured logically, breadcrumbs are provided, and the current page is highlighted in the navigation. Deduct 3 points if direct navigation between related pages is missing, 3 points if the navigation hierarchy is unclear, and 2 points if the menu system isn't responsive. 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 issues, authentication failures, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should include form validation, handle edge cases, and provide meaningful error messages, 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. Interactive property maps with virtual tours 2. AI-powered rent optimization suggestions 3. Integrated maintenance request system with priority handling). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple user profile management systems) 2. Function modules unrelated to property management (e.g., a built-in game for tenants) 3. Fancy effects that affect performance (e.g., excessive animations on dashboard). 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/business logic/presentation layers), code reusability, and adherence to design patterns. Deduct 5 points if global state pollution is found or appropriate design patterns are not used; deduct 3 points if the code duplication rate is too high (over 30%); deduct 2 points if there's no error logging mechanism. 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 suitable for a commercial property system (professional blues/grays with accent 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 property listing interactions. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast scrolling through property listings, and 5 points for hard-to-find key function buttons like contract creation. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "medium"
-}

package/library/management_systems-frontend_backend_platforms/company-announcement-management-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 603,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Ensure the generated code is executable for demonstration. Please develop a company announcement management system. Administrators can publish announcements, set publishing and expiration times, and all logged-in users can browse existing announcements, while expired announcements should not be visible.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the announcement CRUD system fully implemented?",
-      "description": "Review whether the code accurately implements complete announcement management operations through proper backend APIs and frontend interfaces, including create, read, update, delete functionalities with proper form validation and data persistence. Score 0 if core CRUD operations are missing, 5 if only basic create/read is implemented, and 10 if all operations including batch management and rich text editing are fully supported.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the time-based visibility control mechanism properly implemented?",
-      "description": "Check whether the system correctly handles announcement publishing time, expiration time, and automatic visibility switching. Verify timezone handling, server-client time synchronization, and background scheduled tasks for expiration processing. Deduct 5 points if timezone conversion is missing, and 3 points if expired announcements still appear in listings. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the user authentication and role-based access control system designed?",
-      "description": "Evaluate whether the system implements proper user authentication (login/logout), session management, and role differentiation between administrators and regular users. Check for proper permission validation on both frontend and backend. Deduct 5 points if frontend-only permission control is used, and 3 points if session timeout handling is missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the announcement browsing and filtering functionality comprehensive?",
-      "description": "Check whether the code includes complete announcement browsing features such as pagination, search functionality, category filtering, sorting options (by date, priority), and responsive display. Deduct 5 points if pagination is not implemented, and 3 points if search functionality is missing. Give 10 points if advanced filtering and sorting are fully implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid date inputs, network interruption, unauthorized access attempts, 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. Real-time notification system for new announcements 2. Rich text editor with media embedding 3. Announcement read status tracking 4. Email/SMS notification integration). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple date picker components) 2. Function modules unrelated to announcement management (e.g., built-in chat system) 3. Fancy effects that affect performance (e.g., excessive animations on announcement cards). 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/presentation/data layers), proper database schema design, API documentation, and error logging mechanisms. Deduct 5 points if SQL injection vulnerabilities are found or input sanitization is missing; deduct 5 points if the code lacks proper commenting and documentation; deduct 5 points if no logging system is implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching with proper contrast ratios for accessibility 2) Consistent layout spacing following grid systems 3) Professional typography hierarchy with readable font sizes (≥ 14px for body text). Deduct 3 points for each crowded interface section, 5 points for poor color accessibility, and 5 points for inconsistent visual elements. 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 user experience standards: 1) Form submission feedback with loading states 2) Smooth transitions between different views (300-500ms duration) 3) Clear visual hierarchy and focus management 4) Responsive design across different screen sizes. Deduct 5 points for each operation without proper feedback, 3 points for jarring transitions, and 5 points for poor mobile responsiveness. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "medium"
-}

package/library/management_systems-frontend_backend_platforms/computer-application-lottery-draw-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 1345,
-  "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. Help me write a locally launched computer application including both frontend and backend, implementing the following lottery logic: from numbers 1-200, draw two numbers from each group of ten, for a total of forty \"general benefit\" prizes, and additionally draw three third-place prizes, two second-place prizes, and one first-place prize.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Lottery Core Algorithm Implementation",
-      "description": "Evaluate the implementation of the core lottery drawing algorithm that correctly selects numbers according to the specified requirements: 40 'general benefit' prizes (two from each group of ten numbers 1-200), plus 3 third-place prizes, 2 second-place prizes, and 1 first-place prize.Check if the algorithm correctly implements: 1) Selection of exactly 2 numbers from each decade (1-10, 11-20, etc.) 2) No duplicates across all prize tiers 3) Clear distinction between general and special prizes. Score 0 if the core algorithm is missing, 5 if partially implemented with errors, and 10 if fully implemented with proper validation.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Frontend-Backend Integration",
-      "description": "Assess how well the frontend and backend components communicate and work together to provide a seamless lottery application.Check for: 1) Proper API endpoints for lottery operations 2) Appropriate data transfer format (JSON/XML) 3) Error handling for failed requests 4) Loading states during backend operations. Deduct 3 points for missing error handling, 3 points for no loading indicators, and 4 points if the integration is completely broken or missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Local Application Deployment",
-      "description": "Evaluate how easily the application can be launched locally with clear setup instructions.Check if the solution includes: 1) Clear setup instructions 2) Dependency management (package.json, requirements.txt, etc.) 3) Configuration options for local environment 4) Single command startup process. Deduct 2 points for each missing component. Award full 10 points only if a novice developer could set up and run the application within 10 minutes.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Lottery Result Visualization",
-      "description": "Evaluate the visual presentation of the lottery results, including how clearly different prize tiers are displayed and distinguished.Check whether: 1) Results clearly distinguish between prize categories 2) Visual hierarchy emphasizes higher-value prizes 3) Animation or visual effects enhance the drawing experience 4) Results are easily readable and accessible. Deduct 2 points for each missing aspect. Give 10 points only if the visualization is both functional and engaging.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Code Robustness",
-      "description": "Evaluate whether the code can handle common abnormal situations and provide friendly error prompts or recovery mechanisms.Evaluate whether the code can handle: 1) Invalid inputs 2) Random number generation edge cases 3) User interaction errors 4) Server/client connection issues. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Innovative Features",
-      "description": "Check whether the code includes surprise features that enhance the lottery experience.Check for features like: 1) Draw history tracking 2) Statistical analysis of past draws 3) Personalized 'lucky number' recommendations 4) Visual/audio feedback during drawing process. Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Redundant Features",
-      "description": "Strictly check for unnecessary or redundant features that complicate the codebase without adding value.Check for three types of redundancy: 1) Multiple implementations of similar functions 2) Unrelated features that distract from the lottery purpose 3) Over-engineered solutions for simple requirements. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Engineering Quality",
-      "description": "Review code architecture, testing, and build processes for professional engineering standards.Review for: 1) Modular design separating lottery logic/UI/data layers 2) Unit test coverage of critical functions 3) Build process automation 4) Clean code principles. 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": "Interface Design Quality",
-      "description": "Evaluate whether the overall UI design follows modern design principles and provides a professional look.Evaluate whether the design follows: 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": "User Interaction Quality",
-      "description": "Judge whether the dynamic effects and user interactions are smooth, intuitive, and provide appropriate feedback.Judge whether interactions: 1) Provide feedback within 100ms of user actions 2) Include appropriate animations for lottery drawing (300-500ms duration) 3) Guide user focus to important elements 4) Make the lottery drawing process exciting. Deduct 5 points for each operation without feedback, 3 points for visual after-images during animations, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "easy"
-}

package/library/management_systems-frontend_backend_platforms/conference-room-equipment-reservation-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 468,
-  "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 for display.\n\n======== ROLE ========\nYou are an experienced code expert. I am providing you with a software development requirement description and asking you to generate project code based on these requirements. Strictly follow the rules to help the user generate complete project code with simple and easy-to-understand comments. Don't output anything else.\n\n======== OUTPUT RULES ========\n1. You should always generate complete, runnable project code. Please ensure the project is complete and executable\n2. Ensure all code files you output are complete, don't omit any code\n3. Carefully review and check all code before final output, evaluating its executability. If the code cannot be executed or contains errors, it needs to be regenerated\n4. If the requirements include external API access or need to use user data (images, videos, audio, etc.), please provide mock data\n\n======== PROJECT REQUIREMENTS ========\nImplement a conference room equipment reservation system where users can view the equipment configuration and availability of conference rooms and submit reservation requests; administrators can manage conference room information, including equipment updates and reservation approvals.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the conference room listing and detail view fully implemented?",
-      "description": "Evaluate whether the code properly implements a listing of all conference rooms with filtering/sorting capabilities, and whether each room has a detailed view showing its capacity, equipment, and availability calendar. Check if users can easily search rooms based on equipment needs and available time slots. Score 0 if room listing is missing, 5 if only basic listing without filtering is implemented, and 10 if comprehensive search, filtering and detailed view are fully included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the reservation submission and management functionality complete?",
-      "description": "Check whether users can select available time slots, specify required equipment, and submit reservation requests with all necessary details (date, time, duration, purpose, etc.). Verify if the system validates conflicts, shows confirmation feedback, and allows users to view, modify or cancel their existing reservations. Deduct 5 points if conflict validation is missing, 3 points if reservation modification is not supported. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the admin management interface comprehensive and secure?",
-      "description": "Assess if administrators can add/edit/delete conference rooms, update equipment configurations, and manage reservation requests (approve/reject with reasons). Check if the admin dashboard provides usage analytics and reports. Verify proper access control mechanisms preventing unauthorized access to admin functions. Deduct 5 points if equipment management is incomplete, 3 points if reservation approval workflow is missing, and 5 points if access control is inadequate. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the notification system properly implemented?",
-      "description": "Evaluate whether the system sends notifications for reservation confirmations, rejections, reminders, and changes in room availability. Check if notifications are delivered through appropriate channels (in-app, email) and if users can configure their notification preferences. Deduct 5 points if notifications are one-way only, 3 points if they lack critical information, and 5 points if there's no notification for reservation status changes. 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 double bookings, system downtime, concurrent reservations, form validation, 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 room availability visualization 2. Equipment compatibility checking 3. Meeting suggestions based on past usage patterns). 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 with overlapping purposes) 2. Function modules unrelated to reservation system (e.g., a built-in chat system) 3. Fancy effects that affect performance (e.g., unnecessary animations when switching views). 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 models/views/controllers or using appropriate framework architecture), 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/conference-room-usage-registration-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 1021,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code whenever possible. Generate code for a conference room usage registration system.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the conference room registration system's core functionality fully implemented?",
-      "description": "Review whether the code accurately implements the core registration system including room listing, booking creation, modification and cancellation. Check if it handles time slot management with conflict detection. Score 0 if the core booking logic is missing, 5 if only basic room listing and booking is implemented, and 10 if all features including conflict resolution, recurring bookings, and approval workflows are fully included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the user authentication and authorization system properly implemented?",
-      "description": "Evaluate whether the system implements proper user authentication (login/logout) and role-based authorization (admin, manager, regular user). Check if permissions are correctly enforced for creating, viewing, modifying, and canceling reservations. Deduct 5 points if authentication is missing, 3 points if role-based permissions are not implemented. Full score requires secure password handling and session management.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the data persistence layer well-designed with appropriate validation?",
-      "description": "Check whether the system uses a proper database design with normalized tables for rooms, users, bookings, and potentially equipment. Validate that data integrity constraints are enforced (foreign keys, unique constraints, etc.). Examine if input validation is comprehensive. Deduct 5 points for poor schema design, 3 points for missing validation. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are notifications and reminders functionality implemented?",
-      "description": "Assess whether the system provides automated notifications for booking confirmations, reminders before meetings, and changes/cancellations. Check for both email and in-app notification capabilities. Deduct 5 points if notifications are entirely missing, 3 points if they're incomplete or unreliable. Give 10 points if notifications are customizable and include multiple channels.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as concurrent booking requests, invalid inputs, server 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. Room utilization analytics 2. Integration with calendar systems 3. QR code check-in/verification 4. Equipment reservation alongside room booking). 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 creation pathways with different logic) 2. Function modules unrelated to room booking (e.g., a built-in chat system) 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 controllers/services/repositories), 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": "medium"
-}

package/library/management_systems-frontend_backend_platforms/contract-management-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 646,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Translation\n\nYou are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable for demonstration purposes.\n\n======== ROLE ========\nYou are an experienced code expert. I will provide you with a software development requirement description, and I need you to generate project code based on these requirements. Strictly follow the rules to help users generate complete project code with clear and easy-to-understand comments. Don't output anything else.\n\n======== OUTPUT RULES ========\n1. Always generate complete, runnable project code and ensure the project is fully executable\n2. Ensure all code files you output are complete without omitting any code\n3. Carefully review and check all code before final output, evaluating its executability. If the code cannot be executed or contains errors, regenerate it\n4. If the requirements involve external API access or need to use user data (images, videos, audio, etc.), please provide simulated data\n\n======== PROJECT REQUIREMENTS ========\nPlease write code to implement a contract management system where users can upload contract files, categorize and tag them with keywords, and support online contract signing. The system should provide contract template management, allowing users to quickly generate standard contracts. Administrators should be able to review contract signing status and generate contract signing statistical reports.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the contract upload and storage system fully implemented?",
-      "description": "Check if the code implements complete file upload functionality with multi-format support (PDF, DOCX, etc.), secure storage mechanisms, version control for contracts, and proper file validation. Score 0 if upload functionality is missing, 5 if basic upload exists without validation or version control, and 10 if comprehensive upload with security measures and version tracking is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the contract categorization and tagging system properly implemented?",
-      "description": "Evaluate whether the code includes a robust categorization system with hierarchical categories, tag management with autocomplete suggestions, search functionality by tags/categories, and batch tagging capabilities. Deduct 3 points if hierarchical categories are missing, 3 points if tag search is inefficient, and 3 points if no tag analytics are provided. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the online contract signing functionality complete?",
-      "description": "Review the implementation of digital signature capabilities, including authentication verification, signature positioning, multi-party signing workflow, signature validation, and audit trails. Deduct 5 points if signature verification is weak, 3 points if the signing workflow doesn't support multiple parties, and 3 points if there's no audit trail. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the contract template management system effectively designed?",
-      "description": "Check if the system includes template creation/editing, variable field definition, template versioning, preview functionality before generation, and mass generation capabilities. Deduct 3 points if template versioning is missing, 3 points if variable field management is limited, and 3 points if there's no preview feature. 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 file upload failures, signature verification errors, invalid template data, 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-assisted contract analysis 2. Blockchain verification for signatures 3. Real-time collaboration on contract drafting). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple file upload mechanisms coexisting) 2. Function modules unrelated to contract management (e.g., a built-in chat system) 3. Fancy effects that affect performance (e.g., unnecessary animations on contract view). 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 contract data/view/business logic 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 administrative reporting and analytics functionality complete?",
-      "description": "Judge whether the admin dashboard provides comprehensive reporting features: 1) Contract status visualization with filtering options 2) Statistical reports with exportable formats (PDF, Excel) 3) Performance metrics tracking (avg. signing time, rejection rates). Deduct 3 points for each missing report type, 3 points for non-interactive dashboards, and 5 points if data visualization is poor or misleading. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "hard"
-}