architecture-docs

Produce architecture documentation for technical audiences using established frameworks — the C4 model for system structure (Context / Container / Component / Code), Architectural Decision Records (ADRs) for capturing the why behind significant design choices, OpenAPI for HTTP API specifications, and system / component design documents for engineers who need to build against or reason about the architecture. Use when someone asks to document system architecture, write an ADR, capture an architectural decision, generate C4 diagrams (context / container / component), produce an OpenAPI spec, draft a component design doc, or document how services integrate. Trigger phrases include "create a C4 diagram", "write an ADR for X", "document the architecture", "specify the API", "OpenAPI spec for", "system design doc", "decision record", "architecture overview". Not for: end-user-facing docs (use the `aeo-docs:diataxis` skill instead — tutorials, how-tos, references, explanations live there), README content, or code-le

インストールへ移動

リポジトリ: AeyeOps/aeo-skill-marketplace
ソースの最終更新活動: 2026年5月8日 07:36
検出された SKILL.md の言語: 英語
スター: 3
フォーク: 2

インストール方法

デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。

npx skills add https://github.com/AeyeOps/aeo-skill-marketplace --skill architecture-docs

コマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。

ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。

ソースファイルを確認

インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。

ファイルエクスプローラー

5 ファイル

SKILL.md

ソースの指示 · 読み取り専用プレビュー

検索に戻るインストールに戻る

vscode-extension

Contains verified extension development workflows, webview CSP pitfall resolutions, and profile-based install fixes that produce more correct results than reasoning from general training alone. Targets stable VS Code on Windows/macOS/Linux desktop — not code-insiders on WSL/Linux (use vscode-insiders-extension for that). Consult when building or debugging a VS Code extension, scaffolding with esbuild, fixing blank webview panels or silent CSP violations, troubleshooting extensions that won't load after install with profiles, adding dual TreeView+WebviewView toggle panels, or publishing to the marketplace. Do NOT use for code-insiders on WSL/Linux (use vscode-insiders-extension), VS Code user configuration (themes, keybindings, tasks.json), Chrome/browser extensions, Electron apps, JupyterLab plugins, or Monaco Editor embeds.

2026-07-12

markdown-mermaid

Craft Mermaid diagrams within Markdown for flowcharts, ERDs, sequence diagrams, state machines, Gantt charts, and mindmaps. Includes validated syntax templates, layout optimization, and cross-platform rendering for GitHub, GitLab, VS Code, and Obsidian. Use when: creating diagrams in markdown files, debugging "diagram not rendering" errors, selecting diagram types for docs, visualizing database schemas or API flows, or fixing Mermaid syntax issues.

2026-07-12

n8n-code-javascript

Implement JavaScript logic in n8n Code nodes with $input, $json, $node, and $helpers APIs. Includes HTTP requests, Luxon DateTime operations, error debugging, and mode selection (Run Once vs Run for Each). Engage for custom data transformations or complex business logic.

2026-07-12

このリポジトリのすべてを見る

Architecture Documentation

Architecture documentation serves a different audience and purpose than user-facing documentation. The reader is a developer, architect, or technical stakeholder who needs to implement against, integrate with, or reason about the system. The output is structural and decision-oriented, not learning-oriented.

If the request is to write user-facing docs (tutorials, how-tos, references, explanations that live in docs/), use the aeo-docs:diataxis skill instead. This skill covers the architectural-artifact side: structure diagrams, decision records, API specs, system / component design.

The four artifact types

Artifact

What it captures

Audience

Path

C4 diagrams

System structure at four zoom levels

Everyone (Context) → Architects (Code)

name

architecture-docs

description

Architecture Documentation

The four artifact types

Artifact	What it captures	Audience	Path
C4 diagrams	System structure at four zoom levels	Everyone (Context) → Architects (Code)

Level	Audience	What's shown
1. System Context	Everyone	The system as a single box, the people and external systems it interacts with
2. Container	Technical stakeholders	High-level technology choices (apps, databases, services)
3. Component	Architects, senior developers	Major building blocks inside a container
4. Code	Developers	Class / module structure inside a component (often skipped in favor of code itself)

Anti-pattern	What it looks like	Fix
Implementation tour	Documentation that just narrates the code structure file by file	Capture decisions and structure that aren't obvious from the code
Audience-blind	One doc trying to serve executives, architects, and devs	Multiple short docs, each with a stated audience
Frozen artifact	Doc is months out of date, nobody trusts it, but it persists	Either keep it current or delete it; stale architecture docs cause wrong implementation
ADR as proposal	Using ADRs to propose decisions instead of recording accepted ones	Use a regular design doc for proposals; the ADR captures the outcome
C4 Code level for everything	Generating Code-level diagrams that immediately go stale	Skip the Code level unless an audience specifically needs it

architecture-docs

インストール方法

ソースファイルを確認

Architecture Documentation

The four artifact types

Architecture Documentation

The four artifact types

Picking the artifact

C4 Model — what each level captures

Architectural Decision Records (ADRs)

OpenAPI specifications

System and component design documents

Diagrams

Voice and register

Anti-patterns

Output paths summary

architecture-docs

ソース情報

インストール方法

ソースファイルを確認

このリポジトリの他の Skills

このリポジトリの他の Skills

Architecture Documentation

The four artifact types

Architecture Documentation

The four artifact types

Picking the artifact

C4 Model — what each level captures

Architectural Decision Records (ADRs)

OpenAPI specifications

System and component design documents

Diagrams

Voice and register

Anti-patterns

Output paths summary