Skip to main content
The AI System Prompts Collection thrives on community contributions. Whether you’ve discovered new prompts, found updates to existing ones, or want to improve documentation, your contributions are valuable.

​
Ways to Contribute

Submit New Prompts

Add system prompts from AI tools not yet in the collection

Update Existing Prompts

Submit newer versions of prompts as tools evolve

Improve Documentation

Add context, READMEs, or clarifying notes

Report Issues

Let us know about outdated or incorrect prompts

​
Contribution Guidelines

​
Before You Contribute

1

Check for Duplicates

Search the repository to ensure the prompt isn’t already included. Check both the tool’s directory and any related directories.
2

Verify Authenticity

Ensure the prompts you’re submitting are genuine system prompts, not user-generated content or speculation.
3

Respect Ethics

Only submit prompts obtained through legitimate means. Do not submit prompts obtained through:
  • Hacking or unauthorized access
  • Violating terms of service
  • Exploiting security vulnerabilities maliciously
While this collection aims to be comprehensive, we’re committed to responsible disclosure. If you discover a serious security vulnerability, consider reporting it to the tool’s developers first before making it public.

​
How to Submit Prompts

​
Repository Structure

Follow the existing organization pattern: 
[Tool Name]/
├── README.md (optional, but recommended)
├── Prompt.txt
├── Version 2.0.txt (if multiple versions)
└── [Other relevant files]

​
File Naming Conventions

If there’s only one prompt for a tool:
Tool Name/Prompt.txt
or
Tool Name/System Prompt.txt

​
Step-by-Step Submission

1

Fork the Repository

Go to github.com/x1xhlol/system-prompts-and-models-of-ai-tools and click Fork in the top right.
2

Create a Branch

Create a descriptive branch for your contribution:
git checkout -b add-toolname-prompts
3

Add Your Files

Create the appropriate directory structure and add your prompt files:
mkdir "New Tool Name"
cd "New Tool Name"
# Add your prompt files
4

Include Context (Recommended)

Create a README.md in the tool’s directory with:
  • When the prompt was obtained
  • How it was obtained (if relevant)
  • Which version of the tool it’s from
  • Any special notes or observations
Example:
# Tool Name Prompts

System prompts from [Tool Name] version 2.5
Obtained: March 2026

## Notes
- This prompt is used for the agent mode
- Updated to include new tool calling capabilities
5

Commit Your Changes

Write a clear commit message:
git add .
git commit -m "Add [Tool Name] system prompts v2.5"
6

Push and Create PR

Push your branch and create a pull request:
git push origin add-toolname-prompts
Then open a pull request on GitHub with:
  • Clear title describing what you’re adding
  • Description of the prompts and their source
  • Any relevant context or notes

​
Quality Standards

To maintain the collection’s quality, please ensure:
Submit the full system prompt, not fragments or partial content. If you only have a portion, note this clearly in the README.
Use .txt files for prompts to ensure maximum compatibility. Avoid proprietary formats.
If known, include:
  • Which tool/platform the prompt is from
  • Version or date information
  • Any relevant model information (e.g., “uses Claude Sonnet 4.5”)
  • Remove unnecessary whitespace
  • Preserve the original structure and formatting
  • Use UTF-8 encoding

​
Updating Existing Prompts

When submitting updates to existing prompts:
Do not overwrite existing prompt files. Instead, add new files with version numbers or dates to preserve the historical record.
For example, if Tool Name/Prompt.txt exists:
  1. Rename it to Tool Name/Prompt v1.0.txt (if not already versioned)
  2. Add your new prompt as Tool Name/Prompt v2.0.txt
  3. Update the README to note both versions

​
Documentation Contributions

You can also help by:
  • Adding README files to directories that lack them
  • Improving existing documentation
  • Adding context about how prompts were obtained
  • Creating guides for specific use cases
  • Fixing typos or formatting issues

​
Reporting Issues

Found something wrong? Help us fix it:
1

Check Existing Issues

Search GitHub Issues to see if it’s already reported.
2

Create a New Issue

If not found, create a new issue with:
  • Clear title: “[Tool Name] prompt is outdated” or “Missing prompt for [Tool]”
  • Description: What’s wrong or what’s missing
  • Evidence: Links or screenshots if applicable
3

Suggest Solutions

If you know how to fix it, mention that in the issue. Even better, submit a PR!

​
Community Standards

When contributing:

Be Respectful

Treat other contributors with respect. We’re all here to learn and share.

Be Accurate

Only submit verified information. If you’re uncertain, ask or note your uncertainty.

Be Responsible

Consider the ethical implications of what you’re sharing. Our goal is education, not exploitation.

Be Patient

Pull requests are reviewed as time allows. Maintainers volunteer their time.

​
Recognition

Contributors are valued members of the community:
  • Your GitHub profile will appear in the repository’s contributor list
  • Significant contributions may be highlighted in updates
  • You’re helping thousands of developers and researchers learn

​
Questions?

Not sure about something? Reach out:

Ready to Contribute?

Head to the GitHub repository and start your first contribution

Build docs developers (and LLMs) love

Get started for freeTalk to us