Skip to content

docs: recommended Trinity prompt page (#3187) - #3188

Merged
vybe merged 1 commit into
devfrom
docs/3187-recommended-fleet-prompt
Oct 3, 2026
Merged

vybe merged 1 commit into
devfrom
docs/3187-recommended-fleet-prompt

Conversation

@trinity-ability

Copy link
Copy Markdown
Contributor

Summary

Adds docs/user-docs/agents/recommended-fleet-prompt.md — a user-docs page for the Trinity prompt (Settings → General, trinity_prompt):

  • what the Trinity prompt is and how it relates to the platform instructions and each agent's CLAUDE.md
  • what not to put there (copies of platform instructions go stale)
  • the recommended prompt in one copy-pasteable block
  • per-rule evidence table with sources, plus caveats
  • note that a system manifest's top-level prompt: replaces it

Linked from guides/using-trinity.md (Settings → General row), the agent-guardrails See Also list, and the user-docs README index.

Docs only; no code or platform-instruction changes.

Closes #3187

🤖 Generated with Claude Code

…eet rules (#3187)

New page docs/user-docs/agents/recommended-fleet-prompt.md:
- what the Trinity prompt is: Settings → General (admin), the
  `trinity_prompt` setting, appended as "## Custom Instructions" to
  the platform instructions on every chat/task turn, and how it relates
  to the platform instructions and each agent's CLAUDE.md
- what not to put there: copies of platform instructions (they go stale
  and contradict the live text); keep it short
- the recommended prompt in one copy-pasteable block (verbatim from #3187)
- where it came from, a per-rule evidence table linking all 17 sources,
  and the caveats (benchmark scope, re-check after model upgrades,
  vendor claims)
- a note that a system manifest's top-level `prompt:` replaces it

Linked from the Settings → General row in guides/using-trinity.md, the
agent-guardrails See Also list, and the user-docs README index.

Docs only; no code or platform-instruction changes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@vybe vybe left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/validate-pr: Lane A (docs only). Links and anchors resolve; the '## Custom Instructions' placement and the manifest-prompt replacement claims match platform_prompt_service.py / system-manifest.md. All checks green.

@vybe
vybe merged commit 92647ee into dev Oct 3, 2026
23 checks passed
vybe pushed a commit that referenced this pull request Oct 3, 2026
…AUDE.md at startup (#3194) (#3195)

The Settings → Trinity Prompt section still described the file-based
delivery retired in #136: "injected into all agents' CLAUDE.md at startup",
"existing agents need to be restarted". get_platform_system_prompt() reads
trinity_prompt on every chat/task turn and appends it under
"## Custom Instructions" after the platform instructions, so admins were
told to restart agents for nothing.

Copy only, no behaviour change:
- description: added to every agent's instructions each turn; applies from
  the next turn, no restart
- field help: drops CLAUDE.md
- "How it works": real order (platform instructions, then Custom
  Instructions), warns that a system manifest's top-level `prompt:` replaces
  the setting, and carries the fleet-rules-only / keep-it-short guidance

The recommended-prompt docs page (#3187/#3188) is not published yet, so
the box carries its guidance without a link.

Test: src/frontend/tests/unit/trinityPromptCopy.spec.js mounts Settings.vue
(jsdom, admin, General tab) and asserts on rendered text. Before the copy
change, 5 of 6 tests went red on the rendered strings (the sixth, the
section-renders guard, stays green by design so the negatives can't pass
against an unrendered page).

Co-authored-by: Trinity Agent (trinity) <trinity-agent@ability.ai>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants