lnai — Unified AI Config for Claude, Cursor, Copilot & More

What it is

lnai is a CLI tool that lets developers define AI coding tool configurations in a single .ai/ directory and automatically sync them to native config formats for seven or more tools: Claude Code (CLAUDE.md), Cursor (.cursor/rules), GitHub Copilot (.github/copilot-instructions.md), Gemini CLI (GEMINI.md), Codex (AGENTS.md), OpenCode, and Windsurf (.windsurfrules).

The target audience is developers and teams who use multiple AI coding assistants and are tired of maintaining duplicate config files. Instead of writing the same rules in five different formats, you write them once and let lnai generate the rest.

How it saves time or tokens

Maintaining separate config files for each AI tool is tedious and error-prone. When you update a coding standard in one file, you have to remember to update all the others. lnai eliminates this duplication -- a single lnai sync command propagates changes to every tool. This also prevents the common problem where one tool follows updated rules while another still operates on stale instructions.

Because configs are generated from a single source, teams can version-control the .ai/ directory and review changes in one place during pull requests.

How to use

1. Install globally:

npm install -g lnai

1. Initialize in your project:

lnai init

1. Edit your configs in the .ai/ directory.
2. Sync to all tools:

lnai sync

Example

# After editing .ai/rules/typescript.md with your coding standards
$ lnai sync

Synced to:
  - .claude/CLAUDE.md
  - .cursor/rules/typescript.mdc
  - .github/copilot-instructions.md
  - GEMINI.md
  - AGENTS.md
  - .windsurfrules

All seven tools now follow the same TypeScript coding standards from a single source file.

Related on TokRepo

• AI tools for coding -- Other tools that enhance AI-assisted development workflows
• Prompt library -- Reusable prompt templates that pair well with lnai configs

Common pitfalls

• Running lnai sync before committing changes -- the generated files can clutter your git diff. Add a pre-commit hook or run sync as part of your CI pipeline.
• Assuming all tools interpret rules identically -- each AI tool has different context window sizes and config parsing behavior. Test critical rules in each tool after syncing.
• Forgetting to add the .ai/ directory to version control -- without it, other team members will not get the configs.