For your agent
Every TurbineKit project ships the files a coding agent reads before it changes code. They are short, plain, and kept in step with the code.
- AGENTS.mdThe map of the project and its house rulesRead first
- SETUP.mdSetup, service by service, with boxes your agent ticksAbout 10 minutes
- LAUNCH.mdThe checklist before real people arriveBefore launch
- SkillsA recipe for each common change8 skills
Which agents
Any agent that reads AGENTS.md: Claude Code, Codex, Cursor and others.
CLAUDE.md is one line, @AGENTS.md, so Claude Code reads the same file. The
skills are in .agents/skills/ and linked from .claude/skills/.
Why files, and not a prompt
A prompt is gone after one chat. A file in the repository is read by every agent, in every session, and it changes in the same pull request as the code it describes. When the code moves, the rules move with it.
Run one command. The CLI asks the rest, and your agent takes it from there.
pnpm create turbinekit my-appSee the prompt
Paste it into an agent that can run commands, such as Claude Code, Codex or Cursor.
Create a new TurbineKit project with me.
TurbineKit (https://turbinekit.dev) is an open-source Turborepo and Next.js starter. Its CLI, create-turbinekit, needs Node.js 24 and pnpm 10 (run `corepack enable` once).
1. Run `pnpm dlx create-turbinekit --help` to see its options.
2. Ask me its questions one at a time, with their defaults: the folder, the product name, one sentence about the product, the company or legal name, the contact email, the languages and the modules. Skip what I have already told you.
3. The CLI only asks questions in an interactive terminal, so run it with my answers as options and `--yes`. Show me the command before you run it.
4. In the new folder, read AGENTS.md. Then do "1. Minimal setup" in SETUP.md, and tick each box you finish.
5. Tell me the URL of the running app, and which services SETUP.md lists next.No sign-up, no API keys. Needs Node.js 24 and pnpm 10.