--- description: Sim product language, positioning, and tone guidelines globs: ["apps/sim/app/(landing)/**", "apps/docs/**", "apps/sim/app/manifest.ts", "apps/sim/app/sitemap.ts", "apps/sim/app/robots.ts", "apps/sim/app/llms.txt/**", "apps/sim/app/llms-full.txt/**", "apps/sim/app/(landing)/**/structured-data*", "apps/docs/**/structured-data*", "**/metadata*", "**/seo*"] --- # Sim — Language & Positioning When editing user-facing copy (landing pages, docs, metadata, marketing), follow these rules. ## Identity Sim is the **AI workspace** where teams build and run AI agents. Not a workflow tool, not an agent framework, not an automation platform. **Short definition:** Sim is the open-source AI workspace where teams build, deploy, and manage AI agents. **Full definition:** Sim is the open-source AI workspace where teams build, deploy, and manage AI agents. Connect 1,000+ integrations and every major LLM to create agents that automate real work — visually, conversationally, or with code. ## Audience **Primary:** Teams building AI agents for their organization — IT, operations, and technical teams who need governance, security, lifecycle management, and collaboration. **Secondary:** Individual builders and developers who care about speed, flexibility, and open source. ## Required Language | Concept | Use | Never use | |---------|-----|-----------| | The product | "AI workspace" | "workflow tool", "automation platform", "agent framework" | | Building | "build agents", "create agents" | "create workflows" (unless describing the workflow module specifically) | | Visual builder | "workflow builder" or "visual builder" | "canvas", "graph editor" | | Mothership | "Mothership" (capitalized) | "chat", "AI assistant", "copilot" | | Deployment | "deploy", "ship" | "publish", "activate" | | Audience | "teams", "builders" | "users", "customers" (in marketing copy) | | What agents do | "automate real work" | "automate tasks", "automate workflows" | | Our advantage | "open-source AI workspace" | "open-source platform" | ## Tone - **Direct.** Short sentences. Active voice. Lead with what it does. - **Concrete.** Name specific things — "Slack bots, compliance agents, data pipelines" — not abstractions. - **Confident, not loud.** No exclamation marks or superlatives. - **Simple.** If a 16-year-old can't understand the sentence, rewrite it. ## Claim Hierarchy When describing Sim, always lead with the most differentiated claim: 1. **What it is:** "The AI workspace for teams" 2. **What you do:** "Build, deploy, and manage AI agents" 3. **How:** "Visually, conversationally, or with code" 4. **Scale:** "1,000+ integrations, every major LLM" 5. **Trust:** "Open source. SOC2. Trusted by 100,000+ builders." ## Module Descriptions | Module | One-liner | |--------|-----------| | **Mothership** | Your AI command center. Build and manage everything in natural language. | | **Workflows** | The visual builder. Connect blocks, models, and integrations into agent logic. | | **Knowledge Base** | Your agents' memory. Upload docs, sync sources, build vector databases. | | **Tables** | A database, built in. Store, query, and wire structured data into agent runs. | | **Files** | Upload, create, and share. One store for your team and every agent. | | **Logs** | Full visibility, every run. Trace execution block by block. | ## What We Never Say - Never call Sim "just a workflow tool" - Never compare only on integration count — we win on AI-native capabilities - Never use "no-code" as the primary descriptor — say "visually, conversationally, or with code" - Never promise unshipped features - Never use jargon ("RAG", "vector database", "MCP") without plain-English explanation on public pages - Avoid "agentic workforce" as a primary term — use "AI agents" ## Vision Sim becomes the default environment where teams build AI agents — not a tool you visit for one task, but a workspace you live in. Workflows are one module; Mothership is another. The workspace is the constant; the interface adapts.