Skip to content
Agentmart
Submit a tool

init-project

Initialize a new project with Claude Code .claude/ directory, CLAUDE.md, framework-specific rules, and standard configuration (set up project, init…

Skill by roborracle

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/roborracle-init-project

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Initialize a new project with Claude Code .claude/ directory, CLAUDE.md, framework-specific rules, and standard configuration (set up project, init, bootstrap, new project).

Use cases: agent-building

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/init-project

What's inside

Skill name
init-project
Description
Initialize a new project with Claude Code .claude/ directory, CLAUDE.md, framework-specific rules, and standard configuration (set up project, init, bootstrap, new project).
License
MIT
Instructions
77 lines in SKILL.md · view on GitHub

Files (4)

  • SKILL.md
  • nextjs.md · packs/
  • python.md · packs/
  • wordpress.md · packs/

SKILL.md (first lines)

# Initialize Project Configuration

Set up this project's `.claude/` directory with standard configuration, framework-specific rules, and optional PRD scaffolding.

## 1. Check Current State
```bash
ls -la .claude/ 2>/dev/null || echo "No .claude directory found"
ls package.json composer.json requirements.txt pyproject.toml Cargo.toml 2>/dev/null || echo "No package manifest found"
```

## 2. Create Directory Structure
```bash
mkdir -p .claude/skills .claude/rules
```

## 3. Detect Stack and Install Framework Pack

Check which stack this project uses and copy the matching framework pack from `~/.claude/skills/init-project/packs/` into `.claude/rules/`.

### Detection logic:
- `package.json` with `next` dependency → **Next.js** → copy `packs/nextjs.md` to `.claude/rules/nextjs.md`
- `composer.json` or `wp-content/` exists → **WordPress** → copy `packs/wordpress.md` to `.claude/rules/wordpress.md`
- `requirements.txt` or `pyproject.toml` exists → **Python** → copy `packs/python.md` to `.claude/rules/python.md`
- None detected → ask the user which stack, or skip framework pack

```bash
# Example for Next.js detection:
if [ -f package.json ] && grep -q '"next"' package.json 2>/dev/null; then
  cp ~/.claude/skills/init-project/packs/nextjs.md .claude/rules/nextjs.md
  echo "Installed Next.js framework pack"
fi
```

Only install ONE framework pack per project.

## 4. Create Project CLAUDE.md
Create `.claude/CLAUDE.md` from the template in `~/.claude/rules/documentation-protocol.md` § "Project `CLAUDE.md` template": a thin reference layer holding only this project's deltas (paths, context, stack, overrides, pointers to deeper docs).

## 5. Add to .gitignore
Ensure `.claude/settings.local.json` is in `.gitignore`.

## 6. Project-Level Rules
Only add rules for things the global rules don't already cover. List `~/.claude/rules/` to see the current set.

## 7. Offer PRD Scaffolding
Ask the user if they want a PRD template created. If yes:
```bash
mkdir -p docs/strategy
cp ~/.claude/skills/product-strategist/prd-template.md docs/strategy/prd.md
echo "Created docs/strategy/prd.md — fill in project-specific details"
```

## 8. Check Existing Config
If `.claude/agents/` or `.claude/commands/` exist, list what's in them and leave them in place. Project subagents and commands are current Claude Code features, and removing either is a deletion the user confirms first.

## 9. Verify
```bash
echo "=== Project Config ==="
cat .claude/CLAUDE.md
echo ""
echo "=== Project Rules ==="
ls .claude/rules/ 2>/dev/null || echo "(using globals only)"
echo ""
echo "=== Global Config ==="
echo "Rules:"
ls ~/.claude/rules/
echo "Skills:"
ls ~/.claude/skills/
```

## Do NOT
- Copy global rules into the project (they apply automatically)
- Copy global skills into the project (they're available everywhere)
- Create duplicate skills or duplicate rules
- Install multiple framework packs (one per project)

From roborracle/agent-workflow-kit, MIT.

More from roborracle/agent-workflow-kit

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Sep 24, 2026 (1 month ago)
Last release
Aug 11, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from roborracle

Cite this page

init-project skill. Agent Mart. https://agentmart.dev/skills/roborracle-init-project (last updated 2026-10-24)