What lands in .claude/ when I install?

46 subagents in .claude/agents/, 47 slash commands in .claude/commands/, 61 skills in .claude/skills/ /SKILL.md, and 12 rules in .claude/rules/ imported by CLAUDE.md. Hooks are wired in .claude/settings.json. A CLAUDE.md project-memory file is written at your repo root and auto-synced from a scan of your stack.

Is this the same kit as the Cursor one?

Yes. It is one kit emitted for two targets, not two products. The 61 skills, the agent playbooks, and the command pipelines are the same content. Only the file format and frontmatter differ, because Cursor and Claude Code read different things.

Do the two versions drift apart over time?

They cannot. The .cursor tree is the single source of truth and the .claude tree is generated from it by scripts/build-claude-kit.js. A --check mode regenerates into a temp directory and fails the build if the committed output differs by even one byte.

What does Claude Code get that Cursor does not?

Per-subagent tool and model grants, so a reviewer role is read-only by construction rather than by instruction. Slash commands carry description, argument-hint and allowed-tools frontmatter. Rules are plain .md files imported into context by CLAUDE.md. Hooks live in .claude/settings.json.

Can I install Claude Code only?

Yes. Run npx agentickit-cursor init --target claude and nothing is written to .cursor/ and no CURSOR.md is created. Plain init installs both.

Will it overwrite a CLAUDE.md I already have?

No. If your CLAUDE.md contains real content it is left alone. The installer only writes the file when it is missing or still the unedited placeholder, and your own files under .claude/agents/ survive both init and update.

Does one licence cover both editors?

Yes. --kit engineering, marketing or both is the licence axis. --target cursor, claude or both is free and independent of it.

Claude Code Agents, Skills & Slash Commands for SaaS Founders

What lands in .claude/

46 subagents.claude/agents/<slug>.md, each with a tools and model grant scoped to what that role is allowed to do
47 slash commands.claude/commands/<slug>.md, with description, argument-hint and allowed-tools
61 skills.claude/skills/<slug>/SKILL.md, the playbooks agents must read before acting
12 rules.claude/rules/<name>.md, imported into every session by CLAUDE.md
Hooks.claude/settings.json, which keeps CLAUDE.md in sync with your stack on session start and after edits

Install

Claude Code

# Claude Code only

$npx agentickit-cursor init --target claude

# -> .claude/ + CLAUDE.md

Cursor

# Cursor only

$npx agentickit-cursor init --target cursor

# -> .cursor/ + CURSOR.md

Cursor + Claude Code

# one install, both editors

$npx agentickit-cursor init

# -> .cursor/ + .claude/

--kit engineering | marketing | both selects which assets you get and is tied to your licence. --target cursor | claude | both selects where they are written and is free. The two compose.

How the Claude Code kit is built

The .cursor/ tree is the single source of truth. The Claude Code edition is generated from it by scripts/build-claude-kit.js, which rewrites paths, converts .mdc rules to .md, and attaches the Claude-native frontmatter each asset type needs.

The generated tree is committed, so the npm package ships it, but --check regenerates into a temporary directory and deep-diffs against what is committed. If a single byte differs, the build fails. That is the whole reason the two editions stay honest: no one can hand-patch one editor and forget the other.

What Claude Code gets that Cursor does not

Cursor agent files carry a name and a description. Claude Code subagents also carry a tool grant and a model, which turns a written instruction into an enforced boundary. code-reviewer is not merely told not to edit your code. It is not given the tools to:

---
name: code-reviewer
description: Reviews pull requests for correctness, security, performance...
tools: Read, Glob, Grep, Skill, Bash, TodoWrite
model: opus
---

Slash commands gain frontmatter too, so the harness knows what they accept and may run:

---
description: "Run the full feature pipeline: plan, API, UI, tests, review, security, gate"
argument-hint: "[feature description]"
allowed-tools: Read, Grep, Glob, Edit, Write, Bash(npm test:*), Bash(pnpm test:*), ...
model: opus
---

Rules ship as plain .md and are pulled into context by CLAUDE.md via @.claude/rules/<name>.md imports, rather than Cursor's alwaysApply frontmatter. Hooks live in .claude/settings.json instead of .cursor/hooks.json.

What is identical

All 61 skills are the same files. The agent playbooks, the command pipelines, the stop conditions and the definitions of done are the same content. If you have used the Cursor kit, you already know this one. /ship and /launch behave the same way in both.

Tool grants in practice

Senior Code Reviewer (code-reviewer)Conducts strict PR code reviews for readability, performance, and best practices.
App Security Auditor (security-auditor)Scans for OWASP Top 10 vulnerabilities, XSS, CSRF, injection, and auth leaks.
Technical Lead & System Architect (tech-lead)Oversees architecture, enforces code conventions, and coordinates agent workflows.
API Integration Specialist (api-engineer)Builds bulletproof REST/GraphQL endpoints with Zod validation and types.
Exploratory QA Specialist (qa-explorer)Clicks the app like a new user and files what breaks.
React 19 & Next.js Specialist (react-specialist)Builds modern React 19 UI, Server Components, and sleek client interactions.