Skip to content
Agentmart
Submit a tool

architecture

Create system architecture, Architecture-Change-Definition documents, data flow diagrams, component architecture, and infrastructure diagrams with ASST and…

Skill by x1chg956

IndexedApache-2.0
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/x1chg956-architecture

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Create system architecture, Architecture-Change-Definition documents, data flow diagrams, component architecture, and infrastructure diagrams with ASST and traceability coverage. Use when designing high-level system architecture, enterprise change architecture, microservices layout, cloud infrastructure (AWS/Azure/GCP), on-premises setup, or when the user asks for architecture diagrams. Integrates with UI/UX designer outputs for frontend architecture.

Use cases: design, frontend, testing, devops

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/architecture

What's inside

Skill name
architecture
Description
Create system architecture, Architecture-Change-Definition documents, data flow diagrams, component architecture, and infrastructure diagrams with ASST and traceability coverage. Use when designing high-level system architecture, enterprise change architecture, microservices layout, cloud infrastructure (AWS/Azure/GCP), on-premises setup, or when the user asks for architecture diagrams. Integrates with UI/UX designer outputs for frontend architecture.
License
Apache-2.0
Metadata
owner: enterprise-architecture · domain: design · version: 1.0.0
Instructions
164 lines in SKILL.md · view on GitHub

Files (3)

  • SKILL.md
  • diagram-examples.md · references/
  • subskills.md

SKILL.md (first lines)

# Architecture Design

Create architecture diagrams and Architecture-Change-Definition artifacts using Mermaid only.

## Purpose

Produce enterprise architecture artifacts that are complete, reviewable, and traceable across downstream phases.

## When to Use

- New solution architecture definition
- Major architecture change requests
- Baseline-to-target transition planning

## Inputs Required

- Approved requirements baseline (RD/FSD/user stories)
- Current-state constraints and system inventory
- NFR targets and compliance requirements

## Outputs Produced

- Architecture-Change-Definition document
- Mermaid baseline/target/transition diagrams
- ASST and Well-Architected alignment summary
- Cross-phase traceability matrix

## Workflow

```
1. Understand requirements → 2. Define Architecture-Change-Definition sections → 3. Apply ASST checks → 4. Map Well-Architected principles → 5. Generate diagrams and traceability artifacts
```

## ASST Aspects

Always address ASST in architecture outputs:

- **Availability**: HA strategy, failover, RTO/RPO targets, resilience testing
- **Security**: identity, secrets, encryption, policy controls, auditability
- **Scalability**: horizontal/vertical scaling, capacity model, performance targets
- **Traceability**: explicit links from business goals to architecture decisions and implementation artifacts

## IT Enterprise Architecture Change Definition Coverage

Architecture documents should cover all sections below:

1. Executive summary and change intent
2. Business drivers and strategic alignment
3. Current-state architecture (baseline)
4. Target-state architecture
5. Architecture principles and constraints
6. Options analysis and trade-offs
7. Gap analysis and transition states
8. Work packages and migration roadmap
9. NFR coverage (availability, security, performance, operability)
10. Data architecture and integration impacts
11. Security, risk, and compliance impacts
12. Governance model and decision rights
13. Cost, licensing, and capacity considerations
14. Operational readiness, support model, and DR
15. Traceability matrix and acceptance criteria

## Well-Architected Architecture Principles Integration

For each architecture section, explicitly evaluate:

- **Design for Scalability**
- **Design for Resiliency**
- **Design for Efficiency**
- **Design for Interoperability and Modularity**

## Subskills to Invoke for Enterprise Architecture Documents

For Architecture-Change-Definition depth, compose with these subskills:

1. `user-journey-mapper` for business flow and actor context
2. `api-designer` + `openapi-writer` for interface and contract sections
3. `erd-designer` for data architecture impacts
4. `sequence-designer` + `state-designer` for transition and runtime behavior
5. `runbook-writer` for operational readiness and DR sections
6. `adr-writer` for decisions, trade-offs, and governance trace
7. `low-level-design` for downstream implementation linkage

Carry requirement IDs across all subskill outputs.

## Integration with UI/UX Design

When designing systems with user interfaces, coordinate with the UI/UX designer agents:

| UI/UX Output | Architecture Use |
|--------------|------------------|
| User journeys | Inform API flows and service boundaries |
| Wireframes | Define frontend component structure |
| Figma specs | Specify design token integration |
| HTML prototypes | Validate frontend architecture |

### Frontend Architecture from UI/UX

Use UI/UX designer outputs to inform frontend architecture:

```mermaid
flowchart TB
    subgraph design["UI/UX Design Layer"]
        journeys[User Journeys]
        wireframes[Wireframes]
        figma[Figma Specs]
    end
    
    subgraph frontend["Frontend Architecture"]
        components[Component Library]
        pages[Page Components]
        state[State Management]
        api_client[API Client]
    end
    
    subgraph backend["Backend Services"]
        gateway[API Gateway]
        services[Microservices]
    end

From x1chg956/sdlc-skills, Apache-2.0.

More from x1chg956/sdlc-skills

Signals

Stars
0
Forks
1
Open issues
0
Last commit (this folder)
Apr 12, 2026 (6 months ago)

From GitHub (fetched Oct 24, 2026).

Details

Version
1.0.0
License
Apache-2.0
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from x1chg956

Cite this page

architecture skill. Agent Mart. https://agentmart.dev/skills/x1chg956-architecture (last updated 2026-10-24)