Skip to content

AI tool integration

How OTF works with Claude Code, Cursor and Antigravity.

OTF is AI-native by design. Every kit ships with config files for the major AI coding assistants so that "ask Claude to add a screen" or "tell Cursor to wire a route" produces code that follows the kit's conventions — not Claude's training data's conventions.

What "AI-native" means here

Three claims that aren't quite the same:

  1. The kits include AI configs out of the box. Every kit has a CLAUDE.md, .cursorrules, task prompts under ai/prompts. Open the kit in any of these tools and you don't need to explain anything — the tool already knows the stack, the file map, the conventions, the deploy flow.

  2. The configs are kept in sync. A single source of truth (the upcoming @otfdashkit/ai CLI) generates each tool's file, so they don't drift. Manual edits live inside // @otf-keep blocks that the regenerator never overwrites.

  3. Components are designed to be modified. Every component sits in a single file. Names are explicit. There's no clever inheritance. AI tools edit them cleanly because a human would too.

The four supported tools

ToolConfig file shippedHow it reads context
Claude CodeCLAUDE.md, AGENTS.mdAuto-loaded into every prompt
Cursor.cursorrulesAuto-loaded into chat
AntigravityAGENTS.mdRead by the agent on session start

If you use a different tool (Aider, Continue, GitHub Copilot Workspace), point it at AGENTS.md — it's the most universally-readable of the configs.

What's in a kit's CLAUDE.md

Take the SaaS Dashboard kit as a reference. Its CLAUDE.md contains:

  • Stack table — Vite + React 19 + TanStack Router + TanStack Query + Hono + Drizzle + Better Auth
  • Project structure — top-down map of src/, server/, where each entity lives
  • Patterns — the canonical optimistic-update hook shape, Hono route shape, screen-add procedure
  • Theming — token classes only, CSS load order, default theme bootstrap
  • Conventions — no comments unless explaining a non-obvious why; strict TypeScript; functional components; Tailwind tokens only
  • Deploy — exact command to ship; what env vars are required

That's enough for an AI to add a new screen, wire a Hono route, or refactor a component without diverging from the rest of the codebase.

What's coming: @otfdashkit/ai CLI

Currently each kit's CLAUDE.md / .cursorrules / AGENTS.md are hand-maintained. Phase 6 of the OTF roadmap ships @otfdashkit/ai — a CLI that:

  • Reads a single otf.config.ts per project
  • Generates CLAUDE.md and .cursorrules from one source
  • Preserves manual customizations inside // @otf-keep blocks
  • Re-runs cleanly on every kit update so the configs stay in sync with the codebase
# (coming soon)
npx @otfdashkit/ai generate --tools=claude,cursor,antigravity

Until that ships, the per-tool guides below describe the file structures by hand.

Per-tool guides

FAQ

Free with your email

Get the free AI configs pack

The AI files every kit ships with. Drop them in and your AI tool knows your project.

  • CLAUDE.mdProject context
  • .cursorrulesRules for Cursor
  • prompts/Task prompts

No spam. Unsubscribe any time.