Now I have a solid reference. Let me create all four files.Everything works. Let me copy all files to the output directory.Your `api-route-scaffolder` skill is ready. Here's a summary of what was built and the key decisions made: **SKILL.md** — Uses `keyword` invocation triggered by phrases like "new endpoint", "add route", "scaffold controller". The nine-step How It Works section wires Claude's behavior precisely: run the conflict check first, read an existing pattern before writing, compile-check at the end. Five hard guardrails prevent the two most common mistakes (silent overwrites, inventing response helper patterns). **PATTERNS.md** — Six opinionated, before/after patterns covering: file naming, thin controllers, service interfaces, router-level auth middleware, test skeleton structure, and alphabetical router index registration. Every pattern includes the "why" framed for a B2B multi-tenant context. **EXAMPLES.md** — Three fully worked examples covering the three scenarios your team actually hits: basic CRUD, a webhook endpoint with no auth middleware, and a nested resource (`/dashboards/:dashboardId/widgets`). Each includes the exact TypeScript output as indented plain text and a "Why this works" note that explains non-obvious decisions like `mergeParams: true`. **run.py** — A 110-line CLI tool that does two jobs: `--check` emits a JSON manifest of the five target file paths and any conflicts (exit 2 on conflict), `--generate` writes the route file to disk. Claude runs the check first to get exact paths, then uses Write/Edit tools for the other four files. Tested locally — `report`, `dashboard-widget`, and nested base paths all resolve correctly. **To install:** drop the `api-route-scaffolder/` directory into your Claude Code skills folder and ensure it's referenced in your `CLAUDE.md` or skills config. Claude will auto-trigger on any message containing the keyword phrases.