@getollie/cli 0.0.5 → 0.2.1

package/library/web_applications-education_learning/programming-teaching-website-with-editor.json

@@ -1,68 +0,0 @@
-{
-  "index": 687,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to make the generated code executable for demonstration. Design a programming teaching website that provides a code editor with real-time preview functionality. Users can write HTML, CSS, and JavaScript code online and view the running results on the same page in real time. The website needs to offer code highlighting, auto-completion, and syntax checking features. Implement a code saving function that allows users to create projects and return to continue editing at any time. The website should include a series of programming challenges, providing immediate feedback and suggestions for next steps in learning upon completion of each challenge.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the code editor implementation complete?",
-      "description": "Review whether the code implements a fully functional editor with key features: syntax highlighting (proper coloring for HTML, CSS, and JavaScript), auto-completion (suggests tags, properties, or functions), and syntax checking (real-time error detection). Score 0 if none of these features are implemented, 5 if only highlighting is present, and 10 if all three core features are properly implemented with accurate language detection.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the real-time preview functionality properly implemented?",
-      "description": "Evaluate the real-time preview mechanism. Check if changes in the editor are reflected in the preview without requiring manual refresh. Verify the preview works for all three languages (HTML structure, CSS styling, and JavaScript functionality). Deduct 3 points if there's a noticeable delay (>1s), 4 points if certain code types don't update properly, and 5 points if manual refresh is required. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the code saving and project management system functional?",
-      "description": "Check if the system allows users to save projects with appropriate metadata (title, description, timestamps), load previously saved projects, and automatically save changes (autosave). Evaluate if the solution includes proper state persistence (localStorage, database, or cloud storage). Deduct 4 points if there's no version history, 3 points if the autosave feature is missing, and 5 points if projects can't be organized or categorized. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are the programming challenges and learning path features implemented?",
-      "description": "Assess the quality and implementation of programming challenges. Check for: progression system with increasing difficulty, immediate feedback mechanisms that highlight errors or suggest improvements, and next-step learning recommendations. Deduct 4 points if challenges lack clear goals, 3 points if feedback is generic/unhelpful, and 5 points if there's no learning path progression. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid syntax input, network interruption during save, browser compatibility issues) and provide friendly error messages 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. Multiple view modes like split/side-by-side/preview only 2. Social sharing of code snippets 3. Themes and personalization options 4. Collaborative editing features). 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 code parsing libraries doing the same job) 2. Function modules unrelated to code editing and learning (e.g., a built-in game irrelevant to programming) 3. Fancy effects that affect performance (e.g., excessive animations that slow down the editor). 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/preview/storage components), unit test coverage, 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 is not optimized for performance. 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 (editor and preview panels should have adequate proportions) 3) Professional font system (monospace fonts for code, appropriate contrast). Deduct 3 points for each cramped visual element, 5 points for a glaring color combination, and 5 points for poor visual hierarchy between editor and preview sections. 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) Typing feedback with no perceptible lag (<50ms) 2) Smooth transitions between different views/panels 3) Clear visual feedback for actions like saving, error detection, or challenge completion. Deduct 5 points for editor lag during typing, 3 points for jarring transitions between editor and preview, and 5 points for confusing or missing action feedback. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Education/Learning",
-  "difficulty": "medium"
-}

package/library/web_applications-education_learning/pyside6-flashcards-random-sequential-reverse-order.json

@@ -1,68 +0,0 @@
-{
-  "index": 1218,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Make sure that the code you generate is executable when possible. Create a software similar to Anki using PySide6, but without the spaced repetition scheduling - only include options for random, sequential, or reverse order.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core flashcard review functionality implemented?",
-      "description": "Review whether the code includes the essential flashcard functions: adding cards, viewing cards, flipping/revealing answers, and marking cards as correct/incorrect. The implementation should handle different card types (text, images) and support basic styling. Score 0 if there's no functional review system, 5 if only basic text cards are supported, and 10 if it includes multiple card types with proper navigation.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the three required card ordering modes correctly implemented?",
-      "description": "Check if the application properly implements random, sequential, and reverse order card review modes. The random mode should use a proper randomization algorithm (not pseudo-random patterns), sequential should maintain deck order, and reverse should correctly invert the sequence. Deduct 3 points if any mode is missing, 5 points if the randomization has obvious patterns, and 3 points if mode switching causes state issues. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the card management system complete?",
-      "description": "Evaluate if the code provides comprehensive card management features including creating decks, adding/editing/deleting cards, organizing cards into categories/decks, and importing/exporting functionality. Deduct 5 points if editing capabilities are missing, 3 points if there's no export/import function, and 5 points if deck organization is insufficient. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is PySide6 utilized properly and effectively?",
-      "description": "Assess whether the implementation uses PySide6 components appropriately - proper use of widgets (QLabel, QPushButton, etc.), layouts (QVBoxLayout, QGridLayout, etc.), signals/slots mechanism for event handling, and style sheets for visual customization. Deduct 5 points for using direct Tkinter or other frameworks instead of PySide6, 3 points for poor widget hierarchy, and 3 points for not utilizing Qt's signal-slot mechanism. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid card formats, database corruption, file permission 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. Card statistics and progress tracking 2. Custom card templates or formatting 3. Light/dark mode support). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple ways to view statistics) 2. Function modules unrelated to flashcard review (e.g., a built-in calculator) 3. Fancy effects that affect performance (e.g., excessive animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating card logic/UI/data persistence layers), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance. Deduct 5 points for each operation without feedback, 3 points for visual after-images during transitions, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Education/Learning",
-  "difficulty": "easy"
-}

package/library/web_applications-education_learning/qingdao-subway-map-vue2-canvas.json

@@ -1,68 +0,0 @@
-{
-  "index": 882,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure that the code you generate is executable for display. Create a Qingdao subway map of all lines using Vue2 and Canvas, making special markings for transfer stations. The map should be zoomable and scalable, with a background image that can also be zoomed and scaled. Place it in a container that is 1006px high and 500px wide.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the complete Qingdao subway map implemented with accurate line representation?",
-      "description": "Review whether the code accurately implements all subway lines in Qingdao with correct routes, station names, and line colors. Verify that the data structure properly represents the network topology. Score 0 if only partial lines are implemented, 5 if all lines are present but with minor inaccuracies, and 10 if the complete subway network is precisely rendered with proper geographical relationships.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are transfer stations properly highlighted and differentiated?",
-      "description": "Check whether transfer stations are visually distinguished from regular stations (e.g., different shapes, sizes, colors, or special markers). Verify that the code handles the logic for identifying intersecting lines and appropriately renders these transfer points. Deduct 5 points if transfer stations aren't visually differentiated, 3 points if the differentiation is subtle or inconsistent. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the zoom and scale functionality properly implemented?",
-      "description": "Evaluate if the Vue2/Canvas implementation includes smooth zooming and scaling capabilities with proper event handling. Check for pinch-to-zoom support on touch devices, mouse wheel zoom for desktop, and intuitive scale controls. Deduct 5 points if zooming causes rendering artifacts, 3 points if zoom levels are limited or jerky. The code should maintain proper aspect ratios during scaling and preserve station relative positions. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the background image handling correct with zoom/scale synchronization?",
-      "description": "Verify that the background image scales and zooms in sync with the subway map overlay. Check if the image resolution adapts appropriately to different zoom levels without pixelation or blurring. Deduct 5 points if background-map synchronization is inconsistent during zoom operations, 3 points if image quality degrades significantly at higher zoom levels. Check that the background handles the required 1006px by 500px container constraints. 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 missing data, browser compatibility issues, window resizing, touch/mouse input variations, 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. Station information popups on hover/click 2. Animated train movements along routes 3. Interactive path finding between stations). 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 zoom implementations coexisting) 2. Function modules unrelated to subway visualization (e.g., a built-in weather widget) 3. Fancy effects that affect performance (e.g., unnecessary animations or visual effects). 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 Vue2 component architecture (such as separating map rendering/controls/data management), modular organization, and proper use of Vue lifecycle methods. Deduct 5 points if global state pollution is found or Vue best practices are not followed; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if canvas drawing operations are not optimized or if rendering performance suffers. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the subway map visualization follows transit map design principles: 1) Clear line distinction with appropriate color coding 2) Proper station labeling with legible typography (minimum 12px font size) 3) Professional layout with balanced station spacing and line angles (preferring 45° or 90° angles). Deduct 3 points for cluttered station labels, 5 points for poor color choices making lines difficult to distinguish, and 5 points for chaotic line routing that doesn't resemble standard transit map conventions. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the map interactions conform to user expectations: 1) Responsive zoom controls with <100ms feedback 2) Smooth pan/drag operations without jitter 3) Appropriate animation durations (200-400ms) for transitions. Deduct 5 points for each operation with noticeable lag, 3 points for jerky animations during interactions, and 5 points for controls that are difficult to discover or use. Test if the map behaves correctly within the specified 1006px × 500px container across different screen sizes. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Education/Learning",
-  "difficulty": "medium"
-}

package/library/web_applications-education_learning/random-name-caller-html-webpage-apple-style.json

@@ -1,68 +0,0 @@
-{
-  "index": 1803,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Ensure that the generated code is executable for demonstration. Help me create a random name-calling HTML webpage with the following requirements: it should only identify names, include a start button, a pause button, and a reset button. I should be able to upload an xlsx format document which the system can recognize for the name-calling activity. The reset function should be able to loop, and the webpage style should emulate the Apple official website's design.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core name-calling functionality correctly implemented?",
-      "description": "Evaluate whether the code properly implements random name selection from the uploaded list. Check if the randomization algorithm ensures each name has equal probability of being selected and if the system prevents repetition until all names have been called. Score 0 if the core functionality is missing, 5 if basic random selection works but with flaws, 10 if the implementation is complete with proper randomization and non-repetition control.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Does the Excel (xlsx) file upload and parsing feature work properly?",
-      "description": "Assess the file upload mechanism and xlsx parsing implementation. Check if the code handles different Excel formats, properly extracts name data from various column structures, and provides clear feedback on successful upload. Deduct 5 points if the parser only works with specific Excel structures, 3 points if error handling is missing for malformed files, and 2 points if there's no visual feedback during the upload process. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are all required control buttons (start, pause, reset) implemented with proper functionality?",
-      "description": "Verify that all three buttons (start, pause, reset) are implemented with correct functionality. Start should begin the name-calling process, pause should temporarily halt it while preserving state, and reset should clear the current session and allow restarting. Deduct 3 points for each button with incorrect behavior, 2 points if the buttons lack proper state management (e.g., disabling start when already running). The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the looping reset function properly implemented?",
-      "description": "Examine whether the reset function allows for proper looping through all names and restarting the process. Check if the system tracks which names have already been called and can properly reset this tracking. Score 0 if reset doesn't work, 5 if it resets but doesn't properly prepare for a new complete cycle, and 10 if it fully implements the looping functionality with clear state management.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid file uploads, empty name lists, rapid button clicking, browser compatibility 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. Animation effects when displaying selected names 2. Sound effects for selection process 3. Statistics tracking of selected names 4. Custom configuration options for selection speed or display style). 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 reset the system) 2. Function modules unrelated to name-calling (e.g., unnecessary analytics) 3. Fancy effects that affect performance (e.g., excessive animations that slow down the interface). 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/file handling components), code organization, and maintainability. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there are no comments or documentation for key functions. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet Apple's design standards?",
-      "description": "Evaluate whether the design authentically replicates Apple's official website aesthetic: 1) Clean, minimalist design with ample white space 2) San Francisco or similar font family with proper typography hierarchy 3) Subtle shadows and refined animations 4) High-quality imagery and icons. Deduct 3 points for each element that doesn't match Apple's design language, 5 points for inconsistent styling across components, and 5 points for poor responsive design. 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 Apple's interaction patterns: 1) Subtle animations for state changes 2) Smooth transitions between different states 3) Immediate visual feedback for user actions 4) Accessible interface with proper focus states. Deduct 5 points for choppy animations, 3 points for delayed response to user input, and 5 points for missing transition effects between name selections. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Education/Learning",
-  "difficulty": "easy"
-}

package/library/web_applications-education_learning/react-jupyter-notebook-renderer.json

@@ -1,68 +0,0 @@
-{
-  "index": 1536,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the generated code is executable for demonstration purposes. Could you write a React page that renders a Jupyter notebook page?",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the basic Jupyter notebook structure properly implemented in React?",
-      "description": "Check if the code implements the core Jupyter notebook components: cells (code, markdown), cell execution counter, toolbar, and menu bar. Score 0 if essential components are missing, 5 if basic components are present but lack proper styling or hierarchy, and 10 if the structure closely resembles an actual Jupyter notebook with proper component organization.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the different cell types (code, markdown, raw) properly implemented with correct rendering?",
-      "description": "Evaluate whether the code implements different cell types with appropriate editors and renderers. Code cells should have syntax highlighting, markdown cells should render formatted text, and there should be UI to switch between cell types. Deduct 3 points if syntax highlighting is missing, 4 points if markdown rendering is incorrect, and 5 points if cell type switching is not implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is there a working code execution simulation mechanism?",
-      "description": "Check if the React implementation includes a mechanism to simulate code execution (even if through mock data or simple JavaScript evaluation). The implementation should show execution status (running/completed), display output (text, graphs, tables), and handle execution errors. Deduct 5 points if execution status indicators are missing, and 5 points if output rendering is not implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are cell manipulation functions (add, delete, move, run) implemented?",
-      "description": "Verify if the implementation includes common cell operations like adding new cells, deleting cells, moving cells up/down, and running cells individually or in sequence. Each missing function deducts 2.5 points. Check if keyboard shortcuts are implemented for these operations (an additional 2.5 points for complete shortcuts). The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common edge cases (such as invalid cell content, long outputs, rendering errors) and provides appropriate error handling. Code with strong robustness should effectively handle these edge cases, giving 10 points. If error handling is basic, give 5 points, and if no error handling exists, 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 simulation 2. Dark/light theme switching 3. Cell folding/collapsing). 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 execute code) 2. Function modules unrelated to Jupyter notebooks (e.g., unrelated dashboard elements) 3. Fancy effects that affect performance (e.g., unnecessary animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review component structure (proper separation of concerns), state management approach, use of React hooks and patterns, and code reusability. Deduct 5 points if global state is poorly managed; deduct 3 points if React anti-patterns are found; deduct 2 points if there's significant code duplication. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the design follows Jupyter's familiar interface standards while maintaining modern UI principles: 1) Proper color scheme matching Jupyter's palette 2) Clear visual hierarchy with consistent spacing 3) Appropriate typography (code vs. text differentiation). Deduct 3 points for each significant deviation from Jupyter's recognizable interface, 4 points for poor visual hierarchy, and 3 points for inconsistent typography. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the interactions match the expected Jupyter experience: 1) Smooth cell focus transitions 2) Appropriate feedback when executing code 3) Intuitive keyboard navigation between cells. Deduct 3 points for laggy cell transitions, 4 points for missing execution feedback, and 3 points for unintuitive keyboard navigation. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Education/Learning",
-  "difficulty": "hard"
-}

package/library/web_applications-education_learning/real-time-convertible-bond-market-info-webpage.json

@@ -1,68 +0,0 @@
-{
-  "index": 324,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Be careful to ensure that the generated code is executable for demonstration. Create a small webpage that displays real-time convertible bond market information.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the real-time data fetching mechanism implemented correctly?",
-      "description": "Review if the code implements proper API calls for fetching convertible bond data, includes error handling for API failures, and utilizes appropriate polling intervals or WebSocket connections. Score 0 if there's no real-time data implementation, 5 if basic polling is implemented without error handling, and 10 if it includes proper error handling, connection management, and fallback mechanisms.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Does the webpage display all essential convertible bond information?",
-      "description": "Check if the display includes critical bond metrics such as current price, yield to maturity, conversion premium, underlying stock performance, and bond rating. Deduct 2 points for each missing essential data point. The display should also include search/filter capabilities and sorting options. Give 10 points if all essential information is present with proper organization.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is there appropriate data visualization for bond performance?",
-      "description": "Evaluate whether the code implements visual elements (charts, graphs) for bond price history, yield curves, or comparison with underlying stocks. Deduct 5 points if there are no visualizations, 3 points if visualizations are present but lack interactivity (zoom, hover details). Give full 10 points if visualizations are interactive, responsive, and professionally rendered.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the code implement alerting or notification features?",
-      "description": "Assess if the webpage includes functionality for price alerts, conversion opportunity notifications, or significant event indicators. Score 0 if no alerting features exist, 5 if basic visual indicators are present without configuration options, and 10 if comprehensive, configurable alert systems are implemented with both visual and audio notifications.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as API failure, data format changes, network interruption, 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. Automated bond recommendation system 2. Market sentiment analysis visualization 3. Customizable dashboard layouts). 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 sort the same data) 2. Function modules unrelated to bond markets (e.g., cryptocurrency trackers) 3. Fancy effects that affect performance (e.g., excessive animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating data fetching/visualization/user interface layers), code reusability, and performance 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 there's no consideration for performance with large datasets. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the financial data display follows industry design principles: 1) Clear information hierarchy with important metrics emphasized 2) Proper use of color to indicate market movements (e.g., red for down, green for up) 3) Professional typography with adequate contrast ratios. Deduct 3 points for cluttered layouts, 5 points for misleading visual representations of data, and 5 points for poor readability of critical information. 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 financial application standards: 1) Real-time updates without page flicker 2) Smooth transitions for changing data values 3) Clear loading states during data fetching. Deduct 5 points for jarring data refreshes, 3 points for lack of visual feedback during user interactions, and 5 points for confusing navigation between different bond information views. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Education/Learning",
-  "difficulty": "hard"
-}

package/library/web_applications-education_learning/recipe-search-system-frontend-backend-java.json

@@ -1,68 +0,0 @@
-{
-  "index": 776,
-  "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 when possible. Hello, I want to create a recipe search system, designing the frontend, backend, and algorithmic models. For the algorithmic models, I'm using Python and already have mature model code. Now I need your help designing the frontend and backend code, with requirements for rapid development and Java as the backend language.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the recipe search frontend interface well designed?",
-      "description": "Review whether the frontend code implements an intuitive and user-friendly interface with proper search inputs, filters (ingredient, cuisine type, preparation time, etc.), and result display. Check for responsive design that works across devices. Score 0 if the interface is not implemented, 5 if only basic search functionality exists, and 10 if the interface includes advanced filtering, auto-suggestions, and a visually appealing recipe card display.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the Java backend architecture properly implemented?",
-      "description": "Evaluate the backend architecture for proper API design, RESTful principles, dependency injection, and service layer organization. Check if proper design patterns are used and if the code follows Java best practices. Deduct 5 points if there's no clear separation of concerns, 3 points if error handling is missing, and 3 points if data validation is inadequate. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the recipe search algorithm effectively integrated with the backend?",
-      "description": "Check whether the Python algorithmic model is properly integrated with the Java backend (using technologies like REST API, gRPC, or JNI). Verify the integration implementation includes proper serialization/deserialization, error handling, and efficient data transfer. Deduct 5 points if integration is unreliable or inefficient, 3 points if there's no caching mechanism for frequently accessed recipes. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the data persistence layer properly designed?",
-      "description": "Evaluate the database schema design for recipe storage, user preferences, and search history. Check for proper indexing to support fast searches, ORM implementation, and query optimization. Deduct 5 points if there's no consideration for recipe metadata (like ingredients, nutritional info), 3 points if there's no transaction management, and 3 points if there's no database migration strategy. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid search inputs, API failures, algorithm exceptions, 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. Personalized recipe recommendations 2. Nutritional analysis visualization 3. Interactive cooking steps with timers). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple search implementations) 2. Function modules unrelated to recipe search (e.g., a built-in weather widget) 3. Fancy effects that affect performance (e.g., excessive animations during recipe display). 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/business logic/data layers), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 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) Search results appear within 300ms 2) Recipe card animations controlled between 300-500ms 3) Clear visual feedback during search operations. Deduct 5 points for each operation without feedback, 3 points for visual stuttering during search result loading, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Education/Learning",
-  "difficulty": "medium"
-}

package/library/web_applications-education_learning/runnable-laboratory-website-template.json

@@ -1,68 +0,0 @@
-{
-  "index": 741,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable for demonstration purposes. Create a runnable laboratory website template.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the laboratory website structure properly implemented?",
-      "description": "Evaluate whether the HTML structure follows semantic markup principles with proper use of <header>, <nav>, <main>, <section>, <footer> tags. Check if the document includes essential meta tags for SEO and responsive design. Deduct 3 points if semantic HTML5 elements are not used; deduct 3 points if the responsive meta viewport tag is missing; deduct 4 points if the document structure is illogical. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the navigation and information architecture well-designed?",
-      "description": "Assess whether the site includes essential laboratory website sections (Home, Research, Team, Publications, Resources, Contact) with logical organization and clear navigation paths. Navigation should be accessible both on desktop and mobile. Deduct 3 points if key sections are missing; deduct 4 points if the navigation is not responsive; deduct 3 points if there's no visual indication of current page. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Does the website feature research presentation capabilities?",
-      "description": "Check whether the website includes components for showcasing research projects, such as project cards, publication listings, or interactive demonstrations. There should be clear categorization of research areas and filtering capabilities. Deduct 5 points if research presentation is limited to static text; deduct 5 points if there's no visual representation of research data/projects. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there functionality for team member profiles and academic credentials?",
-      "description": "Evaluate if the website includes a team section with proper profile structure (photo, name, position, research interests, contact info, publications links). Check if there's a hierarchical representation of lab leadership, researchers, students, and alumni. Deduct 3 points if profiles lack academic credentials; deduct 4 points if the layout doesn't scale for different team sizes; deduct 3 points if there's no individual profile page template. 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 missing images, varied content lengths, browser compatibility issues, etc.) and provide graceful fallbacks. Check for form validation if contact forms are implemented. Deduct 3 points for each unhandled edge case; deduct 5 points if the site breaks completely on older browsers. The full score is 10 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. Interactive research visualizations 2. Publication citation generator 3. Lab equipment booking system 4. Research timeline). 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 navigation systems) 2. Function modules unrelated to academic/laboratory context 3. Fancy effects that affect performance (e.g., excessive animations that distract from content). 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 layout/components/styles), CSS organization (consistent naming convention, preferably BEM or similar), and JavaScript structure (event delegation, proper module pattern). Deduct 5 points if global CSS/JS pollution is found; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no separation of concerns. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional academic standards?",
-      "description": "Evaluate whether the design follows professional academic website standards: 1) Clean, credible appearance with appropriate whitespace 2) Academic color scheme (typically institutional colors or conservative palettes) 3) Professional typography (readable fonts, proper hierarchy, line length ≤80 characters). Deduct 3 points for cluttered layouts, 5 points for inappropriate color schemes for academic context, and 5 points for poor typography that reduces readability. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the site accessible and responsive across devices?",
-      "description": "Judge whether the website meets accessibility standards (WCAG) and performs well across device sizes: 1) Proper contrast ratios and focus states 2) Responsive layouts that adapt from mobile to desktop 3) Content readability on all screen sizes. Deduct 4 points for non-responsive layouts; deduct 3 points for each major accessibility violation (missing alt text, keyboard navigation issues); deduct 3 points for poor performance on mobile devices. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Education/Learning",
-  "difficulty": "easy"
-}