Curated collection of high-quality prompts for various use cases. Includes role-based prompts, task-specific templates, and prompt refinement techniques. Use when user needs prompt templates, role-play prompts, or ready-to-use prompt examples for coding, writing, analysis, or creative tasks.
Add this skill
npx mdskills install sickn33/prompt-libraryWell-organized reference library of prompts with clear categorization and practical templates
1---2name: prompt-library3description: "Curated collection of high-quality prompts for various use cases. Includes role-based prompts, task-specific templates, and prompt refinement techniques. Use when user needs prompt templates, role-play prompts, or ready-to-use prompt examples for coding, writing, analysis, or creative tasks."4---56# 📝 Prompt Library78> A comprehensive collection of battle-tested prompts inspired by [awesome-chatgpt-prompts](https://github.com/f/awesome-chatgpt-prompts) and community best practices.910## When to Use This Skill1112Use this skill when the user:1314- Needs ready-to-use prompt templates15- Wants role-based prompts (act as X)16- Asks for prompt examples or inspiration17- Needs task-specific prompt patterns18- Wants to improve their prompting1920## Prompt Categories2122### 🎭 Role-Based Prompts2324#### Expert Developer2526```27Act as an expert software developer with 15+ years of experience. You specialize in clean code, SOLID principles, and pragmatic architecture. When reviewing code:281. Identify bugs and potential issues292. Suggest performance improvements303. Recommend better patterns314. Explain your reasoning clearly32Always prioritize readability and maintainability over cleverness.33```3435#### Code Reviewer3637```38Act as a senior code reviewer. Your role is to:391. Check for bugs, edge cases, and error handling402. Evaluate code structure and organization413. Assess naming conventions and readability424. Identify potential security issues435. Suggest improvements with specific examples4445Format your review as:46🔴 Critical Issues (must fix)47🟡 Suggestions (should consider)48🟢 Praise (what's done well)49```5051#### Technical Writer5253```54Act as a technical documentation expert. Transform complex technical concepts into clear, accessible documentation. Follow these principles:55- Use simple language, avoid jargon56- Include practical examples57- Structure with clear headings58- Add code snippets where helpful59- Consider the reader's experience level60```6162#### System Architect6364```65Act as a senior system architect designing for scale. Consider:66- Scalability (horizontal and vertical)67- Reliability (fault tolerance, redundancy)68- Maintainability (modularity, clear boundaries)69- Performance (latency, throughput)70- Cost efficiency7172Provide architecture decisions with trade-off analysis.73```7475### 🛠️ Task-Specific Prompts7677#### Debug This Code7879```80Debug the following code. Your analysis should include:81821. **Problem Identification**: What exactly is failing?832. **Root Cause**: Why is it failing?843. **Fix**: Provide corrected code854. **Prevention**: How to prevent similar bugs8687Show your debugging thought process step by step.88```8990#### Explain Like I'm 5 (ELI5)9192```93Explain [CONCEPT] as if I'm 5 years old. Use:94- Simple everyday analogies95- No technical jargon96- Short sentences97- Relatable examples from daily life98- A fun, engaging tone99```100101#### Code Refactoring102103```104Refactor this code following these priorities:1051. Readability first1062. Remove duplication (DRY)1073. Single responsibility per function1084. Meaningful names1095. Add comments only where necessary110111Show before/after with explanation of changes.112```113114#### Write Tests115116```117Write comprehensive tests for this code:1181. Happy path scenarios1192. Edge cases1203. Error conditions1214. Boundary values122123Use [FRAMEWORK] testing conventions. Include:124- Descriptive test names125- Arrange-Act-Assert pattern126- Mocking where appropriate127```128129#### API Documentation130131```132Generate API documentation for this endpoint including:133- Endpoint URL and method134- Request parameters (path, query, body)135- Request/response examples136- Error codes and meanings137- Authentication requirements138- Rate limits if applicable139140Format as OpenAPI/Swagger or Markdown.141```142143### 📊 Analysis Prompts144145#### Code Complexity Analysis146147```148Analyze the complexity of this codebase:1491501. **Cyclomatic Complexity**: Identify complex functions1512. **Coupling**: Find tightly coupled components1523. **Cohesion**: Assess module cohesion1534. **Dependencies**: Map critical dependencies1545. **Technical Debt**: Highlight areas needing refactoring155156Rate each area and provide actionable recommendations.157```158159#### Performance Analysis160161```162Analyze this code for performance issues:1631641. **Time Complexity**: Big O analysis1652. **Space Complexity**: Memory usage patterns1663. **I/O Bottlenecks**: Database, network, disk1674. **Algorithmic Issues**: Inefficient patterns1685. **Quick Wins**: Easy optimizations169170Prioritize findings by impact.171```172173#### Security Review174175```176Perform a security review of this code:1771781. **Input Validation**: Check all inputs1792. **Authentication/Authorization**: Access control1803. **Data Protection**: Sensitive data handling1814. **Injection Vulnerabilities**: SQL, XSS, etc.1825. **Dependencies**: Known vulnerabilities183184Classify issues by severity (Critical/High/Medium/Low).185```186187### 🎨 Creative Prompts188189#### Brainstorm Features190191```192Brainstorm features for [PRODUCT]:193194For each feature, provide:195- Name and one-line description196- User value proposition197- Implementation complexity (Low/Med/High)198- Dependencies on other features199200Generate 10 ideas, then rank top 3 by impact/effort ratio.201```202203#### Name Generator204205```206Generate names for [PROJECT/FEATURE]:207208Provide 10 options in these categories:209- Descriptive (what it does)210- Evocative (how it feels)211- Acronyms (memorable abbreviations)212- Metaphorical (analogies)213214For each, explain the reasoning and check domain availability patterns.215```216217### 🔄 Transformation Prompts218219#### Migrate Code220221```222Migrate this code from [SOURCE] to [TARGET]:2232241. Identify equivalent constructs2252. Handle incompatible features2263. Preserve functionality exactly2274. Follow target language idioms2285. Add necessary dependencies229230Show the migration step by step with explanations.231```232233#### Convert Format234235```236Convert this [SOURCE_FORMAT] to [TARGET_FORMAT]:237238Requirements:239- Preserve all data240- Use idiomatic target format241- Handle edge cases242- Validate the output243- Provide sample verification244```245246## Prompt Engineering Techniques247248### Chain of Thought (CoT)249250```251Let's solve this step by step:2521. First, I'll understand the problem2532. Then, I'll identify the key components2543. Next, I'll work through the logic2554. Finally, I'll verify the solution256257[Your question here]258```259260### Few-Shot Learning261262```263Here are some examples of the task:264265Example 1:266Input: [example input 1]267Output: [example output 1]268269Example 2:270Input: [example input 2]271Output: [example output 2]272273Now complete this:274Input: [actual input]275Output:276```277278### Persona Pattern279280```281You are [PERSONA] with [TRAITS].282Your communication style is [STYLE].283You prioritize [VALUES].284285When responding:286- [Behavior 1]287- [Behavior 2]288- [Behavior 3]289```290291### Structured Output292293```294Respond in the following JSON format:295{296 "analysis": "your analysis here",297 "recommendations": ["rec1", "rec2"],298 "confidence": 0.0-1.0,299 "caveats": ["caveat1"]300}301```302303## Prompt Improvement Checklist304305When crafting prompts, ensure:306307- [ ] **Clear objective**: What exactly do you want?308- [ ] **Context provided**: Background information included?309- [ ] **Format specified**: How should output be structured?310- [ ] **Examples given**: Are there reference examples?311- [ ] **Constraints defined**: Any limitations or requirements?312- [ ] **Success criteria**: How do you measure good output?313314## Resources315316- [awesome-chatgpt-prompts](https://github.com/f/awesome-chatgpt-prompts)317- [prompts.chat](https://prompts.chat)318- [Learn Prompting](https://learnprompting.org/)319320---321322> 💡 **Tip**: The best prompts are specific, provide context, and include examples of desired output.323
Full transparency — inspect the skill content before installing.