@getollie/cli 0.0.4 → 0.2.0

package/library/management_systems-frontend_backend_platforms/software-development-documentation-management-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 659,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code whenever possible. Please write code to implement a software development documentation management system where developers can upload and manage API documentation, technical specifications, system design documents, etc. The system should support online Markdown editing, automatic generation of API interface documentation, and provide version management and change history tracking. Administrators should be able to assign project access permissions and manage team members.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Markdown editing system fully implemented?",
-      "description": "Examine whether the code provides a complete Markdown editor with real-time preview, syntax highlighting, keyboard shortcuts, and image embedding. Check if the editor includes specialized technical documentation features like code block syntax highlighting, table formatting, and mathematical formula support. Score 0 if basic editor functions are missing, 5 if only basic Markdown is supported, and 10 if it includes advanced technical documentation features.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the API documentation auto-generation feature properly implemented?",
-      "description": "Verify if the system can parse code from common languages (Java, JavaScript, Python, etc.) to extract API definitions, parameters, and return types. Check whether it generates standardized documentation formats (OpenAPI/Swagger, JSDoc, etc.). Deduct 5 points if only one language is supported, 3 points if the generated documentation lacks examples, and 2 points if schema validation is missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Does the version control system meet professional requirements?",
-      "description": "Assess if the version management includes document branching, conflict resolution, difference comparison visualization, and automatic merge suggestions. Check if it supports reverting to previous versions and maintains a complete audit trail. Deduct 5 points if branching is not supported, 3 points if visual diff is missing, and 3 points if there's no conflict resolution mechanism. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the permission and access control system comprehensive?",
-      "description": "Evaluate whether the system implements role-based access control (RBAC) with granular permissions at project, document, and section levels. Check if it includes approval workflows, temporary access grants, and audit logging of permission changes. Deduct 5 points if only basic role assignments exist, 3 points if permission inheritance is not implemented, and 3 points if there's no audit trail for access 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 concurrent editing conflicts, network interruption during document saving, invalid Markdown syntax, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. AI-assisted documentation generation 2. Interactive API testing within documentation 3. Automatic code sample generation 4. Knowledge graph of document relationships). 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 implementations of similar functions (e.g., multiple document parsers doing the same thing) 2. Function modules unrelated to documentation management (e.g., a built-in chat system) 3. Fancy effects that affect performance (e.g., excessive animations in the documentation UI). 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 editor/storage/permission 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) Editor response delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual feedback for saving/publishing operations. Deduct 5 points for each operation without feedback, 3 points for sluggish editing experience with large documents, and 5 points for confusing navigation between document sections. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "hard"
-}

package/library/management_systems-frontend_backend_platforms/sports-venue-management-platform.json

@@ -1,68 +0,0 @@
-{
-  "index": 819,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable when possible.\n\n1. **Data Dashboard** (Blue Theme)\n   - User Data: Member growth trends/activity analysis\n   - Revenue Data: Income flow/profit sharing ratio settings\n   - Market Analysis: Monitoring of competitors' activities\n\n2. **Member Management** (Purple Theme)\n   - Complete User List: Supports batch operations (tag grouping/status filtering)\n   - Star Players: Set users as venue ambassadors (displayed in user interface)\n   - Blacklist: Management of rule-violating users\n\n3. **Activity Operations** (Orange Theme)\n   - Activity Publishing: Create matches/training/ticket sales events (automatically synced to user interface)\n   - Activity Calendar: Timeline view of published activities\n   - Feedback Collection: Management of user evaluations after events\n\n4. **Venue Management** (Green Theme)\n   - Real-time Monitoring: Occupancy rate heat map\n   - Equipment Configuration: Hawkeye system/lighting control integration\n   - Dynamic Codes: Generate time-limited venue reservation links\n\n5. **Team Management** (Red Theme)\n   - Coach Profiles: Qualification certification/course scheduling\n   - Authorization System: Set permission levels for coach accounts\n   - Training Schedule: Student registration and progress tracking\n\nRegarding the above categories, the five major modules are a bit too many, so they need to be consolidated.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the consolidated dashboard architecture properly implemented?",
-      "description": "Evaluate whether the code effectively consolidates the five modules into a coherent dashboard system with logical navigation. Check for hierarchical organization, responsive layout, and efficient state management across modules. Score 0 if modules remain completely separate, 5 if basic consolidation exists but with navigation issues, and 10 if modules are seamlessly integrated with consistent theming and cross-module data sharing.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the data visualization components professionally implemented?",
-      "description": "Review the implementation of charts and graphs for the Data Dashboard. Check for proper use of D3.js/Chart.js/ECharts libraries, responsive resizing, interactive tooltips, and appropriate visualization types for different data (line charts for trends, pie charts for ratios, etc.). Assess whether visualizations include proper axes, legends, and animations. Score 0 if visualizations are static images, 5 if basic charts exist without interactivity, and 10 if fully interactive, responsively designed visualizations with appropriate data loading states are implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the management functionality for users/venues/activities comprehensively implemented?",
-      "description": "Examine the CRUD operations across management modules. Check for filtering capabilities, batch operations, data validation, and proper state updates. Verify implementation of specialized features like tagging users, blacklisting, heat map visualization for venue occupancy, and activity timeline views. Deduct 3 points if basic CRUD is missing, 3 points if filtering/sorting is absent, and 4 points if specialized module features (like venue heat maps or activity calendars) are not implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the theming system properly implemented with consistent color schemes?",
-      "description": "Evaluate the theming implementation for the specified color schemes (Blue/Purple/Orange/Green/Red). Check for CSS variables or theming system (like styled-components or Material UI theming), proper contrast ratios for accessibility, and consistent application across components. Assess whether theme switching is smoothly implemented when navigating between modules. Deduct 3 points for inconsistent theme application, 3 points for poor contrast/accessibility issues, and 4 points if theme integration across consolidated modules is broken. 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 empty data states, network errors, user input validation, permission handling) and provide friendly error prompts or recovery mechanisms. Check for proper loading states, error boundaries, form validation, and defensive coding practices. 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-driven analytics for predicting member trends 2. Natural language generation for automated activity reports 3. Interactive drag-and-drop schedule builder 4. Real-time collaboration features for team management). 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 features across modules (e.g., multiple user selection mechanisms) 2. Function modules unrelated to the specified requirements (e.g., unnecessary social networking features) 3. Fancy effects that affect performance (e.g., excessive animations or 3D elements). 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/UI/logic layers), state management approach, component reusability, and build process. Check for proper use of design patterns, code organization, and performance optimizations like memoization or virtualized lists for large datasets. Deduct 5 points if global state pollution is found; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if no performance optimizations are implemented for data-heavy views. 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 within each theme module with proper color contrast 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) 4) Consistent component styling across modules. Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic dashboard 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 animations for module switching controlled between 300-500ms 3) Clear visual focus guidance for important dashboard metrics and alerts. Check for skeleton screens during data loading, smooth transitions between views, and intuitive navigation between the consolidated modules. Deduct 5 points for each operation without feedback, 3 points for jarring transitions between modules, 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/srm-supplier-admission-kanban-stage-tool.json

@@ -1,68 +0,0 @@
-{
-  "index": 719,
-  "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. Please create an interface for the supplier admission center in an SRM system, which includes a stage progression tool for each phase and a kanban board displaying the task lists for pending items at each stage.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the supplier admission center interface fully implemented?",
-      "description": "Evaluate whether the code implements all required components: a central dashboard view, stage progression tool showing different phases (e.g., initial contact, qualification, documentation, evaluation, approval), and a kanban board displaying task lists for each stage. Score 0 if main components are missing, 5 if only basic layout is present, and 10 if all components are properly implemented with clear visual hierarchy and information architecture.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the stage progression tool correctly implemented?",
-      "description": "Check if the stage progression tool visually represents the supplier onboarding pipeline with clear status indicators for each stage. It should include: 1) Visual indication of current stage, 2) Completed stages, 3) Upcoming stages, 4) Stage transitions with appropriate animations, and 5) Stage-specific metadata (time in stage, completion percentage). Deduct 2 points for each missing element. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the kanban board functionality properly implemented?",
-      "description": "Assess whether the kanban board correctly displays task cards organized by stages, with drag-and-drop functionality between columns, task filtering capabilities, and status updates reflected in real-time. Check that each task card contains essential information (task name, assignee, due date, priority). Deduct 3 points if drag-and-drop is not implemented, 2 points if filtering is missing, and 2 points if cards lack essential information. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are the data structures and state management appropriate for an SRM system?",
-      "description": "Review whether the code uses appropriate data structures for supplier information, stage definitions, and task management. Check if state management handles complex relationships between suppliers, approval stages, and associated tasks. Evaluate whether the code handles data mutations properly with proper validation. Deduct 3 points for inappropriate data modeling, 4 points for inefficient state management, and 3 points for missing validation. 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 empty data states, network errors, user operation 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. Real-time collaboration indicators 2. Automated task progression based on conditions 3. Interactive supplier performance metrics 4. Intelligent stage duration predictions). 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 state management approaches coexisting) 2. Function modules unrelated to supplier management (e.g., built-in general chat system) 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 business logic/view/data layers), component reusability, code organization, 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) 4) Consistent use of enterprise UI components. Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance for supplier progression workflow 4) Intuitive drag-and-drop interactions for kanban tasks. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast sliding, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "medium"
-}

package/library/management_systems-frontend_backend_platforms/student-classroom-completion-status-record-webpage.json

@@ -1,68 +0,0 @@
-{
-  "index": 873,
-  "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. Help me create a webpage that records student classroom completion status.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core student record functionality fully implemented?",
-      "description": "Review whether the code accurately implements a student record system with features for adding, editing, and deleting student completion records. Check if it includes student identification, completion status tracking, and timestamp recording. Score 0 if the core functionality is missing, 5 if only basic recording is implemented, and 10 if comprehensive tracking with detailed status indicators is included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is data persistence implemented?",
-      "description": "Evaluate whether the application implements proper data storage (localStorage, IndexedDB, or server-side storage). Check if data survives page refreshes and browser restarts. Deduct 5 points if only temporary memory storage is used, 3 points if persistence exists but without error handling for storage failures. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the data visualization and reporting feature implemented?",
-      "description": "Assess whether the code includes visualization of completion data (charts, progress bars, or summary statistics). Check for filtering options, sorting capabilities, and exportable reports. Deduct 5 points if only raw data is displayed without visualization, 3 points if visualization exists but lacks interactivity. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the classroom management system comprehensively designed?",
-      "description": "Check if the implementation includes class/course management, multiple classroom support, student grouping, and batch operations. Deduct 5 points if only single-class tracking is implemented, 3 points if classroom management exists but without organizational hierarchy. Give 10 points if the system supports complete classroom ecosystem management.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid input, database errors, concurrent edits, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should 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. Automatic attendance tracking 2. AI-powered insights on student performance 3. Real-time collaborative editing). 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 record the same information) 2. Function modules unrelated to classroom management (e.g., a built-in game) 3. Fancy effects that affect performance (e.g., unnecessary animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating data/UI/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 scrolling, 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/student-grade-recording-analysis-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 1099,
-  "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. Well, there are so many tools that it's overwhelming. I haven't used any of these tools before and don't know how to use them. Which tool would you recommend that's easy to learn? Please tell me the detailed steps to help me develop a student grade recording and analysis system.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is there a comprehensive implementation of a student grade recording system?",
-      "description": "Is there a comprehensive implementation of a student grade recording system?",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the grade analysis functionality properly implemented?",
-      "description": "Is the grade analysis functionality properly implemented?",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the user interface intuitive for educational staff with varying technical skills?",
-      "description": "Is the user interface intuitive for educational staff with varying technical skills?",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are the step-by-step instructions clear and complete for a beginner?",
-      "description": "Are the step-by-step instructions clear and complete for a beginner?",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Is the code robust?",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Are there any innovative features that are eye-catching?",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Are there any redundant features?",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Does the code have engineering quality?",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Does the interface vision meet professional design standards?",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Is the dynamic interaction smooth and seamless?",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "easy"
-}

package/library/management_systems-frontend_backend_platforms/student-info-query-frontend-website.json

@@ -1,68 +0,0 @@
-{
-  "index": 1282,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable for demonstration. I need a student information query frontend website (in Python) that displays class information by searching fields like class and name, supporting fuzzy queries. The database fields include name and class.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the basic student information query function fully implemented?",
-      "description": "Review whether the code properly implements the core query functionality with both name and class search fields. Check if the search logic handles both exact and fuzzy matching. Score 0 if search functionality is not implemented, 5 if only basic exact matching is implemented, and 10 if both fields support comprehensive fuzzy search with proper indexing and error handling.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the Python web framework implementation appropriate and well-configured?",
-      "description": "Evaluate the choice and implementation of the Python web framework (Flask, Django, etc.). Check for proper routing, request handling, and response formatting. Deduct 3 points if the framework is poorly configured, 3 points if routing is messy, and 4 points if there are security vulnerabilities in the request handling. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the database interaction properly implemented?",
-      "description": "Assess the database connection, query construction, and data retrieval logic. Check for proper parameterized queries to prevent SQL injection, efficient query design, and appropriate error handling. Deduct 3 points for non-parameterized queries, 3 points for inefficient queries that would scale poorly, and 4 points if connection pooling or resource management is absent. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the search functionality optimized for usability and performance?",
-      "description": "Examine the search implementation for features like result pagination, search highlighting, auto-suggestions, and quick filtering. Check if the search is optimized for performance with proper indexing strategies. Deduct 3 points if pagination is missing, 3 points if search performance is not optimized, and 4 points if the interface lacks user-friendly search features. 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 empty search results, malformed queries, database connection 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. Export search results to CSV/PDF 2. Data visualization components for class statistics 3. Responsive design that works well on mobile devices). 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 implementations) 2. Function modules unrelated to student information query (e.g., unnecessary social media integrations) 3. Fancy effects that affect performance (e.g., heavy animations that slow down search results). 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 database 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 dependency management is poor or configuration is hardcoded. 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) Search results appear within 500ms 2) Loading indicators for longer operations 3) Clear visual focus guidance for search fields and results. Deduct 5 points for searches without loading indicators, 3 points for jarring page refreshes instead of smooth updates, and 5 points for unintuitive navigation between search and results. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "easy"
-}

package/library/management_systems-frontend_backend_platforms/student-information-management-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 1412,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate, professional responses. Make sure the code you produce is executable for demonstration. Student Information Management System, requirements: student personal information, grade statistics and query, exam paper archiving, error analysis.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the student information management module fully implemented?",
-      "description": "Evaluate whether the code includes CRUD operations for student data (add, retrieve, update, delete). Check for proper data validation (e.g., format validation for email/phone, required fields checking). Review if student profiles include essential fields (name, ID, contact info, enrollment date, etc.). Score 0 if core functionality is missing, 5 if basic operations are implemented with minimal validation, 10 if comprehensive student management with robust validation is present.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the grade statistics and query system comprehensive?",
-      "description": "Check whether the system supports multiple query parameters (by student ID, name, course, score range, time period). Evaluate if statistical functions are implemented (average, median, standard deviation, percentile ranking, etc.). Review if the code includes data visualization components for grades (charts, graphs). Deduct 3 points if sorting/filtering options are limited, 5 points if statistical calculations are missing, and 3 points if visual representation is absent. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the exam paper archiving system properly designed?",
-      "description": "Review if the code implements secure storage for exam papers with proper versioning control. Check if the system supports various file formats (PDF, images, etc.) and includes metadata tagging (subject, exam date, difficulty level, topics covered). Evaluate search/retrieval functionality by various parameters. Deduct 5 points if versioning is missing, 3 points if file format support is limited, and 3 points if search capabilities are basic. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the error analysis functionality effectively implemented?",
-      "description": "Examine if the code provides tools for tracking common mistakes, identifying knowledge gaps, and generating improvement recommendations. Check for pattern recognition in errors and trend analysis over time. Review if the system correlates errors with specific topics/concepts. Deduct 5 points if only basic error logging exists without analysis, 3 points if trend tracking is missing, and 3 points if personalized recommendations are absent. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code handles common error scenarios (invalid input, database connection failures, file upload issues, concurrent access conflicts). Check for proper exception handling with meaningful error messages for users and detailed logging for administrators. Review if the system includes data backup/recovery mechanisms. Code with strong robustness should handle these edge cases effectively, giving 10 points. If robustness is average, give 5 points, and if exceptions are unhandled, 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 learning recommendations based on error patterns 2. Automatic grade report generation with customizable templates 3. Mobile-responsive design with notification systems 4. Integration with external learning management systems). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Duplicate implementation of similar functionality (e.g., multiple ways to calculate the same statistics) 2. Function modules unrelated to student/grade management (e.g., built-in games or entertainment features) 3. Overly complex animations or visual effects that slow down performance. 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 data models, services, controllers, views), code reusability, and maintainability. Check for proper comments/documentation, consistent naming conventions, and code organization. Evaluate database design principles (normalization, indexing, constraints). Deduct 5 points if global state is overused, 5 points if code duplication rate exceeds 30%, and 5 points if proper security measures (authentication, authorization, input sanitization) are missing. 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 design principles: 1) Consistent color scheme appropriate for an educational tool (no more than 3 primary colors) 2) Proper information hierarchy with clear visual separation between different functional areas 3) Appropriate typography for readability (headings vs. data display vs. input forms). Deduct 3 points for cluttered layouts, 5 points for poor color combinations affecting readability, and 5 points for inconsistent styling across different screens. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and intuitive?",
-      "description": "Judge whether the system provides appropriate feedback for user actions: 1) Form validation with clear error messages 2) Loading indicators for data processing operations 3) Confirmation dialogs for critical actions (deletions, grade changes) 4) Intuitive navigation between different system modules. Deduct 5 points for operations without feedback, 3 points for confusing navigation paths, and 5 points for unintuitive data entry workflows or hard-to-locate key functions. Full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-Frontend/Backend Platforms",
-  "difficulty": "hard"
-}

package/library/management_systems-frontend_backend_platforms/student-roll-call-software.json

@@ -1,68 +0,0 @@
-{
-  "index": 870,
-  "question": "You are a coding expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code when possible. How do I create a student roll call software?",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core roll call functionality fully implemented?",
-      "description": "Review whether the code implements the essential features for student attendance tracking: student data management (add/edit/delete), attendance status recording (present/absent/late), and date/time tracking. Score 0 if the core functionality is missing, 5 if basic attendance recording is implemented, and 10 if features include batch operations and attendance statistics.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is there a proper student data management system?",
-      "description": "Check whether the software includes comprehensive student data management capabilities: importing/exporting student lists, search/filter functions, and data validation. Deduct 5 points if there's no data persistence mechanism, 3 points if student information is limited to basic fields only (missing photo/ID/contact details), and 3 points if there's no bulk import option from CSV/Excel. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Does the software have reporting and analytics capabilities?",
-      "description": "Evaluate whether the code includes attendance statistics and reporting: individual student attendance rates, class-wide analytics, and exportable reports (PDF/Excel). Deduct 5 points if there are no visual charts for attendance trends, 3 points if detailed filtering options are missing, and 5 points if there's no export functionality. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are there multiple attendance verification methods?",
-      "description": "Check whether the software implements various attendance verification methods: manual roll call, barcode/QR code scanning, facial recognition, or automated verification. Deduct 3 points for each missing verification method beyond basic manual entry. Give 10 points if at least three methods are implemented with seamless switching between them.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as duplicate entries, network issues when saving data, invalid student IDs, etc.) and provide friendly error messages 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. Automated notifications for absent students/parents 2. Integration with calendar for scheduling 3. Voice command support for faster roll calls). 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 add students that cause confusion) 2. Function modules unrelated to attendance tracking (e.g., a built-in game) 3. Fancy effects that affect performance (e.g., unnecessary animations that slow down the roll call process). 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/business logic layers), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Roll call operation completes within 1-2 seconds 2) Search/filter results update in real-time 3) Clear visual feedback for attendance status changes. Deduct 5 points for each operation without feedback, 3 points for laggy interface when handling large class sizes, 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"
-}