setup-project
Setup Project
Skill for auto-configuring new projects with standardized scripts and detecting available CLI tools.
Workflow
Phase 1: Detect Project Type
Check for project indicators:
ls package.json pyproject.toml requirements.txt go.mod Cargo.toml 2>/dev/null
Use the detection table from references/cli-detection.md (section "Deteccion de Tipo de Proyecto") to determine project type and base check script.
If no project type detected:
"No supported project files found. This skill supports Node.js, Python, Go, and Rust projects."
Phase 2: Add Check Script
Node.js projects
Read package.json and analyze existing scripts. Build the check script based on available scripts:
| Script Exists | Include in check |
|---|---|
lint |
npm run lint |
typecheck |
npm run typecheck |
test |
npm run test |
build |
npm run build |
Example: if all exist:
"check": "npm run lint && npm run typecheck && npm run test && npm run build"
Detect package manager using lockfile detection from references/cli-detection.md. Use the detected package manager in the check script (e.g., bun run instead of npm run).
Add the check script to package.json using Edit tool.
Python projects
For pyproject.toml projects:
"check": "ruff check . && pytest"
For requirements.txt only:
"check": "pytest"
Add as a script in pyproject.toml under [project.scripts] or suggest creating a Makefile with a check target.
Go / Rust projects
Suggest creating a Makefile with a check target using the commands from references/cli-detection.md.
Phase 3: Detect Installed CLIs
Detect CLIs using the table and commands from references/cli-detection.md. Display results as a status table.
Only show installation commands for missing CLIs if the user asks.
Phase 4: Detect CI/CD Workflows
ls .github/workflows/*.yml 2>/dev/null || echo "NO_WORKFLOWS"
If no workflows found:
"No GitHub Actions workflows configured. Want me to set up basic CI for this project?"
If user agrees, suggest running the /github-actions skill or offer to create a basic workflow.
If workflows exist: report them.
Phase 5: Update/Create Project CLAUDE.md
Check if CLAUDE.md exists. If it does, add/update an "Available CLIs" section with detected tools. If not, create a minimal one with:
- Repository overview (ask user or infer from project config)
- Available CLIs section (only installed CLIs)
- Quick start commands
Phase 6: Output Summary
Setup Complete
==============
Project Type: [Node.js / Python / Go / Rust]
Package Manager: [npm / bun / pnpm]
Check Script: Added to [package.json / pyproject.toml / Makefile]
- Includes: [lint, typecheck, test, build]
Available CLIs: X/Y
- Installed: [list]
- Missing: [list]
GitHub Actions: [status]
CLAUDE.md: [Updated / Created]
More from testacode/llm-toolkit
claude-md-writer
Escribe y mejora archivos CLAUDE.md siguiendo best practices de Anthropic. Este skill se activa cuando el usuario dice "crear CLAUDE.md", "mejorar CLAUDE.md", "actualizar CLAUDE.md", "revisar CLAUDE.md", "escribir instrucciones del proyecto", "create CLAUDE.md", "improve CLAUDE.md", "review CLAUDE.md", "write project instructions", "optimize docs for Claude", "auditar CLAUDE.md", "audit CLAUDE.md", "limpiar CLAUDE.md", "dead weight", o configura un nuevo repositorio.
53doc-writer
Este skill se usa para crear documentos tecnicos organizados en /docs (specs, planes de implementacion, ADRs, documentacion de referencia). Se activa cuando el usuario dice "crear documento", "escribir spec", "documentar esto", "creame una spec", "escribime documentacion", "hacer documentacion", "write a spec", "create documentation", "write an ADR", o quiere agregar documentacion tecnica al proyecto.
44llms-txt-generator
This skill generates llms.txt documentation optimized for AI/LLM consumption. It should be used when the user says "crear llms.txt", "generate llms.txt", "documentar para AI", "document for AI", "crear documentacion para LLMs", "generate docs for LLMs", "make repo readable for Claude", or wants to create structured machine-readable documentation following the llms.txt standard.
40doc-organizer
Este skill se usa cuando el usuario pide "organizar docs", "ordenar documentacion", "mover documentos a carpetas", "categorizar archivos md", "reorganizar documentacion", o cuando hay archivos .md sueltos en docs/ que necesitan ser movidos a subcarpetas tematicas. Organiza y categoriza documentos tecnicos en la estructura correcta del proyecto.
28feature-planner
Planifica features con entrevista estructurada y crea tareas. Este skill se activa cuando el usuario dice "quiero agregar", "planificar feature", "nueva funcionalidad", "implementar esto", "crear plan", "planificar antes de codear", "disenar feature", "como deberia implementar esto", "pensar la arquitectura", o quiere alinear antes de escribir codigo.
27nextjs-project-starter
Creates Next.js projects with a configurable stack (Mantine, Supabase, Zustand, Zod). This skill should be used when the user says "create a Next.js project", "new web project", "bootstrap fullstack app", "start new app", "crear proyecto Next.js", "nuevo proyecto web", "empezar app fullstack", or wants to scaffold a new personal project from scratch.
25