[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-74e65a1b-9486-4436-bc03-c62650176007":3,"$fwk9NTV35iln8eMS12Lj3yEvjti88nHDCvCL75aCYtvY":42},{"id":4,"title":5,"description":6,"categoryId":7,"moduleId":8,"tags":9,"prompt":10,"icon":11,"source":12,"sourceUrl":13,"authorId":14,"authorName":15,"isPublic":16,"stars":17,"runs":18,"createdAt":19,"updatedAt":19,"module":20,"category":27,"packages":33},"74e65a1b-9486-4436-bc03-c62650176007","prompt-library","一个由[awesome-chatgpt-prompts](https:\u002F\u002Fgithub.com\u002Ff\u002Fawesome-chatgpt-prompts)和社区最佳实践启发的全面实战提示集合。","cat_coding_backend","mod_coding","sickn33,coding","---\nname: prompt-library\ndescription: \"A comprehensive collection of battle-tested prompts inspired by [awesome-chatgpt-prompts](https:\u002F\u002Fgithub.com\u002Ff\u002Fawesome-chatgpt-prompts) and community best practices.\"\nrisk: unknown\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# 📝 Prompt Library\n\n> A comprehensive collection of battle-tested prompts inspired by [awesome-chatgpt-prompts](https:\u002F\u002Fgithub.com\u002Ff\u002Fawesome-chatgpt-prompts) and community best practices.\n\n## When to Use This Skill\n\nUse this skill when the user:\n\n- Needs ready-to-use prompt templates\n- Wants role-based prompts (act as X)\n- Asks for prompt examples or inspiration\n- Needs task-specific prompt patterns\n- Wants to improve their prompting\n\n## Prompt Categories\n\n### 🎭 Role-Based Prompts\n\n#### Expert Developer\n\n```\nAct as an expert software developer with 15+ years of experience. You specialize in clean code, SOLID principles, and pragmatic architecture. When reviewing code:\n1. Identify bugs and potential issues\n2. Suggest performance improvements\n3. Recommend better patterns\n4. Explain your reasoning clearly\nAlways prioritize readability and maintainability over cleverness.\n```\n\n#### Code Reviewer\n\n```\nAct as a senior code reviewer. Your role is to:\n1. Check for bugs, edge cases, and error handling\n2. Evaluate code structure and organization\n3. Assess naming conventions and readability\n4. Identify potential security issues\n5. Suggest improvements with specific examples\n\nFormat your review as:\n🔴 Critical Issues (must fix)\n🟡 Suggestions (should consider)\n🟢 Praise (what's done well)\n```\n\n#### Technical Writer\n\n```\nAct as a technical documentation expert. Transform complex technical concepts into clear, accessible documentation. Follow these principles:\n- Use simple language, avoid jargon\n- Include practical examples\n- Structure with clear headings\n- Add code snippets where helpful\n- Consider the reader's experience level\n```\n\n#### System Architect\n\n```\nAct as a senior system architect designing for scale. Consider:\n- Scalability (horizontal and vertical)\n- Reliability (fault tolerance, redundancy)\n- Maintainability (modularity, clear boundaries)\n- Performance (latency, throughput)\n- Cost efficiency\n\nProvide architecture decisions with trade-off analysis.\n```\n\n### 🛠️ Task-Specific Prompts\n\n#### Debug This Code\n\n```\nDebug the following code. Your analysis should include:\n\n1. **Problem Identification**: What exactly is failing?\n2. **Root Cause**: Why is it failing?\n3. **Fix**: Provide corrected code\n4. **Prevention**: How to prevent similar bugs\n\nShow your debugging thought process step by step.\n```\n\n#### Explain Like I'm 5 (ELI5)\n\n```\nExplain [CONCEPT] as if I'm 5 years old. Use:\n- Simple everyday analogies\n- No technical jargon\n- Short sentences\n- Relatable examples from daily life\n- A fun, engaging tone\n```\n\n#### Code Refactoring\n\n```\nRefactor this code following these priorities:\n1. Readability first\n2. Remove duplication (DRY)\n3. Single responsibility per function\n4. Meaningful names\n5. Add comments only where necessary\n\nShow before\u002Fafter with explanation of changes.\n```\n\n#### Write Tests\n\n```\nWrite comprehensive tests for this code:\n1. Happy path scenarios\n2. Edge cases\n3. Error conditions\n4. Boundary values\n\nUse [FRAMEWORK] testing conventions. Include:\n- Descriptive test names\n- Arrange-Act-Assert pattern\n- Mocking where appropriate\n```\n\n#### API Documentation\n\n```\nGenerate API documentation for this endpoint including:\n- Endpoint URL and method\n- Request parameters (path, query, body)\n- Request\u002Fresponse examples\n- Error codes and meanings\n- Authentication requirements\n- Rate limits if applicable\n\nFormat as OpenAPI\u002FSwagger or Markdown.\n```\n\n### 📊 Analysis Prompts\n\n#### Code Complexity Analysis\n\n```\nAnalyze the complexity of this codebase:\n\n1. **Cyclomatic Complexity**: Identify complex functions\n2. **Coupling**: Find tightly coupled components\n3. **Cohesion**: Assess module cohesion\n4. **Dependencies**: Map critical dependencies\n5. **Technical Debt**: Highlight areas needing refactoring\n\nRate each area and provide actionable recommendations.\n```\n\n#### Performance Analysis\n\n```\nAnalyze this code for performance issues:\n\n1. **Time Complexity**: Big O analysis\n2. **Space Complexity**: Memory usage patterns\n3. **I\u002FO Bottlenecks**: Database, network, disk\n4. **Algorithmic Issues**: Inefficient patterns\n5. **Quick Wins**: Easy optimizations\n\nPrioritize findings by impact.\n```\n\n#### Security Review\n\n```\nPerform a security review of this code:\n\n1. **Input Validation**: Check all inputs\n2. **Authentication\u002FAuthorization**: Access control\n3. **Data Protection**: Sensitive data handling\n4. **Injection Vulnerabilities**: SQL, XSS, etc.\n5. **Dependencies**: Known vulnerabilities\n\nClassify issues by severity (Critical\u002FHigh\u002FMedium\u002FLow).\n```\n\n### 🎨 Creative Prompts\n\n#### Brainstorm Features\n\n```\nBrainstorm features for [PRODUCT]:\n\nFor each feature, provide:\n- Name and one-line description\n- User value proposition\n- Implementation complexity (Low\u002FMed\u002FHigh)\n- Dependencies on other features\n\nGenerate 10 ideas, then rank top 3 by impact\u002Feffort ratio.\n```\n\n#### Name Generator\n\n```\nGenerate names for [PROJECT\u002FFEATURE]:\n\nProvide 10 options in these categories:\n- Descriptive (what it does)\n- Evocative (how it feels)\n- Acronyms (memorable abbreviations)\n- Metaphorical (analogies)\n\nFor each, explain the reasoning and check domain availability patterns.\n```\n\n### 🔄 Transformation Prompts\n\n#### Migrate Code\n\n```\nMigrate this code from [SOURCE] to [TARGET]:\n\n1. Identify equivalent constructs\n2. Handle incompatible features\n3. Preserve functionality exactly\n4. Follow target language idioms\n5. Add necessary dependencies\n\nShow the migration step by step with explanations.\n```\n\n#### Convert Format\n\n```\nConvert this [SOURCE_FORMAT] to [TARGET_FORMAT]:\n\nRequirements:\n- Preserve all data\n- Use idiomatic target format\n- Handle edge cases\n- Validate the output\n- Provide sample verification\n```\n\n## Prompt Engineering Techniques\n\n### Chain of Thought (CoT)\n\n```\nLet's solve this step by step:\n1. First, I'll understand the problem\n2. Then, I'll identify the key components\n3. Next, I'll work through the logic\n4. Finally, I'll verify the solution\n\n[Your question here]\n```\n\n### Few-Shot Learning\n\n```\nHere are some examples of the task:\n\nExample 1:\nInput: [example input 1]\nOutput: [example output 1]\n\nExample 2:\nInput: [example input 2]\nOutput: [example output 2]\n\nNow complete this:\nInput: [actual input]\nOutput:\n```\n\n### Persona Pattern\n\n```\nYou are [PERSONA] with [TRAITS].\nYour communication style is [STYLE].\nYou prioritize [VALUES].\n\nWhen responding:\n- [Behavior 1]\n- [Behavior 2]\n- [Behavior 3]\n```\n\n### Structured Output\n\n```\nRespond in the following JSON format:\n{\n  \"analysis\": \"your analysis here\",\n  \"recommendations\": [\"rec1\", \"rec2\"],\n  \"confidence\": 0.0-1.0,\n  \"caveats\": [\"caveat1\"]\n}\n```\n\n## Prompt Improvement Checklist\n\nWhen crafting prompts, ensure:\n\n- [ ] **Clear objective**: What exactly do you want?\n- [ ] **Context provided**: Background information included?\n- [ ] **Format specified**: How should output be structured?\n- [ ] **Examples given**: Are there reference examples?\n- [ ] **Constraints defined**: Any limitations or requirements?\n- [ ] **Success criteria**: How do you measure good output?\n\n## Resources\n\n- [awesome-chatgpt-prompts](https:\u002F\u002Fgithub.com\u002Ff\u002Fawesome-chatgpt-prompts)\n- [prompts.chat](https:\u002F\u002Fprompts.chat)\n- [Learn Prompting](https:\u002F\u002Flearnprompting.org\u002F)\n\n---\n\n> 💡 **Tip**: The best prompts are specific, provide context, and include examples of desired output.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","","imported","https:\u002F\u002Fgithub.com\u002Fsickn33\u002Fantigravity-awesome-skills","user_system_seed","SkillOPIC",true,186,1559,"2026-05-16 13:35:36",{"id":8,"name":21,"slug":22,"icon":23,"description":24,"sort":25,"createdAt":26},"编程开发","coding","mdi-code-braces","代码生成、调试、审查，提升开发效率",2,"2026-05-16 12:53:40",{"id":7,"name":28,"slug":29,"icon":30,"description":31,"moduleId":8,"sort":25,"skillCount":32,"createdAt":26},"后端开发","backend","mdi-server","API、数据库、服务端架构",296,[34],{"id":35,"skillId":4,"version":36,"fileName":37,"fileSize":38,"filePath":39,"fileHash":40,"manifest":41,"createdAt":19},"1c9fcc7d-0d90-4e0c-ac94-b8116300f7ce","1.0.0","prompt-library.zip",3605,"uploads\u002Fskills\u002F74e65a1b-9486-4436-bc03-c62650176007\u002Fprompt-library.zip","0a0783d4e4d5e3ee830991a0e51577176e93da09e049d930d2a9187528ff6d36","[{\"path\":\"SKILL.md\",\"isDirectory\":false,\"size\":7893}]",{"code":43,"message":44,"data":45},200,"success",{"items":46,"stats":47,"page":50},[],{"averageRating":48,"totalRatings":48,"ratingCounts":49},0,[48,48,48,48,48],{"limit":51,"offset":48,"hasMore":52,"nextOffset":51,"ratedOnly":16},15,false]