Thanks to
### [Make your AI agents self-healing](https://github.com/latitude-dev/latitude-llm)
[Open Source.](https://github.com/latitude-dev/latitude-llm)
---
[](https://cloudback.it)
[](https://deepwiki.com/x1xhlol/system-prompts-and-models-of-ai-tools)
---
## Security Notice for AI Startups
> **Warning:** If you're an AI startup, make sure your data is secure. Exposed prompts or AI models can easily become a target for hackers.
> **Important:** Interested in securing your AI systems?
> Check out **[ZeroLeaks](https://zeroleaks.ai/)**, a service designed to help startups **identify and secure** prompt injection and system prompt extraction risks.
---
## Support the Project
If you find this collection valuable and appreciate the effort involved in obtaining and sharing these insights, please consider supporting the project.
You can show your support via:
- **Cryptocurrency:**
- **BTC:** `bc1q7zldmzjwspnaa48udvelwe6k3fef7xrrhg5625`
- **LTC:** `LRWgqwEYDwqau1WeiTs6Mjg85NJ7m3fsdQ`
- **ETH:** `0x3f844B2cc3c4b7242964373fB0A41C4fdffB192A`
- **Patreon:** https://patreon.com/lucknite
- **Ko-fi:** https://ko-fi.com/lucknite
Thank you for your support!
---
# Sponsors
Sponsor the most comprehensive repository of AI system prompts and reach thousands of developers.
[Get Started](mailto:lucasvalbuena@pm.me)
---
## Roadmap & Feedback
> Open an issue.
> **Latest Update:** 12/07/2026
---
## Connect With Me
- **X:** [Lucknite](https://x.com/Lucknite)
- **Discord**: `x1xhlol`
- **Email**: `lucasvalbuena@pm.me
**Drop a star if you find this useful!**
---
## 🚀 Quick Start Guide
This repository contains system prompts, tool definitions, and related prompt artifacts for a wide range of AI tools.
### Option 1: Browse Online
Navigate the folders in the repository and open the tool/vendor you want.
### Option 2: Clone Locally
```bash
git clone https://github.com/x1xhlol/system-prompts-and-models-of-ai-tools.git
cd system-prompts-and-models-of-ai-tools
```
### Option 3: Use as a Knowledge Base
1. Collect prompts relevant to your workflow
2. Load them into your preferred assistant, project, or note system
3. Build a comparison/reference workspace for prompt engineering
### Most Requested Additions Merged Here
- [Claude Design](./Anthropic/Claude%20Design/Create%20Design%20System.txt)
- [Claude Fable 5](./Anthropic/Claude%20Fable%205.txt)
- [Gemini 3.5 Prompt](./Google/Gemini/Gemini%203.5%20Prompt.txt)
- [GitHub Copilot](./GitHub/Copilot/Prompt.txt)
- [GitHub Spark](./GitHub/Spark/System%20Prompt.txt)
- [MiCode](./Xiaomi/MiCode/System%20Prompt.md)
---
## 📖 Repository Structure
The rebuilt workspace is organized primarily by **vendor / model family**.
Typical structure:
```
Vendor or Tool/
├── Prompt.txt / System Prompt.txt / *.md
├── Tools.json
└── Additional versions or related notes
```
Useful generated indexes:
- [Catalog](./CATALOG.md)
- [Prompt Index JSON](./prompts-index.json)
- [Prompt Inventory JSON](./prompts.json)
- [Rebuild Summary](./REBUILD_SUMMARY.md)
---
## 💡 Use Cases
### 🎯 For Developers
- Review prompt behavior across coding agents
- Compare tool schemas and agent capabilities
- Reuse prompt patterns for internal assistants
### 📝 For Researchers
- Track system-instruction evolution across tools
- Study prompt design patterns by vendor and product
- Build datasets for prompt analysis
### 🏢 For Teams
- Create internal reference libraries
- Standardize prompt review workflows
- Preserve historical prompt/tool snapshots
---
## 🤝 Contributing
Contributions are welcome.
### Suggested contribution flow
1. Add or update a tool/vendor folder
2. Keep filenames descriptive and consistent
3. Include tools/config JSON when available
4. Prefer clear provenance in PR descriptions
5. Update indexes or docs when structure changes substantially
### Recommended PR details
- Type: New Prompt / Update / Fix / Documentation
- Tool or Vendor
- Brief description of what changed
- Source / verification notes if available
Thanks to everyone who helps expand and clean up the repository.