@getollie/cli 0.0.4 → 0.2.0

package/library/web_applications-communication/aesthetically-pleasing-login-page.json

@@ -1,68 +0,0 @@
-{
-  "index": 960,
-  "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 when possible. Create an aesthetically pleasing login page with a reasonable layout.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the login form functionality fully implemented?",
-      "description": "Evaluate whether the code includes all essential login form elements (username/email field, password field, submit button) and implements basic form validation. Score 0 if form elements are missing, 5 if basic elements exist without validation, and 10 if complete with client-side validation (including input format checking, required field validation, and error display).",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the password security properly addressed?",
-      "description": "Check whether the code implements password field masking, password strength indicators, and security features like CSRF protection. Deduct 3 points if password masking is missing, 4 points if there's no password strength indicator, and 3 points if there's no option to show/hide password. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are alternative login methods and account recovery options provided?",
-      "description": "Review whether the page includes social login options (OAuth integration), 'forgot password' functionality, and 'remember me' option. Deduct 3 points for each missing feature. Additionally, check if there's a sign-up link for new users. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the form submission and response handling properly implemented?",
-      "description": "Evaluate whether the code includes proper form submission handling, loading states during submission, and appropriate feedback after submission (success/error messages). Deduct 5 points if there's no visual feedback during submission, and 5 points if error handling is inadequate. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid inputs, failed submissions, browser compatibility issues) and provide friendly error prompts. 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. Animated transitions 2. Dark/light mode toggle 3. Locale/language selection 4. Accessibility features beyond standard). 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 form validation code 2. Unnecessary scripts or stylesheets 3. Fancy effects that affect performance (e.g., excessive animations or high-resource background effects). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core login functionality is interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (separation of HTML, CSS, and JavaScript), code organization, and maintainability. Deduct 5 points if inline styles are overused; deduct 3 points if JavaScript is not separated from HTML; deduct 2 points if there's no responsive design for different screen sizes. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance for form fields. Deduct 5 points for each operation without feedback, 3 points for jarring transitions, and 5 points for poor keyboard navigation support. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Communication",
-  "difficulty": "easy"
-}

package/library/web_applications-communication/agreement-image-upload-component.json

@@ -1,68 +0,0 @@
-{
-  "index": 1700,
-  "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 demonstration purposes. Transform the collection agreement and profit-sharing agreement into a component with a plus sign for image uploads, and also include functionality to display the uploaded images.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the component structure properly implemented?",
-      "description": "Review whether the code correctly implements a reusable component structure that integrates both collection agreement and profit-sharing agreement functionality. Check if the component uses proper encapsulation, follows component design patterns, and separates concerns. Score 0 if the component structure is missing, 5 if basic structure is implemented but lacks proper organization, and 10 if the component is well-structured, reusable, and follows best practices.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the image upload functionality with plus sign UI fully implemented?",
-      "description": "Evaluate whether the code implements a user-friendly image upload interface with a visible plus sign indicator. Check if it includes proper visual feedback during hover/click states, handles multiple image formats, provides file size validation, and includes loading states. Deduct 3 points if the plus sign UI is missing, 5 points if upload functionality doesn't work, and 2 points if there's no visual feedback during upload process. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the image display functionality properly implemented?",
-      "description": "Check whether the uploaded images are properly displayed with appropriate sizing, formatting, and layout considerations. Evaluate if the implementation includes image preview capabilities, thumbnail generation, gallery view options, and proper handling of different aspect ratios. Deduct 5 points if images aren't displayed after upload, 3 points if the display lacks proper formatting controls, and 2 points if there's no preview functionality. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the agreement functionality properly integrated with the image component?",
-      "description": "Assess whether both collection and profit-sharing agreement functionalities are properly integrated with the image upload/display component. Check if the agreements can be properly linked to specific uploaded images, if agreement terms are clearly presented, and if user confirmation workflows are implemented. Deduct 5 points if agreements are not connected to images, 3 points if agreement workflows are incomplete, and 3 points if agreement text is not customizable. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid file types, oversized images, network errors during upload, missing image sources, and permission issues) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Drag-and-drop image uploading 2. Image editing tools 3. Agreement template selection 4. Digital signature integration). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple image upload handlers) 2. Function modules unrelated to agreements or image management (e.g., unrelated user profile features) 3. Fancy effects that affect performance (e.g., unnecessary animations that slow down the upload 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 UI components/business logic/API calls), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast sliding, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Communication",
-  "difficulty": "easy"
-}

package/library/web_applications-communication/ai-chat-conversation-page-react-tdesign.json

@@ -1,68 +0,0 @@
-{
-  "index": 1145,
-  "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. Implement an AI chat conversation page with streaming loading using React combined with TDesign.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the React component structure properly organized?",
-      "description": "Check if the code follows React best practices with proper component hierarchy, separation of concerns, and use of hooks. Components should be modular, reusable, and follow a clear naming convention. Deduct 5 points if components are overly complex or have mixed responsibilities; deduct 5 points if hooks usage doesn't follow React rules; deduct 5 points if prop drilling is excessive without proper state management. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the streaming chat functionality correctly implemented?",
-      "description": "Evaluate if the code properly implements a streaming response mechanism that displays AI responses character by character. Check for proper handling of async operations, usage of fetch API or similar methods with ReadableStream, and correct state updates for real-time text display. Score 0 if streaming is not implemented, 5 if basic implementation exists but has flaws, and 10 if streaming works flawlessly with proper error handling and loading states.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is TDesign properly integrated and utilized?",
-      "description": "Verify if TDesign components are correctly imported, configured, and used according to the official documentation. Check whether the application leverages TDesign's theming capabilities, responsive design features, and component props. Deduct 3 points if TDesign is improperly imported, 3 points if components are misused, and 4 points if the design system's full potential is not utilized. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the chat UI follow conversational interface best practices?",
-      "description": "Assess whether the chat interface includes essential elements such as message bubbles with clear sender distinction, timestamp display, message status indicators (sending/sent/error), and proper scrolling behavior (auto-scroll to new messages). Deduct 2 points for each missing essential element. Check if the interface handles long messages, code blocks, and various content types appropriately. 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 failures, API errors, empty responses, 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. Syntax highlighting for code in responses 2. Markdown rendering capability 3. Voice input/output integration). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple state management solutions used simultaneously) 2. Function modules unrelated to chat (e.g., unnecessary user dashboards) 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/API layers), proper TypeScript typing (if used), and good project structure. 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 error boundary implementation for React. 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 (consistent with TDesign theme) 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) Loading states for messages being sent 2) Smooth transition animations for new messages appearing 3) Clear visual indications of streaming text. Deduct 5 points for each operation without feedback, 3 points for jerky animations during streaming, and 5 points for lack of proper scrolling behavior when new content appears. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Communication",
-  "difficulty": "easy"
-}

package/library/web_applications-communication/android-chat-interface-json-data.json

@@ -1,68 +0,0 @@
-{
-  "index": 331,
-  "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 display. {\n    \"code\": 200,\n    \"message\": \"success\",\n    \"data\": {\n        \"records\": [\n            {\n                \"id\": 95,\n                \"type\": \"text\",\n                \"content\": \"Test\\n\",\n                \"userId\": 1811,\n                \"name\": \"Bishih(⊙o⊙)?\",\n                \"avatar\": \"https://api.dicebear.com/6.x/pixel-art/svg?seed=Raccoon\",\n                \"location\": \"China|Mobile\",\n                \"isRecalled\": false,\n                \"time\": \"2025-03-29 15:38:01\"\n            },\n            {\n                \"id\": 94,\n                \"type\": \"text\",\n                \"content\": \"Hahaha\\n\",\n                \"userId\": 1811,\n                \"name\": \"Bishih(⊙o⊙)?\",\n                \"avatar\": \"https://api.dicebear.com/6.x/pixel-art/svg?seed=Raccoon\",\n                \"location\": \"China|Mobile\",\n                \"isRecalled\": false,\n                \"time\": \"2025-03-29 15:37:57\"\n            },\n            {\n                \"id\": 93,\n                \"type\": \"text\",\n                \"content\": \"Upvote\",\n                \"userId\": 1811,\n                \"name\": \"Bishih(⊙o⊙)?\",\n                \"avatar\": \"https://api.dicebear.com/6.x/pixel-art/svg?seed=Raccoon\",\n                \"location\": \"China|Mobile\",\n                \"isRecalled\": false,\n                \"time\": \"2025-03-29 15:37:53\"\n            },\n            {\n                \"id\": 92,\n                \"type\": \"text\",\n                \"content\": \"Message recalled\",\n                \"userId\": 1,\n                \"name\": \"Yuanchi\",\n                \"avatar\": \"https://image.yc-hequan.com/localFile/local-plus/20250318/IMG_20230822_233601_edit_39814454869289.jpg\",\n                \"location\": \"China|Mobile\",\n                \"isRecalled\": true,\n                \"time\": \"2025-03-29 14:28:53\"\n            },\n            {\n                \"id\": 91,\n                \"type\": \"text\",\n                \"content\": \"Message recalled\",\n                \"userId\": 1,\n                \"name\": \"Yuanchi\",\n                \"avatar\": \"https://image.yc-hequan.com/localFile/local-plus/20250318/IMG_20230822_233601_edit_39814454869289.jpg\",\n                \"location\": \"China|Mobile\",\n                \"isRecalled\": true,\n                \"time\": \"2025-03-29 14:28:11\"\n            },\n            {\n                \"id\": 90,\n                \"type\": \"text\",\n                \"content\": \"Message recalled\",\n                \"userId\": 1,\n                \"name\": \"Yuanchi\",\n                \"avatar\": \"https://image.yc-hequan.com/localFile/local-plus/20250318/IMG_20230822_233601_edit_39814454869289.jpg\",\n                \"location\": \"China|Mobile\",\n                \"isRecalled\": true,\n                \"time\": \"2025-03-29 14:27:45\"\n            },\n            {\n                \"id\": 89,\n                \"type\": \"text\",\n                \"content\": \"Message recalled\",\n                \"userId\": 1,\n                \"name\": \"Yuanchi\",\n                \"avatar\": \"https://image.yc-hequan.com/localFile/local-plus/20250318/IMG_20230822_233601_edit_39814454869289.jpg\",\n                \"location\": \"China|Mobile\",\n                \"isRecalled\": true,\n                \"time\": \"2025-03-29 14:25:53\"\n            },\n            {\n                \"id\": 88,\n                \"type\": \"text\",\n                \"content\": \"Message recalled\",\n                \"userId\": 1,\n                \"name\": \"Yuanchi\",\n                \"avatar\": \"https://image.yc-hequan.com/localFile/local-plus/20250318/IMG_20230822_233601_edit_39814454869289.jpg\",\n                \"location\": \"China|Mobile\",\n                \"isRecalled\": true,\n                \"time\": \"2025-03-29 14:25:32\"\n            },\n            {\n                \"id\": 87,\n                \"type\": \"text\",\n                \"content\": \"Message recalled\",\n                \"userId\": 1,\n                \"name\": \"Yuanchi\",\n                \"avatar\": \"https://image.yc-hequan.com/localFile/local-plus/20250318/IMG_20230822_233601_edit_39814454869289.jpg\",\n                \"location\": \"China|Mobile\",\n                \"isRecalled\": true,\n                \"time\": \"2025-03-29 14:25:04\"\n            },\n            {\n                \"id\": 86,\n                \"type\": \"text\",\n                \"content\": \"Message recalled\",\n                \"userId\": 1,\n                \"name\": \"Yuanchi\",\n                \"avatar\": \"https://image.yc-hequan.com/localFile/local-plus/20250318/IMG_20230822_233601_edit_39814454869289.jpg\",\n                \"location\": \"China|Mobile\",\n                \"isRecalled\": true,\n                \"time\": \"2025-03-29 14:24:18\"\n            }\n        ],\n        \"total\": 33,\n        \"size\": 10,\n        \"current\": 1,\n        \"orders\": [],\n        \"optimizeCountSql\": true,\n        \"searchCount\": true,\n        \"countId\": null,\n        \"maxLimit\": null,\n        \"pages\": 4\n    },\n    \"extra\": {}\n}                          Please write an Android chat interface based on this JSON data, with logic to display chat bubbles on the right if the userId equals the current user's, otherwise on the left. (Assume the current user's userId is 1) Please use Java language for this chat interface.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Android chat interface UI implementation complete?",
-      "description": "Evaluate whether the code implements all essential UI components for a chat interface: RecyclerView with proper adapters, message bubble layouts (left/right alignment), user avatars, timestamps, and message status indicators. Score 0 if missing core UI components, 5 if basic implementation is present, and 10 if the interface includes sophisticated UI elements like bubble tails, read receipts, and proper padding based on Material Design guidelines.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the chat message alignment logic correctly implemented?",
-      "description": "Verify if the code correctly positions messages on the right side for userId=1 (current user) and on the left for other users. Deduct 5 points if the alignment logic is incorrect or inconsistent. Check if message bubbles have appropriate styling differences (color, shape, padding) based on sender. Full score requires visual evidence of proper message alignment in screenshots.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the message recall handling implemented properly?",
-      "description": "Assess how recalled messages (isRecalled=true) are displayed differently from regular messages. Verify if the UI shows 'Message recalled' text with appropriate styling. Check if the code handles recall state transitions. Deduct 5 points if recalled messages are not visually distinct, and 3 points if there's no support for recall status changes after loading.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the data pagination and loading mechanism implemented?",
-      "description": "Evaluate if the code handles the pagination parameters (total, size, current, pages) from the JSON data. Check for implementation of pagination controls or infinite scrolling. Verify proper loading of additional message pages. Deduct 5 points if pagination is not implemented at all, and 3 points if loading indicators are missing during page transitions.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as empty messages, null avatar URLs, network issues, or JSON parsing 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. Message reactions/emoji support 2. Voice message playback controls 3. Animated typing indicators 4. Smart date separators between message groups). 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 view binding approaches coexisting) 2. Function modules unrelated to chat display (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/data/network layers), use of design patterns (Adapter, ViewHolder, etc.), and proper memory management. Deduct 5 points if global state pollution is found or if RecyclerView implementation is inefficient; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if no ViewHolder pattern is used. 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 Android Material Design principles: 1) Appropriate use of elevation and shadows for message bubbles 2) Proper layout spacing (element spacing follows the 8dp multiple principle) 3) Professional typography system (body text size ≥ 14sp, proper line height). Deduct 3 points for each crowded visual element, 5 points for inconsistent styling, and 5 points for improper text wrapping or overflow. 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) Smooth scrolling performance with proper view recycling 2) Message sending/loading animations between 300-500ms 3) Clear visual feedback for user actions. Deduct 5 points for each operation without feedback, 3 points for stuttering during fast scrolling, and 5 points for poor list item reuse implementation causing visual glitches. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Communication",
-  "difficulty": "medium"
-}

package/library/web_applications-communication/animal-translator-html-software.json

@@ -1,68 +0,0 @@
-{
-  "index": 1424,
-  "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 demonstrable. Help me create an animal translator, which is an HTML software that can translate human language into animal language.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core translation engine fully implemented?",
-      "description": "Review whether the code accurately implements the translation logic from human language to animal language through JavaScript, including multiple animal language types (cat, dog, bird, etc.) and proper phonetic mapping algorithms. Score 0 if no translation logic is implemented, 5 if only basic single animal translation exists, and 10 if multiple animal languages with comprehensive vocabulary mapping are included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the language input and output system properly designed?",
-      "description": "Check whether the input system supports multiple formats (text input, voice recognition, file upload) and the output system provides various presentation methods (text display, audio playback, visual phonetics). Deduct 5 points if voice input/output is missing, and 3 points if no input validation is implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the animal language database comprehensive and accurate?",
-      "description": "Evaluate whether the animal language system includes scientifically-based or creatively consistent language rules, proper grammar structures, and vocabulary databases for different animals. Two-way translation capability is required. Deduct 5 points if animal languages lack consistency or logical structure. Check whether multiple animal species are supported with distinct linguistic characteristics. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the user interaction workflow complete and intuitive?",
-      "description": "Check whether the code includes complete user workflow management, including language selection, translation history, favorites, and sharing functionality. Deduct 5 points if translation history is not implemented, and 3 points if no progress indicators are shown during translation. Give 10 points if the complete user journey is seamlessly integrated.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as empty input, unsupported characters, network issues, browser compatibility problems, 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 pronunciation guide with IPA notation 2. Animal avatar animations that speak the translated text 3. Cultural context explanations for animal communication patterns 4. Batch translation for conversations). 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 translation engines coexisting unnecessarily) 2. Function modules unrelated to animal translation (e.g., a built-in weather widget) 3. Fancy effects that affect performance (e.g., excessive particle animations during translation). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core translation 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 translation logic/UI components/data layers), code organization, and maintainability. Deduct 5 points if global state pollution is found or proper separation of concerns is not implemented; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if no proper error handling or logging mechanisms exist. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching with animal-themed aesthetics (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional typography system (body font size ≥ 14px, line height over 1.5 times) 4) Intuitive iconography for different animals. Deduct 3 points for each cramped visual element, 5 points for jarring color combinations, and 5 points for chaotic layout hierarchy. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Translation trigger response delay ≤ 100ms 2) Transition animations between different animal modes controlled between 300-500ms 3) Clear visual feedback during translation process 4) Smooth animal character animations if present. Deduct 5 points for each operation without feedback, 3 points for laggy animations during mode switching, and 5 points for unclear translation status indicators. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Communication",
-  "difficulty": "medium"
-}

package/library/web_applications-communication/anonymous-online-voting-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 1181,
-  "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. Design an anonymous online voting system to be published in a fixed group where 17 members have voting rights. The voting requires selecting 3 people from 4 candidates through multiple selection. The system needs to prevent duplicate voting from these 17 people and display voting results after the deadline. Display results in HTML. The candidates are: Zheng Geng, Ge Daoshun, Huang Yiran, and Song Yuting. The voters are: Zheng Geng, Guo Mingkai, Huang Yiran, Song Yuting, Ye Zhen, Wang Yuanxin, Gao Yijun, Wu Fang, Zhang Zhihui, Ling Sicheng, Xu Jinsheng, Chi Zihua, Ge Daoshun, Xu Shiling, Zhang Di, Zhang Fangzhou, and Fan Lingling.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the anonymous voting system properly implemented?",
-      "description": "Review whether the code implements a secure anonymous voting system where voters cannot be identified from their votes. Check if a voter authentication mechanism exists without revealing identity in the results. Score 0 if anonymity is not implemented, 5 if basic anonymity is implemented but with flaws, and 10 if complete anonymity with cryptographic protection is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the multiple selection voting mechanism correctly implemented?",
-      "description": "Verify if the system properly constrains voters to select exactly 3 candidates from the 4 options. Check if the UI clearly indicates the selection requirement and prevents submission with invalid selections (less than 3 or more than 3). Deduct 5 points if validation is missing, 3 points if validation exists but has bugs. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the duplicate voting prevention mechanism effective?",
-      "description": "Evaluate how the system prevents the 17 specified voters from voting multiple times. Check for session management, cookies, authentication tokens, or other methods to track who has voted. Assess if the implementation securely stores this information. Score 0 if duplicate voting is possible, 5 if prevention exists but can be bypassed, and 10 if the prevention mechanism is robust.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the deadline and result display functionality implemented correctly?",
-      "description": "Check if the system has a configurable deadline after which voting closes and results are automatically displayed. Verify if the transition from voting to results display is seamless. Deduct 5 points if deadline implementation is missing, 3 points if result display doesn't show automatically. Award full 10 points if both are implemented correctly with appropriate time handling.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as browser crashes, network interruptions, page refreshes, or concurrent voting) 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 voting statistics (visible only after deadline) 2. Secure voting verification receipts 3. Interactive result visualization). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple voter verification methods) 2. Function modules unrelated to voting (e.g., unnecessary animations) 3. Fancy effects that affect 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 (such as separating voting logic/UI/authentication layers), clean code practices, and security considerations. 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 are security vulnerabilities like XSS or CSRF. 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 status for voting selection and submission. Deduct 5 points for operations without feedback, 3 points for confusing selection states, and 5 points for unclear submission confirmation. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Communication",
-  "difficulty": "easy"
-}

package/library/web_applications-communication/blazor-server-auth-microservice-timestamp.json

@@ -1,68 +0,0 @@
-{
-  "index": 311,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Try to ensure the generated code is executable.\n\nMicroservice 1: Authentication Microservice\nAPI Controller Code:\n```csharp\nnamespace AuthService.Controllers\n{\n    [ApiController]\n    [Route(\"api/[controller]\")]\n    public class AuthController : ControllerBase\n    {\n        private readonly UserManager<IdentityUser> _userManager;\n        private readonly SignInManager<IdentityUser> _signInManager;\n        private readonly IConfiguration _configuration;\n\n        public AuthController(UserManager<IdentityUser> userManager, SignInManager<IdentityUser> signInManager, IConfiguration configuration)\n        {\n            _userManager = userManager;\n            _signInManager = signInManager;\n            _configuration = configuration;\n        }\n\n        [HttpPost(\"register\")]\n        public async Task<IActionResult> Register(RegisterModel model)\n        {\n            var user = new IdentityUser { UserName = model.Username, Email = model.Email };\n            var result = await _userManager.CreateAsync(user, model.Password);\n\n            if (result.Succeeded)\n            {\n                return Ok();\n            }\n\n            return BadRequest(result.Errors);\n        }\n\n        [HttpPost(\"login\")]\n        public async Task<IActionResult> Login(LoginModel model)\n        {\n            var result = await _signInManager.PasswordSignInAsync(model.Username, model.Password, false, false);\n\n            if (result.Succeeded)\n            {\n                var user = await _userManager.FindByNameAsync(model.Username);\n                try\n                {\n                    var token = GenerateJwtToken(user!);\n\n\n                    return Ok(new { token });\n                }\n                catch(Exception e)\n                {\n                    throw e;\n                }\n            }\n\n            return Unauthorized();\n        }\n\n        private string GenerateJwtToken(IdentityUser user)\n        {\n            var claims = new[]\n            {\n                new Claim(JwtRegisteredClaimNames.Sub, user.UserName!),\n                new Claim(JwtRegisteredClaimNames.Jti, Guid.NewGuid().ToString())\n            };\n\n            var key = new SymmetricSecurityKey(Encoding.UTF8.GetBytes(_configuration[\"Jwt:Key\"]!));\n            var creds = new SigningCredentials(key, SecurityAlgorithms.HmacSha256);\n\n            var token = new JwtSecurityToken(\n                issuer: _configuration[\"Jwt:Issuer\"],\n                audience: _configuration[\"Jwt:Audience\"],\n                claims: claims,\n                expires: DateTime.Now.AddMinutes(30),\n                signingCredentials: creds);\n\n            return new JwtSecurityTokenHandler().WriteToken(token);\n        }\n    }\n}\n```\n\nMicroservice 2: Timestamp Microservice:\nController Code:\n```csharp\nnamespace TimestampService.Controllers\n{\n    [ApiController]\n    [Route(\"api/[controller]\")]\n    [Authorize] // Add this attribute to require authentication\n    public class TimestampController : ControllerBase\n    {\n        private readonly TimestampDbContext _context;\n\n        public TimestampController(TimestampDbContext context)\n        {\n            _context = context;\n        }\n\n        [HttpGet]\n        public IActionResult GetTimestamp()\n        {\n            var timestamp = new TimestampRecord\n            {\n                Timestamp = DateTime.UtcNow\n            };\n\n            _context.Timestamps.Add(timestamp);\n            _context.SaveChanges();\n\n            return Ok(timestamp);\n        }\n    }\n}\n```\n\nNow please help me create a Blazor Server project: Blazor has two interfaces: a login interface that authenticates through the API, and a work page that requires login to access. If not logged in, it redirects to the login page (implemented using @Attribute Authorize). The work page has a button and a textbox. When the button is clicked, it retrieves values from microservice 2, where the authentication token is the same as the Blazor verification token, and displays the returned values in the textbox.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Blazor authentication implementation complete?",
-      "description": "Check if the Blazor project correctly implements authentication using JWT tokens from the Auth microservice. The code should include proper token storage (localStorage/sessionStorage), token validation, handling token expiration, and redirect logic. Verify that authentication state is preserved across page refreshes.Score 0 if authentication is not implemented, 5 if basic token storage exists but without proper validation/expiration handling, 10 if complete with refresh token mechanism and secure storage.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the login interface properly implemented?",
-      "description": "Evaluate if the login interface includes username/password fields with proper validation (required fields, minimum length, etc.), appropriate error handling (displaying API error messages), loading states during authentication, and proper handling of API responses. Check for CSRF protection if using cookie-based auth.Score 0 if basic login form is missing, 5 if form exists but lacks validation or error handling, 10 if the form has complete validation, error handling, and security measures.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the work page and authorization correctly implemented?",
-      "description": "Check if the work page is properly protected with [Authorize] attribute, has proper UI components (button and textbox as required), and correctly redirects unauthorized users to the login page. Examine if the authorization is validated both on the client and server sides to prevent unauthorized access.Score 0 if authorization is missing, 5 if authorization exists but redirect logic is flawed or inconsistent, 10 if authorization is complete with proper redirect logic and security checks.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the API integration with microservice 2 properly implemented?",
-      "description": "Verify if the Blazor application correctly passes JWT tokens to the Timestamp microservice, handles API responses appropriately, and updates UI based on responses. Check for proper error handling for API failures, network issues, and token validation problems.Score 0 if API integration is missing, 5 if basic integration exists but lacks error handling, 10 if integration includes proper error handling, loading states, and retry mechanisms.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as API failures, token expiration during session, network interruption, validation errors, etc.) and provide friendly error prompts or recovery mechanisms. Check for proper exception handling and fallback 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. Persistent login with refresh token 2. Multi-factor authentication 3. User session management with logout functionality 4. Dark mode for the application 5. Responsive design for mobile compatibility).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 authentication methods or token validations 2. Unnecessary API calls or state management 3. Excessive UI elements that complicate the user experience.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 authentication logic/UI components/API services), component reusability, code organization, and proper dependency injection. Check for code duplication, global state management, and adherence to Blazor best practices.Deduct 5 points if global state pollution is found or proper component structure is not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if dependency injection is not properly utilized.",
-      "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). Check for consistent styling between login and work pages.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 feedback during API calls and authentication. Check loading indicators during API operations and transitions between pages.Deduct 5 points for each operation without feedback, 3 points for visual lag during operations, 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/campus-lost-found-wechat-mini-program.json

@@ -1,68 +0,0 @@
-{
-  "index": 1497,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to make the code you generate executable for demonstration purposes. Development of a modular-designed WeChat mini program for campus lost and found.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the basic architecture of the WeChat mini program properly implemented?",
-      "description": "Review whether the code accurately implements the WeChat mini program structure with appropriate app.js, app.json, and page directories. Check if the project uses the correct folder structure (pages, components, utils, etc.) and follows WeChat mini program development conventions. Score 0 if the basic structure is missing, 5 if only basic structure exists without proper organization, and 10 if the architecture follows best practices for WeChat mini programs.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the core lost and found features fully implemented?",
-      "description": "Evaluate the completeness of lost and found functionalities: item posting (with images, descriptions, location tags), item searching/filtering, user notifications, and contact mechanisms. Deduct 3 points if image upload is missing, 3 points if location tagging isn't implemented, 2 points if search/filter functionality is limited, and 2 points if notification system is incomplete. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the campus-specific functionality properly designed and implemented?",
-      "description": "Check if the mini program has campus-specific features like campus map integration, building/location selection, student verification system, and campus-based filtering. Deduct 3 points if campus map integration is missing, 2 points if location selection is generic rather than campus-specific, 3 points if student verification is absent, and 2 points if campus-based filtering isn't implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the modular design approach effectively applied?",
-      "description": "Assess whether the code implements proper component-based architecture with reusable UI components, service layers, and state management. Check for separation of concerns between data models, business logic, and UI. Deduct 3 points if components aren't reusable, 3 points if business logic is mixed with UI code, and 4 points if there's no clear state management approach. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as network errors, image loading failures, permission denials, 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 image recognition for item categorization 2. Lost item location heat map visualization 3. Seamless integration with campus ID systems). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple notification systems coexisting) 2. Function modules unrelated to campus lost and found (e.g., a built-in game feature) 3. Fancy effects that affect performance (e.g., unnecessary animations on every screen). 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/UI/network layers), code organization, naming conventions, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 3 points if the code duplication rate is too high (over 30%); deduct 2 points if the naming conventions are inconsistent. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface design meet WeChat mini program standards?",
-      "description": "Evaluate whether the overall design follows WeChat mini program design principles: 1) Consistent with WeChat visual language (proper use of navigation bar, tab bar, etc.) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional typography system (body font size ≥ 14px, appropriate contrast). Deduct 3 points for each inconsistency with WeChat design standards, 3 points for poor information hierarchy, and 4 points for chaotic layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the user experience optimized for the campus context?",
-      "description": "Judge whether the app is optimized for campus users: 1) Fast loading time (initial render ≤ 2s) 2) Minimal steps to report lost/found items (≤ 3 screens) 3) Clear visual guidance for first-time users 4) Campus-specific terminology and workflows. Deduct 3 points for poor performance, 3 points for complex user flows, 2 points for lack of onboarding guidance, and 2 points for generic UX not tailored to campus context. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Communication",
-  "difficulty": "medium"
-}