@getollie/cli 0.0.1

package/library/management_systems-file_management/wechat-mini-program-pdf-download-forward.json

@@ -0,0 +1,68 @@
+{
+  "index": 1364,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the code you generate is executable. Help me provide an example of a WeChat Mini Program that downloads and forwards PDF files stored in the cloud.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the PDF download functionality fully implemented?",
+      "description": "Review whether the code accurately implements the PDF download functionality through wx.downloadFile API, handling large files with proper timeout settings, progress indicators, and error handling. Score 0 if core download logic is not implemented, 5 if basic download works but lacks progress tracking, and 10 if it includes complete download management with retry mechanisms and network condition adaptations.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the file forwarding mechanism properly implemented?",
+      "description": "Evaluate whether the code uses wx.shareFileMessage API correctly to forward PDF files to chats, including proper file selection UI, preview before sharing, and handling of sharing cancellations. Deduct 5 points if only direct forwarding is supported without preview, and 3 points if sharing failures aren't properly handled. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is cloud storage integration correctly implemented?",
+      "description": "Check whether the code implements proper integration with cloud services (WeChat Cloud or third-party services like OSS), includes authentication mechanisms, handles token expiration, and implements proper file listing with pagination. Deduct 5 points if cloud authentication is hardcoded, 3 points if file listing doesn't support searching/filtering. Give 10 points if fully implemented with proper security measures.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is file management functionality comprehensive?",
+      "description": "Assess whether the code includes complete file management features such as listing downloaded PDFs, deleting local files to free up space, file categorization, and search functionality. Deduct 5 points if only basic listing is provided, 3 points if file metadata (size, date) isn't displayed. The full score is 10 points for comprehensive file management with sorting options.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as broken downloads, network interruption, insufficient storage space, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should effectively handle edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. PDF thumbnail generation 2. Background downloading when app is inactive 3. Batch downloading/sharing). 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 file download methods coexisting) 2. Function modules unrelated to PDF handling (e.g., built-in video player) 3. Fancy effects that affect performance (e.g., complex animations during downloads). 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 network/storage/UI layers), component reuse, and proper code organization according to Mini Program standards. 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 custom components aren't properly encapsulated. 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 WeChat design guidelines: 1) Proper use of WeChat's design language 2) Consistent spacing and layout 3) Clear visual hierarchy for file operations. Deduct 3 points for each UI element that doesn't match WeChat's style, 5 points for overcomplicated interfaces, and 5 points for poor information hierarchy. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the dynamic effects conform to Mini Program interaction standards: 1) Responsive download buttons 2) Smooth transitions between screens 3) Clear visual feedback during operations. Deduct 5 points for each operation without feedback, 3 points for laggy animations, and 5 points for unintuitive navigation patterns. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-File Management",
+  "difficulty": "medium"
+}

package/library/management_systems-frontend_backend_platforms/academic-conference-submission-system-with-review.json

@@ -0,0 +1,68 @@
+{
+  "index": 657,
+  "question": "You are a code expert. Please utilize your professional knowledge to generate accurate, expert responses. Pay attention to ensuring that the generated code is executable for demonstration. Create an academic conference submission system that supports PDF paper uploads and automatically checks format standards (pages, font, margins). Provide double-blind review mode (automatically removing author information) and support submission progress tracking on PC/mobile devices. Include plagiarism detection status indicators (integrated with Turnitin).",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the PDF upload and format validation system fully implemented?",
+      "description": "Review whether the code implements a complete PDF upload system with format validation functionalities including page count verification, font detection, and margin measurement. Score 0 if uploading is not implemented, 5 if only basic PDF uploading works without validation, and 10 if all format validations are correctly implemented with appropriate error handling and user feedback.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the double-blind review mode properly implemented?",
+      "description": "Evaluate whether the system can automatically detect and remove author information from submitted PDFs and metadata. Check for watermarking or other techniques to track submissions anonymously. Deduct 5 points if author information is only removed from metadata but not from the PDF content, and 3 points if the anonymization process is not reversible for administrators. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the submission tracking functionality cross-platform compatible?",
+      "description": "Check whether the tracking system works seamlessly on both PC and mobile devices with responsive design principles. Verify if real-time status updates are implemented and if the interface adapts appropriately to different screen sizes. Deduct 3 points for non-responsive designs, 5 points if mobile experience is significantly degraded, and 5 points if real-time updates require manual refresh. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the Turnitin plagiarism detection integration implemented effectively?",
+      "description": "Assess whether the code includes proper API integration with Turnitin or similar plagiarism detection services, with appropriate status indicators and result visualization. Check for proper error handling if the service is unavailable and queueing mechanisms for large volumes. Deduct 5 points if only mock integration is provided, and 3 points if results are not clearly visualized. 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 corrupted PDFs, network interruptions, session timeouts, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. AI-based format suggestion engine 2. Automated citation validation 3. Interactive submission workflow with progress visualization). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple file validation systems coexisting) 2. Function modules unrelated to academic submission (e.g., extensive social sharing features) 3. Fancy effects that affect performance (e.g., heavy animations on status pages). 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 storage/validation/UI 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 appropriate for academic contexts (professional, understated palette) 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 inappropriate color combinations, 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) Upload feedback with clear progress indicators 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance for multi-step submission process. Deduct 5 points for each operation without feedback, 3 points for jarring state transitions, and 5 points for confusing navigation in the submission workflow. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "medium"
+}

package/library/management_systems-frontend_backend_platforms/account-management-interface-design.json

@@ -0,0 +1,68 @@
+{
+  "index": 1695,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Main Interface Design\n\n## Account Overview:\nDisplays key information including current account equity, available margin, floating profit/loss, etc.\n\n## Manual Operation Area:\nIncludes buy and sell buttons, position closing options, and features for setting stop-loss and take-profit points.\n\n## Parameter Configuration Area:\nAllows users to set parameters such as the percentage of funds used for each trade, initial position size, etc.\n\n## Daily Profit/Loss Chart:\nGraphically displays daily profit and loss information.\n\n## 2. Functional Modules\n\n### 2.1 Account Equity Monitoring\n- Use AccountEquity() to retrieve account equity.\n- Regularly refresh (e.g., every minute) and update on the interface.\n\n### 2.2 Automatic Position Size Adjustment\n- Users input specific equity-to-position size ratios in the parameter configuration area (e.g., $300 corresponds to 0.01 lot).\n- Calculate appropriate lot size based on current account equity and set ratios, applying this calculation when opening new orders.\n\n### 2.3 Manual Order Placement and Closure\n- Provide intuitive interface for users to select currency pair, lot size, stop-loss/take-profit levels before clicking \"Buy\" or \"Sell\" to place orders.\n- Display a list of all open positions, allowing users to close positions directly by clicking on the corresponding order.\n\n### 2.4 Daily Profit/Loss Statistics\n- Record total daily profit/loss at the end of each day (determined by server time).\n- Use chart libraries (such as standard chart functions in MQL4) to draw daily profit/loss graphs.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the trading interface dashboard fully implemented?",
+      "description": "Review whether the code accurately implements all four main interface sections: Account Overview (displaying current equity, available margin, floating P&L), Manual Operation Area (buy/sell buttons, position closing, stop-loss/take-profit settings), Parameter Configuration Area (fund percentage settings, initial position size), and Daily P&L Chart (graphical display). Score 0 if core dashboard components are missing, 5 if only basic account display is implemented, and 10 if all interface sections are fully functional with real-time data updates.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the account equity monitoring and automatic position size adjustment system properly implemented?",
+      "description": "Check whether the AccountEquity() function is correctly integrated with regular refresh mechanisms (every minute updates), and verify if the automatic position size calculation based on equity-to-lot ratios is accurately implemented. The system should dynamically calculate appropriate lot sizes based on current account equity and user-defined ratios (e.g., $300 = 0.01 lot). Deduct 5 points if real-time monitoring is missing, and 3 points if position size calculations are inaccurate. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the manual trading functionality and order management system complete?",
+      "description": "Evaluate whether the manual order placement system includes intuitive currency pair selection, lot size input, stop-loss/take-profit level settings, and functional buy/sell execution. Verify if the open positions list displays all active orders with direct closing capabilities. The system should handle order validation and execution feedback. Deduct 5 points if order placement lacks proper validation, and 3 points if position management interface is incomplete. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the daily profit/loss statistics and charting system properly constructed?",
+      "description": "Check whether the code includes complete daily P&L recording mechanism based on server time, with proper data storage and retrieval. Verify if chart libraries (MQL4 standard chart functions or equivalent) are correctly implemented to visualize daily profit/loss trends. The system should maintain historical data and provide clear graphical representation. Deduct 5 points if data persistence is not implemented, and 3 points if charting functionality is missing. Give 10 points if fully implemented with historical data management.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common trading platform exceptions (such as connection failures, invalid order parameters, insufficient margin, market closure, etc.) and provide appropriate error handling or recovery mechanisms. Code with strong robustness should effectively handle these edge cases and provide clear user feedback, giving 10 points. If robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that enhance trading experience?",
+      "description": "Check whether the code includes valuable features that improve trading efficiency (e.g., 1. Risk management alerts and notifications 2. Trading performance analytics and insights 3. Customizable dashboard layouts 4. Advanced order types like trailing stops). 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 trading functions (e.g., multiple order placement logics coexisting) 2. Function modules unrelated to trading operations (e.g., built-in games or entertainment features) 3. Excessive visual effects that affect trading performance (e.g., complex animations during critical operations). Deduct 3 points for each redundancy found, and directly deduct 10 points if core trading 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 trading logic/UI/data management layers), error handling coverage, and code maintainability. Deduct 5 points if global state pollution is found or proper design patterns are not used; deduct 5 points if code duplication rate is too high (over 30%); deduct 5 points if the architecture is not scalable for future trading features. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the trading interface design meet professional financial software standards?",
+      "description": "Evaluate whether the overall design follows professional trading platform principles: 1) Clear information hierarchy with critical trading data prominently displayed 2) Consistent color coding for profit (green) and loss (red) indicators 3) Professional typography with readable font sizes (≥12px for numbers, ≥14px for text) 4) Proper spacing and alignment following grid systems. Deduct 3 points for each confusing visual element, 5 points for unprofessional color schemes, and 5 points for cluttered layout that hinders trading decisions. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the trading interaction smooth and responsive?",
+      "description": "Judge whether the trading operations meet professional standards: 1) Order execution feedback ≤ 50ms 2) Real-time data updates without lag 3) Clear confirmation dialogs for critical actions (order placement/closure) 4) Intuitive navigation between different trading functions. Deduct 5 points for each operation without immediate feedback, 3 points for delayed data updates that could affect trading decisions, and 5 points for unclear or hard-to-access critical trading functions. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "medium"
+}

package/library/management_systems-frontend_backend_platforms/admin-page-data-view-edit-api-monitoring.json

@@ -0,0 +1,68 @@
+{
+  "index": 1484,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to generate executable code whenever possible. I need an admin page that allows for convenient viewing and editing of all data, and where all detailed API requests can be monitored from the admin interface.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the admin dashboard UI fully implemented?",
+      "description": "Review whether the code properly implements a complete admin dashboard with navigation, layout components, and organized sections for data management. Score 0 if only HTML structure without functionality, 5 if basic UI elements are present but lack cohesiveness, and 10 if a professional and complete dashboard interface is implemented with responsive design considerations.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the data viewing/editing functionality complete?",
+      "description": "Evaluate whether the implementation includes data tables/lists with pagination, sorting, filtering capabilities, and proper CRUD operations. Check if form validation is implemented for data editing. Deduct 3 points if pagination is missing, 3 points if sorting/filtering is absent, and 5 points if edit/delete operations are incomplete. Full score requires complete data management with optimistic UI updates.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the API monitoring system implemented effectively?",
+      "description": "Check whether the code includes real-time API request monitoring with detailed information (method, URL, payload, headers, response, timing). Deduct 5 points if monitoring is not real-time, 3 points if request details are insufficient, and 3 points if there's no way to filter or search through requests. Full score requires complete monitoring with visual indicators for request status and performance metrics.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is authentication and authorization properly implemented?",
+      "description": "Review whether the admin interface implements secure login, role-based permissions, and protection against unauthorized access. Check for token management, session handling, and proper API security. Deduct 5 points for missing authentication, 3 points for lack of role-based controls, and 3 points for security vulnerabilities (XSS, CSRF). Give 10 points only if the implementation follows security best practices.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as network failures, invalid inputs, server errors, 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. Dark/light theme switching 2. Dashboard customization 3. Export options for data/logs 4. Visualizations of API performance). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple data fetching methods) 2. Function modules unrelated to admin purposes (e.g., end-user features) 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/UI/API layers), component reusability, state management approach, and code organization. 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 clear architecture. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the admin interface follows modern design principles: 1) Consistent color scheme appropriate for data-heavy interfaces 2) Proper layout spacing with clear visual hierarchy 3) Professional typography with adequate contrast ratios for readability. Deduct 3 points for cluttered layouts, 5 points for poor information hierarchy, and 5 points for accessibility issues. 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 professional admin interface standards: 1) Immediate feedback for user actions 2) Loading states for asynchronous operations 3) Smooth transitions between views without jarring changes. Deduct 5 points for missing loading indicators, 3 points for laggy interactions, and 5 points for confusing navigation patterns. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "easy"
+}

package/library/management_systems-frontend_backend_platforms/admin-profile-and-password-management.json

@@ -0,0 +1,68 @@
+{
+  "index": 239,
+  "question": "You are a Code Expert\n\n**Admin Information Management**\n\nThis module provides comprehensive management functionality for administrator accounts, supporting dynamic updates of basic information such as username and phone number through Vue.js form components. Password modification uses SHA-256 encryption storage and enforces complexity validation (minimum 8 characters including upper/lowercase letters and special characters). The backend verifies operation permissions through JWT tokens, and all sensitive operations (such as password resets) are recorded in detailed audit logs (including operation time, IP address, and action type) to ensure traceability of operations. How to implement this with:\n\n```html\n<template>\n    <div class=\"profile-container\">\n        <el-card class=\"profile-card\" shadow=\"hover\">\n            <template #header>\n                <div class=\"card-header\">\n                    <span class=\"card-title\">Admin Information</span>\n                </div>\n            </template>\n\n            <el-form :model=\"profileForm\" :rules=\"rules\" ref=\"profileFormRef\" label-width=\"100px\">\n                <el-form-item label=\"Username\" prop=\"adminName\">\n                    <el-input v-model=\"profileForm.adminName\" disabled />\n                </el-form-item>\n                <el-form-item label=\"Nickname\" prop=\"nickName\">\n                    <el-input v-model=\"profileForm.nickName\" />\n                </el-form-item>\n                <el-form-item label=\"Phone Number\" prop=\"phoneNumber\">\n                    <el-input v-model=\"profileForm.phoneNumber\" />\n                </el-form-item>\n                <el-form-item>\n                    <el-button type=\"primary\" @click=\"handleUpdate\" :loading=\"updateLoading\">\n                        <el-icon><Check /></el-icon>\n                        <span>Save Changes</span>\n                    </el-button>\n                    <el-button type=\"text\" @click=\"showPasswordDialog\" class=\"password-button\">\n                        <el-icon><Lock /></el-icon>\n                        <span>Change Password</span>\n                    </el-button>\n                </el-form-item>\n            </el-form>\n        </el-card>\n\n        <!-- Password Change Dialog -->\n        <el-dialog v-model=\"passwordDialogVisible\" title=\"Change Password\" width=\"30%\" class=\"password-dialog\">\n            <el-form :model=\"passwordForm\" :rules=\"passwordRules\" ref=\"passwordFormRef\">\n                <el-form-item label=\"Current Password\" prop=\"oldPassword\">\n                    <el-input v-model=\"passwordForm.oldPassword\" show-password />\n                </el-form-item>\n                <el-form-item label=\"New Password\" prop=\"newPassword\">\n                    <el-input v-model=\"passwordForm.newPassword\" show-password />\n                </el-form-item>\n                <el-form-item label=\"Confirm Password\" prop=\"confirmPassword\">\n                    <el-input v-model=\"passwordForm.confirmPassword\" show-password />\n                </el-form-item>\n            </el-form>\n            <template #footer>\n                <el-button @click=\"passwordDialogVisible = false\">Cancel</el-button>\n                <el-button type=\"primary\" @click=\"handlePasswordSubmit\">Confirm Change</el-button>\n            </template>\n        </el-dialog>\n    </div>\n</template>\n\n<script>\n    import { ref, onMounted } from 'vue';\n    import { ElMessage } from 'element-plus';\n    import { Check, Lock } from '@element-plus/icons-vue';\n    import { getAdminInfo, updateAdmin, updateAdminPassword } from '@/api/admin';\n\n    export default {\n        setup() {\n            // Admin information form\n            const profileForm = ref({\n                adminName: '',\n                nickName: '',\n                phoneNumber: '',\n            });\n\n            // Password change form\n            const passwordForm = ref({\n                oldPassword: '',\n                newPassword: '',\n                confirmPassword: '',\n            });\n\n            // Form validation rules\n            const rules = ref({\n                nickName: [\n                    { required: true, message: 'Please enter a nickname', trigger: 'blur' },\n                    { min: 2, max: 18, message: 'Nickname length must be between 2 and 18 characters', trigger: 'blur' },\n                ],\n                phoneNumber: [\n                    { required: true, message: 'Please enter a phone number', trigger: 'blur' },\n                    {\n                        pattern: /^1[3-9]\\d{9}$/,\n                        message: 'Please enter a valid phone number',\n                        trigger: 'blur',\n                    },\n                ],\n            });\n\n            // Password change validation rules\n            const passwordRules = ref({\n                oldPassword: [\n                    { required: true, message: 'Please enter current password', trigger: 'blur' },\n                ],\n                newPassword: [\n                    { required: true, message: 'Please enter new password', trigger: 'blur' },\n                    {\n                        pattern: /^(?=.*[A-Za-z])(?=.*\\d)[A-Za-z\\d]{8,20}$/,\n                        message: 'Password must contain letters and numbers, length 8-20 characters',\n                        trigger: 'blur',\n                    },\n                ],\n                confirmPassword: [\n                    { required: true, message: 'Please confirm new password', trigger: 'blur' },\n                    {\n                        validator: (rule, value, callback) => {\n                            if (value !== passwordForm.value.newPassword) {\n                                callback(new Error('The two passwords do not match'));\n                            } else {\n                                callback();\n                            }\n                        },\n                        trigger: 'blur',\n                    },\n                ],\n            });\n\n            // Form references\n            const profileFormRef = ref(null);\n            const passwordFormRef = ref(null);\n\n            // Password dialog visibility status\n            const passwordDialogVisible = ref(false);\n\n            // Loading status\n            const updateLoading = ref(false);\n\n            // Get admin information\n            const fetchAdminInfo = async () => {\n                try {\n                    const res = await getAdminInfo();\n                    if (res.code === 200) {\n                        profileForm.value = res.data;\n                    } else {\n                        ElMessage.error('Failed to get information');\n                    }\n                } catch (error) {\n                    console.error('Failed to get information:', error);\n                    ElMessage.error('Failed to get information');\n                }\n            };\n\n            // Handle save changes\n            const handleUpdate = async () => {\n                try {\n                    updateLoading.value = true;\n                    await profileFormRef.value.validate();\n                    const res = await updateAdmin(profileForm.value);\n                    if (res.code === 200) {\n                        ElMessage.success('Changes saved successfully');\n                    } else {\n                        ElMessage.error('Failed to save changes');\n                    }\n                } catch (error) {\n                    console.error('Failed to save changes:', error);\n                    ElMessage.error('Failed to save changes');\n                } finally {\n                    updateLoading.value = false;\n                }\n            };\n\n            // Show password change dialog\n            const showPasswordDialog = () => {\n                passwordDialogVisible.value = true;\n            };\n\n            // Handle password change submission\n            const handlePasswordSubmit = async () => {\n                try {\n                    await passwordFormRef.value.validate();\n                    const res = await updateAdminPassword({\n                        oldPwd: passwordForm.value.oldPassword,\n                        newPwd: passwordForm.value.newPassword,\n                    });\n                    if (res.code === 200) {\n                        ElMessage.success('Password changed successfully');\n                        passwordDialogVisible.value = false;\n                        passwordFormRef.value.resetFields();\n                    } else {\n                        ElMessage.error(res.message || 'Failed to change password');\n                    }\n                } catch (error) {\n                    console.error('Failed to change password:', error);\n                    ElMessage.error(error.response?.data?.message || 'Failed to change password');\n                }\n            };\n\n            // Get admin information when component is mounted\n            onMounted(() => {\n                fetchAdminInfo();\n            });\n\n            return {\n                profileForm,\n                passwordForm,\n                rules,\n                passwordRules,\n                profileFormRef,\n                passwordFormRef,\n                passwordDialogVisible,\n                updateLoading,\n                handleUpdate,\n                showPasswordDialog,\n                handlePasswordSubmit,\n                Check,\n                Lock,\n            };\n        },\n    };\n</script>\n\n<style scoped>\n    .profile-container {\n        display: flex;\n        justify-content: center; /* Horizontal center */\n        align-items: center; /* Vertical center */\n        height: 100vh; /* Make container fill the entire viewport height */\n        background: linear-gradient(135deg, #f5f7fa, #c3cfe2);\n    }\n\n    .profile-card {\n        width: 800px;\n        margin: 0 auto;\n        border-radius: 10px;\n        box-shadow: 0 4px 12px rgba(0, 0, 0, 0.1);\n        background: #fff;\n    }\n\n    .card-header {\n        display: flex;\n        justify-content: space-between;\n        align-items: center;\n    }\n\n    .card-title {\n        font-size: 18px;\n        font-weight: bold;\n        color: #303133;\n    }\n\n    .password-button {\n        margin-left: 10px;\n    }\n\n    .password-dialog {\n        border-radius: 10px;\n    }\n\n    .password-dialog .el-dialog__header {\n        border-bottom: 1px solid #eee;\n        padding-bottom: 10px;\n    }\n\n    .password-dialog .el-dialog__footer {\n        border-top: 1px solid #eee;\n        padding-top: 10px;\n    }\n</style>\n```\n\nThis is my profile center frontend, \n\n```html\n<template>\n    <div class=\"login-container\">\n        <div class=\"login-box\">\n            <div class=\"login-header\">\n                <span class=\"login-title\">Admin Management System</span>\n            </div>\n            <el-form\n                    :model=\"loginForm\"\n                    :rules=\"rules\"\n                    ref=\"loginFormRef\"\n                    label-width=\"80px\"\n                    class=\"login-form\"\n            >\n                <el-form-item label=\"Account\" prop=\"adminName\">\n                    <el-input\n                            v-model=\"loginForm.adminName\"\n                            placeholder=\"Please enter username\"\n                            clearable\n                    ></el-input>\n                </el-form-item>\n                <el-form-item label=\"Password\" prop=\"password\">\n                    <el-input\n                            v-model=\"loginForm.password\"\n                            type=\"password\"\n                            placeholder=\"Please enter password\"\n                            show-password\n                            clearable\n                    ></el-input>\n                </el-form-item>\n                <el-form-item>\n                    <el-button\n                            type=\"primary\"\n                            style=\"width: 100%\"\n                            @click=\"handleLogin\"\n                            :loading=\"loading\"\n                    >\n                        Login\n                    </el-button>\n                </el-form-item>\n                <div class=\"login-footer\">\n                    <span>Don't have an account?</span>\n                    <el-link type=\"primary\" @click=\"goToRegister\">Register</el-link>\n                </div>\n            </el-form>\n        </div>\n    </div>\n</template>\n\n<script setup>\n    import { ref } from 'vue';\n    import { useRouter } from 'vue-router';\n    import { ElMessage } from 'element-plus';\n    import { login } from '@/api/admin'; // Import login API\n\n    const router = useRouter();\n\n    // Login form data\n    const loginForm = ref({\n        adminName: '',\n        password: '',\n    });\n\n    // Form validation rules\n    const rules = ref({\n        adminName: [\n            { required: true, message: 'Please enter username', trigger: 'blur' },\n            { min: 5, max: 18, message: 'Username length must be between 5 and 18 characters', trigger: 'blur' },\n        ],\n        password: [\n            { required: true, message: 'Please enter password', trigger: 'blur' },\n            { min: 3, max: 20, message: 'Password length must be between 3 and 20 characters', trigger: 'blur' },\n        ],\n    });\n\n    // Form reference\n    const loginFormRef = ref(null);\n\n    // Login button loading status\n    const loading = ref(false);\n\n    // Handle login\n    const handleLogin = async () => {\n        try {\n            // Validate form\n            await loginFormRef.value.validate();\n            loading.value = true;\n\n            // Call login API\n            const res = await login({\n                adminName: loginForm.value.adminName,\n                password: loginForm.value.password,\n            });\n            if (res.code === 200) {\n                // Login successful, save token and redirect to home page\n                localStorage.setItem('token', res.token); // Save token\n                router.push('/index/activity'); // Redirect to home page\n            } else {\n                ElMessage.error(res.msg || 'Login failed, please check your account or password');\n            }\n        } catch (error) {\n            console.error('Login failed:', error);\n            ElMessage.error('Login failed, please try again later');\n        } finally {\n            loading.value = false;\n        }\n    };\n\n    // Navigate to registration page\n    const goToRegister = () => {\n        router.push('/register');\n    };\n</script>\n\n<style scoped>\n    .login-container {\n        display: flex;\n        justify-content: center;\n        align-items: center;\n        height: 100vh;\n        background-color: #f6f6f6;\n    }\n\n    .login-box {\n        width: 400px;\n        padding: 30px;\n        background-color: #fff;\n        border-radius: 8px;\n        box-shadow: 0 2px 12px 0 rgba(0, 0, 0, 0.1);\n    }\n\n    .login-header {\n        text-align: center;\n        margin-bottom: 20px;\n    }\n\n    .login-title {\n        font-size: 24px;\n        font-weight: bold;\n        color: #333;\n    }\n\n    .login-form {\n        margin-top: 20px;\n    }\n\n    .login-footer {\n        text-align: center;\n        margin-top: 20px;\n        color: #666;\n    }\n</style>\n```\n\nThis is the login frontend, \n\n```html\n<template>\n    <div class=\"register-container\">\n        <div class=\"register-box\">\n            <div class=\"register-header\">\n                <span class=\"register-title\">Register New Account</span>\n            </div>\n            <el-form\n                    :model=\"registerForm\"\n                    :rules=\"rules\"\n                    ref=\"registerFormRef\"\n                    label-width=\"80px\"\n                    class=\"register-form\"\n            >\n                <el-form-item label=\"Username\" prop=\"adminName\">\n                    <el-input\n                            v-model=\"registerForm.adminName\"\n                            placeholder=\"Please enter username\"\n                            clearable\n                    ></el-input>\n                </el-form-item>\n                <el-form-item label=\"Nickname\" prop=\"nickName\">\n                    <el-input\n                            v-model=\"registerForm.nickName\"\n                            placeholder=\"Please enter nickname\"\n                            clearable\n                    ></el-input>\n                </el-form-item>\n                <el-form-item label=\"Password\" prop=\"password\">\n                    <el-input\n                            v-model=\"registerForm.password\"\n                            type=\"password\"\n                            placeholder=\"Please enter password\"\n                            show-password\n                            clearable\n                    ></el-input>\n                </el-form-item>\n                <el-form-item label=\"Confirm Password\" prop=\"confirmPassword\">\n                    <el-input\n                            v-model=\"registerForm.confirmPassword\"\n                            type=\"password\"\n                            placeholder=\"Please re-enter password\"\n                            show-password\n                            clearable\n                    ></el-input>\n                </el-form-item>\n                <el-form-item label=\"Phone Number\" prop=\"phoneNumber\">\n                    <el-input\n                            v-model=\"registerForm.phoneNumber\"\n                            placeholder=\"Please enter phone number\"\n                            clearable\n                    ></el-input>\n                </el-form-item>\n                <el-form-item>\n                    <el-button\n                            type=\"primary\"\n                            style=\"width: 100%\"\n                            @click=\"handleRegister\"\n                            :loading=\"loading\"\n                    >\n                        Register\n                    </el-button>\n                </el-form-item>\n                <div class=\"register-footer\">\n                    <span>Already have an account?</span>\n                    <el-link type=\"primary\" @click=\"goToLogin\">Login</el-link>\n                </div>\n            </el-form>\n        </div>\n    </div>\n</template>\n\n<script setup>\n    import { ref } from 'vue';\n    import { useRouter } from 'vue-router';\n    import { ElMessage } from 'element-plus';\n    import { register } from '@/api/admin'; // Import registration API\n\n    const router = useRouter();\n\n    // Registration form data\n    const registerForm = ref({\n        adminName: '',\n        nickName: '',\n        password: '',\n        confirmPassword: '',\n        phoneNumber: '',\n    });\n\n    // Form validation rules\n    const rules = ref({\n        adminName: [\n            { required: true, message: 'Please enter username', trigger: 'blur' },\n            { min: 5, max: 18, message: 'Username length must be between 5 and 18 characters', trigger: 'blur' },\n        ],\n        nickName: [\n            { required: true, message: 'Please enter nickname', trigger: 'blur' },\n            { min: 2, max: 18, message: 'Nickname length must be between 2 and 18 characters', trigger: 'blur' },\n        ],\n        password: [\n            { required: true, message: 'Please enter password', trigger: 'blur' },\n            { min: 6, max: 20, message: 'Password length must be between 6 and 20 characters', trigger: 'blur' },\n        ],\n        confirmPassword: [\n            { required: true, message: 'Please re-enter password', trigger: 'blur' },\n            {\n                validator: (rule, value, callback) => {\n                    if (value !== registerForm.value.password) {\n                        callback(new Error('The two passwords do not match'));\n                    } else {\n                        callback();\n                    }\n                },\n                trigger: 'blur',\n            },\n        ],\n        phoneNumber: [\n            { required: true, message: 'Please enter phone number', trigger: 'blur' },\n            {\n                pattern: /^1[3-9]\\d{9}$/,\n                message: 'Please enter a valid phone number',\n                trigger: 'blur',\n            },\n        ],\n    });\n\n    // Form reference\n    const registerFormRef = ref(null);\n\n    // Registration button loading status\n    const loading = ref(false);\n\n    // Handle registration\n    const handleRegister = async () => {\n        try {\n            // Validate form\n            await registerFormRef.value.validate();\n            loading.value = true;\n\n            // Call registration API\n            const res = await register({\n                adminName: registerForm.value.adminName,\n                nickName: registerForm.value.nickName,\n                password: registerForm.value.password,\n                phoneNumber: registerForm.value.phoneNumber,\n            });\n            if (res.code === 200) {\n                ElMessage.success('Registration successful, please login');\n                router.push('/'); // Redirect to login page\n            } else {\n                ElMessage.error(res.msg || 'Registration failed, please try again later');\n            }\n        } catch (error) {\n            console.error('Registration failed:', error);\n            ElMessage.error('Registration failed, please try again later');\n        } finally {\n            loading.value = false;\n        }\n    };\n\n    // Navigate to login page\n    const goToLogin = () => {\n        router.push('/login');\n    };\n</script>\n\n<style scoped>\n    .register-container {\n        display: flex;\n        justify-content: center;\n        align-items: center;\n        height: 100vh;\n        background-color: #f6f6f6;\n    }\n\n    .register-box {\n        width: 400px;\n        padding: 30px;\n        background-color: #fff;\n        border-radius: 8px;\n        box-shadow: 0 2px 12px 0 rgba(0, 0, 0, 0.1);\n    }\n\n    .register-header {\n        text-align: center;\n        margin-bottom: 20px;\n    }\n\n    .register-title {\n        font-size: 24px;\n        font-weight: bold;\n        color: #333;\n    }\n\n    .register-form {\n        margin-top: 20px;\n    }\n\n    .register-footer {\n        text-align: center;\n        margin-top: 20px;\n        color: #666;\n    }\n</style>\n```\n\nThis is the registration frontend, but I'm wondering if administrator registration should be more complex, or if there shouldn't be registration at all, \n\n```java\npackage com.example.graduation_project.controller;\n\n\nimport com.example.graduation_project.pojo.entire.Admin;\nimport com.example.graduation_project.service.AdminService;\nimport com.example.graduation_project.utils.JwtUtils;\nimport com.example.graduation_project.utils.Result;\nimport com.example.graduation_project.utils.ThreadLocalUtil;\nimport org.springframework.beans.factory.annotation.Autowired;\nimport org.springframework.validation.annotation.Validated;\nimport org.springframework.web.bind.annotation.*;\n\nimport javax.servlet.http.HttpServletRequest;\nimport java.util.Map;\n\n@RestController\n@RequestMapping(\"/admin\")\npublic class AdminController {\n    @Autowired\n    private AdminService adminService;\n\n    @PostMapping(\"/login\")\n    public Result login(@Validated @RequestBody Admin admin){\n        String adminName = admin.getAdminName();\n        String adminPassword = admin.getPassword();\n        Admin queryAdmin = adminService.adminLogin(adminName,adminPassword);\n        if (queryAdmin!=null && queryAdmin.getAdminName().equals(adminName) && queryAdmin.getPassword().equals(adminPassword) && \"1\".equals(queryAdmin.getAuthority())){\n            String token = JwtUtils.createToken(queryAdmin.getAdminId(),\"admin\");\n            return Result.success(\"Login successful\", (Long) null, token);\n        }else{\n            return Result.error(\"Login failed\");\n        }\n        /*String token = JwtUtils.createToken(queryAdmin.getAdminId());\n        System.out.println(\"The login token is:\"+token);\n        if(token!=null)\n            return Result.success(token);\n        else\n            return Result.error(\"Incorrect username or password\",null);*/\n    }\n\n    @PostMapping(\"/register\")\n    public Result register(@Validated @RequestBody Admin admin){\n        //Query admin information\n        String adminName = admin.getAdminName();\n        String password = admin.getPassword();\n        Admin queryAdmin = adminService.selectAdminByName(adminName);\n        if(adminName!=null&&adminName.length()>=5&&adminName.length()<=16 && password!=null&&password.length()>=5&&password.length()<=16){\n            if(queryAdmin==null){\n                //Not in use\n                //Register\n                admin.setAuthority(\"1\");\n                int f = adminService.insertAdmin(admin);\n                if(f>0){\n                    return Result.success(\"Registration successful\");\n                }else{\n                    return Result.error(\"Registration failed\");\n                }\n            }else//Already in use\n                return Result.error(\"Username is already taken\");\n        }else{\n            return Result.error(\"Invalid parameters\");\n        }\n    }\n\n    @GetMapping(\"/adminInfo\")\n    public Result adminInfo(/*HttpServletRequest request*/){\n        //Query information based on admin ID\n        /*String token = request.getHeader(\"Authorization\");\n        Integer adminId = JwtUtils.getAdminId(token);\n        Admin adminInfo = adminService.selectAdminById(adminId);*/\n        // Get current logged-in admin ID\n        Integer adminId = ThreadLocalUtil.getId();\n        // Get current logged-in role\n        String role = ThreadLocalUtil.getRole();\n        // Ensure the current user is an admin\n        if (!\"admin\".equals(role)) {\n            return Result.error(\"Access denied\");\n        }\n        Admin adminInfo = adminService.selectAdminById(adminId);\n        if(adminInfo!=null){\n            return Result.success(adminInfo);\n        }else{\n            return Result.error(null);\n        }\n    }\n\n    @PutMapping(\"/adminUpdate\")\n    public Result updateAdmin(@RequestBody Admin admin){\n        int f = adminService.updateAdmin(admin);\n        if (f>0)\n            return Result.success(\"Update successful\");\n        else\n            return Result.error(\"Update failed\");\n    }\n\n    @PatchMapping(\"/adminUpdatePwd\")\n    public Result updateAdminPwd(@RequestBody Map<String,String> params,HttpServletRequest request){\n        String oldPwd = params.get(\"oldPwd\");\n        String newPwd = params.get(\"newPwd\");\n\n\n        if(oldPwd==null || newPwd==null){\n            return Result.error(\"Missing parameters\");\n        }else{\n            // Get current logged-in admin ID\n            Integer adminId = ThreadLocalUtil.getId();\n            // Get current logged-in role\n            String role = ThreadLocalUtil.getRole();\n\n            // Ensure the current user is an admin\n            if (!\"admin\".equals(role)) {\n                return Result.error(\"Access denied\");\n            }\n            Admin adminInfo = adminService.selectAdminById(adminId);\n            System.out.println(adminInfo.getPassword());\n            if(!adminInfo.getPassword().equals(oldPwd)){\n                return Result.error(\"Incorrect original password\");\n            }\n            adminService.updateAdminPwd(newPwd,adminId);\n            return Result.success(\"Password changed successfully\");\n        }\n    }\n\n}\n```\n\nThis is the controller layer, \n\n```java\npackage com.example.graduation_project.pojo.entire;\n\npublic class Admin extends BaseEntity{\n    private int adminId;\n\n    private String adminName;\n\n    private String nickName;\n    //@JsonIgnore //Makes Spring MVC ignore the password when converting the current object to a JSON string, so the final JSON string doesn't have a password property.\n    private String password;\n\n    private String phoneNumber;\n\n    private String authority;\n\n\n    public int getAdminId() {\n        return adminId;\n    }\n\n    public void setAdminId(int adminId) {\n        this.adminId = adminId;\n    }\n\n    public String getAdminName() {\n        return adminName;\n    }\n\n    public void setAdminName(String adminName) {\n        this.adminName = adminName;\n    }\n\n    public String getNickName() {\n        return nickName;\n    }\n\n    public void setNickName(String nickName) {\n        this.nickName = nickName;\n    }\n\n    public String getPassword() {\n        return password;\n    }\n\n    public void setPassword(String password) {\n        this.password = password;\n    }\n\n    public String getPhoneNumber() {\n        return phoneNumber;\n    }\n\n    public void setPhoneNumber(String phoneNumber) {\n        this.phoneNumber = phoneNumber;\n    }\n\n    public String getAuthority() {\n        return authority;\n    }\n\n    public void setAuthority(String authority) {\n        this.authority = authority;\n    }\n\n\n    @Override\n    public String toString() {\n        return \"Admin{\" +\n                \"adminId=\" + adminId +\n                \", adminName='\" + adminName + '\\'' +\n                \", nickName='\" + nickName + '\\'' +\n                \", password='\" + password + '\\'' +\n                \", phoneNumber='\" + phoneNumber + '\\'' +\n                \", authority='\" + authority + '\\'' +\n                '}';\n    }\n}\n```\n\nThis is the entity class, \n\n```xml\n<?xml version=\"1.0\" encoding=\"UTF-8\" ?>\n<!DOCTYPE mapper PUBLIC \"-//mybatis.org//DTD Mapper 3.0//EN\"\n        \"http://mybatis.org/dtd/mybatis-3-mapper.dtd\" >\n\n<mapper namespace=\"com.example.graduation_project.mapper.AdminMapper\">\n    <resultMap id=\"AdminResult\" type=\"com.example.graduation_project.pojo.entire.Admin\">\n        <id     property=\"adminId\"      column=\"admin_id\"     />\n        <result property=\"adminName\"    column=\"admin_name\"   />\n        <result property=\"nickName\"     column=\"nick_name\"   />\n        <result property=\"password\"     column=\"password\"       />\n        <result property=\"phoneNumber\"  column=\"phone_number\" />\n        <result property=\"authority\"    column=\"authority\"    />\n        <result property=\"createTime\"   column=\"create_time\" />\n        <result property=\"updateTime\"   column=\"update_time\" />\n    </resultMap>\n    <insert id=\"insertAdmin\" parameterType=\"com.example.graduation_project.pojo.entire.Admin\">\n        insert into g_admin(\n            <if test=\"adminName!=null and adminName!=''\">admin_name,</if>\n            <if test=\"nickName!=null and nickName!=''\">nick_name,</if>\n            <if test=\"password!=null and password!=''\">password,</if>\n            <if test=\"phoneNumber!=null and phoneNumber!=''\">phone_number,</if>\n            <if test=\"authority!=null and authority!=''\">authority,</if>\n            create_time\n        ) values (\n            <if test=\"adminName!=null and adminName!=''\">#{adminName},</if>\n            <if test=\"nickName!=null and nickName!=''\">#{nickName},</if>\n            <if test=\"password!=null and password!=''\">#{password},</if>\n            <if test=\"phoneNumber!=null and phoneNumber!=''\">#{phoneNumber},</if>\n            <if test=\"authority!=null and authority!=''\">#{authority},</if>\n            sysdate()\n        )\n    </insert>\n\n    <select id=\"adminLogin\" parameterType=\"com.example.graduation_project.pojo.entire.Admin\" resultMap=\"AdminResult\">\n        select * from g_admin where admin_name = #{adminName} and password = #{password}\n    </select>\n\n    <select id=\"selectAdminById\" parameterType=\"com.example.graduation_project.pojo.entire.Admin\" resultMap=\"AdminResult\">\n        select * from g_admin where admin_id = #{adminId}\n    </select>\n\n    <select id=\"selectAdminByName\" parameterType=\"com.example.graduation_project.pojo.entire.Admin\" resultMap=\"AdminResult\">\n        select * from g_admin where admin_name = #{adminName}\n    </select>\n    \n    <update id=\"updateAdmin\" parameterType=\"com.example.graduation_project.pojo.entire.Admin\">\n    update g_admin\n    <set>\n        <if test=\"nickName!=null and nickName!=''\">nick_name=#{nickName},</if>\n        <if test=\"phoneNumber!=null and phoneNumber!=''\">phone_number=#{phoneNumber},</if>\n        update_time=sysdate()\n    </set>\n    where admin_id = #{adminId}\n    </update>\n\n    <update id=\"updateAdminPwd\" parameterType=\"com.example.graduation_project.pojo.entire.Admin\">\n        update g_admin set password=#{newPwd},update_time = sysdate() where admin_id = #{adminId}\n    </update>\n</mapper>\n```\n\nThis is mapper.xml, if I want to implement \"Admin Information Management - This module provides comprehensive management functionality for administrator accounts, supporting dynamic updates of basic information such as username and phone number through Vue.js form components. Password modification uses SHA-256 encryption storage and enforces complexity validation (minimum 8 characters including upper/lowercase letters and special characters). The backend verifies operation permissions through JWT tokens, and all sensitive operations (such as password resets) are recorded in detailed audit logs (including operation time, IP address, and action type) to ensure traceability",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is User Information Update Functionality Properly Implemented?",
+      "description": "Review whether the Vue.js form components correctly handle basic information updates (nickname and phone number) with proper validation and server communication.Score 0 if the form submission doesn't work, 5 if it works but has validation issues, 10 if it's fully functional with complete validation and error handling. Deduct 2 points if there's no loading state during submission or no success/error feedback.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is Password Management System Securely Implemented?",
+      "description": "Evaluate whether the password modification functionality implements SHA-256 encryption and enforces complexity requirements (minimum 8 characters with uppercase, lowercase, and special characters).Score 0 if plaintext password storage exists, 3 if basic hashing is used but not SHA-256, 6 if SHA-256 is implemented but without proper complexity validation, and 10 if both SHA-256 and complete password complexity requirements are properly enforced. Deduct 3 points if client-side validation exists without server-side validation.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is JWT Token Authentication System Properly Implemented?",
+      "description": "Check if the JWT implementation follows security best practices for token generation, validation, expiration, and storage, and properly restricts access to authorized administrators only.Score 0 if JWT is not implemented or has critical flaws, 5 if basic implementation exists with some security issues, and 10 if JWT implementation includes token expiration, proper secret management, and role-based validation. Deduct 3 points if tokens are stored insecurely (e.g., in localStorage without additional protections).",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the Audit Logging System Comprehensive?",
+      "description": "Verify if the code includes detailed audit logging for sensitive operations, capturing operation time, IP address, action type, and associated user information.Score 0 if audit logging is completely missing, 5 if basic logging exists but misses critical fields (IP, time, action type), and 10 if comprehensive logging is implemented for all sensitive operations with all required fields. Deduct 3 points if logs are not properly secured or if there's no mechanism to prevent log tampering.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the Code Robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (invalid inputs, network failures, authorization errors) and provide friendly error prompts or recovery mechanisms.Score 0 if no error handling exists, 5 if basic error handling is present but incomplete, and 10 if comprehensive error handling covers all edge cases with user-friendly messages. Deduct 2 points for each unhandled edge case found in critical functionality.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are There Any Innovative Features That Are Eye-Catching?",
+      "description": "Check whether the code includes surprise features that enhance security or user experience (e.g., 1. Multi-factor authentication 2. Session timeout management 3. Failed login attempt limiting).Add 3 points for each practical innovative security 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 password validation methods) 2. Function modules unrelated to admin management 3. Unnecessary complexity that impacts maintainability.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 (separation of concerns between components/layers), code reuse, and adherence to established design patterns.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 clear separation between UI, business logic, and data layers. 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 2) Proper layout spacing 3) 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": "Is the Dynamic Interaction Smooth and Seamless?",
+      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Clear form validation feedback 3) Smooth transitions between components.Deduct 5 points for each operation without feedback, 3 points for delayed validation feedback, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "easy"
+}

package/library/management_systems-frontend_backend_platforms/age-friendly-renovation-consulting-app.json

@@ -0,0 +1,68 @@
+{
+  "index": 1014,
+  "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. Write a fully operational code for an age-friendly renovation consulting app with the following requirements:\n\n1. Free registration for part-time/full-time designers, with the platform taking a 10% commission from each design project fee.\n\n2. Designers can freely choose projects. After accepting a job, the platform takes 10% of the deposit, and the project will be listed on the platform.\n\n3. Clients can select designers based on style preferences, with past case studies available for reference. Style consultation is free. Based on client preferences, designers will create style concepts. To obtain initial design drafts (which only include effect renderings without dimensions, just a general layout), clients must pay a deposit of 30% of the total project amount. The platform takes a 10% commission from this deposit. The platform only provides design solutions and consultation, not renovation materials or labor.\n\n4. After signing a contract and paying the 30% deposit, clients can view preliminary renderings (without source files).\n\n5. If clients are satisfied with the design, they pay the remaining balance. Designers will then visit the site to make detailed adjustments, maintain ongoing communication, provide source files, and implement the design plan.\n\n6. Please help me identify any design considerations I may have overlooked.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the registration and user management system fully implemented?",
+      "description": "Review whether the code implements separate registration flows for designers and clients with appropriate validation, profile management, and authentication mechanisms. Check if designers can upload portfolios/past projects, and whether verification mechanisms for professional credentials are included. Score 0 if core registration functionality is missing, 5 if basic registration exists without role differentiation, and 10 if full registration with proper role separation and profile management is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the project listing and selection system properly implemented?",
+      "description": "Evaluate whether the system allows clients to post renovation projects with requirements, and designers to browse and accept projects. Check if the system handles the 10% platform commission calculation correctly, and if project status tracking (available, in progress, completed) is implemented. Deduct 5 points if commission calculation is incorrect, 3 points if project status transitions are incomplete. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the payment processing and deposit system securely implemented?",
+      "description": "Check if the code implements the 30% deposit payment flow securely, with proper validation and error handling. Verify that payment confirmations are sent to all parties, and the platform's 10% commission is calculated correctly. Score 0 if payment handling is absent, 5 if only basic payment functionality exists without proper security measures, and 10 if a complete, secure payment system with commission handling is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the design workflow and deliverables system well-structured?",
+      "description": "Assess whether the code includes functionality for: free style consultation, concept creation, preliminary rendering viewing (without source files), and final deliverables after full payment. Check if there's a mechanism for designers to upload work and clients to review it. Deduct 5 points if the staged deliverable process is not implemented, and 3 points if there's no distinction between preliminary and final deliverables. 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 payment failures, incomplete user profiles, abandoned projects, 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. AR visualization of design concepts in client's space 2. AI-assisted style matching system 3. Interactive revision tracking for design iterations). 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 payment processing systems) 2. Function modules unrelated to renovation consulting (e.g., a built-in social network) 3. Fancy effects that affect performance (e.g., excessive animations on critical paths). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating business logic/UI/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). Check if the interface is age-friendly with adequate text size, contrast, and intuitive navigation. 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. Assess if the app provides appropriate feedback during critical operations like payments and project submissions. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast sliding, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "medium"
+}

package/library/management_systems-frontend_backend_platforms/ai-software-engineering-portal-app-store-style.json

@@ -0,0 +1,68 @@
+{
+  "index": 1702,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate, professional responses. Be sure to provide executable code where possible. Design an AI intelligent portal for software engineering in the style of the App Store, displaying icons for various software engineering tools including requirements engineering tools, design engineering tools, software development tools, documentation generation tools, etc., covering all stages of software engineering. Please generate runnable code based on Bootstrap.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the AI intelligent portal structure fully implemented?",
+      "description": "Review whether the code implements a complete portal structure using Bootstrap's grid system, with proper responsive layout and navigation components. Score 0 if there's only basic HTML without Bootstrap integration, 5 if basic Bootstrap components are used but lacks organization, and 10 if the portal has a properly structured grid layout with responsive behavior across all screen sizes.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are all software engineering stages represented with appropriate categorization?",
+      "description": "Check whether the portal includes comprehensive categorization of software engineering tools covering: requirements engineering, design engineering, development, testing, deployment, maintenance, and documentation. Deduct 2 points for each major category missing. The portal should demonstrate clear visual separation between categories (through tabs, sections, or filtering). The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the tool display system properly implemented with App Store-like card views?",
+      "description": "Evaluate whether the code creates proper card-based displays for each tool with consistent sizing, proper spacing, and uniform presentation of tool information (icon, name, description, rating, etc.). Score 0 if tools are displayed as simple lists, 5 if basic cards are implemented but lack visual hierarchy, and 10 if cards follow App Store design patterns with proper shadows, hover effects, and interaction feedback.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is AI intelligence incorporated into the portal functionality?",
+      "description": "Assess whether the code implements AI features such as personalized recommendations, intelligent search, tool compatibility suggestions, or workflow optimization. Score 0 if no AI components are present, 5 if basic filtering/search is labeled as AI without actual intelligent behavior, and 10 if the portal includes JavaScript implementation of at least two legitimate AI-assisted features with proper explanation of the underlying logic.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as missing images, search with no results, filtering with empty categories, 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. Dark/light mode toggle 2. Tool comparison function 3. Integration with actual API endpoints). 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 mechanisms coexisting) 2. Function modules unrelated to software engineering tools (e.g., a built-in media player) 3. Fancy effects that affect performance (e.g., excessive animations or transitions). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (separation of HTML structure, CSS styling, and JavaScript functionality), code reusability, and clean organization. Deduct 5 points if inline styles are used extensively; deduct 5 points if JavaScript is not organized in functions or modules; deduct 5 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 overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors beyond Bootstrap defaults) 2) Proper layout spacing (element spacing follows consistent margins and padding) 3) Professional font system (appropriate heading and body text hierarchy). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic arrangement of tool cards. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance for search and filtering. Deduct 5 points for each operation without feedback, 3 points for clunky transitions between views or categories, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Management Systems-Frontend/Backend Platforms",
+  "difficulty": "easy"
+}