project-setup

Initialize or update .claude project structure with automatic project type detection.

Updated May 11, 2026
One-click install
npx skills add https://github.com/TomasGC/Meerkat --skill project-setup-tomasgc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-setup
Source: https://github.com/TomasGC/Meerkat/tree/main/skills/project-setup
Command: npx skills add https://github.com/TomasGC/Meerkat --skill project-setup-tomasgc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up and maintaining a consistent Claude Code configuration (.claude/ directory) across projects is manual and error-prone, especially when detecting project types, syncing templates, and preserving existing customizations. ## Core Features & Use Cases - Dual-mode operation: CREATE mode initializes a complete .claude/ structure from templates; UPDATE mode compares existing files against the latest template while preserving user customizations. - Automatic project type detection: Identifies Go, Node.js, Vue.js, .NET, ASP.NET MVC, and other stacks via indicator files like go.mod, package.json, and *.csproj. - Template injection and maintenance tooling: Generates CLAUDE.md, contexts/, settings files, plus PowerShell sync/validation scripts, examples, and documentation. - Use Case: You clone a Go microservice repository and want Claude Code configured. Run the skill to detect the Go project, generate CLAUDE.md with build/test commands, create kanban and architecture contexts, and produce maintenance scripts. ## Quick Start Ask Claude to initialize the project setup for the current directory and confirm the detected project type.

Frequently Asked Questions about project-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I initialize a .claude directory for my project?

Invoke the project-setup skill in a directory without an existing .claude/ folder. It auto-detects your project type from files like go.mod or package.json, then copies and injects templates to create CLAUDE.md, contexts/, and settings files.

How does project type detection work in Claude Code setup?

Detection checks indicator files in priority order: go.mod for Go, package.json with cypress for Node.js, package.json with vite config for Vue.js, and *.csproj files for .NET or ASP.NET MVC. Ambiguous detections are confirmed with the user before proceeding.

Will updating .claude overwrite my customizations?

No. UPDATE mode reads existing files first, extracts user-specific sections like project names and custom rules, and merges template updates with your content. Non-standard custom files are analyzed and only deleted after explicit user confirmation.

What project types does the setup skill support?

Supported types include Go, Node.js with Cypress, Vue.js 3 with Vite, .NET, ASP.NET MVC with Razor views, Python, and Rust. Unknown projects fall back to a minimal generic template without language-specific content.

What happens to scripts in the .claude root during updates?

UPDATE mode moves *.sh, *.ps1, *.psm1, and *.bash files from the .claude/ root into a .claude/scripts/ directory. All references in CLAUDE.md, agents, and skills are updated to the new paths automatically.