AGENT SKILL

software-architecture-documentation

This skill should be used when creating, reviewing, or updating architecture documentation (ARCHITECTURE.md) for a software project. It provides a comprehensive template and best practices for producing documentation that enables rapid codebase comprehension by developers and AI agents.

License 许可
MIT
最近更新
2026-11-10
Stars
★ 0
Forks
0

01 前言 Front Matter

name
software-architecture-documentation
description
This skill should be used when creating, reviewing, or updating architecture documentation (ARCHITECTURE.md) for a software project. It provides a comprehensive template and best practices for producing documentation that enables rapid codebase comprehension by developers and AI agents.

02 资源文件 2

03 SKILL.md 正文

Software Architecture Documentation

Generate comprehensive ARCHITECTURE.md files that enable developers and AI agents to rapidly understand a codebase. Based on the architecture.md template by timajwilliams.

When To Use

  • A new project needs architecture documentation
  • Onboarding documentation is missing or outdated
  • A codebase is being prepared for AI agent interaction
  • Existing architecture docs need review or improvement
  • Documentation completeness audit is requested

Workflow

Creating New Architecture Docs

  1. Explore the codebase - Run tree -L 3 -I 'node_modules|__pycache__|.git|dist|build' to understand directory structure
  2. Identify technologies - Check package.json, requirements.txt, go.mod, Cargo.toml, or similar dependency files
  3. Trace data flow - Follow entry points (routes, handlers) through to storage
  4. Map external dependencies - Review configs and environment variables for third-party services
  5. Load the template - Read references/architecture-template.md and fill in each section
  6. Verify accuracy - Cross-reference documented structure against actual code

Reviewing Existing Docs

  1. Compare against template - Read references/architecture-template.md to identify missing sections
  2. Verify currency - Check if documented structure matches actual codebase
  3. Test comprehension - Determine if someone can navigate the codebase using only the doc
  4. Update stale sections - Prioritize project structure and external integrations

Output Location

Place the generated documentation at ARCHITECTURE.md in the repository root, or docs/ARCHITECTURE.md if documentation is centralized.

Key Principles

  1. Optimize for speed - Enable rapid comprehension, not exhaustive coverage
  2. Stay current - Outdated docs are worse than no docs
  3. Be honest - Document what exists, not what is wished for
  4. Link, don't duplicate - Reference code files instead of copying content
  5. Use portable diagrams - ASCII art or Mermaid for version control friendliness

Resources

  • references/architecture-template.md - The complete 11-section template to fill in
  • references/writing-guide.md - Best practices, anti-patterns, and project-type-specific guidance

04 同仓库更多 Skills

tzeusy-org
tzeusy-org/ai-bootstrap

user-run

Use when a step needs privileges this session lacks (docker, sudo, another user's checkout or secrets, host access) and the owner must run it as tze. Writes a reviewable /home/orca/.tmp/<slug>/run.sh that impersonates tze (USER_TO_IMPERSONATE overrides), tees timestamped logs plus latest.log and collects artifacts there; Claude presents it with a risk and time brief, then continues from the logs. Triggers: "I'll run it for you", "permission denied on docker.sock", "needs sudo", "sudo: a password is required", "run as tze", "/user-run".

★ 0
tzeusy-org
tzeusy-org/ai-bootstrap

requesting-code-review

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

开发工程师代码审查
★ 0
tzeusy-org
tzeusy-org/ai-bootstrap

receiving-code-review

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

开发工程师代码审查
★ 0
tzeusy-org
tzeusy-org/ai-bootstrap

finishing-a-development-branch

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

★ 0
tzeusy-org
tzeusy-org/ai-bootstrap

executing-plans

Use when you have a written implementation plan to execute in a separate session with review checkpoints

★ 0
tzeusy-org
tzeusy-org/ai-bootstrap

dispatching-parallel-agents

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

★ 0