后端基础知识
- 作者仓库星标 0
- 作者仓库 skills-registry
- 领域
- 工程开发
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @tomevault-io · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
# 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? (`/users` not `/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:
1. **Architecture**: "If I wanted to switch from Express to Fastify, what would need to change?"
2. **Validation**: "What happens if someone sends malformed JSON?"
3. **Auth**: "How do you know this user owns this resource?"
4. **Errors**: "What does the client see when the database is down?"
5. **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](https://github.com/ComeOnOliver/skillshub) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-22 -->
章节与文件索引
按说明文件中的顺序排列。
何时申请
API设计
关注点分离
错误处理
安全性
文件/命令 -> /users · /getUsers · /api/v1/ · SELECT * FROM users WHERE email = '${email}'
内容校验值 -> fd17c4d05888
当前原文的自动摘译,尚未人工审校。
何时申请
在查看以下内容时激活此技能: API 路由处理程序 Express/Fastify/Hono 中间件 数据库查询和模型 身份验证/授权逻辑
API设计
[ ] RESTful:路由是否遵循 REST 约定? (GET 用于读取,POST 用于创建等) [ ] 命名:端点是名词,而不是动词? (
/users不是/getUsers) [ ] 版本控制:API 版本是否可用于将来的更改? (/api/v1/) [ ] 状态代码:是否返回正确的 HTTP 状态代码?关注点分离
[ ] 路由:路由是否只处理 HTTP 问题(req/res)? [ ] 控制器:业务逻辑位于控制器/服务中,而不是路由中吗? [ ] 服务:数据访问是否从业务逻辑中抽象出来? [ ] 模型:模型仅负责数据形状/验证吗?
错误处理
[ ] Try/Catch:异步操作是否正确包装? [ ] 错误响应:返回的错误是否带有正确的状态代码? [ ] 日志记录:是否使用上下文记录错误? [ ] 无泄漏:内部错误是否对客户端隐藏?
安全性
[ ] 输入验证:所有输入在使用前是否经过验证? [ ] 身份验证:受保护的路由是否真正受到保护? [ ] 授权:用户只能访问自己的数据吗? [ ] 速率限制:是否可以保护端点免受滥用?