Agent Skills
› AjayIrkal23/agentic-mercy-10x
› architect-system-design
architect-system-design
GitHub系统架构设计技能，用于任务分解、接口规划及实施计划制定。在代码变更前调用，根据后端或前端需求动态加载对应核心合规标准与插件，定义边界与数据流，并生成Mermaid图表辅助设计决策。
Trigger Scenarios
系统架构设计
模块分解
接口规划
实施路径未定
Install
npx skills add AjayIrkal23/agentic-mercy-10x --skill architect-system-design -g -y
SKILL.md
Frontmatter
{
"name": "architect-system-design",
"schema": 1,
"category": "planning",
"surfaces": [
"planning"
],
"triggers": {
"paths": [],
"intents": [
"planning"
],
"keywords": [
"architect",
"begin",
"changes",
"code",
"decomposition",
"design",
"implementation",
"interface",
"main",
"planning",
"system",
"task"
]
},
"platforms": [
"linux",
"darwin",
"windows"
],
"token-cost": 858,
"description": "ALWAYS invoke when the main task is design, decomposition, interface planning, or implementation planning — MUST use before code changes begin.",
"disable-model-invocation": false
}
Architect System Design
Active stack: Go (GO_UDP) — examples are Go-first; Node/TS/Fastify/Mongo variants in
references/node-stack.md.
Overview
This is the architecture shell.
It does not assume frontend and backend both matter. It classifies the touched surfaces first, then pulls in only the domain skills the design actually needs.
Use When
- The main task is system design, decomposition, or interface planning.
- Contracts, boundaries, phases, or ownership are still being decided.
- The implementation path is not yet decision-complete.
Do Not Use
- Straightforward implementation where scope is already known.
- Unknown failures that need debugging before design.
- Library documentation lookup by itself.
Surface Selection Rule
Choose the touched surface first:
- Backend-only: load the mandatory Backend Core Compliance Set before design decisions:
backend-standards-always-follow,service-layer-standards,backend-api-standards,backend-error-handling, andbackend-performance-standards. Preserveapi-contract-standardsfor envelope/contract work,domain-scaffold-patternsfor new domain/feature skeleton planning, andscaffold-standardsfor concrete backend skeleton details. - Frontend-only: select and load the matching Build Web Apps plugin skill when available, then load the mandatory Frontend Core Compliance Set:
frontend-standards-always-follow:frontend-app-builderfor new/redesign/visual surfaces orfrontend-standards-always-follow:react-best-practicesfor React/Vite/UI/code planning, plusfrontend-standards-always-follow,frontend-structure-standards,frontend-response-handling,frontend-server-data-patterns,frontend-api-standards, andreact-hooks-patterns. - Cross-surface: load the matching Build Web Apps plugin plus Frontend Core Compliance Set and Backend Core Compliance Set, then only the preserved add-ons required by the actual design.
Use project-reference-linkage when the design crosses shared contracts or linked modules.
Use mcp-usage-standards when external verification or MCP choice affects the design.
Use dead-code-and-change-audit if the design becomes a coding task or changes code.
Workflow
- Restate the problem, users, and success condition.
- Identify the touched surfaces, load the matching Build Web Apps plugin for frontend surfaces, and load the Frontend Core Compliance Set or Backend Core Compliance Set required by those surfaces.
- Extract requirements, constraints, and contract implications.
- Define boundaries, interfaces, and key data flow.
- Render the system design (boundaries, interfaces, data flow) as a Mermaid diagram via
claude-mermaid:mermaid-diagrams(plugin path~/.claude/plugins/marketplaces/claude-mermaid/skills/mermaid-diagrams/SKILL.md). Use flowchart for module boundaries, sequence diagram for cross-service flows, state diagram for lifecycle work, ER diagram for new data models. Iterate withmermaid_preview; persist viamermaid_saveinto the design doc. - Call out risks, bottlenecks, and validation needs.
- Produce an implementation-ready plan with phases and acceptance criteria.
Output Contract
- Clear problem framing.
- Touched surfaces and loaded domain standards.
- Interface and boundary decisions.
- Mermaid system / sequence / ER diagram (rendered via
claude-mermaid:mermaid-diagrams) embedded in the design doc. - Risks, assumptions, and acceptance criteria.
- An implementation-ready phase plan.
References
- Use
references/full-guide.mdif you need the previous full strict guide.
Version History
- 581d130 Current 2026-07-19 09:04
