@getollie/cli 0.0.1

package/library/management_systems-frontend_backend_platforms/inventory-management-system-with-alerts.json

@@ -0,0 +1,68 @@
+{
+  "index": 619,
+  "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. Please build an inventory management system. Merchants can add new products through the front-end interface, edit product information (name, price, inventory quantity, etc.), and set low inventory alert functions (displaying warnings when inventory falls below a threshold).",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the product CRUD functionality fully implemented?",
+      "description": "Review whether the code accurately implements all Create, Read, Update, and Delete operations for products. Check if the form validation includes required fields (name, price, quantity), data type validation (price as number), and constraint checks (non-negative values for price and quantity). Score 0 if core CRUD operations are missing, 5 if basic operations are implemented without proper validation, and 10 if all operations are implemented with comprehensive validation.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the inventory alert system properly implemented?",
+      "description": "Evaluate whether merchants can set custom threshold values for low inventory alerts. Check if the system provides visual indicators (color coding, icons) when inventory falls below thresholds, and if notifications are displayed in an appropriate manner (not blocking normal operation). Deduct 5 points if threshold configuration is missing, 3 points if visual indicators aren't clear, and 2 points if there's no way to manage/dismiss alerts. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the data persistence mechanism properly designed?",
+      "description": "Check whether the application implements proper data storage (local storage, IndexedDB, or backend database) with error handling for storage failures. Verify if data synchronization occurs at appropriate times (after edits, periodically) and if there's data loss protection when the browser unexpectedly closes. Deduct 5 points for lack of persistence, 3 points for insufficient error handling, and 2 points for missing optimization strategies (like batch updates). The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the inventory history and tracking system implemented?",
+      "description": "Verify if the system tracks inventory changes with timestamps and user information. Check for features like inventory audit trails, change history visualization, and inventory trend analysis. The system should allow filtering/sorting of history records. Deduct 3 points if timestamp tracking is missing, 3 points if there's no way to view history, and 4 points if the history doesn't capture all relevant events (additions, edits, threshold changes). The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid inputs, network failures, concurrent edits, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should prevent data corruption and have proper exception handling throughout the application. Give 10 points for comprehensive error handling, 5 points for basic validation only, and 0 points if errors cause the application to crash.",
+      "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 for quick product lookup 2. Export/import functionality for bulk operations 3. Dashboard with inventory analytics 4. Image management for products). 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 edit the same data) 2. Function modules unrelated to inventory management (e.g., built-in games or media players) 3. Fancy effects that affect performance (e.g., excessive animations or 3D 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 data models/UI components/services), code organization, naming conventions, and reusability. Deduct 5 points if global state management is poorly implemented; deduct 3 points if there's significant code duplication; deduct 2 points if naming conventions are inconsistent or unclear. Check for appropriate comments and documentation. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the UI follows modern inventory management design principles: 1) Clean data display with proper table/grid layouts 2) Consistent color coding for inventory status (low/normal/excess) 3) Professional forms with clear labels and validation feedback. Deduct 3 points for cluttered information display, 4 points for poor information hierarchy, and 3 points for inconsistent styling across the application. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the interactions serve business efficiency: 1) Quick-edit capabilities without excessive page reloads 2) Bulk operations for managing multiple products 3) Responsive filtering and searching with < 200ms response time. Deduct 4 points for requiring multiple clicks for common tasks, 3 points for sluggish responses in data operations, and 3 points for lack of keyboard shortcuts or efficiency features. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "easy"
+}

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

@@ -0,0 +1,68 @@
+{
+  "index": 480,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be mindful to ensure the generated code is executable for demonstration. Develop an inventory management system where users can add, edit and delete inventory items, track inventory quantities, set minimum inventory warning thresholds, generate inventory reports, and support barcode scanning functionality.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the inventory item CRUD system fully implemented?",
+      "description": "Review whether the code accurately implements complete inventory item management through proper data structures and UI components, including add/edit/delete operations with field validation (item name, SKU, category, price, quantity, etc.). Score 0 if core CRUD operations are not implemented, 5 if only basic add/delete is implemented, and 10 if all operations include proper validation, duplicate prevention, and batch operations.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the inventory quantity tracking and threshold warning system implemented?",
+      "description": "Check whether the system includes real-time inventory quantity tracking with automatic updates, configurable minimum stock thresholds, and proactive warning mechanisms (visual alerts, notifications, email triggers). Deduct 5 points if quantity updates are not real-time, and 3 points if warning thresholds cannot be customized per item. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the inventory reporting and analytics functionality designed comprehensively?",
+      "description": "Evaluate whether the system generates comprehensive inventory reports including stock levels, movement history, low-stock alerts, and value calculations. Reports should support multiple formats (PDF, Excel, CSV) and date range filtering. Deduct 5 points if reports lack visual charts/graphs, and 3 points if export functionality is missing. Check whether historical data tracking and trend analysis are implemented. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the barcode scanning functionality integrated effectively?",
+      "description": "Check whether the code includes barcode scanning capabilities using camera API or external scanner integration, with proper barcode format recognition (UPC, EAN, Code128, etc.). Evaluate scanner UI responsiveness, error handling for unrecognized codes, and seamless integration with inventory lookup/addition workflows. Deduct 5 points if camera permission handling is missing, and 3 points if multiple barcode formats are not supported. Give 10 points if fully implemented with offline scanning capability.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid input data, network failures, database connection issues, concurrent access conflicts, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should include input sanitization, transaction rollback, and graceful degradation, 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 demand forecasting 2. Mobile app with offline sync 3. Integration with suppliers for automatic reordering 4. Multi-location inventory tracking 5. Photo recognition for item identification). 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 validation logics for the same field) 2. Function modules unrelated to inventory management (e.g., built-in games or social features) 3. Overly complex animations that affect performance (e.g., excessive transitions on data tables). Deduct 3 points for each redundancy found, and directly deduct 10 points if core inventory 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 layer/business logic/presentation layers), proper error handling, database optimization, and security measures. Deduct 5 points if SQL injection vulnerabilities exist or input validation is missing; deduct 5 points if the code lacks proper separation of concerns; deduct 5 points if database queries are not optimized for large datasets. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching with proper contrast ratios for accessibility 2) Consistent layout spacing using grid systems 3) Professional typography with readable font sizes (≥14px for body text) 4) Intuitive navigation and information hierarchy. Deduct 3 points for each cluttered interface section, 5 points for poor color accessibility, and 5 points for inconsistent design patterns. 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 user experience: 1) Form submissions provide immediate feedback 2) Data table sorting/filtering responds within 200ms 3) Loading states are clearly indicated 4) Barcode scanning provides real-time visual feedback. Deduct 5 points for each operation without proper feedback, 3 points for slow data table performance with large datasets, and 5 points for confusing navigation or unclear action buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "medium"
+}

package/library/management_systems-frontend_backend_platforms/investment-project-economic-evaluation-system.json

@@ -0,0 +1,68 @@
+{
+  "index": 1444,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code for demonstration whenever possible. Help me create an investment project economic evaluation system.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core financial calculation system properly implemented?",
+      "description": "Check whether the code accurately implements essential financial metrics (NPV, IRR, ROI, payback period, etc.) with correct mathematical formulas. Score 0 if core financial calculations are missing, 5 if basic calculations exist but contain formula errors, and 10 if all calculations are accurate with proper edge case handling (e.g., negative cash flows, irregular periods).",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the investment project data modeling comprehensive?",
+      "description": "Evaluate if the code includes a complete data model for investment projects with appropriate entities (project details, cash flow projections, financing sources, risk factors, etc.). Deduct 3 points if key financial parameters are missing, 3 points if there's no provision for different investment types, and 4 points if time-value adjustments (inflation, discounting) aren't supported. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are sensitivity and risk analysis functions implemented?",
+      "description": "Check whether the system can perform sensitivity analysis on key parameters and quantify risk factors (e.g., Monte Carlo simulation, scenario analysis). Deduct 5 points if sensitivity analysis is missing, 3 points if risk quantification methods are absent, and 2 points if there's no visualization of risk distribution. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the comparative analysis system functional?",
+      "description": "Assess whether the code enables direct comparison between multiple investment options, including ranking mechanisms, standardized metrics, and weighted multi-criteria decision support. Deduct 4 points if no direct comparison visualization exists, 3 points if the comparison lacks normalization for different project scales, and 3 points if there's no support for custom evaluation criteria. 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, calculation errors, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should include input validation, error handling for financial edge cases (like division by zero in calculations), and data integrity checks. Give 10 points for comprehensive error handling, 5 points for partial implementation, and 0 points if exceptions are unhandled.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Real-time market data integration 2. AI-powered investment recommendations 3. Automated report generation with executive summaries 4. Industry benchmarking). 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 calculations (e.g., multiple NPV calculation methods) 2. Function modules unrelated to investment evaluation (e.g., accounting features that should be in a separate system) 3. Overly complex visualizations that obscure financial insights. 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 calculation logic/view/data layers), unit test coverage especially for financial calculations, 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 financial software standards?",
+      "description": "Evaluate whether the design follows professional financial software principles: 1) Clean, business-appropriate color scheme (preferably with white background and accent colors for highlighting) 2) Well-organized data tables and charts with proper spacing 3) Clear visual hierarchy for financial metrics (primary KPIs emphasized). Deduct 3 points for cluttered financial dashboards, 5 points for poor data visualization choices, and 5 points for inconsistent financial terminology. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the data visualization effective and insightful?",
+      "description": "Judge whether the financial visualizations follow best practices: 1) Appropriate chart types for different financial metrics (e.g., cash flow waterfall charts, IRR comparison bar charts) 2) Interactive elements allowing drill-down into calculation details 3) Clear labeling of financial data with proper units and time periods. Deduct 5 points for misleading visualizations, 3 points for poor choice of chart types, and 5 points for missing critical financial context in charts. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "hard"
+}

package/library/management_systems-frontend_backend_platforms/investment-system-with-realtime-market-data.json

@@ -0,0 +1,68 @@
+{
+  "index": 457,
+  "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. I am committed to making investment my lifelong hobby and second career. I want to build a stable and profitable investment system that includes stock selection, buy/sell point identification, and position management functions. I need to integrate these features into a frontend software. This software should be able to automatically and independently obtain real-time information about stocks and other markets from public free sources. I have Visual Studio Code software. Please help me generate standalone software that can meet all my requirements above.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the stock selection system fully implemented?",
+      "description": "Review whether the code implements comprehensive stock selection criteria including technical indicators (e.g., RSI, MACD, Moving Averages), fundamental analysis (P/E ratio, EPS growth, etc.), and market sentiment analysis. Check if the system allows for customizable screening parameters and saving favorite screening configurations. Score 0 if no selection system is implemented, 5 if only basic technical indicators are available, and 10 if it includes a comprehensive multi-factor model with backtesting capabilities.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are the buy/sell signal identification algorithms implemented effectively?",
+      "description": "Evaluate whether the code includes multiple technical analysis algorithms for identifying entry/exit points (candlestick patterns, support/resistance levels, volume analysis). Check if it provides visual indicators on charts for identified signals and includes confidence levels for each signal. The system should allow for customizable signal parameters. Deduct 5 points if signals are based solely on single indicators without confirmation strategies, and 3 points if historical accuracy metrics for signals are not provided. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the position management functionality comprehensive?",
+      "description": "Assess whether the code implements portfolio management features including position sizing calculations, risk management rules (stop-loss, take-profit settings), diversification analysis, and overall portfolio performance metrics. Check if it includes scenario analysis for different market conditions. Deduct 5 points if position sizing is simplistic (e.g., fixed percentages only), and 3 points if there's no correlation analysis between holdings. Give 10 points if fully implemented with dynamic risk adjustment capabilities.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the real-time data acquisition system robust and compliant?",
+      "description": "Evaluate if the code effectively obtains market data from free public APIs (like Yahoo Finance, Alpha Vantage) with proper rate limiting, fallback mechanisms, and cache strategies. Check for data validation and error handling for API failures. System must respect API terms of service and include proper attribution. Deduct 5 points for hardcoded API keys, 5 points for missing retry logic, and 5 points for no data freshness indicators. 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 API failures, network interruption, invalid user inputs, 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-based sentiment analysis from news sources 2. Auto-correlation with major economic indicators 3. Pattern recognition from historical market crashes 4. Visualized risk exposure heat maps). 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 indicators (e.g., multiple versions of RSI calculations) 2. Function modules unrelated to investment analysis (e.g., a built-in social media client) 3. Fancy visualizations that sacrifice performance (e.g., 3D charts that obscure data). 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 acquisition/analysis/visualization layers), unit test coverage for calculation accuracy, 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 financial dashboard standards?",
+      "description": "Evaluate whether the design follows professional financial interface principles: 1) Color schemes appropriate for financial data (red/green contrasts for gains/losses, muted backgrounds) 2) Information density optimized for scanning large datasets 3) Professional typography for numerical data (monospaced fonts for alignment, appropriate decimal precision). Deduct 3 points for cluttered dashboards, 5 points for indistinguishable data series in charts, and 5 points for poor information hierarchy. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and responsive for investment decision-making?",
+      "description": "Judge whether the interface facilitates rapid investment decisions: 1) Chart interactions respond in under 100ms 2) Data refresh rates are configurable based on market volatility 3) Critical alerts have distinct visual and optional audio cues. Deduct 5 points for charts that lag during period changes, 3 points for confusing tooltip behaviors, and 5 points for hard-to-access critical functions during market hours. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "hard"
+}

package/library/management_systems-frontend_backend_platforms/iot-platform-web-frontend-vue3-backend-microservice.json

@@ -0,0 +1,68 @@
+{
+  "index": 794,
+  "question": "You are a code expert, please use your professional knowledge to generate accurate, professional responses. Pay attention to ensure that the generated code is executable for display. IoT Platform Web Frontend | Vue3 + Element Plus + ECharts (Data Visualization) | Backend Microservice API Layer | Spring Boot + Spring Cloud (API Gateway, Access Control)",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Vue3 component architecture properly implemented?",
+      "description": "Examine whether the code follows Vue3 best practices: Composition API usage, reactive state management, lifecycle hooks integration, and proper component composition. Check for single-responsibility components and proper prop validation. Deduct 5 points if useSetup() is missing where beneficial; deduct 5 points if reactive() and ref() are misused; deduct 3 points if component hierarchy is unnecessarily deep (>4 levels). Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is Element Plus UI framework implementation optimal?",
+      "description": "Evaluate whether Element Plus components are properly utilized: lazy loading of components, on-demand importing, theme customization, responsive layouts, and proper form validation. Check if UI components match the application's requirements without overengineering. Deduct 5 points for global imports that cause bundle bloat; deduct 3 points for inadequate form validation; deduct 5 points for inconsistent component styling. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are ECharts data visualizations effectively implemented?",
+      "description": "Assess whether ECharts visualizations are properly configured: responsive resizing, appropriate chart types for data representation, performance optimization for large datasets, and interactive features. Charts should provide meaningful insights into IoT data. Deduct 5 points if charts are not resizable; deduct 5 points for inappropriate chart types; deduct 3 points for missing tooltips or legends; deduct 5 points if real-time data updates aren't handled efficiently. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the API integration with Spring Boot backend properly implemented?",
+      "description": "Review the frontend-backend integration: proper API call patterns (Axios/Fetch), error handling, authentication token management, and response parsing. Check for RESTful practices and efficient data fetching strategies. Deduct 5 points for missing loading states; deduct 3 points for improper error handling; deduct 5 points for inefficient data fetching (no pagination/caching); deduct 5 points if authentication headers aren't properly managed. 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 failures, invalid API responses, data validation errors, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should gracefully handle edge cases like offline operation modes for IoT platforms. Give 10 points for comprehensive error handling, 5 points for average implementation, and 0 points if no exceptions are 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 IoT platform experience (e.g., 1. Predictive analytics visualization 2. Custom dashboard builder 3. Device digital twins with 3D visualization 4. Real-time collaborative monitoring). 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 HTTP client wrappers) 2. Function modules unrelated to IoT monitoring (e.g., unnecessary animations) 3. Performance-heavy features that affect responsiveness (e.g., excessive real-time polling without throttling). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (separation of concerns between data, presentation, and business logic), Pinia/Vuex state management patterns, unit test coverage with Vitest/Jest, and build process automation. Deduct 5 points if global state is overused; deduct 5 points if code duplication rate exceeds 30%; deduct 5 points if there's no CI/CD configuration. 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) Consistent color scheme aligned with IoT platform purpose 2) Proper layout spacing (following the 8px grid system) 3) Professional typography system (readable metrics and data fonts). Deduct 3 points for cluttered dashboards, 5 points for color schemes that hinder data interpretation, and 5 points for poor information hierarchy. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the dynamic effects conform to user experience standards: 1) Real-time IoT data updates without UI freezing 2) Transition animations for state changes under 300ms 3) Clear visual feedback for user actions. Deduct 5 points for laggy dashboard updates, 3 points for jarring transitions between views, and 5 points for confusing navigation paths. Check for skeleton screens during loading and optimistic UI updates. Full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "medium"
+}

package/library/management_systems-frontend_backend_platforms/java-picture-book-library-borrowing-system.json

@@ -0,0 +1,68 @@
+{
+  "index": 227,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you provide is executable for demonstration. Create a Java-based picture book library borrowing system code, send me the complete source code that is not duplicated from online sources. Include web pages and layout elements. The quality should be at the graduation project level. The development tool is Eclipse.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Java-based core borrowing system fully implemented?",
+      "description": "Review whether the code accurately implements essential functionalities: user management, book catalog, borrowing/returning process, and reservation system. Score 0 if the core functions are missing, 5 if only basic CRUD operations are implemented, and 10 if it includes advanced features like fine calculation, borrowing history tracking, and book status management.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the database design and interaction properly implemented?",
+      "description": "Evaluate the database schema design (appropriate tables for users, books, transactions), proper implementation of DAO/Repository pattern, and transaction management. Check for proper SQL query optimization and connection pooling. Deduct 5 points for missing transaction handling, 3 points for SQL injection vulnerabilities, and 2 points for inefficient query design. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the web interface implementation complete?",
+      "description": "Check if the web pages include all necessary views: login/registration page, book catalog display, book detail page, user profile, borrowing history, and administrative interfaces. Evaluate the use of appropriate Java web technologies (JSP, Servlet, JSF, or Spring MVC). Deduct 5 points if core pages are missing, 3 points if form validation is inadequate. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the picture book presentation functionality implemented?",
+      "description": "Assess if the system properly handles picture books with image displays, thumbnails generation, and preview capabilities. Check for image loading optimization and responsive display across devices. Score 10 for full implementation with lazy loading and image caching, 5 for basic image display without optimization, and 0 if images aren't properly handled or displayed.",
+      "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, file handling 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. Book recommendation system based on borrowing history 2. QR code generation for quick borrowing 3. Email/SMS notification system). 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 authentication mechanisms) 2. Function modules unrelated to library management (e.g., built-in games) 3. Resource-intensive features that affect performance (e.g., unnecessarily complex 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 MVC architecture, separation of concerns), unit test coverage, and build process configuration (Maven/Gradle). 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 dependency management and build scripts are missing or incomplete. 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 consistent principles) 3) Professional font system (appropriate sizing and hierarchy). 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) Form submission feedback delay ≤ 100ms 2) Page transition and loading indicators 3) Clear visual focus guidance. Deduct 5 points for each operation without feedback, 3 points for jarring page reloads, 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/javafx-real-time-table-update-voice-announcements.json

@@ -0,0 +1,68 @@
+{
+  "index": 364,
+  "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. In JavaFX, when one client adds data to a table, other client pages should update in real-time to display the added data and provide voice announcements.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the JavaFX TableView implementation complete?",
+      "description": "Review whether the code properly implements the TableView with appropriate columns, data binding, and cell factories. Check if the table supports proper data sorting, filtering, and pagination. Score 0 if the TableView is not implemented, 5 if basic implementation without customization, and 10 if fully featured with proper styling and user interaction handling.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the real-time data synchronization mechanism implemented?",
+      "description": "Evaluate whether the code includes a robust real-time communication system (WebSockets, RMI, or similar technology). Check if it handles connection establishment, message serialization/deserialization, and reconnection logic. The implementation should include proper event listeners for data changes. Deduct 5 points if synchronization has noticeable delay (>500ms), and 3 points if the connection management is incomplete. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the voice announcement system properly implemented?",
+      "description": "Check whether the code includes a functional text-to-speech system that announces new data entries. Evaluate if the implementation uses appropriate JavaFX sound libraries or external TTS engines. Voice announcements should be clear, configurable (volume/speed/voice), and not interfere with the application's performance. Deduct 5 points if voice quality is poor, and 3 points if configuration options are missing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the client-server architecture properly designed?",
+      "description": "Review the architecture design to ensure proper separation between client and server components. Check if the server handles concurrent client connections, maintains consistent data state across clients, and implements proper authentication/authorization. Evaluate if the application uses appropriate design patterns (MVC, observer pattern). Deduct 5 points for poor concurrency handling, and 3 points for inadequate error handling during communication. 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 disconnection, server unavailability, concurrent data modification 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. Customizable notification sounds/voices 2. Visual indicators for newly added data 3. Client-specific filters that persist across updates). 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 communication methods (e.g., multiple notification systems running in parallel) 2. Function modules unrelated to the core requirements (e.g., excessive animation effects) 3. Resource-intensive features that affect performance (e.g., constant polling instead of event-based updates). 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/network layers), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern JavaFX design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows consistent principles) 3) Professional font system (readable font sizes, appropriate line heights). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic 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) Data updates appear without noticeable delay 2) Voice announcements are synchronized with visual updates 3) The UI remains responsive during updates and voice playback. Deduct 5 points for laggy updates, 3 points for voice announcements that disrupt the user experience, and 5 points for UI freezing during data operations. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "hard"
+}

package/library/management_systems-frontend_backend_platforms/knowledge-base-management-system.json

@@ -0,0 +1,68 @@
+{
+  "index": 628,
+  "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. Develop a knowledge base management system where users can upload knowledge article files (supporting md, html formats) and add categories and tags to articles; knowledge base administrators (username: knowledgemgr, password: knowpass) can log into the system, manage knowledge articles, organize them by category or tag, and set access permissions for articles.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the basic knowledge base architecture properly implemented?",
+      "description": "Review whether the code establishes a complete knowledge base system with proper model structure for articles, categories, tags, and users. Check if the data models include necessary fields (title, content, author, timestamps, format type) and relationships. Score 0 if core data models are missing, 5 if basic models exist but lack key relationships, and 10 if a complete data architecture with proper relationships is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the file upload functionality fully implemented?",
+      "description": "Evaluate whether the system handles md and html file uploads correctly with proper validation, sanitization, and storage. Check if the code includes content type verification, file size limitations, and security measures against malicious uploads. Deduct 3 points if format validation is missing, 3 points if no security measures against XSS attacks are implemented, and 4 points if the upload process lacks error handling. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are the category and tag management systems functioning correctly?",
+      "description": "Check whether the code enables adding, editing, and deleting categories and tags, as well as assigning them to articles. The system should support hierarchical categories, batch operations, and article filtering by categories/tags. Deduct 3 points if hierarchical categories are not supported, 3 points if batch operations are missing, and 4 points if filtering functionality is incomplete. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the authentication and permission system properly implemented?",
+      "description": "Review whether the code implements secure login functionality for administrators (username: knowledgemgr, password: knowpass), proper session management, and granular access control for articles. Check for password hashing, CSRF protection, and role-based permissions. Deduct 5 points if password security is weak, 3 points if session management is flawed, and 2 points if the permission system doesn't support article-level access control. 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 uploads, authentication failures, concurrent access issues, 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. Full-text search with highlighting 2. Article version history tracking 3. Collaborative editing 4. AI-powered article recommendations). 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 management systems) 2. Function modules unrelated to knowledge base management (e.g., social networking features) 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/service/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": "hard"
+}