菜单
Use when working on backend service architecture, API boundaries, module decomposition, service contracts, and data flow design. Focus on clear ownership, stable interfaces, failure isolation, and maintainability.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Mr-Q526/TeamCC-Platform --skill backend-api-architecture命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| schemaVersion | 2026-04-11T00:00:00.000Z |
| skillId | backend/backend-api-architecture |
| name | backend-api-architecture |
| displayName | Backend API Architecture |
| description | Use when working on backend service architecture, API boundaries, module decomposition, service contracts, and data flow design. Focus on clear ownership, stable interfaces, failure isolation, and maintainability. |
| aliases | ["backend-api-architecture","Backend API Architecture","backendapiarchitecture","服务端","server side","服务接口"] |
| version | 0.1.0 |
| sourceHash | sha256:5f2c5e93c46886529c2661666e0e57abf8c43a59ee2c82638ad8a1dd5b3ca6d9 |
| domain | backend |
| departmentTags | ["backend-platform"] |
| sceneTags | ["architecture"] |
Use this skill when the task involves backend service architecture, API boundaries, module decomposition, service contracts, and data flow design.
Goal: produce reliable engineering guidance and implementation steps focused on clear ownership, stable interfaces, failure isolation, and maintainability.
Use when designing about pages, company story pages, team pages, and mission pages. Basic version focused on trust, narrative, people, values, and company proof; emphasizes fast layout, obvious labels, a minimal section set, and a short checklist.
Use when designing about pages, company story pages, team pages, and mission pages. Pro version focused on trust, narrative, people, values, and company proof; emphasizes deep information architecture, strong hierarchy, explicit states, responsive behavior, accessibility, and validation checks.
Use when the task is to design a management console, 管理后台, admin panel, operations dashboard, moderation tool, or back-office web app. Focus on operator efficiency, table-first layout, filters, bulk actions, status visibility, and low-noise product UI.