What is an AI configuration file?

An AI configuration file (such as CLAUDE.md, .cursorrules, .windsurfrules, copilot-instructions.md or AGENTS.md) is a plain-text file you place at the root of your project. The AI coding assistant reads it before every interaction and uses it as persistent context: your stack, conventions, banned patterns, and project-specific rules. It's the official mechanism vendors recommend for personalizing AI behavior.

Which AI coding assistants are supported?

Five tools, each with its native format: Claude Code (CLAUDE.md + .claude/rules), Cursor (.cursorrules + .cursor/rules), Windsurf (.windsurf/rules), GitHub Copilot (copilot-instructions.md + .github/instructions), and AGENTS.md (universal standard read by Codex, Jules, Gemini, Factory, Zed and 15+ other agents). One questionnaire produces a tailored file for whichever tool you use.

Why should I configure my AI assistant?

Without a config file, the AI guesses from filenames and the file you have open. With one, it follows your conventions silently across the whole session. You stop repeating context in every prompt, and the AI stops suggesting React patterns in a Vue project or the wrong test framework. The output quality difference is not subtle.

Do I need to write the file from scratch?

No, that's exactly what setupkit.app removes. You answer a short questionnaire (your stack, level, conventions, project type) and we produce a file ready to drop into your repo. You can edit it after, but you start from something tailored to you, not a blank page.

Yes. Single-file generations are free and unlimited, for all 5 supported tools, with the full questionnaire. The Pro plan at 15 EUR / month billed yearly (180 EUR), or 20 EUR billed monthly, adds the full multi-file setup, a GitHub scanner that reads your real repo, and your config delivered as a pull request. Teams starts at 75 EUR per month for up to 5 devs, and done-for-you custom setups start at 600 EUR, see /pricing.

What's the difference between CLAUDE.md and .cursorrules?

Same idea, different vendors. CLAUDE.md is read by Claude Code; .cursorrules (or files under .cursor/rules) by Cursor; .windsurf/rules by Windsurf; copilot-instructions.md by GitHub Copilot; AGENTS.md is the universal standard read by Codex, Jules, Gemini, Factory, Zed and 15+ other agents. The format and tone vary slightly per tool: what works in one isn't always optimal in another. setupkit.app outputs the right format for each.

Teams pricing

One shared base, one personal layer per dev

Your tech lead defines the team conventions once. Every developer gets a config that fits their role, and when the base changes, every config follows.

0 / 10 founding team slots claimed, 20% off forever on yearly

Teams

One subscription for your whole team, up to 5 devs included. Pay for 10 months, get 12.

750 EUR/year

How many developers?

developers

Then 150 EUR per extra dev per year.

What you get

A shared base of conventions defined by your tech lead
A personal config layer per developer: tech lead, senior, junior, intern
The cascade: change the base, every config regenerates with each dev's personal layer preserved
Full architecture (rules, memory, skills) built for Claude Code, single files for the other 4 tools
The shared base delivered to your repository as a single pull request
Personal layers stay local and user-level, never committed

Create your team account

More than 20 devs? Talk to us.

Why Teams

Why a living team config beats a copy-pasted file

A file gets copied once and rots. A team config lives with your conventions. Here is what changes with Teams.

Aligned by default, not by luck

Every dev works from the same shared base. No drift, no divergent local copies, no AI suggesting code that breaks your team conventions.

A config per role, not one-size-fits-all

A junior needs guardrails and explanations, a tech lead needs review and architecture support. Each dev gets a personal layer on top of the base, matched to their role.

The cascade keeps everyone in sync

Your conventions change, you update the base once. Every developer's config regenerates automatically with their personal layer preserved. No chasing people to update their files.

Faster onboarding for new hires

A new engineer joins, gets added to the team, and their AI is configured like the rest of the team from day one, with a layer adapted to their level.

FAQ

Frequently asked questions

How is Teams different from the Pro plan?

Pro is built for one developer. Teams adds a shared base of conventions maintained by your tech lead, a personal layer per developer based on their role, and the cascade that regenerates every config when the base changes.

How does the config reach my developers?

Two levels, matching how AI tools natively work. The shared base is committed to your repository through a single pull request. Each developer's personal layer is a local, user-level file downloaded from their dashboard, never committed.

What happens when our conventions change?

You update the shared base once. Every developer's config regenerates with their personalization preserved. That cascade is the whole point: a config that stays alive instead of rotting after the first copy-paste.

Want your team on one living config?

Create your team account, define your shared base, and roll it out to your devs. From 75 EUR per month for up to 5 devs.