Skip to content
ai.

Introduction

dotai is a CLI tool that generates correct configuration files for six AI coding tools from a single .ai/ directory. Write your rules, skills, and agents once — dotai produces the right files for Claude Code, Cursor, Codex, GitHub Copilot, OpenCode, and Antigravity automatically.

The Problem

Section titled “The Problem”

Every AI coding tool has its own configuration format:

ToolConfig files
Claude CodeCLAUDE.md, .claude/settings.json, .mcp.json
Cursor.cursor/rules/*.mdc, .cursor/mcp.json, .cursorignore
CodexAGENTS.md, .codex/config.toml
GitHub Copilot.github/copilot-instructions.md, .github/agents/*.agent.md, .vscode/mcp.json
OpenCode.opencode/instructions/*.md, .opencode/agents/*.md, opencode.json
Antigravity.agent/rules/*.md, .agent/skills/*/SKILL.md, mcp_config.json

When a team uses multiple tools — or different team members prefer different editors — the same rules must be maintained in multiple formats. Config drift is inevitable.

The Solution

Section titled “The Solution”

dotai introduces a single .ai/ directory as the source of truth:

.ai/
├── config.yaml          # Servers, hooks, permissions, settings, ignore patterns
├── directives/          # Markdown instruction files
│   ├── code-style.md
│   └── security.md
├── skills/              # Reusable knowledge packages
│   └── deploy/SKILL.md
└── agents/              # Specialized sub-agents
    └── reviewer.md

Run dotai sync and the CLI reads your .ai/ directory, applies scope precedence rules, and writes the correct output files for each target tool.

How It Works

Section titled “How It Works”
.ai/ sources  →  dotai sync  →  Claude Code files
                              →  Cursor files
                              →  Codex files
                              →  Copilot files
                              →  OpenCode files
                              →  Antigravity files
  1. Define your configuration in .ai/ using 8 entity types: directives, skills, agents, tool servers, hooks, permissions, settings, and ignore patterns.
  2. Sync with dotai sync to generate tool-specific files.
  3. Track changes with content hashing — dotai detects when generated files have been manually edited and warns before overwriting.

Next Steps

Section titled “Next Steps”