@getollie/cli 0.0.1

package/library/management_systems-frontend_backend_platforms/chinese-financial-system-python-react-mysql.json

@@ -0,0 +1,68 @@
+{
+  "index": 1452,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Ensure that the generated code is executable for demonstration. Develop a Chinese financial system using Python, React, and MySQL, including the creation, deletion, modification, and review of accounting vouchers, chart of accounts balance sheet, and financial statements. The system must comply with Chinese accounting law. Access should be restricted to authorized logged-in users only. Please provide detailed code.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Authentication and Authorization System Implementation",
+      "description": "Evaluate the implementation of a secure user authentication and authorization system. Check for proper login flow, session management, password hashing, and role-based access control that restricts financial data access to authorized users only. Review JWT implementation, refresh token mechanism, and protection against common security threats.0 points if basic authentication is missing, 5 points if authentication exists but has security flaws, 10 points for a comprehensive secure solution with proper role management that fully restricts system access to authorized users only.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Accounting Voucher Management Implementation",
+      "description": "Assess the completeness of the voucher system (借贷凭证系统) including creation, modification, deletion, and review workflows. Check if the code enforces double-entry bookkeeping principles with balanced debits and credits. Verify implementation of voucher numbering, date validation, and approval workflow states conforming to Chinese accounting standards.0 points if voucher management is incomplete, 5 points if basic CRUD operations are present but lack validation or approval workflow, 10 points for a comprehensive implementation that includes all accounting validation rules and proper audit trails.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Chart of Accounts and Ledger System",
+      "description": "Review the implementation of the chart of accounts (会计科目表) according to Chinese accounting standards. Check if the account hierarchy is properly designed with appropriate account categories (assets, liabilities, equity, revenue, expenses), account codes, and balancing attributes. Verify that the ledger system properly maintains running balances and historical transactions.0 points if the chart of accounts is missing or fundamentally flawed, 5 points for basic implementation without proper hierarchy or Chinese accounting compliance, 10 points for a complete implementation that follows the latest Chinese accounting standards with proper account relationships.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Financial Statement Generation",
+      "description": "Evaluate the code that generates financial statements (balance sheet/资产负债表, income statement/利润表, cash flow statement/现金流量表) according to Chinese GAAP. Check if the statements correctly aggregate account balances, handle profit calculations, and format the output according to official templates required by Chinese regulatory authorities.0 points if financial statements are missing, 5 points if statements are generated but with calculation errors or non-compliant formatting, 10 points for accurate statements that fully comply with Chinese accounting law and regulatory requirements.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Code Robustness",
+      "description": "Evaluate whether the code can handle common abnormal situations (invalid accounting entries, concurrent edits, database connection issues, etc.) and provide friendly error prompts or recovery mechanisms. Check exception handling, input validation, and transaction integrity.0 points if no exception handling exists, 5 points for basic error handling but missing transaction integrity, 10 points for comprehensive error handling with proper transaction management and data consistency guarantees.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Innovative Financial Features",
+      "description": "Check whether the code includes innovative features that enhance the financial system experience (e.g., 1. Real-time financial dashboard, 2. Automated tax calculation for Chinese tax law, 3. AI-assisted anomaly detection in financial data, 4. Mobile-responsive design for approvals on the go).Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Code Redundancy and Efficiency",
+      "description": "Strictly check for: 1. Redundant implementations of similar financial calculations, 2. Function modules unrelated to accounting needs, 3. Inefficient database queries that would impact performance with large financial datasets.Deduct 3 points for each significant redundancy found, and directly deduct 10 points if core financial functions are compromised by redundant or inefficient code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Engineering Quality and Architecture",
+      "description": "Review the system architecture, examining separation of concerns between backend (Python), frontend (React), and database (MySQL). Check for proper API design, component reusability, and adherence to best practices in each technology stack. Evaluate code organization, naming conventions, and documentation.Deduct 5 points if business and presentation logic are mixed, 5 points if the code lacks proper documentation for financial functions, 5 points if there's no clear architectural pattern. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "UI Design for Financial Data Presentation",
+      "description": "Evaluate whether the React UI follows professional financial system design principles: 1) Clear hierarchy of financial information, 2) Proper data tables for financial entries with sorting/filtering capabilities, 3) Intuitive navigation between different accounting modules, 4) Professional reporting views with proper number formatting for currency.Deduct 3 points for poor financial data visualization, 5 points for confusing navigation between accounting modules, 5 points for improper decimal or currency formatting in financial displays. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Compliance with Chinese Accounting Law",
+      "description": "Judge whether the system implements required regulatory compliance features: 1) Proper audit trails for all financial transactions, 2) Implementation of required accounting periods and closing procedures, 3) Support for Chinese-specific accounting documents and reporting requirements, 4) Data retention policies according to Chinese law.Deduct 5 points for each missing compliance feature, 3 points for incomplete implementation of Chinese accounting standards, and 5 points for any feature that directly contradicts Chinese accounting regulations. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "hard"
+}

package/library/management_systems-frontend_backend_platforms/chronic-disease-management-platform.json

@@ -0,0 +1,68 @@
+{
+  "index": 346,
+  "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. Can you design a chronic disease management care platform that demonstrates real-time data analysis, primarily involving the monitoring of vital signs and medication for hypertension, hyperlipidemia, and hyperglycemia? Please display it using HTML.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the vital sign monitoring system fully implemented?",
+      "description": "Review whether the code accurately implements real-time monitoring displays for key vital signs (blood pressure, blood glucose, and cholesterol levels) using appropriate data visualization techniques and includes threshold alerts for abnormal values. Score 0 if the core monitoring components are missing, 5 if only basic static displays are implemented, and 10 if interactive, real-time monitoring with clinical thresholds is fully included.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the medication management system properly implemented?",
+      "description": "Check whether the code includes functionality for tracking medication adherence, dosage schedules, and refill reminders for hypertension, hyperlipidemia, and hyperglycemia medications. Evaluate if it handles medication conflicts, provides dosage calculators based on vital signs, and includes medication history. Deduct 5 points if medication tracking is only basic lists, 3 points if no adherence tracking exists. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the data analysis and trend visualization system well-designed?",
+      "description": "Evaluate whether the platform includes comprehensive data analysis tools that show trends over time using appropriate charts (line graphs, bar charts, etc.) for all three conditions. Check if interactive elements allow filtering by date ranges and correlation analysis between different metrics. Deduct 5 points if visualizations are static, 3 points if trend analysis is limited to single metrics without correlation capabilities. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is there a comprehensive care plan management system?",
+      "description": "Assess whether the code implements personalized care plan creation, tracking, and adjustment features based on clinical guidelines for chronic disease management. Check for goal-setting tools, progress tracking, and automated care plan recommendations based on vital sign trends. Deduct 5 points if care plans are static, 3 points if there's no ability to track progress against goals. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as missing data points, out-of-range values, connection issues when fetching data, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should implement data validation, error boundaries, and graceful degradation. Give 10 points for comprehensive error handling, 5 points for basic error checks, and 0 points if no exception handling exists.",
+      "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 predictive analytics for health deterioration 2. Integration with wearable device data simulation 3. Virtual health coach with personalized recommendations 4. Gamification elements for treatment adherence). 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 data displays (e.g., multiple charts showing the same information) 2. Function modules unrelated to chronic disease management 3. Excessive animations or visual effects that affect performance and distract from critical health 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 (such as separating data processing/visualization/user interaction layers), component reusability, and code organization. Deduct 5 points if global variables are overused or if there's no clear separation of concerns; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no data validation or sanitization. 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 clinical UI best practices: 1) Appropriate color scheme for healthcare (blue/green tones, clear warning colors for alerts) 2) Clear information hierarchy with critical data prominently displayed 3) Accessible design with readable fonts (minimum 16px for body text) and sufficient contrast ratios (4.5:1). Deduct 3 points for each accessibility violation, 5 points for using inappropriate colors that could cause misinterpretation of medical data, and 5 points for cluttered displays that obscure critical information. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction suitable for healthcare practitioners and patients?",
+      "description": "Judge whether the interface provides appropriate interactions for both clinical and patient use: 1) Clear categorization of information by condition 2) Intuitive navigation between monitoring sections 3) Responsive design that works on both desktop and mobile devices for patient access. Deduct 5 points for interactions requiring multiple clicks to access critical data, 3 points for confusing navigation structures, and 5 points for interactions that don't consider varying levels of technical literacy. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "hard"
+}

package/library/management_systems-frontend_backend_platforms/class-exam-scores-average-display.json

@@ -0,0 +1,68 @@
+{
+  "index": 1640,
+  "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 demonstration. In the username rules, the 5th and 6th digits together represent the class number. For example, 23010102 represents a student from class 01, similarly, 23010201 represents a student from class 02. Please write a template page to view class exam scores and display the class average score. If a student has multiple scores for the same test, only the highest score should be used for calculation. You can name the template yourself, and set the permission so that teachers can view it. The specific organization of the page is up to you.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the exam score viewing template properly implemented?",
+      "description": "Verify that the template correctly displays individual student scores and calculates class averages. The implementation should correctly parse usernames to extract class numbers (5th and 6th digits) and group students accordingly. Check that the highest score is used for calculation when a student has multiple scores for the same test.Score 0 if the core display logic is missing, 5 if basic score display is implemented but without proper class grouping, and 10 if all requirements are fully implemented including proper class extraction from usernames and highest score selection.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the username parsing logic correctly implemented?",
+      "description": "Evaluate whether the code correctly extracts the class number from the 5th and 6th digits of usernames (e.g., 23010102 → class 01, 23010201 → class 02). Check if the extraction logic handles edge cases like invalid usernames or missing digits.Deduct 5 points if the extraction logic is incorrect, 3 points if edge cases aren't handled. Full score if the parsing works correctly for all valid inputs and gracefully handles exceptions.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the highest score selection algorithm properly implemented?",
+      "description": "Check whether the code correctly identifies and uses only the highest score when a student has multiple scores for the same test. The algorithm should efficiently compare and select maximum values without unnecessary iterations.Deduct 5 points if the algorithm incorrectly selects scores, 3 points if it works but is inefficient. Score 10 if the implementation is both correct and optimized.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is teacher permission control properly implemented?",
+      "description": "Evaluate whether the template includes proper access control mechanisms that restrict viewing to teachers only. This should include authentication checks and appropriate error messages for unauthorized access attempts.Score 0 if no permission control exists, 5 if basic authentication is implemented but with security flaws, and 10 if robust permission controls are implemented with proper session validation and error handling.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as missing data, malformed usernames, empty classes, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases.Give 10 points if the code handles all common edge cases, 5 points if handling is average, and 0 points if no exception handling exists.",
+      "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. Sorting/filtering options 2. Visual data representation like charts 3. Export functionality for reports 4. Comparative analysis between classes).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 exam score viewing 3. Fancy effects that affect performance unnecessarily.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), code readability, and maintainability. Check for proper commenting, consistent naming conventions, and reusable components.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 code is poorly documented or difficult to maintain.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times).Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance for interactive elements like sorting buttons or filters.Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast interactions, 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/classroom-assignment-tracker-groups-students.json

@@ -0,0 +1,68 @@
+{
+  "index": 1205,
+  "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 when possible. Help me create a classroom assignment tracking system with a middle section displaying groups in a tiled layout with large, prominent text, and where the right side can show multiple students' names per line for those who haven't completed assignments.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the classroom assignment tracking system fully implemented?",
+      "description": "Review whether the code implements a complete tracking system including the ability to add/remove assignments, track completion status, and manage students and groups. Score 0 if the core functionality is missing, 5 if only basic tracking is implemented, and 10 if the system provides comprehensive assignment management with status updates and filtering capabilities.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the tiled layout with groups in the middle section properly implemented?",
+      "description": "Check if the middle section displays groups in a tiled layout with large, prominent text as specified. The tiles should be visually distinct, properly sized, and maintain consistent spacing. Deduct 3 points if the text is not prominent, 3 points if the tiling is inconsistent, and 4 points if the layout doesn't adapt to different screen sizes. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the right-side panel correctly showing multiple students per line?",
+      "description": "Evaluate whether the right panel shows multiple students' names per line for those who haven't completed assignments. The implementation should optimize space while maintaining readability. Deduct 5 points if only one student is displayed per line, 3 points if the display is cluttered or hard to read, and 2 points if there's no visual differentiation between complete/incomplete status. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the data structure design appropriate for tracking assignments?",
+      "description": "Assess whether the code uses efficient data structures for tracking assignments, students, groups, and completion status. The structure should allow for quick lookups and updates. Deduct 4 points for inefficient data structures that would slow down the application, 3 points for missing relationships between entities, and 3 points if there's no provision for data persistence. 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, missing data, large datasets, 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 progress visualization 2. Automated reminder system 3. Progress tracking over time with charts). 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 track the same data) 2. Function modules unrelated to assignment tracking (e.g., irrelevant calculators or tools) 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 data model/view/controller 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": "easy"
+}

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

@@ -0,0 +1,68 @@
+{
+  "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

@@ -0,0 +1,68 @@
+{
+  "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

@@ -0,0 +1,68 @@
+{
+  "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

@@ -0,0 +1,68 @@
+{
+  "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"
+}