Skip to main content
skill CX Codex

first-commit — Claude Code skill: setup and use

first-commit — a skill for Claude Code that creates projects from kits and maintains them. It runs for new apps, library additions, or projects containing kits.lock.

MIT 1,100 installs ★ 2 updated 2026-11-15

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add Marlon-Chaviano/first-commit --skill first-commit -a claude-code
Open on GitHub

What first-commit does

first-commit builds a project from a kit containing a template, dependencies, agent skills, MCP servers, and AGENTS.md rules. If its MCP server is available, the skill can use recommend_kit and get_kit; otherwise, it can inspect kits with npx create-first-commit list and npx create-first-commit info <kit>.

Before creating a project, it presents a --dry-run plan and asks for approval. The actual command runs other commands and downloads packages. For projects with kits.lock, update refreshes kit contents and add brings in a library; doctor checks whether the project follows its rules. User-edited files are left untouched by update.

After creation, the skill reads AGENTS.md and handles available first steps. Other setup tasks may need API keys or accounts. Community kits require confirmation; using --yes also requires --allow-commands when the user explicitly trusts that kit.

What it helps with

  • create an app from a kit with its dependencies and rules
  • add a library such as Sentry or Stripe to an existing project
  • update a kit project without overwriting edited files
  • check whether a project follows its kit rules

Example prompts for the agent

  • Create an Expo app from a suitable kit and show me the plan first.
  • Add Stripe to this project.
  • Update this project with kits.lock and check its rules.

How to install first-commit

1Skills CLI (Vercel)

npx skills add Marlon-Chaviano/first-commit --skill first-commit -a claude-code

2Manually: put the files in place

~/.claude/skills/first-commit/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/first-commit/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about first-commit

How do I install first-commit in Claude Code?

Run npx skills add Marlon-Chaviano/first-commit --skill first-commit -a claude-code. The skill file is placed at ~/.claude/skills/first-commit/SKILL.md.

What does first-commit do?

It creates projects from kits with templates, dependencies, and AGENTS.md rules. It can also add libraries and update existing projects that contain kits.lock.

What does first-commit need to work?

Project creation and maintenance use npx create-first-commit; when its MCP server is available, the skill can use it to find a kit. Some project setup steps may require API keys or accounts.

Source text

SKILL.md · MIT
---
name: first-commit
description: Start new projects and keep them up to date with first-commit workspace kits (project template + dependencies + agent skills + MCP servers + AGENTS.md rules, installed by `npx create-first-commit`). Use when the user wants to create a new app, landing, SaaS, API, mobile app or browser extension, or to add a library such as Sentry, PostHog, Stripe or Better Auth to an existing project, or when the project has a kits.lock file.
license: MIT
---

# first-commit

`create-first-commit` creates a project from a *kit*: a base project plus the dependencies, agent skills, MCP servers and `AGENTS.md` rules for the stack the user picks. Catalog and configurator: https://first-commit.dev.

## When to use it

- **New project** in an empty folder ("make me a recipes app with Expo", "a landing with animations"): use a kit instead of scaffolding by hand.
- **Existing project with `kits.lock`**: it came from a kit. Use `update` to get the kit's improvements and `add` to add libraries, so the rules in `AGENTS.md` stay in sync.
- **Adding a catalog library** (Sentry, PostHog, Stripe, Resend, Better Auth, Kokonut UI, Motion…) to any project: `add` writes its config and its rule in `AGENTS.md`.

## Create a project

1. Pick the kit. If the first-commit MCP server is available, call `recommend_kit` with the user's description, then `get_kit` for the options. Otherwise:
   - `npx create-first-commit list` — official kits.
   - `npx create-first-commit info <kit>` — options and their values.
2. Choose only the options the user asked for; keep the defaults for everything else. Options are flags: `--<option> <value>` (comma-separated for multi options).
3. **Show the plan and ask before running anything**: `npx create-first-commit <kit> <folder> [options] --dry-run` (or the `plan_init` tool). Installing runs commands and downloads packages.
4. After the user agrees: the same command without `--dry-run` and with `--yes` (or `init_kit` with `approved: true`). It takes a few minutes.
5. Read the new project's `AGENTS.md` and follow its "first steps": do the setup tasks you can, and tell the user which ones need them (API keys, accounts). Copy `.env.example` to `.env` but never invent secret values.

Community kits (`user/kit`) that aren't verified ask for confirmation; with `--yes` they also need `--allow-commands`. Only add it if the user explicitly trusts that kit.

## Maintain a project

- `npx create-first-commit update --dry-run`, then `npx create-first-commit update --yes`: new dependencies, skills, MCP servers and rules from the kit's latest version. Files the user changed are never overwritten; it lists them.
- `npx create-first-commit add <library|owner/repo@skill> --yes`: adds a catalog library with the right variant for the framework (Sentry for Next.js, Expo or Node).
- `npx create-first-commit doctor`: checks that the project still follows its rules (one component library, env vars, skills installed). Exit code 1 means errors; fix them or tell the user.

## Rules

- The rules in `AGENTS.md` between `<!-- kits:start -->` and `<!-- kits:end -->` come from the kit: follow them (for example, "only use the chosen component library"). Don't edit that block by hand; `update` rewrites it.
- Don't install a second library for something the kit already chose (another component system, another auth). Use `add --force` only if the user explicitly wants to switch.

## Composable monorepos

Use the `monorepo` kit to choose web, API, documentation and mobile separately.
`--web nextjs --api django --docs starlight` selects frameworks; library flags
include their service and framework, for example `--web.nextjs.components mantine`
and `--api.fastapi.database sqlmodel`. Use `info monorepo` to inspect exact choices.
Choose `--orchestrator simple|turbo|nx` and `--deployment independent|compose|none`.
A service destination is scoped too: `--web.nextjs.deploy vercel`.

Run `node scripts/workspace.mjs dev|build|verify [service]` from the generated root.
After starting web and API, `node scripts/check-connection.mjs` checks API health and
CORS. Production URLs and secrets belong in the hosting provider, not in the kit.

`kits.lock` v2 records each service separately. Use `add <library> --service web`
to target a service; `update` preserves the topology and updates existing services.
Old v1 projects are not automatically restructured into workspaces.

© Marlon-Chaviano · MIT · Marlon-Chaviano/first-commit

Similar skills

All skills for Agent setup: memory, context, orchestration →

More in the catalog

Project sponsors

Companies that keep this analytics open