service-mapperlisted

# Service Mapper Analyze a codebase and produce a structured, AI-agent-friendly service map. The output documents every microservice, how they communicate, what databases and tables they own, and what external systems they integrate with. ## When to Use - Onboarding to an unfamiliar codebase - Generating or updating a CLAUDE.md or SERVICE-MAP.md - Before planning a new feature (understand what exists) - Auditing service boundaries and ownership - Detecting architectural violations (shared DBs, direct HTTP between services, etc.) - After significant refactoring to verify the architecture still makes sense ## Workflow Execute these steps in order. Each step builds on the previous. ### Step 1: Identify Service Boundaries Scan the repository structure to find all deployable units (services, workers, lambdas, cron jobs). **What to look for:** | Signal | Examples | |--------|----------| | Entrypoints | `main.go`, `main.ts`, `index.ts`, `app.py`, `Program.cs`, `main.rs` | | Build configs | `Dockerfile`, `docker-compose.yaml`, `serverless.yml`, `app.yaml` | | Package manifests | `package.json`, `go.mod`, `Cargo.toml`, `pom.xml`, `*.csproj` | | Deployment specs | K8s manifests, Terraform, Helm charts, DO app specs | | Monorepo markers | `packages/`, `services/`, `apps/`, `cmd/`, `internal/` | **For each service, record:** - Name - Language / framework - Entrypoint file - Port (if HTTP) - Type: `webservice` | `worker` | `cron` | `lambda` | `gateway` ### Step 2: Map Inter-Ser