ai-project-bootstrap
Docs / The generated project / AI rules per tool

AI rules per tool

One source rule per technology, rendered into every tool's own format. A module author writes one file, not eight.

Tool
Where the rules land
Cursor
.cursor/rules/<id>.mdc
Claude Code
.claude/skills/<id>/SKILL.md
GitHub Copilot
.github/copilot-instructions.md + .github/instructions/<id>.instructions.md
Continue.dev
.continue/rules/<id>.md
Cline
.clinerules/<id>.md
Roo Code
.roo/rules/<id>.md
OpenAI Codex
AGENTS.md — read directly
Gemini CLI
GEMINI.md — read directly

What gets written

One rule per selected technology, plus a stack-agnostic set covering architecture, performance, testing and TypeScript. All of it renders from the same source content, so no two tools can quietly disagree about your conventions.

Claude Code frontmatter

SKILL.md needs frontmatter Claude can discover a skill by. The builder synthesises it: description from the manifest, and paths from the same globs the module's Cursor rule already declares. Cursor and Claude activate on the same files without a module author maintaining the glob list twice.

README, CLAUDE, AGENTS and GEMINI are unconditional

They are general project documentation, not per-technology rule output, so they are written regardless of which AI tools you selected.

Changing your mind later

# edit "aiTools" in ai-project.config.json, then:
npx ai-project-bootstrap upgrade
On this page
What gets writtenClaude Code frontmatterChanging your mind later
Source: ARCHITECTURE.md §Multi-provider