Compare commits

...

4 Commits

Author SHA1 Message Date
Kimathi Sedegah
943b391c7c
Merge e34acb79d4 into 7f10715dc9 2025-07-15 14:15:38 +10:00
Lucas Valbuena
7f10715dc9
Update README.md 2025-07-14 22:47:44 +02:00
Kimathi Sedegah
e34acb79d4
Update void.txt 2025-05-29 20:42:07 +00:00
Kimathi Sedegah
dad979a59e
Create void.txt 2025-05-29 20:38:12 +00:00
2 changed files with 64 additions and 20 deletions

View File

@ -6,16 +6,32 @@
[![Build Status](https://app.cloudback.it/badge/x1xhlol/system-prompts-and-models-of-ai-tools)](https://cloudback.it)
---
## ❤️ 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. Your contribution helps keep this resource updated and allows for further exploration.
You can show your support via:
- **PayPal:** `lucknitelol@proton.me`
- **Cryptocurrency:**
- **BTC:** `bc1q7zldmzjwspnaa48udvelwe6k3fef7xrrhg5625`
- **LTC:** `LRWgqwEYDwqau1WeiTs6Mjg85NJ7m3fsdQ`
- **ETH:** `0x3f844B2cc3c4b7242964373fB0A41C4fdffB192A`
🙏 Thank you for your support!
---
## 📑 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)
3. [Connect With Me](#-connect-with-me)
4. [Security Notice for AI Startups](#%EF%B8%8F-security-notice-for-ai-startups)
5. [Star History](#-star-history)
---
@ -43,22 +59,6 @@
---
## ❤️ 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. Your contribution helps keep this resource updated and allows for further exploration.
You can show your support via:
- **PayPal:** `lucknitelol@proton.me`
- **Cryptocurrency:**
- **BTC:** `bc1q7zldmzjwspnaa48udvelwe6k3fef7xrrhg5625`
- **LTC:** `LRWgqwEYDwqau1WeiTs6Mjg85NJ7m3fsdQ`
- **ETH:** `0x3f844B2cc3c4b7242964373fB0A41C4fdffB192A`
🙏 Thank you for your support!
---
## 🛠 Roadmap & Feedback
> **Note:** We no longer use GitHub issues for roadmap and feedback.

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.