mags-setup

MAGS Setup

Analyze the current project and recommend an optimal setup for Claude Code workflows.

Steps

1. Analyze project

Gather project signals in parallel:

• Read .mags/config.yaml to check for a locale field. If present, use this locale value when calling mags_create_doc and mags_scaffold_module throughout this flow.
• Call mags_project_summary for overall context.
• Use Glob to detect project type:
  • package.json — Node/JS project
  • Cargo.toml — Rust project
  • go.mod — Go project
  • pyproject.toml or requirements.txt — Python project
  • pom.xml or build.gradle — Java project
  • *.sln or *.csproj — .NET project
• Use Glob to detect frameworks and tools:
  • next.config.* — Next.js
  • nest-cli.json or src/main.ts with NestJS imports — NestJS
  • prisma/schema.prisma — Prisma ORM
  • docker-compose.* — Docker
  • .github/workflows/ — GitHub Actions CI
  • tailwind.config.* — Tailwind CSS
• Read package.json or equivalent manifest for dependencies.

2. Recommend skills and agents

Based on the detected stack, recommend Claude Code slash commands and workflows. Present as a checklist:

== Recommended Setup for <project name> ==

Detected: <framework> + <language> + <key tools>

SKILLS (slash commands to install)
  [x] /commit        — You have this (from MAGS)
  [ ] /review-pr     — PR review automation
  [ ] /test          — Test generation for <framework>
  [ ] /deploy        — Deploy workflow for <detected CI>

HOOKS (automation triggers)
  [ ] pre-commit     — Lint + typecheck before commit
  [ ] post-save      — Auto-format on save
  [ ] pre-push       — Run tests before push

MCP SERVERS
  [ ] mags           — Already active
  [ ] <db tool>      — Database introspection for <detected DB>
  [ ] <api tool>     — API testing for <detected framework>

Mark items already present with [x]. Only recommend what makes sense for the detected stack.

3. Audit CLAUDE.md

Call mags_audit_claude_md to check the current CLAUDE.md (if it exists) against the project's actual state.