@getollie/cli 0.0.5 → 0.2.1

package/library/management_systems-frontend_backend_platforms/bim-management-system-with-3d-preview.json

@@ -1,68 +0,0 @@
-{
-  "index": 625,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the generated code is executable for demonstration. Create a Building Information Modeling (BIM) management system that supports uploading .rvt/.ifc formats and displays 3D previews. Allow adding tags for floors and disciplines (architecture/structure/MEP), provide measurement tools and sectional view generation capabilities. Model updates must follow an approval workflow (initiate-review-publish).",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the BIM file upload and format conversion system fully implemented?",
-      "description": "Review whether the code accurately implements file upload mechanisms for .rvt and .ifc formats, includes proper validation of file integrity, and conversion to web-compatible 3D formats (e.g., glTF, OBJ). Check if the system handles large file uploads with chunking and progress tracking. Score 0 if upload functionality is missing, 5 if basic upload is implemented without format conversion, and 10 if complete upload, validation, and conversion pipeline is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the 3D model viewer properly implemented with all required functionality?",
-      "description": "Evaluate the implementation of the 3D viewer component. It should support basic navigation (pan, zoom, rotate), camera positioning presets, and display optimization for complex models. Check if the viewer handles different LOD (Level of Detail) to maintain performance with large models. Score 0 if viewer is not implemented, 5 if only basic viewing capabilities exist, and 10 if advanced features like selective rendering, performance optimizations, and cross-browser compatibility are included.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are tagging and classification features complete?",
-      "description": "Check if the system allows adding, editing, and filtering tags for floors and disciplines (architecture/structure/MEP). Evaluate whether the tagging system is hierarchical, supports searching, and is visually integrated with the 3D model. Verify that discipline-specific color coding is applied to model components. Deduct 5 points if tagging is not connected to visual representation, and 3 points if bulk tagging options are missing. Full score requires persistent metadata storage and tag-based filtering in the UI.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are measurement tools and sectional view capabilities implemented?",
-      "description": "Assess whether the code includes comprehensive measurement tools (distance, area, angle) and generating cross-sectional views through the model. Check for accuracy in measurements with proper units conversion. Verify that section planes can be positioned freely and that section views are generated in real-time. Deduct 5 points if only basic measurements are implemented, and 3 points if sectional views lack customization options. The full score requires tools with professional-grade accuracy and intuitive UX.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as corrupted BIM files, browser memory limitations, unsupported model features, etc.) and provide friendly error prompts or recovery mechanisms. Check for validation of user inputs in measurement tools and handling of concurrent user actions. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. AI-powered clash detection 2. Automated space usage analysis 3. VR/AR viewing mode 4. Collaborative annotation systems). 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 measurement tools using different calculation methods) 2. Function modules unrelated to BIM management (e.g., a built-in document editor) 3. Fancy effects that affect performance (e.g., unnecessary particle effects or 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 3D rendering/BIM data processing/approval workflow), unit test coverage, and build process automation. Check for proper memory management when handling large 3D models. 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 that distinguishes different disciplines/systems 2) Proper layout with clear separation between model viewer, navigation controls, and property panels 3) Professional font system with technical readability (body font size ≥ 14px, monospace for measurements). 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 approval workflow fully implemented and intuitive?",
-      "description": "Judge whether the initiate-review-publish workflow is properly implemented with: 1) Clear status indicators for models 2) Role-based permissions for workflow actions 3) Version comparison tools between iterations 4) Comment/feedback system for reviewers. Deduct 5 points if the workflow lacks audit trails, 3 points if notification systems are missing, and 5 points if version control is inadequate. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "hard"
-}

package/library/management_systems-frontend_backend_platforms/blazor-ruoyi-admin-page.json

@@ -1,68 +0,0 @@
-{
-  "index": 1386,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Ensure that the code you generate is executable for demonstration purposes. Write an admin page similar to RuoYi using Blazor.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the basic admin page layout properly implemented with Blazor?",
-      "description": "Evaluate whether the code implements a complete admin layout with header, sidebar, content area, and footer using Blazor components. Check if the layout is responsive and follows modern UI principles. Score 0 if no layout implementation exists, 5 if basic layout is present but with significant issues, and 10 if a complete RuoYi-style layout is implemented with proper component organization.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are authentication and authorization mechanisms implemented?",
-      "description": "Review the implementation of user authentication (login/logout) and role-based authorization. Check if it includes JWT or cookie-based authentication, role-based access control, and permission verification for different operations. Deduct 5 points if authentication is missing, 3 points if role-based controls are absent, and 3 points if permission granularity is insufficient. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the user and role management module implemented?",
-      "description": "Assess whether the system includes comprehensive user and role management features similar to RuoYi, including user CRUD operations, role assignment, department management, and user status control. Score 0 if these features are missing, 5 if only basic user management exists, and 10 if all RuoYi-equivalent user and role management features are implemented with proper data validation.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the system include data table management with CRUD operations?",
-      "description": "Evaluate whether the admin system implements data table management with sorting, filtering, pagination, and CRUD operations. Check if the implementation includes advanced features like batch operations, column customization, and export functionality. Deduct 3 points if pagination is missing, 3 points if filtering is insufficient, and 4 points if CRUD operations are incomplete. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as network errors, invalid inputs, concurrent operations, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Real-time dashboard with SignalR 2. Interactive data visualization 3. Advanced theming capabilities beyond RuoYi). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple authentication mechanisms coexisting) 2. Function modules unrelated to admin system (e.g., unnecessary widgets or components) 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 service/model/view layers), component reusability, 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/building-drawing-management-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 527,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable whenever possible. Please write code to implement a building drawing management system where architects can upload CAD drawings and BIM models. The system should support online drawing preview, version comparison, annotation marking functions, provide project classification and drawing numbering management, support drawing approval workflow, and be able to record drawing modification history and reasons for changes.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the CAD/BIM file upload and storage system fully implemented?",
-      "description": "Review whether the code accurately implements a secure upload mechanism for CAD drawings and BIM models, including proper file type validation, size checking, and storage management. Check if the system handles various CAD/BIM formats (DWG, DXF, RVT, IFC) and optimizes storage through compression or cloud storage integration. Score 0 if the upload functionality is missing, 5 if basic upload exists without format validation, and 10 if a complete, secure, and optimized upload system is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the online drawing preview functionality effectively implemented?",
-      "description": "Evaluate whether the system includes robust rendering engines to display CAD drawings and BIM models directly in the browser without requiring special software. Check if the preview supports essential functions like zooming, panning, layer toggling, and 3D model rotation for BIM. The preview should work across major browsers and maintain drawing fidelity. Deduct 3 points if the preview is limited to certain file types, 4 points if 3D model interactivity is missing, and 3 points if the rendering quality is poor or slow. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "How comprehensive is the version comparison and annotation system?",
-      "description": "Check if the code implements side-by-side visual comparison between drawing versions with highlighted differences and if annotations can be added as overlays on drawings without modifying the original files. The annotation system should support text notes, measurement tools, redline markups, and the ability to assign annotations to specific team members. Deduct 3 points if visual diff is missing, 3 points if annotation types are limited, and 4 points if annotation sharing/assignment capabilities are absent. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the project classification, drawing numbering, and approval workflow system properly implemented?",
-      "description": "Assess whether the system includes a hierarchical project organization structure, an automated drawing numbering system based on configurable rules, and a flexible approval workflow engine. The workflow should support multi-stage approvals with role-based permissions, electronic signatures, and automatic notifications. Deduct 3 points for lacking custom classification hierarchies, 3 points for manual numbering, and 4 points if the approval workflow doesn't support parallel or conditional paths. 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 corrupted CAD files, concurrent edits, server timeouts during large file uploads, permission conflicts, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. AI-powered drawing analysis for errors or compliance issues 2. Automatic generation of viewports and cross-sections from BIM models 3. AR/VR integration for immersive drawing review). 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 viewers with overlapping capabilities) 2. Function modules unrelated to drawing management (e.g., a built-in general chat system not tied to drawings) 3. Fancy effects that affect performance (e.g., excessive animations when switching between drawings). 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 file handling/rendering/workflow layers), unit test coverage, and build process automation. Check for proper handling of large files through streaming or chunked processing. 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 appropriate for a technical CAD/BIM platform (neutral palette with clear accent colors for actions) 2) Proper layout spacing that maximizes drawing visibility while maintaining access to tools 3) Professional typography system that ensures readability of technical annotations and metadata. Deduct 3 points for each crowded toolbar or panel, 5 points for poor drawing-to-interface ratio, and 5 points for unclear visual hierarchy of tools and information. 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 professional CAD/BIM user expectations: 1) Drawing rendering and manipulation response ≤ 200ms 2) Smooth zoom/pan interactions without visual artifacts 3) Intuitive tool selection and application. Deduct 5 points for each operation that causes noticeable lag when manipulating drawings, 3 points for awkward tool switching mechanisms, and 5 points for non-standard interaction patterns that contradict common CAD conventions. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "hard"
-}

package/library/management_systems-frontend_backend_platforms/canteen-inventory-management-system-pyqt.json

@@ -1,68 +0,0 @@
-{
-  "index": 1654,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure that any code you generate is executable and ready for demonstration. Write a canteen inventory management system using PyQt.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core inventory management functionality implemented?",
-      "description": "Review whether the code implements essential inventory management features including: adding/removing items, updating quantities, tracking expiration dates, and categorizing food items. Score 0 if these core functions are missing, 5 if basic CRUD operations are implemented, 10 if it includes advanced features like batch operations and inventory forecasting.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the PyQt UI properly implemented with appropriate layouts?",
-      "description": "Evaluate the PyQt implementation including proper use of layouts (QVBoxLayout, QHBoxLayout, QGridLayout), responsive design principles, and proper widget hierarchy. Deduct 3 points for improper layout management causing visual issues, 3 points for fixed-size elements that don't adapt to window resizing, and 3 points if the UI elements are poorly organized. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is there a proper database integration with CRUD operations?",
-      "description": "Check whether the system properly integrates with a database (SQLite, MySQL, etc.) with proper connection handling, transaction management, and prepared statements to prevent SQL injection. Deduct 5 points if no database is used (only in-memory storage), 3 points if connections aren't properly closed, and 5 points if there's no error handling for database operations. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there a reporting and analysis functionality?",
-      "description": "Assess whether the system includes reporting features such as inventory valuation, consumption trends, stock alerts, and waste tracking. Look for data visualization components and exportable reports. Deduct 3 points for each missing essential report type, 5 points if there's no visualization capability, and 5 points if data export functionality is missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid inputs, database connection failures, concurrent access issues) 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. Barcode/QR code scanning integration 2. AI-powered inventory prediction 3. Supplier management and automated ordering). 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 perform the same task) 2. Function modules unrelated to inventory management (e.g., a built-in game) 3. Fancy effects that affect performance (e.g., unnecessary animations or visual effects). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating UI/business logic/data layers using MVC or MVVM patterns), unit test coverage, and code organization. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there is no separation of concerns. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (consistent margins and padding) 3) Professional font system (readable font sizes, appropriate contrast). Deduct 3 points for each crowded visual element, 5 points for clashing colors, and 5 points for inconsistent visual hierarchy. 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) Appropriate loading indicators for long operations 3) Clear visual focus guidance and keyboard navigation support. Deduct 5 points for each operation without feedback, 3 points for UI freezing during database operations, 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/chinese-financial-system-python-react-mysql.json

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

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

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

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