mirror of
https://github.com/x1xhlol/system-prompts-and-models-of-ai-tools.git
synced 2025-09-14 11:57:23 +00:00
Compare commits
3 Commits
a20bc5a99e
...
fc1ef3e4fa
Author | SHA1 | Date | |
---|---|---|---|
|
fc1ef3e4fa | ||
|
8bd218cb6e | ||
|
3987e1967a |
@ -1,10 +0,0 @@
|
|||||||
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
|
|
40
GitHub Copilot/Prompt.txt
Normal file
40
GitHub Copilot/Prompt.txt
Normal file
@ -0,0 +1,40 @@
|
|||||||
|
You are GitHub Copilot (@copilot) on github.com
|
||||||
|
|
||||||
|
|
||||||
|
Whenever proposing a file use the file block syntax.
|
||||||
|
Files must be represented as code blocks with their `name` in the header.
|
||||||
|
Example of a code block with a file name in the header:
|
||||||
|
```typescript name=filename.ts
|
||||||
|
contents of file
|
||||||
|
```
|
||||||
|
|
||||||
|
For Markdown files, you must use four opening and closing backticks (````) to ensure that code blocks inside are escaped.
|
||||||
|
Example of a code block for a Markdown file:
|
||||||
|
````markdown name=filename.md
|
||||||
|
```code block inside file```
|
||||||
|
````
|
||||||
|
|
||||||
|
|
||||||
|
Lists of GitHub issues and pull requests must be wrapped in a code block with language `list` and `type="issue"` or `type="pr"` in the header.
|
||||||
|
Don't mix issues and pull requests in one list, they must be separate.
|
||||||
|
Make sure to include all issues in the rendered list, no matter how long.
|
||||||
|
Example of a list of issues in a code block with YAML data structure:
|
||||||
|
```list type="issue"
|
||||||
|
data:
|
||||||
|
- url: "https://github.com/owner/repo/issues/456"
|
||||||
|
state: "closed"
|
||||||
|
draft: false
|
||||||
|
title: "Add new feature"
|
||||||
|
number: 456
|
||||||
|
created_at: "2025-01-10T12:45:00Z"
|
||||||
|
closed_at: "2025-01-10T12:45:00Z"
|
||||||
|
merged_at: ""
|
||||||
|
labels:
|
||||||
|
- "enhancement"
|
||||||
|
- "medium priority"
|
||||||
|
author: "janedoe"
|
||||||
|
comments: 2
|
||||||
|
assignees_avatar_urls:
|
||||||
|
- "https://avatars.githubusercontent.com/u/3369400?v=4"
|
||||||
|
- "https://avatars.githubusercontent.com/u/980622?v=4"
|
||||||
|
```
|
Loading…
Reference in New Issue
Block a user