Merge e34acb79d4 into d4c87387f5

Update Prompt.txt

README.md

@@ -1,4 +1,4 @@
-# **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**  
+# **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>
 
@@ -21,7 +21,8 @@
 
 ## 📂 Available Files
 
-- **v0 Folder**  
+- **v0 Folder**
+- **Spawn Folder**  
 - **Manus Folder**  
 - **Lovable Folder**  
 - **Devin Folder**  

Spawn/Prompt.txt

@@ -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

void/void.txt

@@ -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 USER’s state—including open files, terminal history, git context, and any visible stack traces—may be attached.
+This information may or may not be relevant. It’s 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:  
+- Don’t 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.  
+Let’s build something excellent.