@getollie/cli 0.0.5 → 0.2.0

package/library/other-document_editor/vue-microsoft-word-like-editor.json

@@ -1,68 +0,0 @@
-{
-  "index": 1630,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the code you generate is executable for demonstration purposes. Implement an editor similar to Microsoft Word in Vue.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core text editing functionality fully implemented?",
-      "description": "Review whether the code implements essential text editing features using Vue: text input/deletion, cursor positioning, selection, copy/paste, and undo/redo. Check if contentEditable is properly utilized or if a custom implementation handles key events. Score 0 if basic text editing is missing, 5 if only simple text entry works, and 10 if all standard editing operations are fully implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the formatting capabilities comprehensive?",
-      "description": "Evaluate the text formatting features: font styles (bold, italic, underline), font family/size selection, text alignment, paragraph spacing, bullet/numbered lists, and indentation. Verify that formatting is preserved when copying or saving content. Deduct 2 points for each missing core formatting feature. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is document structure management properly implemented?",
-      "description": "Check if the editor supports document structure features like headings, sections, page breaks, headers/footers, and tables. Assess whether the document model maintains a proper hierarchical structure rather than just styling text. Deduct 3 points if headings/sections are missing, 3 points if page management is absent, and 4 points if table support is not implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are file operations and document state management properly handled?",
-      "description": "Review implementation of new document creation, opening existing documents, saving (with appropriate formats like .docx or HTML), auto-save functionality, and document state tracking. Check if the editor prompts users about unsaved changes. Deduct 3 points if save/load is missing, 3 points without auto-save, and 4 points without document state management. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code handles common edge cases (large documents, special characters, pasting from external sources, browser compatibility issues). Test if the editor prevents data loss during unexpected operations or crashes. Code with strong robustness should effectively handle these scenarios, giving 10 points. If robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Real-time collaboration 2. AI-powered writing suggestions 3. Voice-to-text input 4. Advanced find/replace with regex 5. Accessibility features like screen reader support). Add 2 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 functionality (e.g., multiple text selection mechanisms) 2. Function modules unrelated to word processing (e.g., built-in games or unrelated tools) 3. Fancy effects that affect performance (excessive animations or transitions). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review Vue component architecture (proper use of props/events/slots), state management approach, code reusability, and build process. Check for adherence to Vue best practices and performance optimization techniques. Deduct 3 points for improper component design, 3 points for inefficient state management, and 4 points if the code has poor maintainability. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the UI follows Microsoft Word-like design principles: 1) Clean, organized toolbar/ribbon interface 2) Proper use of icons and tooltips 3) Consistent spacing and alignment 4) Professional color scheme similar to Microsoft Office. Deduct 3 points for cluttered toolbars, 3 points for inconsistent visual language, and 4 points for poor overall layout resemblance to a professional word processor. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the editor provides smooth interactions: 1) Responsive typing with no perceptible lag 2) Smooth cursor movement and selection 3) Immediate visual feedback for formatting changes 4) Clean transitions between different view modes. Deduct 3 points for typing lag, 2 points for jerky scrolling/selection, 3 points for delayed formatting feedback, and 2 points for abrupt view transitions. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Other-Document Editor",
-  "difficulty": "medium"
-}

package/library/other-educational/five-elements-generation-destruction-e-language.json

@@ -1,68 +0,0 @@
-{
-  "index": 245,
-  "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. You are an experienced Chinese programming E-language (yiyu) developer. Below are the generation and destruction relationships of the Five Elements: \"Five Elements Generation: Wood generates Fire, Fire generates Earth, Earth generates Metal, Metal generates Water, Water generates Wood. Five Elements Destruction: Wood overcomes Earth, Earth overcomes Water, Water overcomes Fire, Fire overcomes Metal, Metal overcomes Wood.\" Please implement the Five Elements generation and destruction relationships in a Windows window program using E-language.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Five Elements core theory fully implemented?",
-      "description": "Review whether the code accurately implements both the Generation and Destruction relationships of the Five Elements (Wood, Fire, Earth, Metal, Water). Each element should have proper directional relationships with others. Score 0 if the core theory is missing, 5 if only one relationship type is implemented, and 10 if both Generation and Destruction relationships are fully represented with correct directional connections.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the Windows GUI implementation complete?",
-      "description": "Check whether the E-language code properly creates a Windows window with appropriate controls (buttons, labels, graphics) to display and interact with the Five Elements system. The window should have proper title, size, position, and event handling. Deduct 3 points if the window lacks basic properties, 5 points if controls are poorly organized, and 7 points if the GUI doesn't display at all. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the Five Elements visualization properly designed?",
-      "description": "Evaluate whether the Five Elements are visualized clearly with appropriate symbols/images and connection lines showing their relationships. The Generation and Destruction paths should be visually distinct (different colors, line styles, or arrows). Deduct 5 points if elements lack visual distinction, 3 points if relationship lines are confusing, and 5 points if the visualization is static with no interactive component. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there an interactive demonstration of the relationships?",
-      "description": "Assess whether the program allows users to interact with the Five Elements system (e.g., clicking on elements to show their Generation and Destruction relationships, animated demonstrations, or interactive simulations). Deduct 5 points if interaction is limited to static display, 3 points if only one relationship type can be demonstrated, and 5 points if there's no visual feedback during interaction. 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 resource loading failures, unexpected user inputs, window resizing issues, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Animated transitions between elements 2. Sound effects for generation/destruction interactions 3. Traditional Chinese styling or themes). 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 demonstrate the same relationship) 2. Function modules unrelated to the Five Elements theory (e.g., unnecessary game features) 3. Fancy effects that affect performance (e.g., excessive animations that slow down the program). 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/Five Elements logic/event handling), code structure, and E-language best practices. Deduct 5 points if global variable pollution is found or functions are not properly organized; deduct 5 points if the code duplicates logic unnecessarily; deduct 5 points if the code lacks comments or documentation. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows consistent principles) 3) Professional font system (appropriate text size and readability). 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 lag during animations, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Other-Educational",
-  "difficulty": "easy"
-}

package/library/other-financial_platform/mobile-h5-digital-currency-llm-data.json

@@ -1,68 +0,0 @@
-{
-  "index": 1281,
-  "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. Help me create an H5 page similar to Tencent's \"Yuanbao\" (digital currency) using a mobile development framework that can support rendering data returned from large language models.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the mobile H5 framework integration complete and optimized?",
-      "description": "Review whether the code properly integrates mobile-first frameworks (Vue3/React with mobile UI libraries like Vant/Ant Design Mobile), includes viewport meta configuration, touch event handling, and mobile-specific optimizations. Score 0 if basic mobile framework is missing, 5 if only basic responsive layout is implemented, and 10 if comprehensive mobile optimization including gesture handling, scroll optimization, and performance tuning is fully implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the large language model data rendering system robust and efficient?",
-      "description": "Check whether the implementation includes streaming data parsing, markdown/rich text rendering capabilities, code syntax highlighting, and real-time content updates. Must support incremental rendering for long responses and handle various LLM output formats (text, code blocks, lists, tables). Deduct 5 points if streaming rendering is missing, 3 points if content formatting is poor, and 3 points if loading states are not handled properly. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Does the digital currency UI accurately replicate Tencent Yuanbao's design system?",
-      "description": "Evaluate whether the interface closely matches Tencent Yuanbao's visual hierarchy, including proper card layouts, currency display formats, transaction lists, and interactive elements. Must include authentic color schemes, typography, and component styling that reflects professional fintech design standards. Deduct 5 points if visual consistency is poor, 3 points if layout proportions are incorrect, and 5 points if key UI components are missing or poorly implemented. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the chat/conversation interface optimized for LLM interactions?",
-      "description": "Check whether the code implements a conversation interface with proper message bubbles, typing indicators, auto-scroll behavior, and conversation history management. Must support various message types (text, images, files) and include features like message copying, regeneration, and conversation clearing. Deduct 5 points if conversation flow is awkward, 3 points if message display is inconsistent, and 3 points if interaction feedback is missing. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as API failures, network interruption, malformed LLM responses, touch gesture conflicts, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Voice input/output for LLM interactions 2. Smart content summarization and extraction 3. Multi-modal input support with image/document upload 4. Personalized conversation themes). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple message rendering systems coexisting) 2. Function modules unrelated to digital currency/LLM interaction (e.g., built-in games or irrelevant widgets) 3. Heavy animations that affect mobile performance (e.g., complex particle effects or excessive transitions). 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 API layer/UI components/state management), TypeScript usage, component reusability, and build optimization for mobile. Deduct 5 points if global state pollution is found or proper state management is not used; deduct 5 points if component coupling is too high; deduct 5 points if mobile build optimization (code splitting, lazy loading) is missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional fintech design standards?",
-      "description": "Evaluate whether the overall design follows modern fintech app principles: 1) Professional color scheme matching Tencent's brand guidelines 2) Proper mobile layout spacing (following 4px/8px grid system) 3) Clear information hierarchy with appropriate font sizes (≥16px for mobile readability, line height ≥1.4). Deduct 3 points for each cramped mobile layout element, 5 points for unprofessional color combinations, and 5 points for poor content readability on mobile devices. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the mobile interaction smooth and touch-optimized?",
-      "description": "Judge whether the mobile interactions conform to touch interface standards: 1) Touch feedback delay ≤ 100ms with proper haptic responses 2) Smooth scrolling and gesture recognition 3) Proper touch target sizes (≥44px) and spacing 4) Optimized for various screen sizes and orientations. Deduct 5 points for each unresponsive touch interaction, 3 points for scroll lag or gesture conflicts, and 5 points for poor accessibility on different mobile devices. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Other-Financial Platform",
-  "difficulty": "hard"
-}

package/library/other-frontend_development_tools/ai-frontend-development-scaffolding-tools.json

@@ -1,68 +0,0 @@
-{
-  "index": 272,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code examples whenever possible. I am referring to AI-integrated frontend development scaffolding tools like Vue and React.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the AI integration framework clearly defined and properly implemented?",
-      "description": "Check if the code defines a clear integration pattern for AI services with frontend frameworks. Score 0 if no integration architecture is defined, 5 if basic API calls are implemented without proper state management, and 10 if a comprehensive pattern (e.g., middleware, hooks, composables) is established that handles API calls, response processing, error states and loading indicators. The integration should follow the idiomatic patterns of the chosen framework (Vue/React).",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the AI service connections properly abstracted and reusable?",
-      "description": "Evaluate if the code properly abstracts AI service connections through service layers or custom hooks/composables. The abstraction should handle authentication, rate limiting, request formatting, and response normalization. Deduct 3 points if authentication is hardcoded, 3 points if there's no error handling strategy, and 2 points if response parsing is inconsistent. The implementation should enable reusability across components. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Does the scaffolding include proper state management for AI operations?",
-      "description": "Review the state management implementation for AI operations, checking for proper handling of loading states, error states, partial results, and caching strategies. For Vue, look for Pinia/Vuex integration or composable patterns; for React, check for Context API, Redux, or custom hooks. Deduct 3 points if loading states are missing, 3 points for inadequate error handling, and 4 points if no caching/memoization strategy exists. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there a comprehensive set of AI-enhanced UI components?",
-      "description": "Assess the implementation of AI-enhanced UI components such as predictive inputs, content generation tools, recommendation systems, or intelligent forms. Score 0 if no AI-enhanced components exist, 5 if basic components are implemented but lack customization options, and 10 if the code includes a diverse set of polished, reusable AI components with proper documentation and examples. Components should follow the design system of the chosen framework.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as API failures, rate limiting, token expiration, malformed AI 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. Real-time feedback during AI generation 2. Explainable AI visualizations 3. Progressive AI enhancement based on user interaction patterns). 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 AI integrations (e.g., multiple implementations of the same capability) 2. Function modules unrelated to the core AI integration (e.g., unnecessary analytics) 3. Heavyweight dependencies that could affect performance (e.g., including full ML libraries in the frontend). 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 AI service/UI components/application logic), unit test coverage for AI integrations, and build process optimization. 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 doesn't handle AI service environment variables securely. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the AI-integrated components follow modern design principles: 1) Consistent visual language with the rest of the application 2) Clear indication of AI-generated vs. user content 3) Professional loading and error states for AI operations. Deduct 3 points for inconsistent AI component styling, 5 points for confusing AI-generated content presentation, and 5 points for jarring transitions between AI and non-AI elements. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction with AI features smooth and seamless?",
-      "description": "Judge whether the AI interaction patterns conform to human perception characteristics: 1) Progressive feedback during long-running AI operations 2) Appropriate throttling/debouncing of AI requests 3) Clear visual indication of when AI is processing input. Deduct 5 points for each AI operation without feedback, 3 points for jarring UI updates when AI responses arrive, and 5 points for AI features that block the UI thread. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Other-Frontend Development Tools",
-  "difficulty": "hard"
-}

package/library/other-graphics_programming/desktop-heart-code-creation.json

@@ -1,68 +0,0 @@
-{
-  "index": 890,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate, expert responses. Be careful to ensure that the code you generate is executable and can be displayed. Desktop heart code creation.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the desktop heart basic animation implemented correctly?",
-      "description": "Evaluate whether the code implements a functional desktop heart animation with smooth transitions. Check if the heart shape is properly rendered using SVG/Canvas/CSS, and whether it includes proper color gradients or effects. Score 0 if no animation is present, 5 if the heart is static or has minimal animation, and 10 if it has fluid, attractive animations with proper easing functions.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Does the desktop heart follow proper window management?",
-      "description": "Check whether the code properly implements window management features such as 'always on top', proper z-index handling, transparency control, and clickthrough capabilities. Deduct 3 points if the window isn't set to stay on top, 4 points if it interferes with normal desktop interaction, and 3 points if it lacks proper transparency settings. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are interactive features implemented for the desktop heart?",
-      "description": "Assess whether users can interact with the heart through mouse hover, click, drag, or keyboard shortcuts. Check for event listeners and handlers. Deduct 5 points if no interaction is possible, 3 points if the interaction is limited to basic hover effects. Give 10 points if multiple interaction modes are implemented with proper feedback mechanisms.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is a customization system provided for the desktop heart?",
-      "description": "Evaluate whether the code provides options to customize the heart's appearance (color, size, effects), behavior (movement patterns, response to inputs), or includes themes/skins. Deduct 3 points for each major customization category missing. Score 10 if the customization is comprehensive with a settings interface.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as screen resolution changes, system theme switches, multi-monitor setups, etc.) and provide graceful error handling or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Dynamic reactions to system time/events 2. Subtle particle effects or weather animations 3. Integration with system notifications). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant event listeners that could cause memory leaks 2. Unnecessary rendering loops when static display would suffice 3. Excessive animations that drain system resources. Deduct 3 points for each redundancy found, and directly deduct 10 points if core performance is significantly affected by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (separating animation logic/rendering/interaction handling), performance optimization techniques, and resource management. Deduct 5 points if global state pollution is found; deduct 3 points if animation frames are not properly managed; deduct 5 points if the code uses excessive CPU/memory resources. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the desktop heart design meet professional aesthetic standards?",
-      "description": "Evaluate whether the visual design follows good principles: 1) Harmonious color palette with proper contrast 2) Appropriate size that doesn't distract from work 3) Smooth edges and proper anti-aliasing. Deduct 3 points for harsh color combinations, 3 points for pixelated or jagged rendering, and 4 points for disproportionate or oversized elements. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the desktop heart optimized for system resources?",
-      "description": "Judge whether the implementation is optimized for desktop integration: 1) CPU usage remains below 5% when idle 2) Memory footprint under 50MB 3) Proper cleanup on window close or refresh. Deduct 5 points for each resource leak identified, 3 points for noticeable system slowdown during animation, and 5 points for missing throttling/debouncing for intensive operations. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Other-Graphics Programming",
-  "difficulty": "medium"
-}

package/library/other-legal_analysis/user-agreement-terms-of-service.json

@@ -1,68 +0,0 @@
-{
-  "index": 1352,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. User Agreement\n\n**I. General Provisions**\n\n1. Before registering and using the service, users should carefully read this agreement to ensure they fully understand all terms. Unless you accept all terms of this agreement, you have no right to register, log in, or use the services covered by this agreement. Your registration, login, use, and other actions will be considered unconditional acceptance of all terms in this agreement.\n\n2. Unless otherwise explicitly specified, any new features or services launched by this product shall unconditionally be subject to this agreement.\n\n3. Our company reserves the right to modify the terms of this agreement at any time without notice. After our company modifies the agreement terms, if you do not accept the modified terms, please immediately stop using the services provided by this product. Continued use of the services provided by this product will be considered acceptance of the modified agreement.\n\n**II. User Registration**\n\n1. Users should agree to all terms of this agreement and complete the entire registration process according to the page prompts (minors should complete this with their legal guardian). When users click the \"Next\" button during the registration process, it indicates complete acceptance of all terms of this agreement.\n\n2. Users need to register an account for this product before using this service. The product account should be registered with a mobile phone number. Please use a mobile phone number that has not been bound to a product account and has not been banned by this product according to this agreement. This product may change the methods of account registration and binding according to user needs or product requirements without prior notice to users.\n\n3. Users must ensure the authenticity of all information required for service business during the use of this product's services. If problems arise due to inaccurate information, and the consequences resulting from these problems, our company bears no responsibility.\n\n4. When users register and use this product, we will collect personal information that can identify users so that the system can contact users when necessary or provide users with a better experience. Information collected by the system includes but is not limited to user's gender, age, date of birth, city of residence; the system agrees that the use of this information will be constrained by the protection of users' personal privacy information.\n\n**III. Service Content**\n\n1. The specific content of this service is provided by this product according to actual circumstances, including but not limited to users using this product. The product may change the services provided, and the content of services provided by this product may change at any time. Users will receive notification about service changes.\n\n2. Unless otherwise explicitly stated in this agreement, new products, new features, and new services launched by our company are all regulated by the terms of this agreement.\n\n**IV. Service Changes, Interruptions, or Termination**\n\n1. Given the special nature of network services (including but not limited to server stability issues, malicious network attacks, and other uncontrollable circumstances), users agree that our company has the right to interrupt or terminate part or all of the services at any time.\n\n2. Our company needs to regularly or irregularly inspect or maintain the systems or related equipment that provide services. If such circumstances cause service interruption within a reasonable time, our company does not need to bear any responsibility.\n\n3. If any of the following situations occur, our company has the right to change, interrupt, or terminate the services provided to users under this agreement at any time without any responsibility to users or any third party:\n   * According to legal regulations, users should submit true information, but the personal information provided by users is not authentic, or inconsistent with the registration information without providing reasonable proof;\n   * Users violate relevant laws and regulations or the provisions of this agreement;\n   * According to legal regulations or requirements of authorized agencies;\n   * For security reasons or other necessary circumstances.\n\n**V. User Personal Privacy Information Protection**\n\n1. In accordance with legal regulations, we will collect, use, and disclose your personal information in specific situations. The following terms describe how we collect, use, and disclose your personal information.\n\n2. Information Collection\n   * User provided: We will save information you directly provide. For example: We will record your registration information, customer service requests, or other communication records with us. Types of recorded information include: avatar, nickname, gender, date of birth, region, and other information you choose to provide. We collect, use, and disclose personal information to provide services to you through creating accounts, identifying users, responding to inquiries and emails, etc.\n   * Automatic collection: When you contact or use our services, we will automatically collect your information including: Log information (we record all log information when you use the service, including browser information, time of use, browsed web pages, IP address, and sources). We use various technologies to record information, including but not limited to: placing Cookies on your mobile device. Cookies are small data packets stored on your hardware, used to help us improve service quality and your user experience, understand which areas and functions are popular, and count traffic, etc.\n\n**VI. Content Standards**\n\n1. The content referred to in this standard is any content created, uploaded, copied, published, or distributed by users during the use of this service, including but not limited to account avatars, names, personalized signatures and other registration information and verification materials, or text, voice, pictures, graphics, sent messages, replies, and related linked pages, as well as other content generated by using this product account or service.\n\n2. Users pledge that when using this product's services, they must comply with relevant laws and regulations of the People's Republic of China, and must not use this product's services to create, upload, copy, publish, or distribute the following content:\n   * Content opposing the basic principles established by the constitution;\n   * Content endangering national security, leaking state secrets, subverting state power, or undermining national unity;\n   * Content harming national honor and interests;\n   * Content inciting ethnic hatred, ethnic discrimination, or undermining national unity;\n   * Content undermining national religious policies or promoting cults and feudal superstitions;\n   * Content spreading rumors, disrupting social order, or undermining social stability;\n   * Content spreading obscenity, pornography, gambling, violence, murder, terror, or abetting crime;\n   * Content insulting or defaming others, or infringing upon others' legitimate rights and interests;\n   * Content containing other information prohibited by laws and administrative regulations.\n\n3. Users must not use this product account or service to create, upload, copy, publish, or distribute the following content that interferes with the normal operation of this product or infringes on the rights and interests of other users or third-party partners:\n   * Content containing any sexual implications;\n   * Content containing insults, intimidation, or threats;\n   * Content containing harassment, spam, malicious information, or deceptive information;\n   * Content involving others' privacy, personal information, or data;\n   * Content containing other interference with the normal operation of this service or infringing on the legitimate rights and interests of other users or third parties.\n\n**VII. Usage Rules**\n\n1. Any content transmitted or published by users in or through this service does not reflect or represent, nor should it be deemed to reflect or represent, the views, positions, or policies of our company. Our company bears no responsibility for this.\n\n2. When using this product, users must comply with the provisions of relevant laws and regulations of the People's Republic of China, and agree not to use this product for any illegal or improper activities, including but not limited to the following actions:\n   * Interfering with or destroying relevant services, or any servers or networks connected to relevant services, or any policies, requirements, or regulations related to relevant services;\n   * Collecting and storing personal information about any other users for use in any prohibited activities;\n   * Intentionally or unintentionally violating any relevant Chinese laws, regulations, rules, ordinances, or other norms with legal effect.\n\n3. Users are fully responsible for the truthfulness, legality, harmlessness, accuracy, and validity of the information transmitted using this product account or service. Any legal responsibility related to the information disseminated by users shall be borne by the users themselves and has nothing to do with our company. If this causes damage to our company or third parties, users should provide compensation according to law.\n\n4. The services provided by this product may include advertisements. Users agree to display advertisements provided by this product and third-party suppliers and partners during use. Except as explicitly stipulated by laws and regulations, users should be responsible for transactions made based on such advertisement information. Our company bears no responsibility for transactions made by users based on such advertisement information or content provided by the aforementioned advertisers, or losses or damages suffered.\n\n5. To use this product, users must provide their own equipment necessary for accessing the international internet, including computers, mobile phones, and other devices related to accessing the international internet, and pay fees related to this service themselves.\n\n**VIII. Disclaimer**\n\n1. For content transmitted through this product service, our company does not guarantee the correctness, completeness, or quality of the aforementioned content. When accepting relevant services, users may encounter content that is unpleasant, inappropriate, or objectionable. Under no circumstances will our company be responsible for any content, including but not limited to any errors or omissions in any content and any loss or damage derived from them. Users' use of the above content shall be at their own risk.\n\n2. Users expressly agree that the risks and consequences of using this product will be entirely borne by themselves, and our company bears no responsibility to users. If users cause losses to any other third party due to violation of relevant laws, regulations, or any terms under this agreement, users agree to bear the resulting damage compensation liability.\n\n3. Our company respects and protects users' personal privacy rights. However, in cases of malicious network attacks and other uncontrollable circumstances leading to the leakage of users' privacy information, users agree that our company bears no responsibility.\n\n4. Our company bears no responsibility for losses caused by telecommunication system or internet network failures, computer failures, computer system problems, or any other force majeure reasons, but will strive to minimize the losses and impacts caused to users.\n\n**IX. Intellectual Property Statement**\n\n1. Any text, graphics, audio, video, and software (including but not limited to graphics, animations, audio, video, interface design, data, programs, code, documentation) included in this product service or other information or materials are protected by copyright law, trademark law, and other laws and regulations. Without written consent from the relevant rights holders, users may not use such information or materials in any way.\n\n2. This agreement does not grant users the right to use any trademarks, service marks, logos, domain names, and other distinctive brand features of this product. No one may use them without authorization (including but not limited to: illegally copying, distributing, displaying, mirroring, uploading, downloading). Otherwise, our company will pursue legal responsibility according to law.\n\n3. Except as explicitly allowed by this agreement, users may not modify, rent, lease, lend, sell, distribute, reproduce, create derivative works, or use any part or all of the content of this product for any commercial purpose in any form or by any means.\n\n**X. Applicable Law**\n\n1. The conclusion, execution, interpretation of this agreement and resolution of disputes shall be governed by Chinese law and under the jurisdiction of Chinese courts. If any part of the service terms conflicts with the laws of the People's Republic of China, then that part of the terms should be reinterpreted according to legal regulations. The invalidity or reinterpretation of partial terms does not affect the legal effect of the remaining terms.\n\n2. Users and our company unanimously agree to this agreement. If disputes arise during the implementation of this agreement, both parties should resolve them through friendly negotiation; if negotiation fails, either party may directly file a lawsuit with the local people's court.\n\n**XI. Other Provisions**\n\n1. The titles in this agreement are for convenience only and should be ignored when interpreting this agreement.\n\n2. The right to modify and the final interpretation of this agreement belongs to our company.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "User Registration Compliance Analysis",
-      "description": "Check whether the user registration section covers all necessary legal requirements and protections for both users and the company.Evaluate if the registration process includes age verification mechanisms, clear consent indicators, mobile verification logic, and information accuracy requirements. Deduct 3 points if any key registration safeguard is missing, 2 points if consent confirmation is ambiguous, and 3 points if minor registration handling is incomplete. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Privacy Policy Implementation Analysis",
-      "description": "Examine the privacy policy section for compliance with modern data protection regulations and transparency requirements.Review whether the agreement clearly states what personal data is collected, how it's used, stored, and shared. Check for clear opt-out mechanisms, data retention policies, and breach notification procedures. Deduct 3 points for each missing essential privacy element (data collection scope, usage purpose, sharing limitations), 2 points for vague data retention policies, and 5 points if user rights to access/delete data aren't mentioned. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Content Standards and Prohibited Activities Definition",
-      "description": "Analyze how thoroughly the agreement defines acceptable content and prohibited user activities.Evaluate whether the agreement comprehensively covers prohibited content categories (illegal content, harmful content, intellectual property violations) and includes examples for clarity. Check if enforcement mechanisms and penalties for violations are clearly defined. Deduct 3 points if prohibited content categories are insufficiently defined, 2 points if enforcement mechanisms are unclear, and 5 points if potential penalties aren't specified. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Service Changes and Termination Procedures",
-      "description": "Assess whether the agreement adequately addresses service modifications, interruptions, and termination scenarios.Review if the agreement clearly defines circumstances for service changes or termination, notification requirements to users, and what happens to user data after termination. Deduct 3 points if termination notification procedures are missing, 3 points if data handling after termination is unclear, and 4 points if force majeure provisions are insufficiently detailed. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Code Robustness",
-      "description": "Evaluate whether the code can handle common abnormal situations and provide friendly error prompts or recovery mechanisms.Code with strong robustness should be able to 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": "Innovative Features",
-      "description": "Check whether the code includes surprise features that enhance the experience.Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Redundant Features",
-      "description": "Strictly check three types of redundancy: redundant implementation of similar functions, unrelated function modules, and 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": "Legal Compliance and Jurisdiction",
-      "description": "Assess whether the agreement properly addresses legal frameworks, dispute resolution mechanisms, and jurisdictional issues.Review if the agreement specifies governing law, jurisdiction for disputes, arbitration or litigation procedures, and international considerations if applicable. Deduct 3 points if governing law is ambiguous, 3 points if dispute resolution mechanisms are incomplete, and 4 points if international jurisdictional considerations are missing where relevant. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Interface Vision Design Standards",
-      "description": "Evaluate whether the overall design follows modern design principles: harmonious color matching, proper layout spacing, and professional font system.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": "Clarity, Accessibility and Readability",
-      "description": "Evaluate how accessible and understandable the agreement is for average users, considering complex legal language and document structure.Check if the agreement uses plain language explanations alongside legal terms, includes section summaries, proper formatting with headings/subheadings, and visual elements to enhance understanding. Deduct 3 points for excessive legal jargon without explanations, 3 points for poor document structure, and 4 points for lack of emphasis on critical terms. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Other-Legal Analysis",
-  "difficulty": "medium"
-}

package/library/other-mini-program_development/card-style-left-right-waterfall-flow-mini-program.json

@@ -1,68 +0,0 @@
-{
-  "index": 1178,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the code you generate can be executed and displayed. Generate a source code for a card-style, left-right distributed waterfall flow mini-program.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the waterfall flow layout correctly implemented?",
-      "description": "Review whether the code accurately implements a left-right distributed waterfall layout where cards dynamically fill columns based on height. Check if items are properly assigned to the shortest column first. Score 0 if the layout is not implemented, 5 if it's basic but has alignment issues, and 10 if it handles dynamic content heights perfectly with proper column balancing.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the card component properly designed?",
-      "description": "Evaluate the card component structure, including content containers, image handling, text formatting, and responsive design. Check if cards handle various content types (images, text, etc.) with proper aspect ratios and formatting. Deduct 3 points if images aren't optimized, 3 points if text overflow isn't handled, and 3 points if cards lack proper padding/margins. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the infinite scrolling mechanism implemented?",
-      "description": "Check whether the code includes efficient lazy loading with intersection observers or scroll events for continuous content loading. Evaluate if it implements proper thresholds to trigger loading before reaching the bottom and includes loading indicators. Deduct 5 points for missing loading states, 5 points for performance bottlenecks during scrolling. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are mini-program specific features properly utilized?",
-      "description": "Assess whether the implementation leverages mini-program specific capabilities (like wx:for, setData optimizations for WeChat, or equivalent for other platforms). Check for platform adaptation code and proper component lifecycle management. Deduct 3 points for each missed optimization opportunity, 5 points if no platform-specific features are used at all. 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 when loading images, varying screen sizes, empty data sets, 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. Card animations on appearance 2. Pull-to-refresh with custom animations 3. Card interaction effects like swipe actions). 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 calculation of column heights 2. Unnecessary rerendering of the entire waterfall when only appending items 3. Heavy animations that affect scrolling performance. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core waterfall functionality is compromised by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating waterfall layout logic from data fetching and rendering), reusability of components, and code organization. Deduct 5 points if global state pollution is found; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no separation between business logic and UI components. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the card design follows modern design principles: 1) Consistent card styling with proper shadow depth 2) Proper content padding within cards (following the 8px or 16px grid) 3) Balanced negative space between cards. Deduct 3 points for inconsistent card sizes, 5 points for poor typography hierarchy, and 5 points for improper image handling (stretching/distortion). The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the scrolling performance and card loading animations conform to standards: 1) Smooth 60fps scrolling without jank 2) Graceful card appearance animations (fade/slide) under 300ms 3) No layout shifts when new content loads. Deduct 5 points for each visible frame drop during scrolling, 3 points for abrupt content appearances, and 5 points for content jumps during loading. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Other-Mini-Program Development",
-  "difficulty": "medium"
-}

package/library/other-mobile_app_development/develop-react-app-android-ios.json

@@ -1,68 +0,0 @@
-{
-  "index": 885,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code when possible. Help me develop a React app that is compatible with both Android and iOS.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the React Native cross-platform framework properly implemented?",
-      "description": "Review whether the code correctly uses React Native components and APIs that are compatible with both Android and iOS platforms. Check if platform-specific code is properly separated using Platform.OS or platform-specific file extensions (.android.js, .ios.js). Score 0 if using web-only React components, 5 if basic cross-platform components are used but lacks platform optimization, and 10 if comprehensive platform-specific adaptations are implemented with proper fallback mechanisms.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are native device features and permissions properly integrated?",
-      "description": "Evaluate whether the app correctly implements native device capabilities (camera, GPS, push notifications, file system access) with proper permission handling for both platforms. Check if the code includes runtime permission requests for Android 6+ and iOS privacy descriptions. Deduct 5 points if permissions are not properly requested, and 3 points if there's no graceful degradation when permissions are denied. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the navigation and routing system cross-platform compatible?",
-      "description": "Check whether the navigation implementation (React Navigation or similar) properly handles platform-specific navigation patterns - Android back button behavior, iOS swipe gestures, and platform-appropriate transitions. Evaluate if deep linking works on both platforms and if the navigation state is properly managed. Deduct 5 points if platform-specific navigation behaviors are not handled, and 3 points if deep linking is incomplete. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the build and deployment pipeline configured for both platforms?",
-      "description": "Review whether the project includes proper build configurations for both Android (gradle files, signing configs) and iOS (Xcode project, provisioning profiles). Check if automated build scripts, environment-specific configurations, and continuous integration/deployment are set up. Deduct 5 points if build configurations are incomplete for either platform, and 5 points if no automated deployment pipeline exists. 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, device orientation changes, app backgrounding/foregrounding, memory warnings, etc.) and provide friendly error boundaries or recovery mechanisms. Code with strong robustness should effectively handle these mobile-specific 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 impressive features that enhance the mobile experience (e.g., 1. Advanced gesture recognition 2. Offline-first data synchronization 3. Adaptive UI based on device capabilities 4. Integration with platform-specific features like Siri Shortcuts or Android Widgets). 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 platform-specific implementations (e.g., duplicate navigation logic for iOS/Android) 2. Unnecessary third-party libraries that increase bundle size 3. Over-engineered animations that impact performance on lower-end devices. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core mobile functionality is interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular architecture (proper separation of business logic, UI components, and platform-specific code), TypeScript usage, testing setup (unit tests, integration tests, E2E tests), and code organization. Deduct 5 points if there's poor state management or missing type definitions; deduct 5 points if test coverage is below 70%; deduct 5 points if the project structure doesn't follow React Native best practices. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface design meet mobile platform standards?",
-      "description": "Evaluate whether the UI follows platform-specific design guidelines (Material Design for Android, Human Interface Guidelines for iOS): 1) Appropriate touch target sizes (minimum 44pt for iOS, 48dp for Android) 2) Platform-consistent navigation patterns and visual elements 3) Proper handling of different screen densities and safe areas. Deduct 3 points for each non-platform-compliant UI element, 5 points for poor touch accessibility, and 5 points for inconsistent visual hierarchy. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the mobile interaction smooth and performant?",
-      "description": "Judge whether the app performance meets mobile standards: 1) App startup time ≤ 3 seconds 2) 60fps scrolling and animations with no frame drops 3) Proper memory management without leaks 4) Responsive touch interactions with appropriate haptic feedback. Deduct 5 points for each performance bottleneck identified, 3 points for janky animations or slow transitions, and 5 points for poor touch responsiveness. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Other-Mobile App Development",
-  "difficulty": "medium"
-}