api-forge
PadaliyaSavan88/api-forge
An Backend claude skill to scaffold nodeJS project of maintain for build production grade backend.
Instalação
npx convez-ai PadaliyaSavan88/api-forge1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
README
A tradução para o português deste README ainda está na fila.
api-forge
A collection of Claude Code slash commands for building production-grade backend APIs. Based on battle-tested boilerplate patterns.
Author: Savan Padaliya
Available Skills
| Skill | Command | Description |
|---|---|---|
| backend | /backend | Express + TypeScript backend — 3-layer architecture, scaffold or extend |
More skills coming: /frontend, /devops, /database
Install a skill
All platforms — Windows, Mac, Linux (requires Node.js):
npx skills add PadaliyaSavan88/api-forge -a claude-code
Install a specific skill:
npx skills add PadaliyaSavan88/api-forge --skill backend -a claude-code
The
-a claude-codeflag targets Claude Code directly and supports both project-level and global installation.
Mac / Linux alternative (curl):
curl -fsSL https://raw.githubusercontent.com/PadaliyaSavan88/api-forge/main/install.sh | bash -s backend
Skills are installed to ~/.claude/commands/. Restart Claude Code or open a new session after installing.
How it works
Each skill is a markdown file that Claude Code loads as a slash command. When you type /backend in Claude Code, the skill file is injected into context and Claude follows its instructions — analyzing your project, asking the right questions, and scaffolding production-ready code.
/backend — Express + Node.js
3 modes:
- New project — asks 13 init questions (DB, roles, TypeScript strictness, auth, rate limiting, HTTPS strategy, etc.), then generates the full project structure
- Align existing — reads your current
src/structure, identifies gaps vs the pattern, proposes improvements - Extend — adds a new resource (Controller + Service + Zod schema) to an existing project
Architecture:
Controller (HTTP) → Service (business logic) → DB Model (query only)
Always enforced:
{ success, data, message }on every response- Named error classes (ValidationError, NotFoundError, UnauthorizedError, ForbiddenError)
- Zod validation in services
- Centralised config with startup validation
- Winston logging, no console.log
- Pagination on all list endpoints
- Graceful shutdown
- Helmet security headers
Optional (decided at init): ESLint, Prettier, Husky, Vitest/Jest, rate limiting, health check, Swagger, PM2, Docker, HTTPS strategy
Contributing
To add a skill:
- Create
skills/{skill-name}/SKILL.mdwithnameanddescriptionfrontmatter - Add a
skills/{skill-name}/README.md - Add the skill name to
AVAILABLE_SKILLSininstall.sh - Add a row to the skills table in this README