Skip to content
Skills Library
AI & agents · Tool integration

project-setup

/project-setup

Bootstrap a user's project directory for Rook by creating or merging a CLAUDE.md with Rook agent instructions, then initializing Claude Code project config. Use when user mentions: "project setup", "setup project", "init project", "bootstrap project", "add Rook to my project", "setup CLAUDE.md", "configure project for Rook", or when working in a directory that has no Rook context in its CLAUDE.md.

Repository
rook ↗
Licence
MIT
Last repository change
18.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
9
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 18.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • SKILL.md zawiera komentarze HTML (9). Nie widać ich w podglądzie Markdown, a model je czyta.

What it does and when to use it

Bootstrap a user's project directory for Rook by creating or merging a CLAUDE.md with Rook agent instructions, then initializing Claude Code project config. Use when user mentions: "project setup", "setup project", "init project", "bootstrap project", "add Rook to my project", "setup CLAUDE.md", "configure project for Rook", or when working in a directory that has no Rook context in its CLAUDE.md.

Triggers from the description

project setupsetup projectinit projectbootstrap projectadd Rook to my projectsetup CLAUDE.mdconfigure project for Rook
Original author description

Bootstrap a user's project directory for Rook by creating or merging a CLAUDE.md with Rook agent instructions, then initializing Claude Code project config. Use when user mentions: "project setup", "setup project", "init project", "bootstrap project", "add Rook to my project", "setup CLAUDE.md", "configure project for Rook", or when working in a directory that has no Rook context in its CLAUDE.md.

How it works

  1. Prerequisites
  2. Workflow
  3. Updating Rook Instructions
  4. Key Principles
Original SKILL.md headings · 117 lines, 584 words
SKILL.md preview
---
name: project-setup
description: |
  Bootstrap a user's project directory for Rook by creating or merging a
  CLAUDE.md with Rook agent instructions, then initializing Claude Code
  project config. Use when user mentions: "project setup", "setup project",
  "init project", "bootstrap project", "add Rook to my project",
  "setup CLAUDE.md", "configure project for Rook", or when working in a
  directory that has no Rook context in its CLAUDE.md.
---

# Project Setup

Bootstrap the current project directory so Claude Code has Rook context
when working here. Two actions:

1. **CLAUDE.md** — Create or merge Rook agent instructions
2. **/init** — Initialize Claude Code project configuration

## Prerequisites

- Rook must be installed (MCP server registered in `~/.claude.json`)
- The current working directory should be the user's project folder,
  NOT the Rook install directory (`%LOCALAPPDATA%\Rook`)

## Workflow

### Step 0: Detect State

Check the current directory:

1. What is the current working directory? If it's the Rook install root
   (`%LOCALAPPDATA%\Rook` or the Rook source repo), warn the user:
   "You're already in the Rook directory — this skill is for setting up
   your own project folders. cd to your project first."

2. Does `./CLAUDE.md` exist?
   - **No** → Step 1A (create from template)
   - **Yes** → check if it already contains Rook instructions (search
     for the marker `<!-- rook-begin -->`)
     - **Marker found** → tell user "Rook instructions already present
       in CLAUDE.md" and skip to Step 2
     - **No marker** → Step 1B (merge into existing)

### Step 1A: Create CLAUDE.md (no existing file)

Read the Rook agent instruction template. The canonical source is the
installed copy at `%LOCALAPPDATA%\Rook\CLAUDE.md`. If that doesn't
exist, use the template from the Rook repo at `installer/CLAUDE.md`.

Write a new `./CLAUDE.md` with this structure:

```markdown
<!-- rook-begin -->
{contents of the Rook CLAUDE.md template}
<!-- rook-end -->
```

Tell the user: "Created CLAUDE.md with Rook agent instructions. You can
add your own project-specific notes above or below the Rook section."

### Step 1B: Merge into existing CLAUDE.md

The user already has a CLAUDE.md with their own content. Append the Rook
section at the end:

```markdown

{existing CLAUDE.md content unchanged}

<!-- rook-begin -->
{contents of the Rook CLAUDE.md template}
<!-- rook-end -->
```

**Rules:**
- NEVER modify the user's existing content
- Always append at the end, never prepend
- Use the `<!-- rook-begin -->` / `<!-- rook-end -->` markers so future
  updates can find and replace just the Rook section

Tell the user: "Appended Rook agent instructions to your existing
CLAUDE.md. Your project-specific content is untouched."

### Step 2: Initialize Claude Code config

Check if `.claude/` directory exists in the project:

- **If `.claude/` does not exist:** Tell the user to run `/init` in
  Claude Code to create the project configuration. This sets up the
  `.claude/` directory with settings, allowed tools, etc.

- **If `.claude/` already exists:** Skip this step — project config
  is already initialized.

### Step 3: Confirm

Print a summary:

```
Project setup complete for {directory name}:
  [OK] CLAUDE.md — Rook agent instructions {created / merged}
  [OK] .claude/ — Project config {exists / run /init to create}

Next steps:
  1. Open a Rhino file from this project
  2. In Claude Code, type: rhino_ping
  3. You're connected — Rook knows your project context
```

## Updating Rook Instructions

If the user runs `/project-setup` again in a directory that already has
the Rook markers, replace the content between `<!-- rook-begin -->` and
`<!-- rook-end -->` with the latest template. This lets users update
their Rook instructions after a Rook upgrade without losing their own
CLAUDE.md content.

## Key Principles

- **Never clobber user content.** The markers isolate the Rook section.
  Everything outside the markers belongs to the user.
- **Idempotent.** Running the skill twice should produce the same result
  as running it once (update in place via markers).
- **No Rhino dependency.** This skill runs without Rhino — it's pure
  file operations. Don't call `rhino_ping` or any MCP tools.

Versions

RepositoryScoreLicence
This page · bringfire/rook100MIT
vaayne/agent-kit100MIT
linxule/interpretive-orchestration100MIT
Pagepro/nexity100MIT
ahtserhsuddav/create-agent-ready-app100MIT
SckyzO/claude-project-setup100MIT
markshust/hcf100MIT
dwmkerr/claude-toolkit100MIT
shaunandrews/agent-skills100MIT

Identical content appears in 3 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 3abec0401649 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90Project Scaffolding
    This skill should be used when the user wants to set up Claude for a project, create a CLAUDE.md file, scaffold the .claude directory, initialize an AI workflow, configure a project for Claude, set up dev intelligence, initialize a new project, or do a new project setup.…
  • 100init-claude
    Generate a production-grade CLAUDE.md for any project. Detects project type (Go CLI, Node API, full-stack monorepo, IaC, Python, etc.) and generates a comprehensive CLAUDE.md with architecture map, agent routing, dev commands, QA checklist, code standards, and workflow…
  • 100agents-md-author
    Bootstrap or update project AI-agent instruction files (AGENTS.md for Codex, CLAUDE.md for Claude Code, or both) from the current project's structure. Triggers on: write AGENTS.md, write CLAUDE.md, generate AGENTS.md, agent instructions, project conventions for AI, bootstrap…
  • 90execute-grasshopper
    Use when the user asks to build or modify a Grasshopper definition through Rook.
  • 100setperms
    Set tool permissions for Claude Code. Configures allowed commands, rules, and preferences in .claude/ directory. Triggers on: setperms, init tools, configure permissions, setup project, set permissions, init claude.
  • 98context-audit
    [Adam''s Skills] Audits a repository''s Claude context-injection setup — CLAUDE.md, CONTEXT.md, docs/, .claude/agents/, and the per-project memory directory. Reports bloat, broken links, orphaned docs, security risks, missing rules in subagent prompts, settings that override…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.