@getollie/cli 0.0.1

package/library/web_applications-blogs_forums/three-column-web-content-layout.json

@@ -0,0 +1,68 @@
+{
+  "index": 996,
+  "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 displayable whenever possible. Generate three columns: first column: title list on top with image list below; second column: news list on top with image news list below; third column: two image links on top with two news lists below.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the three-column layout structure correctly implemented?",
+      "description": "Review whether the code accurately implements a responsive three-column layout using proper HTML/CSS techniques (flexbox, grid, or appropriate responsive techniques). Check for proper containment, alignment, and spacing between columns. Score 0 if columns are not implemented correctly, 5 if the layout is functional but not responsive, and 10 if the columns are fully responsive with appropriate breakpoints for different screen sizes.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are all content components implemented according to specifications?",
+      "description": "Verify that all required components are included with the correct hierarchy: Column 1 (title list + image list), Column 2 (news list + image news list), Column 3 (two image links + two news lists). Score 0 if major components are missing, 5 if all components exist but with incorrect structure/hierarchy, and 10 if all components are implemented exactly as specified with proper structural relationships.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the content management and data structure well-designed?",
+      "description": "Evaluate whether the code uses efficient data structures (arrays/objects) for storing and organizing the different content types. Check if content is properly separated from presentation. Deduct 5 points if data is hard-coded without structure, 3 points if there's no clear separation between data and presentation. Full marks require modular data handling that would facilitate easy content updates.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are the interactive elements functional and properly implemented?",
+      "description": "Check whether links, hover states, and any interactive elements (like image carousels or clickable news items) are properly implemented. Test for event handling, smooth transitions, and proper feedback on user interaction. Deduct 5 points for non-functional links, 3 points for missing hover states, and 5 points for inaccessible interactive elements. Full score requires complete interaction implementation with appropriate visual feedback.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as missing images, long text content, empty lists, etc.) and provide fallbacks or graceful degradation. Code with strong robustness should effectively handle 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. Lazy loading for images 2. Smooth transitions between content states 3. Theme switching capability). 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 display the same news items) 2. Function modules unrelated to content display (e.g., a built-in calculator) 3. Fancy effects that affect performance (e.g., excessive animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating data/view/controller layers), code reusability, and maintainability. Deduct 5 points if global scope 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 styles and scripts are not properly separated. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast scrolling, and 5 points for hard-to-find content navigation. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Blogs/Forums",
+  "difficulty": "easy"
+}

package/library/web_applications-blogs_forums/vue-news-briefings-search-and-display.json

@@ -0,0 +1,68 @@
+{
+  "index": 1385,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure the generated code is executable for display purposes. I want to use Vue to design a frontend page with the following functionalities: displaying news briefings, having an input field for entering URLs, and the ability to search and display news briefings.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Vue component structure properly designed?",
+      "description": "Review whether the code properly implements Vue's component-based architecture. Check for appropriate component organization (parent-child relationships), proper props passing, and emit event handling. Evaluate the use of Vue lifecycle hooks. Score 0 if components are not used at all, 5 if basic components exist but are poorly organized, and 10 if components follow best practices with clear responsibilities and reusability.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the URL input field properly implemented?",
+      "description": "Check whether the URL input field is properly implemented with validation (checking for valid URL format), error handling, and appropriate user feedback. Verify if v-model is correctly used for two-way binding. Assess if the field includes visual cues for validation states. Deduct 5 points if URL validation is missing, 3 points if there's no error feedback, and 2 points if the input doesn't have proper UI states (focus, error, etc.). The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the news briefing display functionality implemented correctly?",
+      "description": "Evaluate if the news briefings are displayed in a structured way with proper list rendering (v-for) and key binding. Check if the displayed content includes essential news elements (title, summary, source, timestamp, etc.). Deduct 5 points if news items lack visual hierarchy, 3 points if there's no loading state or empty state handling, and 2 points if the layout breaks with different content lengths. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the search functionality implemented efficiently?",
+      "description": "Assess whether the search function uses computed properties or watchers appropriately for filtering news. Check for debouncing on user input, case-insensitive search, and ability to search across multiple fields (title, content, etc.). Verify if search results update reactively. Deduct 5 points if search is not optimized and causes performance issues, 3 points if the search lacks features like highlighting matches, and 2 points if there's no indication of search results count. 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 API failures, invalid URL inputs, empty search results, etc.) and provide friendly error prompts or recovery mechanisms. Check for try-catch blocks around API calls and proper error state management. 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. News categorization with visual indicators 2. Reading time estimation 3. Share functionality for individual news items 4. Dark mode support). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple search methods coexisting) 2. Function modules unrelated to news briefings (e.g., a built-in calculator) 3. Fancy effects that affect performance (e.g., excessive animations on news items). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating API services, UI components, and state management), use of Vue best practices (Composition API or Options API used consistently), and code organization. Check for proper naming conventions, comments, and TypeScript usage if applicable. Deduct 5 points if global state is mismanaged; deduct 5 points if the code has high duplication; deduct 5 points if there's no separation of concerns (mixing API calls with UI logic). 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). Check for proper responsive design using Vue's responsive classes or media queries. 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 API calls 2) Smooth transitions when filtering/searching news (using Vue transitions) 3) Clear visual feedback for user actions. Check for properly implemented animations that enhance rather than hinder the user experience. Deduct 5 points for missing loading indicators, 3 points for jarring transitions between states, and 5 points for unresponsive UI during data operations. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Blogs/Forums",
+  "difficulty": "easy"
+}

package/library/web_applications-business_website/automotive-lean-production-website.json

@@ -0,0 +1,68 @@
+{
+  "index": 335,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to make the code executable for demonstration. Develop a lean production website for the automotive industry and send me the code in HTML format.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core lean production management system fully implemented?",
+      "description": "Review whether the code implements essential lean production features for automotive industry: Kanban boards, JIT inventory management, value stream mapping, and production flow visualization. Score 0 if none implemented, 5 if basic visualization only, and 10 if comprehensive lean production tools are included.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are automotive industry-specific components implemented?",
+      "description": "Check whether the code includes automotive-specific elements such as vehicle assembly line tracking, part inventory management, quality control checkpoints, and defect tracking systems. Deduct 3 points for each missing critical component. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the dashboard for KPI monitoring and real-time production metrics implemented?",
+      "description": "Evaluate the implementation of real-time dashboards showing critical metrics like cycle time, throughput, defect rates, and OEE (Overall Equipment Effectiveness). Assess whether the visualizations use appropriate chart types and provide actionable insights. Deduct 5 points if real-time updates are missing, and 3 points if the metrics aren't industry-relevant. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the responsive design properly implemented for shop floor and management use?",
+      "description": "Check whether the website is usable across different devices (desktop monitors on factory floor, tablets for supervisors, mobile for managers). Test layout at 320px, 768px, and 1200px breakpoints. Deduct 3 points for each breakpoint with significant layout issues. 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 data loading errors, form validation, offline operation capability, 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 predictive maintenance alerts 2. AR-guided assembly instructions 3. Interactive process optimization simulations). 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 data visualization libraries) 2. Function modules unrelated to automotive production (e.g., a built-in game) 3. Fancy effects that affect performance (e.g., excessive animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating data/view/controller layers), performance optimization techniques (lazy loading, code splitting), and maintainability factors. Deduct 5 points if global variable pollution is found; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if no optimizations for industrial environments are implemented. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows industrial UI principles: 1) High contrast for factory visibility (black/white/primary color indicators) 2) Proper information hierarchy (critical alerts prominent) 3) Professional typography system (sans-serif fonts, large touch targets for gloved hands). Deduct 3 points for poor visual hierarchy, 5 points for low-contrast elements unsuitable for factory environments, and 5 points for information overload without clear organization. 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 industrial environment needs: 1) Fast loading time ≤ 2 seconds for critical interfaces 2) Clear state changes for machine status (running/idle/maintenance) 3) Accessible controls for touch/mouse usage with minimal training. Deduct 5 points for each key operation without feedback, 3 points for confusing state transitions, and 5 points for unintuitive navigation patterns. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Other-Business Web Application",
+  "difficulty": "hard"
+}

package/library/web_applications-business_website/electronic-product-homepage-intro-drivers-support.json

@@ -0,0 +1,68 @@
+{
+  "index": 1022,
+  "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 display purposes. Create a homepage for an electronic product that includes product introduction, driver downloads, and after-sales service.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the product introduction section comprehensively implemented?",
+      "description": "Review whether the code includes complete product showcase functionality through HTML/CSS/JavaScript, including product image carousel, detailed specifications table, feature highlights, and comparison charts. Score 0 if only basic text description is provided, 5 if product images and basic specs are included, and 10 if interactive product demos, 360-degree views, or video presentations are fully implemented with responsive design.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the driver download functionality properly structured?",
+      "description": "Check whether the download section includes automatic OS detection, version compatibility checking, download progress tracking, and file integrity verification. The implementation should support categorized downloads (by product model/OS/version) with search and filter capabilities. Deduct 5 points if no automatic OS detection, 3 points if missing download progress indication, and 2 points if no file verification mechanism. Full score requires secure download links with bandwidth optimization.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the after-sales service system well-designed and functional?",
+      "description": "Evaluate whether the service section includes multiple contact methods (live chat, ticket system, FAQ search), warranty status checker, and service request forms with file upload capability. Should implement real-time chat integration or callback request system. Deduct 5 points if only static contact information is provided, 3 points if missing interactive support features, and 2 points if no warranty/service status tracking functionality.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the complete navigation and information architecture constructed?",
+      "description": "Check whether the code includes intuitive site navigation, breadcrumb trails, internal search functionality, and logical information hierarchy. Should implement smooth scrolling between sections, anchor links, and mobile-responsive navigation menu. Deduct 5 points if navigation structure is confusing, 3 points if missing search functionality, and 2 points if mobile navigation is poorly implemented. Give 10 points if includes advanced features like predictive search or personalized content recommendations.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as broken image links, failed downloads, network timeouts, invalid form submissions, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should include form validation, graceful degradation for unsupported browsers, and proper error handling for AJAX requests, 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 user experience (e.g., 1. AR product visualization 2. AI-powered troubleshooting assistant 3. Interactive product configurator 4. Real-time system compatibility checker 5. Community forum integration). Add 3 points for each practical innovative feature implemented (maximum 10 points). Features should be functional, not just decorative.",
+      "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 with same purpose) 2. Feature bloat unrelated to electronic products (e.g., built-in games or social media feeds) 3. Excessive animations that slow down page performance (e.g., unnecessary parallax effects on every section). Deduct 3 points for each redundancy found, and directly deduct 10 points if 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 content/presentation/behavior layers), semantic HTML structure, CSS organization (using methodologies like BEM), and JavaScript best practices. Deduct 5 points if inline styles are extensively used or HTML lacks semantic structure; deduct 3 points if CSS is not organized or lacks vendor prefixes; deduct 2 points if JavaScript lacks proper event handling or memory leak prevention. The full score requires clean, maintainable code with proper documentation.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern web design principles: 1) Professional color scheme matching brand identity (consistent with tech industry standards) 2) Proper typography hierarchy (headings, body text, captions with appropriate contrast ratios ≥4.5:1) 3) Consistent spacing and grid system (following 8px baseline grid) 4) High-quality product imagery with proper optimization. Deduct 3 points for poor visual hierarchy, 5 points for accessibility issues (color contrast, font sizes), and 5 points for unprofessional or inconsistent branding. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the interactive elements conform to user experience best practices: 1) Page load time ≤ 3 seconds with progressive loading 2) Smooth transitions between sections (300-500ms duration) 3) Responsive hover states and click feedback ≤ 100ms 4) Intuitive form interactions with real-time validation 5) Mobile touch interactions optimized for finger navigation. Deduct 5 points for slow page loading, 3 points for missing interaction feedback, 3 points for poor mobile touch experience, and 2 points for jerky animations or transitions. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Business Website",
+  "difficulty": "medium"
+}

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

@@ -0,0 +1,68 @@
+{
+  "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

@@ -0,0 +1,68 @@
+{
+  "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

@@ -0,0 +1,68 @@
+{
+  "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

@@ -0,0 +1,68 @@
+{
+  "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"
+}