@getollie/cli 0.0.1

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

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

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

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

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

package/library/other-mobile_app_development/harmonyos-button-navigation-view.json

@@ -0,0 +1,68 @@
+{
+  "index": 404,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and expert responses. Pay attention to ensure that the generated code is executable for demonstration. Add a view to a HarmonyOS page where clicking a button on the view will navigate to another page on the current page.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the HarmonyOS page structure correctly implemented?",
+      "description": "Review whether the code uses proper HarmonyOS framework structure with correct @Entry and @Component decorators, proper lifecycle methods (aboutToAppear, aboutToDisappear), and follows ArkTS syntax standards. Check if the page implements proper state management using @State, @Prop, or @Link decorators. Score 0 if basic page structure is missing, 5 if only basic structure exists without proper state management, and 10 if complete HarmonyOS page architecture is implemented with proper lifecycle and state management.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the button component and click event handling properly implemented?",
+      "description": "Evaluate whether the Button component is correctly implemented with proper onClick event handler, includes appropriate button styling and accessibility features. Check if the button follows HarmonyOS design guidelines for touch targets (minimum 44vp) and includes proper visual feedback states. Deduct 5 points if onClick handler is missing or incorrect, 3 points if button accessibility is not implemented, and 2 points if visual feedback states are missing. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the page navigation mechanism correctly implemented?",
+      "description": "Check whether the navigation uses proper HarmonyOS router mechanism (router.pushUrl or router.replaceUrl), includes correct page routing configuration, and handles navigation parameters properly. Verify if the target page is properly registered in module.json5 and navigation includes proper error handling. Deduct 5 points if router implementation is incorrect, 3 points if page registration is missing, and 2 points if error handling is not implemented. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the complete navigation lifecycle and data passing implemented?",
+      "description": "Evaluate whether the navigation includes proper data passing between pages using router parameters, implements proper page stack management, and includes back navigation handling. Check if the target page can receive and process passed parameters correctly, and if the navigation maintains proper page lifecycle. Deduct 5 points if data passing is not implemented, 3 points if page stack management is incorrect, and 2 points if back navigation is not handled properly. Give 10 points if fully implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as navigation failures, invalid parameters, page lifecycle errors, memory leaks, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should include try-catch blocks for navigation operations and proper error handling. Give 10 points if fully robust, 5 points if average robustness, and 0 points if no exception handling.",
+      "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 HarmonyOS user experience (e.g., 1. Custom page transition animations 2. Gesture-based navigation 3. Dynamic theme adaptation 4. Advanced state preservation during navigation). Add 3 points for each practical innovative feature implemented that leverages HarmonyOS capabilities (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant navigation implementations (e.g., multiple router calls for same action) 2. Unnecessary UI components unrelated to the navigation task 3. Over-complicated animations or effects that don't serve the core functionality. Deduct 3 points for each redundancy found, and directly deduct 10 points if core navigation functionality is interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review HarmonyOS project structure compliance, proper use of ArkTS language features, component modularity, and build configuration. Check if the code follows HarmonyOS coding standards, uses proper import/export statements, and includes appropriate file organization. Deduct 5 points if project structure doesn't follow HarmonyOS standards; deduct 5 points if code organization is poor; deduct 5 points if build configuration is incomplete. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet HarmonyOS design standards?",
+      "description": "Evaluate whether the design follows HarmonyOS design language principles: 1) Proper use of HarmonyOS color system and themes 2) Correct spacing using HarmonyOS grid system (8vp multiples) 3) Appropriate typography following HarmonyOS font specifications 4) Proper component sizing and touch targets (minimum 44vp). Deduct 3 points for each non-compliant visual element, 5 points for inconsistent design language usage, and 5 points for poor accessibility compliance. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the interactions conform to HarmonyOS UX guidelines: 1) Button press feedback ≤ 100ms 2) Page transition animations follow HarmonyOS motion design (300-400ms duration) 3) Proper loading states during navigation 4) Smooth 60fps performance during interactions. Deduct 5 points for each interaction without proper feedback, 3 points for janky animations or transitions, and 5 points for poor performance during navigation. Full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Other-Mobile App Development",
+  "difficulty": "medium"
+}

package/library/other-mobile_app_development/react-native-tableview-like-with-cell-selection.json

@@ -0,0 +1,68 @@
+{
+  "index": 1451,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure that the code you provide is executable and demonstrable. For an iOS native project, please implement a secondary page using React Native that resembles the native tableview, which can scroll up and down and respond to cell selection. Please provide the complete code.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is a complete React Native component implemented that resembles iOS UITableView?",
+      "description": "Evaluate whether the code implements a proper React Native component that visually and functionally resembles the native iOS UITableView. Check for proper section headers, row styling, separators, and overall visual fidelity to native iOS components. Score 0 if the component is missing or barely resembles a UITableView, 5 if basic structure is implemented but with visual inconsistencies, and 10 if it's virtually indistinguishable from a native implementation.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Does the implementation handle vertical scrolling properly?",
+      "description": "Verify that the React Native implementation properly handles vertical scrolling with iOS-like momentum, bounce effects, scroll indicators, and pull-to-refresh capabilities. Check if FlatList or ScrollView is configured correctly with appropriate performance optimizations. Deduct 3 points if scrolling performance is poor, 3 points if iOS-specific scroll behaviors are missing, and 5 points if scrolling functionality is broken. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is cell selection implemented with proper visual feedback?",
+      "description": "Examine whether cell selection provides the standard iOS highlight effect, proper onPress handlers, and appropriate visual feedback. Check if selection state is properly managed and if there's a haptic feedback implementation. Deduct 5 points if selection visual effect is missing or incorrect, 3 points if selection callback is not implemented, and 2 points if there's no deselection handling. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the integration between React Native and iOS native properly configured?",
+      "description": "Evaluate if the code includes proper React Native to iOS native bridge configuration, including navigation handling between native screens and React Native views. Check for proper module registration, event handling across the bridge, and configuration of the RCTRootView. Deduct 5 points for missing native module integration, 3 points for improper navigation handling, and 5 points for broken communication between native and React Native. 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 failures, network issues, state inconsistencies) and provide friendly error handling. Check for proper componentDidCatch implementations, error boundaries, and fallback UIs. 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. Swipe actions on cells 2. Interactive cell animations 3. Advanced section indexing like in native Contacts app). 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 state management or component re-rendering 2. Unnecessarily complex animations that affect performance 3. Overuse of third-party libraries for simple tasks. 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 component architecture (proper separation of concerns, stateless/stateful components), TypeScript/PropTypes usage, and code organization. Deduct 5 points if there's no component decomposition; deduct 5 points if prop validation is missing; deduct 5 points if styling approach is inconsistent or inline styles are overused. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet iOS design standards?",
+      "description": "Evaluate whether the design follows iOS Human Interface Guidelines: 1) Proper use of system colors 2) Standard font usage (SF Pro or equivalent) 3) Proper margins and layout constraints matching iOS defaults (typically 16pt horizontal margins). Deduct 3 points for each non-iOS-like visual element, 5 points for Android-looking components, and 5 points for improper use of navigation bars or toolbars. 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 iOS interaction standards: 1) Proper cell highlight timings 2) Standard iOS animation durations (typically 0.3s for most transitions) 3) Proper gesture handling that doesn't interfere with native gestures. Deduct 5 points for each janky animation, 3 points for incorrect timing in interactions, and 5 points for gesture conflicts with native iOS gestures. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Other-Mobile App Development",
+  "difficulty": "easy"
+}

package/library/other-mobile_app_development/taro-wechat-code-128-barcode-recognition.json

@@ -0,0 +1,68 @@
+{
+  "index": 1274,
+  "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 purposes. Please use Taro to quickly develop a WeChat Mini Program that can recognize Code 128 barcodes.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Taro environment configured correctly?",
+      "description": "Check whether the code includes proper Taro initialization, with correct dependencies (Taro core, React/Vue binding, WeChat Mini Program adapters) and configuration files (project.config.json, app.config.ts). Verify that the project structure follows Taro conventions and includes appropriate build scripts. Deduct 5 points if essential dependencies are missing, 3 points if configurations are incomplete. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the Code 128 barcode recognition algorithm implemented correctly?",
+      "description": "Evaluate the implementation of the Code 128 barcode decoding algorithm: check for proper handling of start/stop characters, checksum validation, and character set switching (Code 128A/B/C). The implementation should handle different barcode densities and have appropriate error correction. Score 10 points for a complete implementation with all Code 128 features, 5 points for basic recognition without full feature support, and 0 points if the core algorithm is missing or fundamentally flawed.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the camera access functionality properly implemented?",
+      "description": "Review whether the code correctly utilizes Taro's camera component or WeChat's camera API to access the device camera. Check for proper permission handling, preview frame rendering, and frame capturing for barcode processing. The implementation should include focus control, flash control options, and proper camera resolution settings for barcode scanning. Deduct 5 points if camera permissions aren't properly handled, 3 points if preview quality is poor. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the image processing pipeline efficient for barcode detection?",
+      "description": "Analyze the image processing approach: check for preprocessing steps (grayscale conversion, binarization, noise reduction), barcode localization algorithms, and optimization techniques. The implementation should handle various lighting conditions and scan angles. Evaluate processing speed and memory efficiency. Score 10 points for a comprehensive pipeline with optimizations, 5 points for basic functionality that works only in ideal conditions, and 0 points if critical processing steps are missing.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as camera permission denial, poor lighting conditions, partial or damaged barcodes, processing timeout) 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. Batch scanning capability 2. History of scanned codes 3. Scanning statistics and analytics 4. Augmented reality overlay for scan guidance). 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 image processing steps that slow down scanning 2. Function modules unrelated to barcode scanning (e.g., unnecessary social sharing features) 3. Heavy visual effects that affect scanning performance. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating camera handling/image processing/UI layers), unit test coverage for algorithm components, 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 WeChat Mini Program 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) Scan feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual scan guidance and feedback. Deduct 5 points for each operation without feedback, 3 points for laggy camera preview during scanning, and 5 points for confusing user interface during the scanning process. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Other-Mobile App Development",
+  "difficulty": "easy"
+}

package/library/other-mobile_app_development/uniapp-vue3-editor-example.json

@@ -0,0 +1,68 @@
+{
+  "index": 405,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and expert responses. Be sure to ensure that the code you generate is executable for demonstration purposes. Provide an example of using an editor in uniapp, using Vue 3 syntax.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is a complete and functional editor component implemented in UniApp with Vue 3?",
+      "description": "Assess whether the code provides a fully functional editor component that works within the UniApp framework using Vue 3 composition API. Check for essential editor features like text input/output, formatting controls, and cursor management. Score 0 if only boilerplate code is provided, 5 points if basic functionality is implemented but lacks key features, 10 points if the editor is fully functional with all core capabilities.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the editor properly integrated with UniApp's cross-platform capabilities?",
+      "description": "Evaluate whether the implementation correctly uses UniApp's APIs and components to ensure cross-platform compatibility (iOS, Android, H5, mini-programs). Check if platform-specific adaptations are handled appropriately. Deduct 3 points if only works on one platform type, deduct 5 points if platform-specific issues aren't addressed at all. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Does the implementation correctly use Vue 3 composition API features?",
+      "description": "Check if the code properly utilizes Vue 3 composition API (setup(), ref, reactive, computed, watch, lifecycle hooks, etc.) instead of Options API. Assess whether composables are created for reusable functionality. Deduct 5 points if Vue 3 specific features are missing, deduct 3 points if composition API is mixed improperly with Options API. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are editor features like rich text formatting and content management properly implemented?",
+      "description": "Review if the editor includes essential capabilities like text formatting (bold, italic, etc.), media insertion, undo/redo functionality, and content storage/retrieval. Check if the content can be saved and loaded properly. Deduct 3 points for each missing critical feature. 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 input errors, content loading failures, memory management) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. AI-assisted text completion 2. Collaborative editing capabilities 3. Custom toolbar extensions). 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 text processing utilities that do the same thing) 2. Function modules unrelated to the editor (e.g., built-in calculators, calendars) 3. Fancy effects that affect performance (e.g., excessive animations that slow down editing). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating editor logic/view/data handling layers), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the editor UI 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 editor interaction smooth and responsive?",
+      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Text input response ≤ 50ms 2) Formatting change transition between 100-300ms 3) Clear visual feedback when applying formatting. Deduct 5 points for each operation without feedback, 3 points for input lag during typing, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Other-Mobile App Development",
+  "difficulty": "easy"
+}