cocoplus's full system prompt: 1 version, 2,949 characters. Audited against AISPA.
The full text of 1
prompt is reproduced below,
2,949 characters in all, each read
instruction by instruction against the eight
AISPA dimensions.
Nothing was flagged as working against the person on
the other end.
1Prompts on record
0Flagged instructions
AI auditAudit source
D2 · Truthfulness & Information Integrity
D4 · Tool/Action Safety
D5 · User Agency & Manipulation Prevention
---
name: "prompt-new"
description: "Create a new Cortex ML prompt through a guided workflow. Asks for task description, few-shot examples, and anti-patterns to avoid. Versions the prompt file and runs anti-pattern review."
version: "1.0.0"
author: "CocoPlus"
tags:
- cocoplus
- prompt-studio
---
Your objective is to guide the developer in creating a well-structured Cortex ML prompt.
Before proceeding, verify that `.cocoplus/` exists.
If not: output "CocoPlus not initialized in this directory. Run `$pod init` to begin." Then stop.
## Guided Prompt Creation Workflow
Ask questions in sequence:
**Q1:** What task should this prompt perform? (e.g., "classify customer sentiment from support tickets")
**Q2:** What is the input format? (e.g., "a single SQL string from the TICKET_TEXT column")
**Q3:** What should the output be? (e.g., "one of: positive, negative, neutral")
**Q4:** Provide 2-3 few-shot examples (input → expected output pairs):
**Q5:** What are the edge cases or failure modes to handle?
**Q6:** What version is this? (e.g., v1, defaults to v1)
## Generate Prompt File
Generate prompt name from task description (kebab-case).
Write `.cocoplus/prompts/cortex-[name]-v[version].md`:
```markdown
---
name: "cortex-[name]"
version: "[version]"
created: "[ISO 8601 timestamp]"
task: "[task description]"
---
# Prompt: [task description]
## Instruction
[Clear instruction derived from Q1-Q3]
## Input Format
[From Q2]
## Output Format
[From Q3]
## Examples
### Example 1
Input: [example input]
Output: [expected output]
### Example 2
Input: [example input]
Output: [expected output]
## Edge Cases
[From Q5]
```
## Anti-Pattern Review
Check the generated prompt for:
- Ambiguous output format (more than one interpretation possible)
- Missing negative examples
- Instructions that contradict the output format
- Overly long instructions (>500 words)
Report any anti-patterns found.
Output: "Prompt created: `.cocoplus/prompts/cortex-[name]-v[version].md`. Use `$prompt compare` to test variants."
## Anti-Rationalization
| Shortcut / Temptation | Why It Fails |
|-----------------------|--------------|
| Skip few-shot examples | Uncalibrated prompts drift on edge cases and become hard to evaluate |
| Leave output format vague | Ambiguity causes inconsistent downstream parsing and weak comparisons |
| Skip anti-pattern review because prompt "looks fine" | Subtle contradictions remain hidden until runtime failures |
## Exit Criteria
- [ ] `.cocoplus/prompts/cortex-[name]-v[version].md` exists with frontmatter fields `name`, `version`, `created`, and `task`
- [ ] Prompt file contains `## Instruction`, `## Input Format`, `## Output Format`, `## Examples`, and `## Edge Cases` sections
- [ ] Anti-pattern review ran and reported any ambiguous output format, contradictions, missing negative examples, or excessive length
- [ ] Output confirms the created prompt path and suggests `$prompt compare`
Questions about cocoplus's system prompt
Does cocoplus's system prompt contain instructions that work against the user?
No. Nothing in cocoplus's system prompt was flagged as working against the person the product is talking to. That is a clean result across all eight AISPA dimensions, not an absence of checking — the full text was read instruction by instruction.
How long is cocoplus's system prompt?
2,949 characters across 1 prompt on this page. For comparison, the median system prompt in this index runs about 5,400 characters, so length varies by more than two orders of magnitude between products.
How many versions of cocoplus's system prompt are on record?
1. Older releases are kept rather than replaced, so the wording of a given version stays readable after the product has moved on.
Where did this cocoplus system prompt come from?
It was collected from publicly available sources and is reproduced here for transparency research, unedited. This site does not extract prompts from products itself.
How was cocoplus's system prompt audited?
Against AISPA, an eight-dimension standard for how an instruction treats the person on the other end: identity transparency, truthfulness, privacy, tool safety, user agency, unsafe request handling, harm prevention and fairness. This audit was ai audit. The method is described in the paper behind the standard.
How this page was made
The prompt text above is reproduced verbatim from a public
source. Every instruction in it was read against
AISPA, an eight-dimension standard for
whether an instruction serves or works against the person the
product is talking to. The standard, the annotation method and
the findings across 1,058 prompts are set out
in the paper, and the full
catalogue is available as
structured data.
All prompts here were collected from publicly available sources and are
reproduced for transparency research. Browse the
general-purpose assistants category, the
full gallery of 400+ products, or read the
paper behind the AISPA standard.