backend-fundamentals
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- Engineering
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: backend-fundamentals
description: Auto-invoke when reviewing API routes, server logic, Express/Node.js code, or backend architectu…
category: engineering
runtime: no special runtime
---
# backend-fundamentals output preview
## PART A: Task fit
- Use case: Auto-invoke when reviewing API routes, server logic, Express/Node.js code, or backend architecture. Enforces REST conventions, middleware patterns, and separation of concerns. Use when this capability is needed..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “When to Apply / Review Checklist / API Design” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Auto-invoke when reviewing API routes, server logic, Express/Node.js code, or backend architecture. Enforces REST conventions, middleware patterns, and separation of concerns. Use when this capability is needed.”.
- **02** When the source has headings, the agent prioritizes “When to Apply / Review Checklist / API Design” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source mentions slash commands such as `/users`, `/getusers`, `/api`; use them first when your agent supports command triggers.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “When to Apply / Review Checklist / API Design”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: backend-fundamentals
description: Auto-invoke when reviewing API routes, server logic, Express/Node.js code, or backend architectu…
category: engineering
source: tomevault-io/skills-registry
---
# backend-fundamentals
## When to use
- Auto-invoke when reviewing API routes, server logic, Express/Node.js code, or backend architecture. Enforces REST conv…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “When to Apply / Review Checklist / API Design” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "backend-fundamentals" {
input -> user goal + target files + boundaries + acceptance criteria
context -> When to Apply / Review Checklist / API Design
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} Backend Fundamentals Review
"APIs are contracts. Break them, and you break trust."
When to Apply
Activate this skill when reviewing:
- API route handlers
- Express/Fastify/Hono middleware
- Database queries and models
- Authentication/authorization logic
- Server-side business logic
Review Checklist
API Design
- RESTful: Do routes follow REST conventions? (GET for read, POST for create, etc.)
- Naming: Are endpoints nouns, not verbs? (
/usersnot/getUsers) - Versioning: Is API versioned for future changes? (
/api/v1/) - Status Codes: Are correct HTTP status codes returned?
Separation of Concerns
- Routes: Do routes only handle HTTP concerns (req/res)?
- Controllers: Is business logic in controllers/services, not routes?
- Services: Is data access abstracted from business logic?
- Models: Are models responsible only for data shape/validation?
Error Handling
- Try/Catch: Are async operations wrapped properly?
- Error Responses: Are errors returned with proper status codes?
- Logging: Are errors logged with context?
- No Leaks: Are internal errors hidden from clients?
Security
- Input Validation: Is ALL input validated before use?
- Authentication: Are protected routes actually protected?
- Authorization: Can users only access their own data?
- Rate Limiting: Are endpoints protected from abuse?
Common Mistakes (Anti-Patterns)
1. Fat Routes
❌ app.post('/users', async (req, res) => {
// 100 lines of validation, business logic, DB queries
});
✅ app.post('/users', validateUser, userController.create);
2. No Input Validation
❌ const { email } = req.body;
await db.query(`SELECT * FROM users WHERE email = '${email}'`);
✅ const { email } = validateBody(req.body, userSchema);
await User.findByEmail(email); // parameterized
3. Wrong Status Codes
❌ res.status(200).json({ error: 'Not found' });
✅ res.status(404).json({ error: 'User not found' });
4. Leaking Internal Errors
❌ catch (error) {
res.status(500).json({ error: error.message, stack: error.stack });
}
✅ catch (error) {
logger.error('User creation failed', { error, userId });
res.status(500).json({ error: 'Something went wrong' });
}
Socratic Questions
Ask the junior these questions instead of giving answers:
- Architecture: "If I wanted to switch from Express to Fastify, what would need to change?"
- Validation: "What happens if someone sends malformed JSON?"
- Auth: "How do you know this user owns this resource?"
- Errors: "What does the client see when the database is down?"
- Testing: "How would you test this endpoint in isolation?"
HTTP Status Code Reference
| Code | When to Use |
|---|---|
| 200 | Success (with body) |
| 201 | Created (after POST) |
| 204 | Success (no content, after DELETE) |
| 400 | Bad request (validation failed) |
| 401 | Unauthorized (not logged in) |
| 403 | Forbidden (logged in but not allowed) |
| 404 | Not found |
| 409 | Conflict (duplicate resource) |
| 500 | Server error (hide details from client) |
Architecture Layers
Request → Route → Controller → Service → Repository → Database
↓
Middleware (auth, validation, logging)
| Layer | Responsibility |
|---|---|
| Route | HTTP verbs, paths, middleware chain |
| Controller | Request/response handling, calling services |
| Service | Business logic, orchestration |
| Repository | Data access, queries |
Red Flags to Call Out
| Flag | Question to Ask |
|---|---|
| SQL in route handler | "Should data access be in a separate layer?" |
| No try/catch on async | "What happens if this fails?" |
| req.body used directly | "What if someone sends unexpected fields?" |
| Hardcoded secrets | "How would this work in production?" |
| No pagination on list endpoints | "What if there are 10,000 records?" |
Source: ComeOnOliver/skillshub — distributed by TomeVault.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review