用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Dev-Toolbelt/dev-team-agents --skill architecture-docs命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
| name | architecture-docs |
| description | Where architecture documents live, what each contains, and the conformance report format. |
Canonical location, content contract, and conformance reporting format for the documents an architect produces. Load when writing, updating, or validating any of them.
All architecture documents MUST be written to docs/development/ at the project root.
| Document | Location |
|---|---|
| Architecture design | docs/development/architecture.md |
| Tech stack decisions | docs/development/tech-stack.md |
| Code standards | docs/development/code-standards.md |
| Database decisions | docs/development/database.md |
| API contracts | docs/development/api-contracts.md |
| ADRs | docs/development/adrs/NNNN-*.md |
| Conformance reports | docs/development/conformance-report.md |
NEVER write architecture documents to:
.opencode/ — opencode configuration only.claude/ — Claude Code configuration only.dev-team-agents/ — the framework installation directory.)| Document | Must contain |
|---|---|
architecture.md | System design, layers, component boundaries, integration patterns, and the layer depth chosen per domain area. Every significant decision also gets an ADR. |
tech-stack.md | Chosen technologies with rationale, including what was considered and rejected. |
code-standards.md | Patterns, naming conventions, linting rules, and design patterns — specific to this project's stack, not generic advice. |
database.md | Database choice, schema strategy, migration approach, indexing guidelines. Finalize only after database-specialist review. |
api-contracts.md | API style (REST/GraphQL/RPC), versioning policy, auth model, response and error envelope. |
Spec self-review before handing off — silently check every document for: placeholders and TODOs, contradictions between documents, ambiguous decisions, YAGNI violations, and scope creep. Fix inline before asking the user to review.
Produced or updated after each Quality Gate run. Flag every finding with one tag:
| Tag | Meaning |
|---|---|
[ARCH-DEVIATION] | The code does not follow the decided architecture |
[TECH-DEBT] | Acceptable shortcut, but it must be tracked |
[CONFORMANT] | This is correct |
Write to docs/development/conformance-report.md. This file accumulates across sprints —
append, never overwrite.
## Conformance Report — [Sprint / Date]
### Summary
[Overall conformance posture — 1-2 sentences]
### Deviations
| File / Area | Deviation | Severity | Action |
|---|---|---|---|
| service/OrderService.js | Business logic in controller | HIGH | Refactor before next sprint |
### Tech Debt Tracked
| Item | Introduced | Owner | Target Sprint |
|---|---|---|---|
### Conformant Areas
[List areas that were reviewed and passed]