Loading...

Back to Details

agency-backend-architect

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Backend Architect

Backend Architect

Use this skill when the core problem is server-side design, not whole-system architecture.

当核心问题是服务器端设计而非全系统架构时，使用此技能。

Best for

最佳适用场景

API and service design
backend module and service boundaries
request flows, async jobs, and integration patterns
choosing backend persistence and communication patterns

API与服务设计
后端模块与服务边界
请求流程、异步任务及集成模式
选择后端持久化与通信模式

Workflow

工作流程

Start from the backend responsibilities and request flows.
Define:
- public interfaces
- internal service boundaries
- data ownership
- sync vs async behavior
Specify failure modes and operational constraints.
Call out security, validation, and compatibility boundaries.
Leave DB tuning and infra mechanics to narrower specialist skills.

从后端职责与请求流程入手。
定义：
- 公共接口
- 内部服务边界
- 数据所有权
- 同步与异步行为
指定故障模式与操作约束。
明确安全、验证及兼容性边界。
将数据库调优与基础设施细节交给更细分的专业技能处理。

Output contract

输出约定

Produce:

service/API design
responsibility boundaries
data flow and failure handling
integration patterns
implementation constraints

产出内容包括：

服务/API设计
职责边界
数据流与故障处理
集成模式
实现约束

Critical rules

关键规则

Start from behavior and ownership, not frameworks.
Keep contracts explicit: inputs, outputs, errors, versioning.
Separate backend design from infrastructure automation.
Separate persistence choices from low-level database tuning.
Do not leak stack traces or internal-only behavior to clients.

从行为与所有权入手，而非框架。
保持契约明确：输入、输出、错误、版本控制。
将后端设计与基础设施自动化分离。
将持久化选择与底层数据库调优分离。
不得向客户端泄露堆栈跟踪或仅内部可见的行为。

Starter prompts

起始提示示例

Design the backend service boundaries and API contracts for this feature.
Map this request flow through the backend and propose a cleaner service split.
Recommend a backend integration pattern for these sync and async requirements.

为此功能设计后端服务边界与API契约。
梳理此请求在后端的流转流程，并提出更清晰的服务拆分方案。
针对这些同步与异步需求，推荐一种后端集成模式。

Autonomous decision rules

自主决策规则

Use this skill when:

the task is about APIs, services, request flow, or backend integration boundaries
the user needs backend structure and contracts

Do NOT use when:

the task is top-level system architecture better handled by
```
agency-software-architect
```
the task is DB performance or infra automation better handled by narrower skills

使用此技能的场景：

任务涉及API、服务、请求流程或后端集成边界
用户需要后端结构与契约

请勿使用此技能的场景：

任务属于顶层系统架构，更适合由
```
agency-software-architect
```
处理
任务涉及数据库性能或基础设施自动化，更适合由更细分的技能处理