Claude Project System Prompt

# Export format: Claude Project system prompt

Claude Projects accept a long-form markdown system prompt. There is no
hard character limit at export time, but model behavior follows relevance
more than volume — keep it tight and well-structured.

## Output language

**Render all user-visible labels and section titles in the user's
conversation language** — not the language this template file is written
in. The English labels below are canonical references for maintainers;
translate them at render time. Body content inherits its language from
the source files.

For example, a Chinese-speaking user gets `## 关于我` instead of
`## About me`, even though this template uses English headings throughout.

## Structure

Render as a single markdown document with these sections, in order:

1. **About me** — from role pack's identity + responsibilities & goals
2. **Active project context** — from project pack's summary + goal +
   current status
3. **Key decisions** — from project pack's decisions (preserve the "why")
4. **Do not re-suggest** — from project pack's explicitly rejected options
   (this section earns its own heading because it's the highest-value
   context for avoiding repeated AI mistakes)
5. **How I like to work** — from role pack's collaboration preferences
6. **Never** — from role pack's taboos
7. **Tools & stack** — merged from role + project, deduplicated

If the user's export slice doesn't include a role (or doesn't include a
project), simply omit the sections that would have drawn from the missing
side. Don't insert empty headings.

## Style rules

- Use markdown headings (`##`) and bullet lists. Avoid wall-of-text paragraphs.
- Keep language concise — this is reference material the model reads on
  every turn in the project. Verbosity costs attention budget.
- Preserve the user's exact phrasing wherever opinion, taste, or voice is
  involved (collaboration preferences, taboos, voice descriptions).
  Paraphrasing these is a silent lie about the user.
- At the bottom of the document, include an "updated:" footer line listing
  the source files and their `updated:` dates, so the user can audit
  staleness at a glance.

Example footer: