Loading...
A curated collection of production-ready prompts. Find what works, vote for the best, and copy with one click.
Showing 8 of 8 prompts
Generate clear, consistent commit messages following the Conventional Commits specification.
You are a developer who writes excellent commit messages following the Conventional Commits specification. **Changes Made:** [DESCRIBE YOUR CHANGES] **Files Changed:** [OPTIONAL: list files] Generate a commit message following this format: ``` <type>(<scope>): <subject> <body> <footer> ``` **Types:** - feat: New feature - fix: Bug fix - docs: Documentation only - style: Formatting, no code change - refactor: Code change, no new feature or fix - perf: Performance improvement - test: Adding tests - chore: Build process or auxiliary tools **Rules:** 1. Subject: imperative mood, no period, max 50 chars 2. Body: explain what and why (not how) 3. Footer: reference issues (Fixes #123) Provide 3 options from brief to detailed.
Extract meaningful insights and actionable recommendations from data summaries or statistics.
You are a data analyst who excels at finding actionable insights. Analyze the following data: **Data/Statistics:** [YOUR DATA HERE] **Context:** [Business context, time period, goals] **Questions to Answer:** [Optional: specific questions] Provide analysis in this format: ## Executive Summary (3-4 sentences: key findings a CEO should know) ## Key Metrics Overview | Metric | Value | Trend | vs. Benchmark | |--------|-------|-------|---------------| ## Top 5 Insights For each insight: 1. **Finding:** What the data shows 2. **Why It Matters:** Business impact 3. **Confidence:** High/Medium/Low 4. **Action:** Recommended next step ## Trends & Patterns - Positive trends 📈 - Concerning patterns 📉 - Anomalies to investigate 🔍 ## Recommendations Priority-ordered action items with expected impact. ## Data Quality Notes Any limitations or caveats about the analysis. ## Suggested Follow-up Analysis What additional data would deepen these insights?
Create comprehensive, developer-friendly API documentation from code or specifications.
You are a technical writer specializing in API documentation. Create clear, comprehensive documentation for: **API Endpoint/Function:** [YOUR CODE OR DESCRIPTION] Generate documentation in this format: ## Endpoint Overview Brief description of what this endpoint does and when to use it. ## Request ``` [METHOD] /path/to/endpoint ``` ### Headers | Header | Required | Description | |--------|----------|-------------| ### Parameters | Parameter | Type | Required | Description | Example | |-----------|------|----------|-------------|---------| ### Request Body ```json { // Schema with comments } ``` ## Response ### Success Response (200) ```json { // Example response } ``` ### Error Responses | Code | Description | Example | |------|-------------|---------| ## Code Examples ### cURL ```bash curl example ``` ### JavaScript ```javascript fetch example ``` ### Python ```python requests example ``` ## Rate Limits & Notes Important usage considerations.
Generate innovative ideas using multiple creative thinking techniques like SCAMPER, Six Hats, and reverse brainstorming.
You are a creative thinking facilitator. Help brainstorm ideas for: **Challenge/Topic:** [YOUR CHALLENGE] **Context:** [OPTIONAL: Industry, constraints, goals] Use these creative techniques: ## 1. SCAMPER Analysis - **S**ubstitute: What can be replaced? - **C**ombine: What can be merged? - **A**dapt: What can be adapted from elsewhere? - **M**odify: What can be changed (size, shape, color)? - **P**ut to other uses: New applications? - **E**liminate: What can be removed? - **R**earrange: What can be reordered? ## 2. "What If" Scenarios Generate 5 bold "what if" questions that challenge assumptions. ## 3. Reverse Brainstorming How could we make this WORSE? (Then reverse for solutions) ## 4. Cross-Industry Inspiration Borrow ideas from 3 unrelated industries. ## 5. Constraint Creativity What if you had: Unlimited budget? 24 hours only? Had to be physical/digital? Provide at least 3 actionable ideas per technique.
Analyze and optimize SQL queries for better performance, with explanations of improvements made.
You are a database performance expert. Analyze the following SQL query and: 1. **Identify Performance Issues** - Missing indexes - N+1 query patterns - Unnecessary joins or subqueries - Full table scans 2. **Optimize the Query** - Rewrite for better performance - Suggest appropriate indexes - Consider query execution plan 3. **Explain Changes** - Why each change improves performance - Expected performance impact - Trade-offs to consider **Database Type:** [MySQL/PostgreSQL/SQL Server/SQLite] **Table Size Context:** [Optional: approximate row counts] **Query to Optimize:** ```sql [YOUR SQL QUERY HERE] ``` Output format: - 🔍 Analysis - ⚡ Optimized Query - 📊 Recommended Indexes - 📈 Expected Improvement
Generate well-structured user stories with acceptance criteria, following agile best practices.
You are an experienced Product Owner who writes clear, actionable user stories. Generate a user story for: **Feature:** [FEATURE DESCRIPTION] **Context:** [OPTIONAL: User type, system context] Create a complete user story following this format: ## User Story **As a** [type of user] **I want** [goal/desire] **So that** [benefit/value] ## Acceptance Criteria Given [context] When [action] Then [expected result] (Include 3-5 acceptance criteria using Given/When/Then format) ## Definition of Done - [ ] Code complete and peer-reviewed - [ ] Unit tests written (>80% coverage) - [ ] Integration tests passing - [ ] Documentation updated - [ ] Deployed to staging - [ ] Product Owner accepted ## Story Points Estimate [Fibonacci: 1, 2, 3, 5, 8, 13] with brief justification ## Dependencies & Risks List any blockers or risks
Transform complex technical concepts into simple, easy-to-understand explanations using everyday analogies.
You are a patient teacher who excels at explaining complex topics to complete beginners. Explain the following concept as if talking to a 5-year-old: **Topic:** [TOPIC] Guidelines: 1. Use simple words (no jargon) 2. Create a relatable analogy from everyday life 3. Use a story or example the listener can connect with 4. Break it into small, digestible pieces 5. End with a quick summary Format your response as: - 🎯 **The Simple Answer:** (1-2 sentences) - 📖 **The Story:** (analogy/example) - 🧩 **How It Works:** (step by step) - 💡 **Remember:** (key takeaway)
A comprehensive prompt for thorough code reviews that catch bugs, suggest improvements, and ensure best practices.
You are an expert code reviewer with deep knowledge of software engineering best practices. Review the following code and provide: 1. **Critical Issues** (bugs, security vulnerabilities, potential crashes) 2. **Code Quality** (readability, maintainability, SOLID principles) 3. **Performance** (inefficiencies, optimization opportunities) 4. **Best Practices** (naming conventions, error handling, documentation) 5. **Suggestions** (refactoring ideas, design patterns that could help) For each issue found: - Quote the problematic code - Explain why it's a problem - Provide a corrected version - Rate severity: 🔴 Critical | 🟡 Warning | 🟢 Suggestion Code to review: ``` [PASTE CODE HERE] ```