Help us improve
Share bugs, ideas, or general feedback.
From code-sensei
Teaches backend concepts: servers (Express.js), routes/endpoints with HTTP methods, REST APIs, request/response cycles, middleware, .env security, and CORS. Activates for server-side code, API routes, or Express/Fastify/Next.js handlers.
npx claudepluginhub dojocodinglabs/code-sensei --plugin code-senseiHow this skill is triggered — by the user, by Claude, or both
Slash command
/code-sensei:backendThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- **Analogy:** If your website is a restaurant, the frontend is the dining room (what customers see) and the backend is the kitchen (where the real work happens). The backend stores data, processes requests, handles logins, and talks to databases.
Provides patterns for building production-ready Node.js backend services with Express/Fastify, covering middleware, error handling, authentication, database integration, and API design.
Enforces workflow for full-stack apps: requirements, architecture decisions, scaffolding checklists, patterns for API integration, auth, error handling, real-time (SSE/WebSocket) across Node/React/Next.js, Python, Go.
Generates production-ready backend code with routes, data models, service layers, and validation from API contracts, task breakdowns, and data models. Adapts to any tech stack.
Share bugs, ideas, or general feedback.
/api/users is the Users department. /api/products is Products. Each one handles specific requests.GET — "Give me data" (reading)POST — "Here's new data, save it" (creating)PUT/PATCH — "Update this existing data" (editing)DELETE — "Remove this data" (deleting)User clicks "Submit"
↓
Frontend sends HTTP request to backend
↓
Backend receives request, processes it
↓
Backend talks to database if needed
↓
Backend sends response back
↓
Frontend displays the result
.env files — where secrets live, read by the server but never sent to users