Analyze system architecture, module structure, API contracts, data models, and code patterns. Use when designing systems, reviewing module boundaries, evaluating API designs, analyzing data models, checking pattern conformance, tracing decisions, or reviewing frontend architecture. Triggers: "architecture", "module design", "API design", "data model", "boundaries", "patterns", "decisions", "frontend architecture".
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Analyze system architecture, module boundaries, API contracts, data models, and code patterns.
Run the shared context discovery protocol in CONTEXT_DISCOVERY.md. Execute all phases in order (use deep scan mode for Phase 7). Also glob for architecture-specific documents:
docs/adr/**/*.md, docs/architecture/**/*.md, docs/design/**/*.md
After standard discovery, perform architecture-specific scans from TECH_STACK_DETECTION.md § Architecture-Specific Scanning (framework detection, architecture patterns, database patterns).
Parse from $ARGUMENTS:
| Mode | Description |
|---|---|
module <name> | Deep module structure analysis |
api <feature> | API endpoint analysis and design guidance |
data-model <feature> | Database schema and data model analysis |
boundaries | Module boundary and coupling analysis |
patterns | Pattern conformance check |
decisions | ADR and decision traceability |
frontend <feature> | Frontend architecture guidance |
| (none) | Ask what the user needs architectural guidance on |
| Mode | Produces |
|---|---|
module <name> | Structure, domain model, API surface, dependencies, maturity, quality assessment, and prioritized recommendations |
api <feature> | Endpoint design (method, path, DTOs, auth, pagination, errors) matching existing patterns |
data-model <feature> | Schema design (tables, types, relationships, indexes, migrations) matching existing models |
boundaries | Import graph, shared references, coupling analysis, boundary violations |
patterns | Pattern catalog with codebase examples (layering, DTOs, events, testing) |
decisions | Decision traceability table (decision, evidence, status) |
frontend <feature> | Component hierarchy, data flow, state management, design system integration |
See WORKFLOW.md for detailed execution steps per mode.
After producing the analysis, ask the user:
Save this analysis to
{output_dir}/architecture/{filename}.md?
Where {output_dir} comes from .arkhe.yaml (default: arkhe/roadmap).
| Mode | Filename Pattern |
|---|---|
module <name> | module-{name}.md |
api <feature> | api-{feature-slug}.md |
data-model <feature> | data-model-{feature-slug}.md |
boundaries | boundary-analysis.md |
patterns | pattern-catalog.md |
decisions | decision-traceability.md |
frontend <feature> | frontend-{feature-slug}.md |
--deep)When $ARGUMENTS contains --deep, run the full multi-agent pipeline with Adversarial Review. A red team agent actively tries to break the proposed architecture.
See WORKFLOW.md § Deep Pipeline for the 5-phase execution protocol.
Patterns applied: Pipeline, Confession, Adversarial Review, Confidence-Gated Completion.
See the System Architect section of LANE_DISCIPLINE.md. Stay in your lane.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Create, review, and manage Architecture Decision Records (ADRs) with auto-numbering, template detection, quality review, and index maintenance. Use when user mentions "ADR", "architecture decision", "document this decision", "create ADR", "review ADR", editing ADR files (docs/adr/, doc/adr/, .adr/), or discussing architectural choices and tradeoffs.
日本語の概要は準備中です。原文の説明を表示しています。
Converts natural-language descriptions or UI spec files into optimized Google Stitch prompts. Use when creating, refining, or validating design directives for Google Stitch. Use when user says "create a Stitch prompt", "optimize this for Stitch", "convert this spec to a Stitch prompt", "write a UI prompt", or mentions Google Stitch prompt authoring. Follows Stitch best practices with short, directive prompts focused on screens, structure, and visual hierarchy.
日本語の概要は準備中です。原文の説明を表示しています。
Zero-dependency live-preview server providing an agent↔browser bidirectional companion. Watches a content directory, wraps HTML fragments in a frame template, broadcasts live-reload over WebSocket, and captures browser-side click events to a JSONL file. Use when an agent needs to show HTML to the user in a browser and react to clicks — mockups, design exploration, gallery browsing, multi-select choices, prototype iteration. Triggered by "live preview", "browser companion", "preview server", "browser mockup", "show in browser", "arkhe-preview", or any skill that wants to write HTML fragments and have the user see them reload in real time.
日本語の概要は準備中です。原文の説明を表示しています。
Deletes merged git branches (local and remote) and flags stale unmerged branches for manual review. Use when user mentions "cleanup branches", "delete merged branches", "prune old branches", "remove stale branches", "branch cleanup", or runs /cleanup-branches command.
日本語の概要は準備中です。原文の説明を表示しています。
Interactive Claude Code environment setup wizard. Detects existing configuration, guides through best-practice setup for Global CLAUDE.md, project scaffolding, MCP servers, hooks, custom agents, keybindings, and settings. Use when user runs /devtools:code-env-setup, mentions "setup claude code", "configure claude", "claude code setup", "environment setup", or "initialize claude code".
日本語の概要は準備中です。原文の説明を表示しています。
Explains complex code through clear narratives, visual diagrams, and step-by-step breakdowns. Use when user asks to explain code, understand algorithms, analyze design patterns, wants code walkthroughs, or mentions "explain this code", "how does this work", "code breakdown", or "understand this function".
日本語の概要は準備中です。原文の説明を表示しています。