@getollie/cli 0.0.4 → 0.2.0

package/library/management_systems-frontend_backend_platforms/personal-knowledge-base-management-tool.json

@@ -1,68 +0,0 @@
-{
-  "index": 864,
-  "question": "You are a code expert. Please utilize your professional knowledge to generate accurate and professional responses. Be sure to provide executable and demonstrable code whenever possible. As a technical professional, write a complete version of a knowledge base management system for personal use.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core knowledge base storage and retrieval system fully implemented?",
-      "description": "Review whether the code implements a proper data structure for knowledge storage (e.g., relational database, document storage, graph database) with CRUD operations. Check if the code includes proper indexing for efficient knowledge retrieval and supports both structured and unstructured data. Score 0 if core storage functionality is missing, 5 if basic storage is implemented but lacks advanced retrieval, and 10 if the system includes comprehensive storage with efficient indexing and search capabilities.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the knowledge organization and categorization system properly designed?",
-      "description": "Evaluate whether the code implements hierarchical categorization, tagging system, and relationship mapping between knowledge items. Check if it supports metadata management, custom taxonomies, and dynamic reorganization of knowledge. Deduct 5 points if the system doesn't support flexible categorization, 3 points if it lacks relationship management, and 2 points if it doesn't handle metadata effectively. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the search and filtering functionality comprehensive?",
-      "description": "Assess whether the system implements full-text search with ranking algorithms, supports advanced filtering options (date range, category, tags, etc.), and includes features like fuzzy search, synonym support, and search history. Deduct 5 points if only basic string matching is implemented, 3 points if advanced search options are missing, and 2 points if the search lacks performance optimization. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the system include user-friendly content creation and editing tools?",
-      "description": "Check whether the code provides a rich text editor with formatting options, supports multimedia content embedding, offers version history and rollback functionality, and includes draft saving. Score 0 if editing capabilities are minimal, 5 if basic editing is supported without versioning or media handling, and 10 if comprehensive editing tools with versioning and media support are implemented.",
-      "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 edits, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should include input validation, error handling, and data integrity checks. Give 10 points if robustness is comprehensive, 5 points if basic error handling exists, and 0 points if exceptions are not handled properly.",
-      "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 content suggestions 2. Knowledge graph visualization 3. Spaced repetition learning system 4. Automatic content summarization). 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 search engines coexisting) 2. Function modules unrelated to knowledge management (e.g., a built-in game) 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/business logic/view 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 scrolling or searching, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "medium"
-}

package/library/management_systems-frontend_backend_platforms/personal-novel-website-with-mysql.json

@@ -1,68 +0,0 @@
-{
-  "index": 281,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure the code you generate is executable. I need a website with a MySQL database to store novels, novel categories, and user information. The front-end code should provide functionality for uploading and downloading novels, user login and registration, novel detail pages and reading interface, novel categorization, reading progress tracking, a personal profile page, and a \"currently reading\" feature. I want a personal novel website exclusively for myself and people I authorize to access.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the complete user authentication system implemented?",
-      "description": "Review whether the code includes comprehensive authentication implementation, covering registration, login, password reset, and authorization management. The system should use secure password hashing (bcrypt/Argon2), implement JWT or session-based authentication, and include role-based access control (admin vs regular users). Score 0 if basic authentication is missing, 5 if only basic functions exist without security measures, and 10 if the implementation includes all security best practices with invitation-only registration as specified.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the novel database structure properly designed with all required relationships?",
-      "description": "Evaluate the MySQL database schema design, checking for proper normalization, relationships between novels, categories, users, and reading progress. The schema should include appropriate indexes, foreign key constraints, and efficient query structures. Deduct 3 points if novels-to-categories uses a basic relationship rather than a many-to-many junction table; deduct 5 points if reading progress tracking lacks timestamp information or book position markers; deduct 3 points if user permission levels aren't granularly defined. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are the novel upload and download functionalities complete?",
-      "description": "Check whether the code implements secure file handling for uploads (validate file types, scan for malware, handle large files with chunking), supports multiple formats (EPUB, PDF, TXT), and provides efficient download options. The implementation should include metadata extraction, proper storage path management, and content validation. Deduct 5 points if upload size limitations aren't handled; deduct 3 points if download progress indicators are missing; deduct 5 points if no content validation exists. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the novel reading interface well-designed and feature-complete?",
-      "description": "Assess whether the reading interface includes essential features: text size adjustment, theme switching (light/dark mode), bookmarking, highlighting, auto-scroll options, and progress tracking. The UI should be responsive across device sizes and remember user preferences. Deduct 3 points for each missing core feature; deduct 5 points if the interface doesn't adapt to mobile screens; deduct 3 points if reading position isn't automatically saved. 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 database connection failures, invalid uploads, concurrent user edits, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should implement proper error handling, input validation, and graceful degradation. Give 10 points for comprehensive error handling with user-friendly messages, 5 points if basic error handling exists but edge cases are missed, and 0 points if exceptions aren't handled.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. AI-powered reading time estimations 2. Automatic chapter detection and navigation 3. Reading statistics dashboard 4. Social sharing options with access control). 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 progress tracking methods coexisting) 2. Function modules unrelated to novel management (e.g., a built-in game) 3. Fancy effects that affect performance (e.g., unnecessary animations that slow page loading). 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 access/business logic/view layers), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast sliding, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "hard"
-}

package/library/management_systems-frontend_backend_platforms/pharmacy-mini-program-user-order-page.json

@@ -1,68 +0,0 @@
-{
-  "index": 306,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate, professional responses. Be sure to provide executable code where possible. Please help me create a frontend page for a pharmacy store mini-program, which should include user information, a login button, and four order status categories (unpaid, in progress, to be received, and completed). The function menu should include history records, favorites, my customer service, my orders, shipping address, and settings.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the user authentication system properly implemented?",
-      "description": "Review whether the code implements a complete user authentication flow including login button functionality, session management, and secure token storage. Check if there's proper handling of authentication states (logged in/out) and user information display. Score 0 if no authentication logic exists, 5 if basic login UI is present without functionality, 10 if a complete secure authentication system is implemented with proper state management.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the four order status categories fully implemented and visually distinct?",
-      "description": "Verify that all four required order status categories (unpaid, in progress, to be received, and completed) are implemented with clear visual differentiation. Check if the code includes state transitions between categories and proper data binding. Deduct 3 points if any category is missing, 2 points if visual distinction is poor, and 2 points if state transitions are not implemented. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the function menu complete with all required features?",
-      "description": "Confirm that all six specified menu items (history records, favorites, my customer service, my orders, shipping address, and settings) are properly implemented with navigation logic. Each missing feature deducts 1.5 points. Check if each menu item has appropriate icons and leads to the correct functionality. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the pharmacy store context appropriately reflected in the design?",
-      "description": "Evaluate whether the implementation correctly reflects the pharmacy context through appropriate terminology, icons, color schemes (medical blues/greens), and pharmacy-specific features like prescription management or medication categories. Deduct 3 points if the design is generic without pharmacy-specific elements, 3 points if inappropriate terminology is used, and 4 points if the context is completely mismatched. 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, authentication failures, empty data states, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Medication reminder functionality 2. Prescription scanning capability 3. Health tips 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 user profile sections) 2. Function modules unrelated to a pharmacy mini-program (e.g., gaming features) 3. Fancy effects that affect performance (e.g., heavy animations on critical paths). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating UI components/data services/state management), code reusability for similar elements (like order cards), and proper naming conventions. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no clear project structure. 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/phone-program-sort-names-statistics.json

@@ -1,68 +0,0 @@
-{
-  "index": 1757,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure that the code generated is executable for demonstration purposes. Could you write a small program for my phone that can sort 40 names, which can be shared with around 40 people, then consolidate the data and provide statistics?",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the sorting functionality fully implemented?",
-      "description": "Review whether the code accurately implements the name sorting mechanism, with proper algorithm selection for efficiency (like quicksort, mergesort) and support for multiple sorting criteria (alphabetical, length, custom order). Score 0 if sorting is not implemented, 5 if only basic alphabetical sorting is available, and 10 if multiple flexible sorting options with proper complexity analysis are provided.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the data input mechanism user-friendly for mobile devices?",
-      "description": "Evaluate whether the input method is optimized for mobile use, with features like autocomplete, input validation, bulk import options (e.g., from contacts, CSV), and proper keyboard type selection. Check for responsive design that works across different screen sizes. Deduct 5 points if text input fields are not mobile-optimized, and 3 points if there's no input validation. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Does the sharing functionality work effectively for 40 people?",
-      "description": "Check if the code implements practical sharing methods like QR codes, shareable links, email integration, or export options. Verify that sharing preserves data integrity and works without requiring special apps for recipients. Deduct 5 points if sharing requires manual copying, 5 points if there's no confirmation mechanism, and 3 points if privacy controls are absent. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the data consolidation and statistics generation complete?",
-      "description": "Assess whether the program can effectively merge data from multiple sources, handle duplicates, and generate meaningful statistics (e.g., frequency distributions, grouping by categories, visualization of trends). Check for data validation mechanisms and conflict resolution. Deduct 5 points if basic aggregation is missing, 3 points if statistical analysis is limited to counts only, and 5 points if there's no visualization. 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 issues when sharing, duplicate names, special characters in names, empty submissions) 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. Name pronunciation audio recording 2. Auto-grouping algorithms 3. Interactive data visualization of sorting results). 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 sorting implementations without clear purpose) 2. Function modules unrelated to name sorting and statistics (e.g., a built-in game) 3. Fancy effects that affect performance on mobile devices (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/view/controller layers), unit test coverage, and offline functionality. 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 application doesn't work offline. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional mobile design standards?",
-      "description": "Evaluate whether the overall design follows modern mobile design principles: 1) Harmonious color matching suitable for mobile screens (no more than 3 primary colors) 2) Thumb-friendly layout with key interactions in reachable zones 3) Professional typography system (body font size ≥ 16px for readability). Deduct 3 points for each hard-to-tap element, 5 points for poor contrast ratios, and 5 points for layouts requiring horizontal scrolling. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and responsive on mobile devices?",
-      "description": "Judge whether the dynamic effects are optimized for mobile: 1) Touch feedback delay ≤ 100ms 2) Smooth scrolling through potentially long name lists 3) Clear visual indicators of sorting/processing status. Deduct 5 points for each interaction lacking tactile/visual feedback, 3 points for janky animations, and 5 points for any operation taking more than 2 seconds without a progress indicator. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "medium"
-}

package/library/management_systems-frontend_backend_platforms/planet-cloud-jump-system-development.json

@@ -1,68 +0,0 @@
-{
-  "index": 268,
-  "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. You are a senior PHP development engineer, helping me develop a \"Planet Cloud Jump System.\" This system needs to include the following features:\n\n1. **User-related functions:**\n   - User registration and login (supporting phone number registration and email/username registration and login).\n   - User identity verification (personal and business verification).\n   - User center: supports password recovery and profile modification.\n\n2. **Short link generation and redirection function:**\nThe main domain is only used for configuration, redirects mainly rely on the domain pool\n   - Users can generate short links, and the system maps short links to long links.\n   - Targeted redirection based on user devices (Android, iOS, PC/Mac):\n     - Android devices redirect to configured \"android_redirect\" links.\n     - iOS devices redirect to configured \"ios_redirect\" links.\n     - Other devices redirect to configured \"pc_redirect\" links.\n   - Redirect to specific regional links based on user location (obtained via IP, such as Hebei Province, Henan Province, etc.). If there is no matching region rule, redirect to the default \"region_redirect\" link.\n   - If a device or region is restricted, redirect to a custom prompt page (block_pages).\n   - Custom redirection page when opened in WeChat\n   - Custom redirection when opened in QQ\n   - Must have strong protection against Tencent detection and blocking, maintain good camouflage, prevent domains from being blocked by Tencent\n\n3. **Backend management system:**\n   - Admin dashboard (admin_dashboard.php) containing multiple modules:\n     - User management: view, search, delete or disable users.\n     - Device redirection rule management: add, edit, delete device redirection rules (device_redirects table).\n     - Region redirection rule management: add, edit, delete region redirection rules (region_redirects table).\n     - Short link management: view, edit, delete short links (links table).\n     - Prompt page management: upload and edit prompt pages (block_pages table).\n     - IP blacklist management: add, delete, view blacklisted IPs (ip_blacklist table).\n     - Statistical data and access logs: display access logs, device distribution, region distribution, redirection success rates, etc.\n     - System configuration management: set global configurations, such as default redirection links, payment interface configuration, etc.\n\n4. **Payment function:**\n   - Integrate EasyPay, supporting users to purchase short link redirection services.\n   - Purchase records are saved in the purchases table.\n\n5. **Database installer:**\n   - An install.php file for automatically creating databases, all required table structures, and generating the config/config.php file.\n   - Must be easy to install, as it will be given to others like beginners who only need to upload the program to install it.\n\n6. **Logging system:**\n   - Record system logs to the logs/system.log file.\n\nPlease generate complete code, including all PHP files, frontend HTML/CSS/JS files, and database SQL table creation statements, with the following directory structure (please strictly follow this directory structure when generating files):\nDue to the large amount of code, please do not generate simplified versions.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the User System properly implemented?",
-      "description": "Review the implementation of user registration, login, verification, and user center functionality.Award 0 points if core user functions are missing, 5 points if basic functionality exists but has security issues, 10 points for complete implementation with proper security measures (password hashing, session protection, input validation).",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "How complete is the Short Link System implementation?",
-      "description": "Evaluate the short link generation and sophisticated redirection logic based on multiple conditions.Award 0 points if redirection logic is incomplete, 5 points if basic redirection works but lacks sophisticated detection evasion, 10 points for complete implementation with all conditional redirects and Tencent anti-detection measures.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the Admin Dashboard system fully functional?",
-      "description": "Review the backend admin system's modules and management capabilities.Award 0 points if dashboard is incomplete, 5 points if basic functionality exists but lacks advanced features or security, 10 points for comprehensive implementation with all required modules, proper access controls, and data visualization.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "How well is the Payment System integrated?",
-      "description": "Evaluate the EasyPay integration and purchase record management.Award 0 points if payment system is missing, 5 points if basic payment flow exists but lacks transaction security or error handling, 10 points for complete implementation with secure API integration, proper transaction logging, and error handling.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations and provide appropriate error handling.Award 0 points if no exception handling exists, 5 points for basic error handling but lacking comprehensive protection, 10 points for robust implementation with thorough error handling, security measures, and graceful recovery mechanisms.",
-      "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 beyond requirements.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 for redundancy in code and functionality.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 code organization, architecture, and engineering practices.Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if code duplication rate is too high (over 30%); deduct 5 points if build/deployment 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 the design quality of user interfaces.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.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": "hard"
-}

package/library/management_systems-frontend_backend_platforms/plant-protection-software-frontend-pages.json

@@ -1,68 +0,0 @@
-{
-  "index": 779,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable for demonstration purposes. Design a set of frontend pages for plant protection software.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core plant monitoring UI fully implemented?",
-      "description": "Review whether the code accurately implements the plant monitoring dashboard with visualization of plant health metrics, disease identification areas, and treatment tracking. Score 0 if the core UI components are missing, 5 if basic plant status display is implemented, and 10 if comprehensive monitoring with interactive elements is fully included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the plant disease identification feature implemented?",
-      "description": "Check whether the interface includes image upload/camera functionality for plant analysis, visual indicators for identified issues, and proper display of diagnosis results. Deduct 5 points if image processing capabilities are missing, and 3 points if the result presentation is poorly designed. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are treatment recommendations and scheduling functionalities provided?",
-      "description": "Evaluate whether the interface provides contextual treatment recommendations based on identified issues, includes a calendar/scheduling system for treatment planning, and offers notification capabilities. Deduct 5 points if recommendations are static rather than contextual, and 3 points if scheduling features are incomplete. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is a complete plant data management system implemented?",
-      "description": "Check whether the code includes comprehensive plant inventory management, historical data tracking with visualizations (growth charts, treatment history), and data export/sharing capabilities. Deduct 5 points if historical tracking is missing, and 3 points if data manipulation features are incomplete. Give 10 points if fully implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as image upload failures, offline usage, form validation, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. AR visualization for plant inspection 2. Voice-guided treatment instructions 3. Plant health prediction algorithms with visualization). 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 image viewers) 2. Function modules unrelated to plant protection (e.g., a built-in generic calculator) 3. Fancy effects that affect performance (e.g., unnecessary animations slowing down critical functions). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating UI components/data services/state management), component reusability, and responsive design implementation. 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 interface is not responsive across different screen sizes. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the design follows modern agricultural/scientific software principles: 1) Professional color scheme appropriate for plant monitoring (green/earth tones with clear alerting colors) 2) Proper data visualization hierarchy (critical alerts prominent, routine data accessible but not overwhelming) 3) Professional typography system (clear labeling, readable data points, consistent headings). Deduct 3 points for each cluttered screen, 5 points for inappropriate color schemes that hinder plant issue identification, and 5 points for confusing information architecture. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects enhance plant monitoring workflows: 1) Fast-loading disease identification results (≤2 seconds feedback) 2) Smooth transitions between plant records (300-500ms) 3) Intuitive treatment scheduling interactions. Deduct 5 points for each critical operation lacking loading indicators, 3 points for jarring transitions between key screens, and 5 points for unintuitive plant selection or navigation patterns. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "medium"
-}

package/library/management_systems-frontend_backend_platforms/post-accident-summary-management-website.json

@@ -1,68 +0,0 @@
-{
-  "index": 1288,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Take care to ensure that the code you generate is executable. I want to create a website for managing post-accident summary materials, with file upload and management functionality, similar to China Judgments Online. Thank you.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the file upload and management system fully implemented?",
-      "description": "Review whether the code accurately implements multi-format file upload (PDF, DOC, DOCX, images) with proper file validation, size limits, and storage mechanisms. Check if file management includes operations like view, download, delete, and categorization. Score 0 if core upload functionality is missing, 5 if only basic upload is implemented, and 10 if comprehensive file management with metadata handling is fully included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the document search and filtering functionality implemented?",
-      "description": "Check whether the system includes advanced search capabilities with filters for case type, date range, keywords, and document categories. Evaluate if search results are properly paginated and sorted. Two-way verification between front-end filtering and back-end queries is required. Deduct 5 points if full-text search is missing, and 3 points if search performance is not optimized. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the user authentication and authorization system properly designed?",
-      "description": "Evaluate whether the system implements role-based access control (RBAC) with proper user authentication, session management, and permission levels for different user types (admin, reviewer, public). Check if secure login/logout mechanisms are implemented with proper password encryption. Deduct 5 points if JWT token management is missing. Check whether user session timeout and security measures are implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the complete document lifecycle and audit trail constructed?",
-      "description": "Check whether the code includes complete document management lifecycle, including document status tracking (draft, under review, approved, published), version control, and audit logging. Deduct 5 points if document versioning is not implemented, and 3 points if audit trail logging is missing. Give 10 points if comprehensive workflow management with approval processes is fully implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as file upload failures, database connection errors, invalid user inputs, large file handling, 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. OCR text extraction from uploaded documents 2. AI-powered document categorization 3. Advanced analytics dashboard 4. Document preview with annotation capabilities). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple file upload handlers coexisting) 2. Function modules unrelated to document management (e.g., a built-in social media feed) 3. Fancy effects that affect performance (e.g., excessive animations during file processing). 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 API layer/business logic/data access layers), error handling patterns, and security best practices implementation. Deduct 5 points if SQL injection vulnerabilities are found or input validation is missing; deduct 5 points if the code structure is not properly organized with MVC pattern; deduct 5 points if no logging mechanism 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 web design principles: 1) Professional color scheme suitable for legal/official documents (no more than 3 primary colors) 2) Proper layout spacing with consistent grid system (element spacing follows the 8px multiple principle) 3) Professional typography system (body font size ≥ 14px, line height over 1.5 times) 4) Clear navigation and breadcrumb structure. Deduct 3 points for each crowded visual element, 5 points for unprofessional color combinations, and 5 points for chaotic information 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 professional web application standards: 1) File upload progress indication with real-time feedback 2) Loading states for search and filtering operations ≤ 200ms response 3) Smooth transitions between different views (300-500ms duration) 4) Clear visual feedback for all user actions 5) Accessible keyboard navigation. Deduct 5 points for each operation without proper feedback, 3 points for slow file processing without progress indication, and 5 points for hard-to-find critical functions. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "hard"
-}

package/library/management_systems-frontend_backend_platforms/product-order-contract-generation-tool.json

@@ -1,68 +0,0 @@
-{
-  "index": 1049,
-  "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 and ready to be displayed. I want to create a tool that showcases all products, then allows for order selection in different scenarios, and automatically generates the appropriate contract for each selected scenario upon completion.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the product showcase system fully implemented?",
-      "description": "Review whether the code accurately implements a comprehensive product display system through HTML/JavaScript, including product catalog management, search/filter functionality, and detailed product information views. Check if it supports multiple product categories, image galleries, and product specifications display. Score 0 if basic product listing is missing, 5 if only static product display is implemented, and 10 if full interactive product showcase with filtering, sorting, and detailed views is included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the multi-scenario order selection mechanism properly designed?",
-      "description": "Evaluate whether the system provides distinct ordering workflows for different business scenarios (e.g., bulk orders, subscription orders, custom orders). Check if scenario-specific validation rules, pricing models, and order configurations are implemented. The system should dynamically adapt UI elements and available options based on selected scenarios. Deduct 5 points if scenario switching is not smooth, and 3 points if scenario-specific business logic is incomplete. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the automatic contract generation system robust and accurate?",
-      "description": "Check whether the contract generation engine correctly processes order data and generates appropriate legal documents for each scenario. Evaluate if the system uses proper templating mechanisms, supports dynamic clause insertion based on order specifics, and generates contracts in standard formats (PDF/Word). Deduct 5 points if contract templates are static without dynamic content, and 5 points if generated contracts contain formatting errors or missing critical information. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the complete order workflow and state management implemented?",
-      "description": "Review whether the code includes comprehensive order lifecycle management, from product selection through contract generation, including order validation, modification capabilities, order history tracking, and status updates. Check if the system provides order draft saving, modification workflows, and proper state transitions. Deduct 5 points if order persistence is not implemented, and 3 points if order modification/cancellation mechanisms are missing. Give 10 points if fully implemented with proper state management.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid product selections, network failures, malformed order data, contract generation errors, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. AI-powered product recommendations 2. Real-time pricing calculator with bulk discounts 3. Interactive contract preview with clause explanations 4. Order comparison tools 5. Integration with external pricing APIs). 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 product filtering mechanisms coexisting) 2. Function modules unrelated to the core business (e.g., built-in social media sharing) 3. Fancy effects that affect performance (e.g., excessive animations during order processing). 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 product catalog/order management/contract generation layers), component reusability, and proper data flow architecture. 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 proper separation of concerns is not 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 e-commerce and business application design principles: 1) Harmonious color matching with proper brand consistency (no more than 3 primary colors) 2) Professional layout spacing (element spacing follows the 8px multiple principle) 3) Clear information hierarchy for products and orders 4) Professional typography (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for unprofessional color combinations, and 5 points for chaotic product/order 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 business application standards: 1) Product selection feedback delay ≤ 100ms 2) Order form transitions controlled between 300-500ms 3) Clear visual guidance through the ordering process 4) Smooth contract generation progress indicators. Deduct 5 points for each operation without proper feedback, 3 points for laggy product browsing experience, and 5 points if critical action buttons (like 'Generate Contract') are hard to locate or unclear. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "medium"
-}