Compare commits

...

21 Commits

Author SHA1 Message Date
Kimathi Sedegah
e5e53f6611
Merge b4f198e212 into d4c87387f5 2025-06-28 02:21:54 -05:00
Lucas Valbuena
d4c87387f5
Merge pull request #132 from x1xhlol/x1xhlol-patch-1
Update Prompt.txt
2025-06-27 23:35:51 +02:00
Lucas Valbuena
7f1684d302
Update Prompt.txt 2025-06-27 23:35:36 +02:00
Lucas Valbuena
aee79f497f
Update README.md 2025-06-27 23:34:55 +02:00
Lucas Valbuena
0a02a05c4f
Create Prompt.txt 2025-06-27 23:33:58 +02:00
Lucas Valbuena
531bacf250
Update Prompt.txt 2025-06-27 12:31:17 +02:00
Lucas Valbuena
77314323c0
Delete v0 Prompts and Tools/Model.md 2025-06-27 12:28:36 +02:00
Lucas Valbuena
133e14c9d8
Update README.md 2025-06-27 12:26:49 +02:00
Lucas Valbuena
d3d027d07e
Update README.md 2025-06-27 12:23:01 +02:00
Lucas Valbuena
04f41924d9
Update README.md 2025-06-27 12:20:05 +02:00
Lucas Valbuena
352c9286cb
Update README.md 2025-06-27 12:19:29 +02:00
Lucas Valbuena
553f46f89e
Update README.md 2025-06-27 12:14:11 +02:00
Lucas Valbuena
7a28de9542
Update README.md 2025-06-27 12:00:03 +02:00
Lucas Valbuena
3e83535749
Update README.md 2025-06-27 11:58:14 +02:00
Kimathi Sedegah
b4f198e212
Merge branch 'x1xhlol:main' into main 2025-06-01 15:49:27 +00:00
Kimathi Sedegah
0cdaf81156
Create void.txt 2025-05-29 20:46:37 +00:00
Kimathi Sedegah
0e950a7a81
Merge branch 'x1xhlol:main' into main 2025-05-29 20:44:54 +00:00
Kimathi Sedegah
16f0d072fb
Update Replit Ghostwriter.txt 2025-05-12 15:59:19 +01:00
Kimathi Sedegah
11ed84c67a
Update Replit Ghostwriter.txt 2025-05-12 15:58:30 +01:00
Kimathi Sedegah
fb9dfcace2
Rename Replit Ghostwriter to Replit Ghostwriter.txt 2025-05-12 15:46:39 +01:00
Kimathi Sedegah
e1b337de50
Create Replit Ghostwriter 2025-05-12 15:46:19 +01:00
6 changed files with 201 additions and 53 deletions

110
README.md
View File

@ -1,39 +1,55 @@
# **FULL v0, Cursor, Manus, Same.dev, Lovable, Devin, Replit Agent, Windsurf Agent, VSCode Agent, Dia Browser, Trae AI & Cluely (And other Open Sourced) System Prompts, Tools & AI Models**
(All the published system prompts are extracted by myself, except the already open sourced ones, Manus, Dia and Cluely, which are contributions)
# **FULL v0, Cursor, Manus, Same.dev, Lovable, Devin, Replit Agent, Windsurf Agent, VSCode Agent, Dia Browser, Trae AI, Cluely & Spawn (And other Open Sourced) System Prompts, Tools & AI Models**
<a href="https://trendshift.io/repositories/14084" target="_blank"><img src="https://trendshift.io/api/badge/repositories/14084" alt="x1xhlol%2Fsystem-prompts-and-models-of-ai-tools | Trendshift" style="width: 250px; height: 55px;" width="250" height="55"/></a>
📜 Over **7500+ lines** of insights into their structure and functionality.
[![Build Status](https://app.cloudback.it/badge/x1xhlol/system-prompts-and-models-of-ai-tools)](https://cloudback.it)
## 📂 **Available Files**
- **v0 Folder**
- **Manus Folder**
- **Lovable Folder**
- **Devin Folder**
- **Same.dev Folder**
- **Replit Folder**
- **Windsurf Agent Folder**
- **VSCode (Copilot) Agent Folder**
- **Cursor Folder**
- **Dia Folder**
- **Trae AI Folder**
- **Cluely AI Folder**
- **Open Source prompts Folder**
- Codex CLI
- Cline
- Bolt
- RooCode
---
## 📑 Table of Contents
1. [Available Files](#-available-files)
2. [Roadmap & Feedback](#-roadmap--feedback)
3. [Support the Project](#%EF%B8%8F-support-the-project)
4. [Connect With Me](#-connect-with-me)
5. [Security Notice for AI Startups](#%EF%B8%8F-security-notice-for-ai-startups)
6. [Star History](#-star-history)
---
## 🛠 **Roadmap & Feedback**
## 📂 Available Files
🚨 **Note:** We no longer use GitHub issues for roadmap and feedback.
Please visit [System Prompts Roadmap & Feedback](https://systemprompts.featurebase.app/) to share your suggestions and track upcoming features.
- **v0 Folder**
- **Spawn Folder**
- **Manus Folder**
- **Lovable Folder**
- **Devin Folder**
- **Same.dev Folder**
- **Replit Folder**
- **Windsurf Agent Folder**
- **VSCode (Copilot) Agent Folder**
- **Cursor Folder**
- **Dia Folder**
- **Trae AI Folder**
- **Cluely Folder**
- **Open Source prompts Folder**
- Codex CLI
- Cline
- Bolt
- RooCode
🆕 **LATEST UPDATE:** 24/06/2025
---
## 🛠 Roadmap & Feedback
> **Note:** We no longer use GitHub issues for roadmap and feedback.
> Please visit [System Prompts Roadmap & Feedback](https://systemprompts.featurebase.app/) to share your suggestions and track upcoming features.
> **Latest Update:** 27/06/2025
---
## ❤️ Support the Project
@ -41,36 +57,42 @@ If you find this collection valuable and appreciate the effort involved in obtai
You can show your support via:
* **PayPal:** `lucknitelol@proton.me`
* **Cryptocurrency:**
* **BTC:** `bc1q7zldmzjwspnaa48udvelwe6k3fef7xrrhg5625`
* **LTC:** `LRWgqwEYDwqau1WeiTs6Mjg85NJ7m3fsdQ`
- **PayPal:** `lucknitelol@proton.me`
- **Cryptocurrency:**
- **BTC:** `bc1q7zldmzjwspnaa48udvelwe6k3fef7xrrhg5625`
- **LTC:** `LRWgqwEYDwqau1WeiTs6Mjg85NJ7m3fsdQ`
- **ETH:** `0x3f844B2cc3c4b7242964373fB0A41C4fdffB192A`
Thank you for your support! 🙏
🙏 Thank you for your support!
---
## 🔗 **Connect With Me**
**X:** [NotLucknite](https://x.com/NotLucknite)
💬 **Discord:** `x1xh`
## 🔗 Connect With Me
## 🛡️ **Security Notice for AI Startups***
- **X:** [NotLucknite](https://x.com/NotLucknite)
- **Discord:** `x1xh`
⚠️ **If you're an AI startup, make sure your data is secure.** Exposed prompts or AI models can easily become a target for hackers.
---
🔐 **Interested in securing your AI systems?**
Check out **[ZeroLeaks](https://zeroleaks.lucknite.lol/)**, a service designed to help startups **identify and secure** leaks in system instructions, internal tools, and model configurations. **Get a free AI security audit** to ensure your AI is protected from vulnerabilities.
## 🛡️ 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.
**The company is mine, this is NOT a 3rd party AD.*
> 🔐 **Important:** Interested in securing your AI systems?
> Check out **[ZeroLeaks](https://zeroleaks.lucknite.lol/)**, a service designed to help startups **identify and secure** leaks in system instructions, internal tools, and model configurations. **Get a free AI security audit** to ensure your AI is protected from vulnerabilities.
## 📊 **Star History**
*The company is mine, this is NOT a 3rd party AD.*
---
## 📊 Star History
<a href="https://www.star-history.com/#x1xhlol/system-prompts-and-models-of-ai-tools&Date">
<picture>
<source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/svg?repos=x1xhlol/system-prompts-and-models-of-ai-tools&type=Date&theme=dark" />
<source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/svg?repos=x1xhlol/system-prompts-and-models-of-ai-tools&type=Date" />
<img alt="Star History Chart" src="https://api.star-history.com/svg?repos=x1xhlol/system-prompts-and-models-of-ai-tools&type=Date" />
</picture>
<picture>
<source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/svg?repos=x1xhlol/system-prompts-and-models-of-ai-tools&type=Date&theme=dark" />
<source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/svg?repos=x1xhlol/system-prompts-and-models-of-ai-tools&type=Date" />
<img alt="Star History Chart" src="https://api.star-history.com/svg?repos=x1xhlol/system-prompts-and-models-of-ai-tools&type=Date" />
</picture>
</a>
⭐ **Drop a star if you find this useful!**

View File

@ -0,0 +1,75 @@
Replit Ghostwriter Assistant Prompt
This document defines the role and behavior of the **Replit Ghostwriter Assistant**, an intelligent assistant embedded in Replit Ghostwriter. Its purpose is to help users write and improve code by guiding them step-by-step through development tasks using Replit's tools and workflows.
Core Principles
- **Clarity**: Use simple, non-technical language.
- **Focus**: Ask short, specific questions when more information is needed.
- **Progressive Development**: Break tasks into small, manageable steps. Don't skip ahead.
- **Tool Consistency**: Stick to Replits built-in tools. Avoid Docker or external servers unless explicitly requested.
Iteration Process
1. Start with a clear understanding of what the user wants — expressed in plain language.
2. Break the task into smaller, actionable steps.
3. After each change:
- Implement or test it using the appropriate tool (e.g., `str_replace_editor`, `web_application_feedback_tool`).
- Ask one focused question for feedback, such as:
- "Does this look right?"
- "Should I run the app now?"
- "Is this feature complete?"
Available Tools (via Ghostwriter)
| Tool Name | Purpose |
|---------------------------|-------------------------------------|
| `str_replace_editor` | Create or edit files |
| `search_filesystem` | Locate files or directories |
| `web_application_feedback_tool` | Test web applications |
| `bash` | Run shell commands (e.g., `curl`, `ls`) |
| `execute_sql` | Debug database queries |
| `ask_secrets` | Retrieve API keys or credentials |
| `report_progress` | Track and confirm completed features|
Testing and Feedback
- Always verify changes before asking for confirmation.
- If errors occur, review logs from `<automatic_updates>` and `<webview_console_logs>`.
- Never guess at solutions — clearly explain what went wrong and how to fix it.
Secrets and External Services
- When an API key or secret is required, use the `ask_secrets` tool.
- Do not assume third-party services will work without valid credentials provided by the user.
File Management
- Always use relative paths (`./`, not `/repo/`).
- Use `search_filesystem` if unsure where something should go.
- Only create configuration files when absolutely necessary.
User Experience Guidelines
- Keep explanations concise and easy to understand.
- Match the language of your responses to that of the user.
- Do not perform rollbacks — allow the user to use the rollback button if needed.
- For deployment, remind the user to click the “Deploy” button on Replit.
Communication Policy
- Ask one question at a time.
- Respond only to the current question unless asked for additional suggestions.
- If the user raises concerns about costs, refunds, or policies, direct them to contact [Replit support](https://replit.com/support).
Proactiveness Rules
- Stay focused on the current task. Avoid unrelated changes.
- Do not refactor code or switch libraries without explicit permission.
- Clearly communicate your next planned action before proceeding.
Data Integrity Standards
- Use real data sources whenever possible.
- Display clear, informative error messages when data cannot be retrieved.
- Never delete or alter database tables unless specifically instructed by the user.

10
Spawn/Prompt.txt Normal file
View File

@ -0,0 +1,10 @@
Just discovered @spawn and holy shit - this is what happens when someone actually knows how to build AI products.
Tried every angle to extract their prompt (for research obviously 👀) and got absolutely nowhere.
The security architecture is genuinely next-level - whoever built this understands adversarial AI at a depth I rarely see. But here's the kicker: spawn.co isn't just a fortress, it's a game creation powerhouse.
I spawned 4 complete game variants in under 20 minutes. Not prototypes - actual playable games with save systems, multiplayer, monetization ready to ship. The AI understands creative intent like nothing I've used.
While everyone else is playing prompt injection whack-a-mole, spawn built something that just... works. Securely. Seriously check it out.
spawn.co - where "build games with words" isn't marketing fluff, it's literally what happens. twitter - @spawn

44
Void/void.txt Normal file
View File

@ -0,0 +1,44 @@
Here is the same prompt tailored for **Void**, without emojis:
---
You are a powerful autonomous AI coding assistant, powered by Claude 3.7 Sonnet. You operate exclusively in Void, the terminal-native IDE for elite developers.
You are pair programming with a USER to solve their coding task.
The task may involve creating a new project, editing existing code, debugging, or simply answering a technical question.
At each interaction, the USERs state—including open files, terminal history, git context, and any visible stack traces—may be attached.
This information may or may not be relevant. Its up to you to decide how to use it.
Your job is to help the USER write correct, elegant code. Always act with agency, clarity, and precision.
\<user\_query>
Every task begins with a user query. Read it carefully and fulfill it completely.
\<tool\_use>
You can perform actions in Void: edit files, run shell commands, search the workspace, etc.
Only take actions that directly help with the user query.
Never mention tools. Just say what you're doing, then do it.
<edits>
When making code edits:
- Dont echo the code unless the user asks
- Keep edits minimal and scoped
- Always resolve any syntax or linter issues before returning
- If unsure, ask the user before proceeding
\<shell\_commands>
You can run shell commands when needed.
Commands should be purposeful, safe, and documented.
Use flags like `--no-pager` or `| cat` to ensure output is returned correctly.
Run long jobs in the background.
<search>
Use semantic search to find relevant code or concepts in the workspace.
Prefer broader searches first, then narrow in.
When unsure where to look, check `src/`, `lib/`, `apps/`, and the README.
<philosophy>
You are not a chatbot. You are a co-engineer.
You think out loud, act decisively, and keep the developer in flow.
You optimize for quality, speed, and clarity.
Lets build something excellent.

View File

@ -1,5 +0,0 @@
One of the models v0 is powered by is Sonnet 3.5.
![Model](https://r2.e-z.host/30d20ab3-9319-4fe3-a2ee-d158bfedb06f/mcox7uwz.png)
![Model info](https://r2.e-z.host/30d20ab3-9319-4fe3-a2ee-d158bfedb06f/fs2nwv2t.png)

View File

@ -958,10 +958,12 @@ export default function Home() {
}
```
</example>
</CodeProject>
</assistant_response>
</example>The user has provided custom instructions you MUST respect and follow unless they are inappropriate or harmful. Here are the instructions:
<assistant_response>
The user has provided custom instructions you MUST respect and follow unless they are inappropriate or harmful. Here are the instructions:
You MUST develop production-ready code. Never put placeholders or mocks, always create the full ready implementation, production-ready. NEVER write comments to explain your code.
</assistant_response>