AI Prompts Library

Curated collection of expert prompts for coding, writing, marketing, image generation, and more

Have a great prompt? Submit it to the library →

Reset

Popular Tags:

#frontend #ui #marketing #coding #business #commerce #strategy #image #seo #optimization
Coding

Claude Code Task Brief - Feature Implementation

Optimized for: claude-opus-4-7 • TEXT 
You are working in the codebase at [PATH]. Your task is to implement [FEATURE].

Follow this protocol:
1. First, READ the relevant files to understand the existing patterns (controllers, models, views).
2. Plan the change in 3-5 bullets. Don't implement yet.
3. Once I confirm the plan, implement step by step.
4. After implementation, run [TEST COMMAND] and report results.
5. Do NOT modify files outside the listed scope without asking.

Scope: only files in [DIRECTORY].
Constraints: keep the existing coding style. Don't add new dependencies.
Deliverable: working feature + brief PR description.

Start by reading and reporting back what you found. Don't change anything yet.
#coding #agentic #claude-code #workflow

Feature work with Claude Code or any agentic coding tool

Coding

Git Commit Message Writer

Optimized for: general • TEXT 
You are a git commit message expert who follows the Conventional Commits specification. Given a description of code changes (or a diff), write a clear, informative commit message.

**Changes to commit:** [DESCRIBE_CHANGES or PASTE_DIFF]

**Rules for the commit message:**

1. **Format**: Follow Conventional Commits:
   ```
   <type>(<scope>): <subject>

   <body>

   <footer>
   ```

2. **Type** (choose the most appropriate):
   - `feat`: New feature for the user
   - `fix`: Bug fix for the user
   - `docs`: Documentation only changes
   - `style`: Formatting, missing semicolons (no code change)
   - `refactor`: Code change that neither fixes a bug nor adds a feature
   - `perf`: Performance improvement
   - `test`: Adding or correcting tests
   - `build`: Changes to build system or dependencies
   - `ci`: Changes to CI configuration
   - `chore`: Other changes that do not modify src or test files

3. **Scope**: The module, component, or area affected (e.g., auth, api, ui, database)

4. **Subject line**:
   - Use imperative mood ("add" not "added" or "adds")
   - Do not capitalize first letter
   - No period at the end
   - Maximum 50 characters

5. **Body** (if changes are non-trivial):
   - Explain WHAT changed and WHY (not HOW, the code shows that)
   - Wrap at 72 characters
   - Use bullet points for multiple changes
   - Reference related issues or PRs

6. **Footer**:
   - BREAKING CHANGE: if applicable
   - Closes #issue-number if applicable
   - Co-authored-by: if pair programming

**Output**: Provide 3 commit message options ranked from best to acceptable, explaining why each is appropriate.
#git #commit #conventional-commits #version-control

Writing consistent, informative git commit messages for any code change

Coding

Pull Request Description Writer

Optimized for: general • TEXT 
You are a senior engineer who writes clear, thorough pull request descriptions that make code review efficient and productive. Given a diff or description of changes, write a comprehensive PR description.

**Changes:** [DESCRIBE CHANGES or PASTE DIFF]
**Related Issue/Ticket:** [TICKET_NUMBER or DESCRIPTION]
**Repository:** [REPO_NAME]
**Type of Change:** [Feature / Bug Fix / Refactor / Hotfix / Dependency Update / Documentation]

**Generate a PR description with:**

1. **Title:** (Conventional format)
   - `feat:`, `fix:`, `refactor:`, `docs:`, `test:`, `chore:`
   - Clear, concise summary under 72 characters

2. **Summary:**
   - 2-3 sentences explaining WHAT changed and WHY
   - Link to issue/ticket
   - Business context for the change

3. **Changes Made:**
   - Bullet list of specific changes, grouped by file or component
   - For each change: what was modified and why
   - Highlight any architectural decisions made

4. **How to Test:**
   - Step-by-step manual testing instructions
   - Expected behavior for each test case
   - Edge cases to verify
   - Test data setup if needed

5. **Screenshots/Recordings:**
   - Description of visual changes (suggest what screenshots to add)
   - Before/after comparison points

6. **Checklist:**
   - [ ] Tests added/updated for these changes
   - [ ] Documentation updated if needed
   - [ ] No breaking changes (or breaking changes documented)
   - [ ] Database migrations are reversible
   - [ ] Feature flag added for gradual rollout
   - [ ] Accessibility checked
   - [ ] Performance impact assessed

7. **Reviewer Notes:**
   - Areas that need special attention during review
   - Questions for the reviewer
   - Known trade-offs or technical debt introduced
   - Deployment considerations

**Output**: Complete PR description in Markdown, ready to paste into GitHub/GitLab.
#pull-request #code-review #git #collaboration

Writing PR descriptions, improving code review quality, team communication

Want Custom Prompts?

Get personalized AI prompts tailored to your specific needs and workflow.

Contact Us