Express api mean

Skill endorphin-ai/claude-code-teams/mean-team/.claude/skills/express-api-mean

🍕 One Pizza Team [AI Agents Team ] | Claude Code Agent Squads

Install

npx -y skills add endorphin-ai/claude-code-teams --skill express-api-mean

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Express.js API architecture for MEAN stack apps. Use when designing REST endpoints, middleware chains, authentication flows, error handling contracts, and request/response schemas.

SKILL.md

2.7 KB, as published. Nobody here has run it

Express Api Mean

Purpose

Design REST API architectures for MEAN stack applications using Express.js. Produce endpoint contracts, middleware chains, authentication flows, error handling patterns, and request/response schemas that backend developers implement directly.

Key Patterns

REST Endpoint Design

Resource-based URLs: /api/users, /api/posts, /api/posts/:id/comments
HTTP methods: GET (read), POST (create), PUT (full update), PATCH (partial update), DELETE (remove)
Consistent success response: { success: true, data: {...}, pagination: {...} }
Consistent error response: { success: false, error: { code, message, details } }

Middleware Architecture

Request flow: CORS -> Body Parser -> Rate Limiter -> Auth -> Validation -> Controller -> Response

Global middleware: CORS, body-parser, morgan (logging), helmet (security headers), compression
Route middleware: auth (JWT verify), validate (Joi/express-validator), authorize (role check)
Error middleware: Global error handler as last middleware

Authentication Flow (JWT)

POST /api/auth/register -> hash password -> save user -> return JWT
POST /api/auth/login -> verify credentials -> return JWT + refresh token
POST /api/auth/refresh -> verify refresh token -> return new JWT
Protected routes: Authorization: Bearer <token> header -> verify middleware

Controller Pattern

Use asyncHandler wrapper to avoid try/catch boilerplate
Use ApiError class for consistent error throwing
All list endpoints include pagination (page, limit, total, pages)
Sort by -createdAt by default (newest first)

Conventions

All routes prefixed with /api/
Use plural nouns for resources: /users not /user
Nested resources max 2 levels: /posts/:id/comments
HTTP status codes: 200 (OK), 201 (Created), 400 (Bad Request), 401 (Unauthorized), 403 (Forbidden), 404 (Not Found), 409 (Conflict), 422 (Validation), 500 (Server Error)
Validate request body with Joi or express-validator
Pagination on all list endpoints (default: page=1, limit=20)
Use express-rate-limit on auth routes (max 10 attempts per 15 min)
Use helmet for security headers

Knowledge Strategy

Patterns to capture: Endpoint designs that worked well, middleware chains for common scenarios, auth patterns
Examples to collect: Complete route files, controller patterns, middleware implementations
Update permission: Agents may freely add/update files in references/. Changes to SKILL.md or scripts/ require user approval.