@getollie/cli 0.0.5 → 0.2.0

package/library/web_applications-communication/chaoshan-culture-calendar-forum-app.json

@@ -1,68 +0,0 @@
-{
-  "index": 1539,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable and ready for demonstration. I want to create a software about Chaoshan, including calendars with important dates for different regions, customs and traditions, and forum-like features (similar to WeChat Moments).",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the calendar system with regional important dates fully implemented?",
-      "description": "Evaluate the calendar implementation to see if it properly displays important Chaoshan regional dates and events. Check whether it supports customization for different regions within Chaoshan (Chaozhou, Shantou, Jieyang), includes lunar calendar conversion for traditional festivals, and offers filtering/categorization of events. Score 0 if the calendar system is not implemented, 5 if basic calendar functionality exists but lacks regional specificity, and 10 if the implementation is comprehensive with region-specific important dates and proper cultural annotation.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "How well are the Chaoshan customs and traditions documented and presented?",
-      "description": "Assess the quality and comprehensiveness of the cultural content. Check if the code implements interactive displays of Chaoshan traditions (such as Kungfu Tea ceremony, Chaoshan cuisine, opera), includes multimedia elements (images, audio, video), and provides historical context. Evaluate whether the information architecture allows for easy navigation between related customs. Deduct 5 points if cultural documentation is sparse or inaccurate, 3 points if multimedia elements are missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the forum/WeChat Moments-like feature functional and culturally appropriate?",
-      "description": "Examine the social platform functionality, including post creation, commenting, image sharing, and user profiles. Check whether the UI adheres to familiar WeChat Moments patterns while incorporating Chaoshan cultural elements. Verify the implementation of privacy controls and content filtering. Score 0 if the forum feature is not implemented, 5 if basic posting functionality exists but lacks social interaction features, and 10 if the implementation includes robust interaction capabilities with cultural contextualization.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there proper integration between the calendar, cultural content, and social features?",
-      "description": "Evaluate how well the three main components are integrated. Check if calendar events can be shared to the forum, if cultural content can be referenced in posts, and if user-generated content can enhance cultural documentation. Assess if the navigation between sections is intuitive. Deduct 5 points if components operate in isolation with minimal cross-functionality, 3 points if the integration exists but is cumbersome to use. 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 disconnections, invalid user inputs, missing cultural data, calendar date conversion errors) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. AR visualization of Chaoshan customs 2. Dialect translation/pronunciation guide 3. Interactive cultural heritage map 4. AI-powered Chaoshan cultural assistant). 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 news feeds with overlapping content) 2. Function modules unrelated to Chaoshan culture (e.g., general social media features that don't connect to the cultural focus) 3. Fancy effects that affect performance (e.g., excessive animations when displaying calendar events). 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 cultural data/UI/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 design principles while incorporating Chaoshan aesthetic elements: 1) Harmonious color matching (traditional Chaoshan colors used appropriately) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system that supports both standard and any special Chaoshan characters. 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 when switching between calendar, cultural content, and forum sections. 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": "Web Applications-Communication",
-  "difficulty": "hard"
-}

package/library/web_applications-communication/collaborative-whiteboard-tool.json

@@ -1,68 +0,0 @@
-{
-  "index": 680,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable when possible. Implement a simple collaborative whiteboard tool where users can draw, add shapes and text on a canvas, and share content in real-time with other users for collaboration.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the canvas drawing functionality fully implemented?",
-      "description": "Review whether the code accurately implements the basic drawing functions (line, freehand, shapes, text) using HTML5 Canvas or SVG. Check if the tool includes brush size/color selection, eraser tool, and shape manipulation (resize, rotate, move). Score 0 if core drawing functionality is missing, 5 if only basic drawing is implemented, and 10 if it includes comprehensive drawing tools with customization options.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the real-time collaboration mechanism properly implemented?",
-      "description": "Evaluate the implementation of WebSocket or similar technology for real-time data synchronization between users. Check if the system broadcasts drawing events to all connected clients and manages concurrent edits appropriately. Deduct 5 points if there's no conflict resolution strategy, and 3 points if synchronization has noticeable lag (>200ms). The full score requires bidirectional communication with proper event serialization.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is there a proper user session and presence management system?",
-      "description": "Check if the code includes user identification, cursor/pointer tracking for different users, and visual indicators showing who is currently active/drawing. Evaluate whether the system handles user joins/leaves gracefully and maintains session state. Deduct 5 points if there's no visual differentiation between users' actions, and 3 points if the presence system lacks reconnection handling.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the whiteboard implement content persistence and history?",
-      "description": "Assess whether the whiteboard state can be saved (locally or server-side) and loaded later. Check if there's an undo/redo functionality with reasonable history depth. Verify if users can export their work as images or in a shareable format. Deduct 5 points if persistence is missing entirely and 3 points if history management is limited or buggy.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as network disconnections, browser compatibility issues, concurrent edits, large canvas operations, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. AI-assisted shape recognition 2. Collaborative presentation mode 3. Real-time audio/video chat integration 4. Smart object alignment). 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 drawing engines coexisting) 2. Function modules unrelated to whiteboard collaboration (e.g., a built-in file manager) 3. Fancy effects that affect performance (e.g., excessive animations or transitions). 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 drawing logic/UI/networking layers), component reusability, and code organization. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no clear separation between front-end and back-end concerns. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Clean toolbar organization with clear iconography. Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic tool placement that hinders usability. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the drawing experience feels natural and responsive: 1) Drawing latency ≤ 50ms 2) Smooth rendering without jitter during continuous drawing 3) Intuitive selection and manipulation of objects. Deduct 5 points for noticeable lag when drawing, 3 points for jerky animations during object manipulation, and 5 points for unintuitive tool switching that disrupts workflow. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Communication",
-  "difficulty": "hard"
-}

package/library/web_applications-communication/collapsible-sidebar-streaming-content-input-bar.json

@@ -1,68 +0,0 @@
-{
-  "index": 1526,
-  "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 whenever possible. Implement the frontend for the page described above, including the collapsible sidebar on the left, the streaming response content frame on the right, and the input bar at the bottom right (supporting file and image imports).",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the collapsible sidebar implementation complete?",
-      "description": "Check whether the sidebar can be collapsed/expanded with smooth animation (duration between 200-300ms). Verify that the sidebar maintains its state across screen size changes and includes proper icon transitions. Score 0 if the sidebar isn't collapsible, 5 if basic toggle functionality exists but lacks animation/transitions, and 10 if fully implemented with responsive behavior and proper state management.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the streaming response content frame properly implemented?",
-      "description": "Evaluate the streaming content implementation for proper text animation (character-by-character or word-by-word appearance), scroll management (auto-scroll with user override detection), and proper formatting of code blocks and other content types. Deduct 5 points if streaming animation is missing, 3 points if code syntax highlighting is absent, and 5 points if the scroll behavior is problematic. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the input bar functionality complete?",
-      "description": "Assess whether the input bar properly handles multiline input, expands vertically with content (with reasonable max-height), and includes a clear send button. Check for keyboard shortcuts (Enter to send, Shift+Enter for new line). Deduct 5 points if file/image import functionality is missing, 3 points if the input doesn't auto-resize, and 5 points if keyboard shortcuts are not implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the file and image import functionality properly implemented?",
-      "description": "Verify that the code handles file/image uploads with proper preview, progress indication, size validation (reject files >10MB), and format validation. Check for drag-and-drop support and clipboard paste functionality. Deduct 5 points if only button upload is supported (no drag-and-drop), 5 points if there's no upload validation, and 7 points if image previews are missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as out-of-bounds input, network interruption, 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. Dark/light mode toggle 2. Keyboard shortcut guide 3. Message search functionality 4. Markdown preview while typing). 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 collapse the sidebar) 2. Function modules unrelated to a chat interface (e.g., built-in games) 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 UI components/state management/API services), component reusability, and build process configuration. 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 configured properly. 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": "Web Applications-Communication",
-  "difficulty": "medium"
-}

package/library/web_applications-communication/customer-service-chat-button-with-backend.json

@@ -1,68 +0,0 @@
-{
-  "index": 1266,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable and ready for display. Help me write JavaScript code: Create a live customer service chat button in the bottom left corner of my website, with a backend interface where I can view incoming messages.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the chat button UI implementation complete?",
-      "description": "Check if the code properly implements a visually appealing button fixed in the bottom left corner that expands into a chat window. Verify CSS positioning (fixed position, z-index handling), responsive design across different screen sizes, and proper state handling (minimized/expanded). Deduct 3 points if the button isn't properly positioned, 5 points if it's not responsive, and 3 points if state transitions aren't smooth. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the chat interface functionality fully developed?",
-      "description": "Evaluate if the chat component includes essential features: message input box, send button, message history display, timestamps, user identification, and message status indicators (sent/delivered/read). Messages should properly scroll and stack, with clear visual distinction between sent and received messages. Score 0 if core chat functionality is missing, 5 if basic messaging works but lacks visual polish, and 10 if all expected chat UI components are implemented professionally. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the real-time messaging functionality implemented?",
-      "description": "Review the implementation of real-time message handling using technologies like WebSockets, Server-Sent Events, or polling. Check for message queue management, reconnection logic, and offline message handling. Deduct 5 points if messages aren't delivered in real-time, 3 points if there's no reconnection handling, and 5 points if there's no offline message support. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the admin backend interface properly implemented?",
-      "description": "Assess the admin interface for viewing and responding to customer messages. Check for features like multiple conversation management, search functionality, customer information display, and notification systems for new messages. Deduct 5 points if there's no way to respond to messages, 3 points if multiple conversations aren't supported, and 5 points if there are no notifications for new messages. 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 interruption, server errors, user input validation, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Typing indicators 2. Read receipts 3. File/image sharing capabilities 4. Auto-response templates 5. Customer satisfaction ratings). 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 message sending methods) 2. Function modules unrelated to customer service chat (e.g., unnecessary analytics) 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 UI/logic/network layers), error handling, and maintainability. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no proper error handling or logging. 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 message scrolling, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Communication",
-  "difficulty": "medium"
-}

package/library/web_applications-communication/customer-service-chat-springboot-websocket-offline.json

@@ -1,68 +0,0 @@
-{
-  "index": 797,
-  "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. Implement a customer service chat function using Thymeleaf, WebSocket, Spring Boot, MyBatis, and MySQL, with offline support functionality and complete front-end and back-end code. The customer service system should support one-to-many communications.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the WebSocket implementation complete for real-time chat?",
-      "description": "Review whether the WebSocket communication is properly implemented with Spring's STOMP support, including connection establishment, message routing, and error handling. Check for proper endpoint configuration, message converters, and session management. Score 0 if WebSocket is not implemented, 5 if basic messaging works but lacks proper error handling or reconnection logic, and 10 if fully implemented with heartbeat mechanism and connection state management.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the offline support functionality properly implemented?",
-      "description": "Evaluate whether the system can handle offline scenarios by storing undelivered messages in the database and delivering them when users reconnect. Check if read receipts are implemented, and if the system can track message delivery status. Deduct 5 points if offline messages aren't persisted, 3 points if there's no visual indication of message delivery status, and 2 points if there's no mechanism to handle message order when delivering offline messages. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the one-to-many communication model properly designed?",
-      "description": "Check if the system allows customer service representatives to handle multiple customers simultaneously with proper UI for switching between conversations, conversation grouping, and prioritization. Verify if there's a queuing system for unattended customers. Deduct 5 points if there's no way to handle multiple conversations simultaneously, 3 points if there's no conversation prioritization, and 2 points if there's no visual indication of new messages in inactive conversations. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the database design complete and properly implemented with MyBatis?",
-      "description": "Evaluate the database schema design for users, conversations, messages, and their relationships. Check if MyBatis mappers, XML configurations, and DTOs are properly implemented. Look for proper transaction management and connection pooling. Deduct 5 points if the schema design doesn't support the requirements, 3 points if there are no indexes on frequently queried columns, and 2 points if there's no pagination for message history. 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 WebSocket disconnections, database connection 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. AI-powered response suggestions 2. Sentiment analysis for customer messages 3. Automatic translation for multi-language support 4. File/image sharing with preview). 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 message sending mechanisms) 2. Function modules unrelated to customer service chat (e.g., unnecessary social 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 controller/service/repository layers), unit test coverage, and build process automation. Check if Spring Boot best practices are followed. 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 Thymeleaf templates and CSS follow 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). Review if the chat interface is intuitive with clear visual 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) Message sending/receiving feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance. Check if new messages are appropriately highlighted and if there are typing indicators. Deduct 5 points for each operation without feedback, 3 points for jerky scrolling when loading message history, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Communication",
-  "difficulty": "hard"
-}

package/library/web_applications-communication/dormitory-room-414-official-website.json

@@ -1,68 +0,0 @@
-{
-  "index": 1082,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure that the code you generate is executable for display purposes. Help me write a web page in HTML that serves as the official website for Dormitory Room 414, and ensure the encoding format is GB2312.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the HTML structure semantically correct and follows GB2312 encoding?",
-      "description": "Review whether the HTML uses proper semantic tags (header, nav, main, section, footer) and includes correct GB2312 encoding declaration in meta charset. Check if Chinese characters display correctly without garbled text. Score 0 if encoding is incorrect or semantic structure is missing, 5 if basic structure exists but semantic tags are incomplete, and 10 if fully semantic HTML with proper GB2312 encoding is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Does the website contain complete dormitory-themed content sections?",
-      "description": "Check whether the website includes essential sections for a dormitory official website: member introductions, dormitory life showcase, activity records, contact information, and dormitory rules/culture. Each section should have meaningful placeholder content or real content. Deduct 2 points for each missing core section. Score 10 if all sections are comprehensive and well-organized.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the navigation system intuitive and functional?",
-      "description": "Evaluate whether the navigation menu is clearly structured with smooth anchor links or page transitions. Check for breadcrumb navigation, active state indicators, and mobile-responsive navigation collapse. Deduct 3 points if navigation links don't work, 2 points if no active states are shown, and 2 points if mobile navigation is not considered. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are interactive elements and dynamic features properly implemented?",
-      "description": "Check if the website includes interactive features like image galleries, contact forms, comment sections, or interactive dormitory member cards. Evaluate JavaScript functionality for dynamic content loading, form validation, and user interactions. Score 0 if no interactive elements exist, 5 if basic interactions are present but limited, and 10 if comprehensive interactive features enhance user engagement.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as missing images, form validation errors, browser compatibility issues, etc.) and provide friendly error prompts or fallback mechanisms. Code with strong robustness should effectively handle edge cases and provide graceful degradation. Give 10 points if fully robust, 5 points if average robustness, and 0 points if no error handling exists.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that enhance the dormitory website experience?",
-      "description": "Check whether the code includes creative features that make the dormitory website stand out (e.g., 1. Interactive dormitory floor plan 2. Member mood/status indicators 3. Shared calendar for dormitory activities 4. Photo timeline of dormitory memories 5. Virtual guest book). 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 contact forms) 2. Function modules unrelated to dormitory life (e.g., e-commerce functionality) 3. Excessive animations that slow down page loading. Deduct 3 points for each redundancy found, and directly deduct 10 points if core dormitory website functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review code organization (separation of HTML/CSS/JS), proper file structure, and clean coding practices. Check for code reusability, proper commenting, and adherence to web standards. Deduct 5 points if inline styles dominate over external CSS; deduct 5 points if code duplication rate is too high (over 30%); deduct 3 points if no proper file organization exists. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface design meet professional dormitory website standards?",
-      "description": "Evaluate whether the design creates a warm, welcoming dormitory atmosphere: 1) Harmonious color scheme suitable for dormitory theme (warm tones preferred) 2) Proper layout with adequate whitespace (8px grid system) 3) Readable typography (body font ≥ 14px, line height ≥ 1.5) 4) Consistent visual hierarchy. Deduct 3 points for each cluttered section, 5 points for inappropriate color choices, and 5 points for poor readability. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the user interaction smooth and responsive?",
-      "description": "Judge whether interactions feel natural and responsive: 1) Hover effects and click feedback ≤ 100ms 2) Smooth transitions between sections (300-500ms duration) 3) Clear visual focus and navigation cues 4) Mobile-friendly touch interactions. Deduct 5 points for each unresponsive interaction, 3 points for jarring transitions, and 5 points if mobile usability is poor. Full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Communication",
-  "difficulty": "medium"
-}

package/library/web_applications-communication/draggable-menu-buttons.json

@@ -1,68 +0,0 @@
-{
-  "index": 1033,
-  "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. Modify the menu buttons so they can be dragged, and provide me with all the complete code so I can easily copy it!",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the draggable menu button functionality fully implemented?",
-      "description": "Check if the code implements proper mouse/touch event handling for dragging (mousedown/touchstart, mousemove/touchmove, mouseup/touchend), maintains state during drag operations, and correctly updates the button's position based on cursor/touch movement. Score 0 if dragging is not implemented, 5 if basic dragging works with issues, and 10 if the implementation is complete with smooth drag behavior.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is cross-browser compatibility addressed?",
-      "description": "Evaluate whether the code handles both mouse and touch events appropriately for different devices, uses vendor prefixes where necessary, and implements feature detection to ensure maximum compatibility across browsers. Deduct 3 points if touch events are missing, 3 points if vendor prefixes are not used where needed, and 4 points if no feature detection is implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are boundaries and constraints properly implemented?",
-      "description": "Check if the code prevents menu buttons from being dragged outside the visible area, implements collision detection with screen edges, and ensures buttons remain accessible to users. Deduct 5 points if buttons can be dragged out of view, 3 points if there's no boundary enforcement, and 2 points if the buttons can overlap in an unusable way. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the implementation include a clean reset or save position functionality?",
-      "description": "Assess whether the code includes mechanisms to reset button positions to default, save positions between sessions (using localStorage/sessionStorage), and restore positions on page reload. Score 0 if neither reset nor save functions exist, 5 if only basic position management is implemented, and 10 if complete position management with persistence is included.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as rapid clicks, dragging outside the window, browser resize events, etc.) and provide friendly error handling 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. Animation effects during dragging 2. Snapping to grid or alignment guides 3. Multi-touch support for simultaneous button movements). 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 event listeners that could cause memory leaks 2. Unnecessary wrapper elements that complicate the DOM structure 3. Over-engineered solutions for simple dragging operations. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review code organization (separation of concerns between dragging logic and UI), use of modern JavaScript practices, and performance considerations. Deduct 5 points if global scope is polluted with variables; deduct 3 points if event delegation isn't used for multiple buttons; deduct 2 points if RAF (requestAnimationFrame) isn't used for smooth animations. 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) Visual feedback during drag operations 2) Proper sizing for touch targets (at least 44×44px) 3) Consistent styling that matches the rest of the UI. Deduct 3 points for missing hover/active states, 5 points for inadequately sized touch targets, and 2 points for inconsistent styling. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the drag interaction conforms to human perception characteristics: 1) No lag between cursor/touch movement and button position updates 2) Proper acceleration/deceleration if momentum is implemented 3) Clear visual indication of draggable elements. Deduct 5 points for noticeable lag during dragging, 3 points for jumpy movement, and 2 points for lack of visual affordances indicating draggability. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Communication",
-  "difficulty": "easy"
-}

package/library/web_applications-communication/dynamic-login-form-validation-captcha.json

@@ -1,68 +0,0 @@
-{
-  "index": 1715,
-  "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. The login interface employs a dynamic form validation mechanism, supporting both username/password login and mobile phone verification code login modes, with built-in CAPTCHA to prevent brute force attacks. Design the HTML.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Are both login modes fully implemented?",
-      "description": "Review whether the code implements both username/password and mobile verification code login modes with smooth toggle functionality. The toggle should preserve entered data when switching modes. Score 0 if only one mode is implemented, 5 if both modes exist but switching causes data loss, and 10 if both modes function seamlessly with proper state management.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the form validation mechanism comprehensive?",
-      "description": "Evaluate the validation logic for all input fields: username format validation, password strength requirements, mobile number formatting, and verification code length checking. Real-time validation with clear visual feedback is required. Deduct 2 points for each field missing validation, 3 points if validation only happens on submission rather than in real-time, and 5 points if error messages are generic rather than specific to the error type.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the CAPTCHA mechanism properly implemented?",
-      "description": "Check if the CAPTCHA implementation includes auto-refresh functionality, accessibility considerations (audio alternative), and proper integration with form submission validation. The CAPTCHA should appear after failed attempts and include anti-automation measures. Deduct 5 points if CAPTCHA is purely decorative without validation logic, and 3 points if it lacks refresh capabilities. Give 10 points for a complete implementation with security considerations.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the mobile verification code delivery system implemented securely?",
-      "description": "Verify that the code includes rate limiting for SMS requests, countdown timer between requests (typically 60 seconds), proper mobile number validation before sending, and visual feedback during the waiting period. Deduct 5 points if rate limiting is absent, 3 points if there's no countdown timer, and 3 points if the mobile validation occurs only after sending rather than before.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as network delays, invalid inputs, session timeouts, 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. Password strength visual indicator 2. Social login integration 3. Dark/light mode toggle 4. Persistent login option with security warning). 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 validation logic (e.g., multiple password validation functions) 2. Function modules unrelated to login (e.g., newsletter signup within login form) 3. Excessive animations or effects that affect loading 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 validation logic, UI components, and event handling), code reusability, and maintainability. Deduct 5 points if global variables are excessively used; deduct 5 points if the code contains hardcoded values instead of constants; deduct 5 points if there's significant code duplication. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the login form follows modern design principles: 1) Consistent input field styling with clear focus states 2) Proper spacing between form elements (8px grid system) 3) Professional typography with adequate contrast for accessibility. Deduct 3 points for inconsistent styling between input fields, 5 points for poor visual hierarchy (unclear what action to take), and 5 points for inadequate responsive design considerations. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the form interactions feel natural: 1) Immediate visual feedback on input validation (≤100ms) 2) Smooth transitions between login modes (300-500ms) 3) Appropriate loading indicators during submission. Deduct 5 points for lack of submission state indication, 3 points for jarring mode transitions, and 5 points for delayed validation feedback causing user confusion. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Communication",
-  "difficulty": "medium"
-}