Stats

Actions

Tags

Help us improve

Share bugs, ideas, or general feedback.

init-claude-setup | Claude Setup

Skill

init-claude-setup

From Claude Setup

Initializes project-level Claude setup by adding .gitignore entries and creating settings.local.json. Does not copy agent/skill files — for projects with globally installed agents.

developer-tools

$

npx claudepluginhub nickmaglowsch/claude-setup --plugin claude-setup

Popularity

Parent stars

28

Parent forks

5

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/claude-setup:init-claude-setup

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

You are initializing project-level Claude configuration for this repository. Follow the steps below strictly in order.

SKILL.md

73 lines · ~621 tokens

Similar Skills

init-project

32

Automatically configure Claude Code best practices for new projects: directory skeleton, AGENTS.md, hooks, and interactive placeholders fill. Invoke via `/init-project`.

8 files

setupdotclaude

517

Bootstraps .claude/ dotclaude config from template if missing, then customizes all files to match project's tech stack, conventions, and patterns. Interactive via user confirmations.

project-init

339

Initializes Claude Code project configuration: reads global protocol, analyzes project, generates CLAUDE.md, AGENTS.md, and docs/. Installs skills, sets up .claude/ and .codex/ directories.

14 files

Stats

LanguageShell

Parent stars28

Parent forks5

MaintenanceGood

Last CommitJun 6, 2026

Actions

View Source View Plugin View on GitHub View README

Tags

project-initialization

Help us improve

Share bugs, ideas, or general feedback.

Init Claude Setup

You are initializing project-level Claude configuration for this repository. Follow the steps below strictly in order.

Step 1 — Detect if already fully set up

Check whether .claude/agents/ or .claude/settings.local.json exists in the current working directory.

If .claude/agents/ exists: inform the user that this project already has a full local Claude install and no initialization is needed. Stop here.
If .claude/settings.local.json exists: inform the user that this project already has project-level Claude setup and no initialization is needed. Stop here.

Step 2 — Add .gitignore entries

Read .gitignore in the project root. If it does not exist, treat it as empty.
Ensure the following entries are present (add only the ones that are missing). Group them under a # .claude section comment if you are adding any:

# .claude
.devcontainer/.env
.claude/settings.local.json
.claude/auth.local.md
.claude-worktrees/
.DS_Store
tasks/**
qa-output/**
debug-output/
.playwright-cli/

Do not duplicate any entry that already exists in the file (even if it appears outside a # .claude section).
If entries were already present, note that and skip.

Step 3 — Create .claude/settings.local.json

Check if .claude/settings.local.json exists.
If it does not exist, create it with this content:

{
  "permissions": {
    "allow": [],
    "deny": []
  }
}

If it already exists, skip this step and note it.

Step 4 — Summary

Print a clear summary of what was done:

## Claude project setup complete

- .gitignore: [added N entries / already up to date]
- .claude/settings.local.json: [created / already existed]

### Next steps
- Run `claude login` if you haven't already
- Edit `.claude/settings.local.json` to configure per-project tool permissions
- Agents and skills are available through the installed `claude-setup` plugin
- The /claude-setup:qa skill uses `playwright-cli` for browser automation — run `playwright-cli install` to set it up

Rules

Never overwrite files that already exist (settings.local.json) — only create them if missing
Never remove existing .gitignore entries — only add missing ones