Help us improve
Share bugs, ideas, or general feedback.
From kjgarza-base
Generate the entire API package or add a new feature route. Use without arguments to scaffold the full API, or pass a feature name to add a single route.
npx claudepluginhub kjgarza/marketplace-claude --plugin kjgarza-baseHow this command is triggered — by the user, by Claude, or both
Slash command
/kjgarza-base:generate-apiFiles this command reads when invoked
The summary Claude sees in its command listing — used to decide when to auto-load this command
Generate API code in packages/api/. If "$ARGUMENTS" is empty or "all", scaffold the entire API package. If "$ARGUMENTS" names a specific feature (e.g. "themes", "content", "usage"), add that feature as a new route module to the existing API. ## Before writing any code 1. Read CLAUDE.md at the repo root and any CLAUDE.md inside packages/api/. 2. Read README.md at the repo root. 3. Read docs/DESIGN.md — especially the Architecture Decisions, dependency direction, and data modeling sections. 4. Read packages/core/src/index.ts to see what core exports are available. 5. Read packages/core/src/...
/generate-rest-apiGenerates production-ready RESTful APIs from schemas using OpenAPI-first design, producing spec, controllers, routes, models, middleware, services, tests, and docs for Express, FastAPI, etc.
/express-api-scaffoldGenerates production-ready Express.js REST API boilerplate with TypeScript, JWT auth, Prisma/TypeORM database, Zod validation, Jest tests, and Docker. Accepts project name and --database, --auth flags.
/generate-api-docsGenerates OpenAPI 3.0/Swagger API documentation from codebase analysis, creating interactive Swagger UI, ReDoc, TypeScript clients, and Postman collections.
/kasi-backendRuns multi-mode backend missions (fix/audit/scaffold/design/perf/security) on API/controller/service/route/DB code, auto-detecting Laravel or Node stacks and producing prioritized reports/fixes.
/full-stack-featureOrchestrates interactive, phased full-stack feature development across backend, frontend, database, and infrastructure layers, producing files in .full-stack-feature/ with user checkpoints.
Share bugs, ideas, or general feedback.
Generate API code in packages/api/. If "$ARGUMENTS" is empty or "all", scaffold the entire API package. If "$ARGUMENTS" names a specific feature (e.g. "themes", "content", "usage"), add that feature as a new route module to the existing API.
headline, text, datePublished, isPartOf, commentCount, upvoteCount, etc. Do not rename fields at the API layer.{ error: string, details?: unknown } shape with appropriate HTTP status codes.Produce the complete packages/api/ package:
dev, start, and test scripts to package.json.Produce only the new feature module:
Core logic, database migrations, frontend code, MCP tools, or anything outside packages/api/.