commit d8bdd46977e6f3149bad61343331c099236770d1 Author: Jeff Date: Fri Nov 7 12:27:31 2025 -0500 initial commit diff --git a/README.md b/README.md new file mode 100644 index 0000000..53f45aa --- /dev/null +++ b/README.md @@ -0,0 +1,2 @@ +# ai-prompt-library +Library of AI prompts diff --git a/prompts/.DS_Store b/prompts/.DS_Store new file mode 100644 index 0000000..4101a91 Binary files /dev/null and b/prompts/.DS_Store differ diff --git a/prompts/coding/code-review.md b/prompts/coding/code-review.md new file mode 100644 index 0000000..9d6b665 --- /dev/null +++ b/prompts/coding/code-review.md @@ -0,0 +1,29 @@ +--- +name: Code Review Assistant +description: Comprehensive code review for quality, performance, and security +tags: coding, review, quality, security +--- + +Please review the following code with a focus on: + +## Code Quality +- Readability and maintainability +- Adherence to best practices and conventions +- Code organization and structure + +## Functionality +- Logic correctness +- Edge cases and error handling +- Potential bugs or issues + +## Performance +- Algorithm efficiency +- Resource usage +- Optimization opportunities + +## Security +- Input validation +- Authentication/authorization +- Potential vulnerabilities + +Please provide specific, actionable feedback with examples where applicable. diff --git a/prompts/coding/refactor.md b/prompts/coding/refactor.md new file mode 100644 index 0000000..3613671 --- /dev/null +++ b/prompts/coding/refactor.md @@ -0,0 +1,16 @@ +--- +name: Refactoring Assistant +description: Help refactor code to improve quality and maintainability +tags: coding, refactor, clean-code +--- + +Please refactor the following code to improve: + +1. **Readability**: Make the code easier to understand +2. **Maintainability**: Simplify future modifications +3. **Performance**: Optimize where beneficial +4. **Design Patterns**: Apply appropriate patterns +5. **DRY Principle**: Eliminate code duplication +6. **Naming**: Use clear, descriptive names + +Provide the refactored code with explanations for each change. diff --git a/prompts/compliment-mixer.md b/prompts/compliment-mixer.md new file mode 100644 index 0000000..62ceca0 --- /dev/null +++ b/prompts/compliment-mixer.md @@ -0,0 +1,3 @@ +Create a "Compliment Mixer" app that allows users to generate and save personalized compliments. Create a custom UI so the user can enter two adjectives that describe a person (e.g., "brilliant", "fearless") and a name (e.g., "Alex"). The app then generates a compliment sentence that combines those words and the name using a random sentence template. The user can save the compliment to Salesforce and view a list of the 5 most recent compliments they've generated. + +The code should follow standard Salesforce styling and development best practices and be deployable to a scratch org or sandbox. Keep it fun, readable, and beginner-friendly. \ No newline at end of file diff --git a/prompts/general/brainstorm.md b/prompts/general/brainstorm.md new file mode 100644 index 0000000..2e95d2d --- /dev/null +++ b/prompts/general/brainstorm.md @@ -0,0 +1,25 @@ +--- +name: Brainstorming Assistant +description: Generate creative ideas and solutions +tags: brainstorming, creativity, ideation +--- + +Let's brainstorm ideas for [TOPIC/PROBLEM]. + +Please provide: + +1. **10 Creative Ideas**: Think outside the box, no idea is too wild + +2. **3 Practical Solutions**: Focus on feasibility and impact + +3. **Potential Challenges**: What obstacles might we face? + +4. **Next Steps**: Concrete actions to explore the best ideas + +Use the following approach: +- Consider multiple perspectives +- Combine different concepts +- Question assumptions +- Look for patterns and connections + +Format ideas clearly with brief explanations for each. diff --git a/prompts/writing/blog-post.md b/prompts/writing/blog-post.md new file mode 100644 index 0000000..839b952 --- /dev/null +++ b/prompts/writing/blog-post.md @@ -0,0 +1,32 @@ +--- +name: Blog Post Writer +description: Create engaging blog posts on technical topics +tags: writing, blog, content +--- + +Write an engaging blog post about [TOPIC] with the following structure: + +## Opening Hook +Start with an interesting question, statistic, or story that captures attention. + +## Introduction +- Explain why this topic matters +- What problem does it solve? +- Who is this for? + +## Main Content +Break down the topic into digestible sections: +- Use clear headings and subheadings +- Include practical examples +- Add code snippets or screenshots where relevant +- Explain complex concepts simply + +## Key Takeaways +Summarize the main points in 3-5 bullet points. + +## Call to Action +End with a question or suggestion for next steps. + +**Tone**: Professional but conversational +**Length**: 1000-1500 words +**Audience**: Developers with intermediate experience diff --git a/rules/coding/apex-standards.md b/rules/coding/apex-standards.md new file mode 100644 index 0000000..5a28e9e --- /dev/null +++ b/rules/coding/apex-standards.md @@ -0,0 +1,2 @@ +- ALWAYS use an existing Salesforce DX MCP Server tool before calling the sf CLI. +- When calling the Salesforce CLI, always use sf. NEVER use the deprecated sfdx CLI or the sfdx-style commands. \ No newline at end of file diff --git a/rules/project-a.md b/rules/project-a.md new file mode 100644 index 0000000..0a46e43 --- /dev/null +++ b/rules/project-a.md @@ -0,0 +1 @@ +Always use Flows for automation. \ No newline at end of file diff --git a/rules/project-b.md b/rules/project-b.md new file mode 100644 index 0000000..6cb853c --- /dev/null +++ b/rules/project-b.md @@ -0,0 +1 @@ +Always use Apex for automation. \ No newline at end of file