Agentic OS Style Guide

Write for people who want to complete a setup or understand a concept quickly.

Writing rules

• Use simple English.
• Prefer active voice.
• Keep sentences short.
• Explain one idea at a time.
• Use examples when a concept is abstract.
• Link to related pages when the reader may need more context.
• Use the exact product terms from this guide.
• Do not include secrets, real tokens, private URLs, or real customer data.

Product terms

Page types

Use:

• Concept pages to explain what something is.
• How-to pages to help users finish one task.
• Tutorial pages to guide a first-time path.
• Reference pages for commands, settings, and APIs.
• Troubleshooting pages for symptoms, causes, and fixes.

Fumadocs components

Approved components:

• Callouts for warnings, notes, and important setup details.
• Cards for entry pages and topic overviews.
• Tabs when one task has separate paths, such as Docker, Coolify, Railway, and VPS.
• Collapsibles for optional detail.
• Titled code blocks for commands and config.
• Images with clear alt text.
• Tables for comparison and reference.

Use a component only when it makes the page easier to follow.

Visual rules

Follow the Command Centre visual direction.

• Use the Agentic OS / Command Centre logo from public/assets/.
• Use terracotta and orange as the main brand colors.
• Use neutral surfaces and high contrast text.
• Use Inter for body text when the platform allows it.
• Use Epilogue for headings when the platform allows it.
• Use Space Grotesk for labels or code-like UI text when practical.
• Keep the Fumadocs Notebook layout.

For exact tokens, see Visual style.

Examples

Good:

Run this command from the Agentic OS workspace.

Avoid:

Execute the following operation from the repository root directory context.

Links

Prefer internal links when a concept already has a page.

Examples:

• Link to Team OS when explaining hosted team setup.
• Link to Memory when explaining search or imports.
• Link to Troubleshooting when a setup step can fail.

Document Team OS safely

When you document Team OS, be precise about trust and permissions.

• Say which actor performs the action: owner, admin, member, local client, or hosted server.
• Say which resource is affected: team, client, skill, memory, file, or invite.
• Say what the server checks before allowing the action.
• Explain that the hosted server does not trust identity sent by a local client.
• Use placeholders for secrets, such as YOUR_DATABASE_URL and YOUR_AUTH_SECRET.
• Never publish real server URLs, tokens, passwords, cookies, or customer data.