Agent skill

Designing Architecture

by CloudAI-X in CloudAI-X/claude-workflow-v2

Designs software architecture and selects appropriate patterns for projects.

MITAuto-check passedDevelopment

Install Designing Architecture

skills CLI

$ npx skills add CloudAI-X/claude-workflow-v2 --skill designing-architecture -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install CloudAI-X/claude-workflow-v2 designing-architecture --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/CloudAI-X/claude-workflow-v2.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/designing-architecture .claude/skills/designing-architecture && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "designing-architecture" agent skill from https://github.com/CloudAI-X/claude-workflow-v2/tree/main/skills/designing-architecture into .claude/skills/designing-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "designing-architecture", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/CloudAI-X/claude-workflow-v2/tree/main/skills/designing-architecture

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add CloudAI-X/claude-workflow-v2 --skill designing-architecture -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install CloudAI-X/claude-workflow-v2 designing-architecture --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/CloudAI-X/claude-workflow-v2.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/designing-architecture .agents/skills/designing-architecture && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "designing-architecture" agent skill from https://github.com/CloudAI-X/claude-workflow-v2/tree/main/skills/designing-architecture into .agents/skills/designing-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "designing-architecture", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add CloudAI-X/claude-workflow-v2 --skill designing-architecture -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install CloudAI-X/claude-workflow-v2 designing-architecture --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/CloudAI-X/claude-workflow-v2.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/designing-architecture .cursor/skills/designing-architecture && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "designing-architecture" agent skill from https://github.com/CloudAI-X/claude-workflow-v2/tree/main/skills/designing-architecture into .cursor/skills/designing-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "designing-architecture", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/CloudAI-X/claude-workflow-v2.git --path skills/designing-architecture

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add CloudAI-X/claude-workflow-v2 --skill designing-architecture -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install CloudAI-X/claude-workflow-v2 designing-architecture --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/CloudAI-X/claude-workflow-v2.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/designing-architecture .gemini/skills/designing-architecture && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "designing-architecture" agent skill from https://github.com/CloudAI-X/claude-workflow-v2/tree/main/skills/designing-architecture into .gemini/skills/designing-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "designing-architecture", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install CloudAI-X/claude-workflow-v2 designing-architecture

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add CloudAI-X/claude-workflow-v2 --skill designing-architecture -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/CloudAI-X/claude-workflow-v2.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/designing-architecture .github/skills/designing-architecture && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "designing-architecture" agent skill from https://github.com/CloudAI-X/claude-workflow-v2/tree/main/skills/designing-architecture into .github/skills/designing-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "designing-architecture", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add CloudAI-X/claude-workflow-v2 --skill designing-architecture -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install CloudAI-X/claude-workflow-v2 designing-architecture --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/CloudAI-X/claude-workflow-v2.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/designing-architecture .opencode/skills/designing-architecture && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "designing-architecture" agent skill from https://github.com/CloudAI-X/claude-workflow-v2/tree/main/skills/designing-architecture into .opencode/skills/designing-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "designing-architecture", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: designing-architecture
GitHub stars: 1.4k
Used in: 1 other repo
Token cost: ~1.4k tokens
SKILL.md length: 230 words
Files: 1
Skills in repo: 13
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Designs software architecture and selects appropriate patterns for projects.

Works in 5 steps: Layered Architecture → Clean Architecture → Hexagonal (Ports & Adapters) → …
Designing systems
SKILL.md covers Architecture Decision Workflow, Pattern Selection Guide, Common Patterns and Directory Structure Patterns, plus 3 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Designing Architecture is an agent skill from CloudAI-X/claude-workflow-v2. Designs software architecture and selects appropriate patterns for projects. Use when designing systems, choosing architecture patterns, structuring projects, making technical decisions, or when asked about microservices, monoliths, or architectural approaches.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Software architecture, Microservices and Event-driven systems. The repository describes itself as: Universal Claude Code workflow plugin with agents, skills, hooks, and commands. The licence is MIT.

When your agent uses it

Designing systems
Choosing architecture patterns
Structuring projects
Making technical decisions

Example prompts

“Use the designing-architecture skill to design software architecture and selects appropriate patterns for projects”
“/designing-architecture”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Layered Architecture
Clean Architecture
Hexagonal (Ports & Adapters)
Event-Driven Architecture
CQRS (Command Query Responsibility Segregation)

What it can do on your machine

Read from SKILL.md and the folder at commit 3b5a89e. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Designing Architecture loads about 1.4k tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 230 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~71
When it runs · the whole SKILL.md, loaded when a task matches: ~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from CloudAI-X/claude-workflow-v2 at commit 3b5a89e, republished under its MIT licence (© CloudAI-X). 230 words, ~1,448 tokens.

Download SKILL.mdSave it as .claude/skills/designing-architecture/SKILL.md (or your agent's skills folder).

name: designing-architecture
description: Designs software architecture and selects appropriate patterns for projects. Use when designing systems, choosing architecture patterns, structuring projects, making technical decisions, or when asked about microservices, monoliths, or architectural approaches.

Designing Architecture

When to Load

Trigger: System design, module structure, new project scaffolding, choosing architecture patterns
Skip: Simple bug fixes or minor code changes that don't affect architecture

Architecture Decision Workflow

Copy this checklist and track progress:

Architecture Design Progress:
- [ ] Step 1: Understand requirements and constraints
- [ ] Step 2: Assess project size and team capabilities
- [ ] Step 3: Select architecture pattern
- [ ] Step 4: Define directory structure
- [ ] Step 5: Document trade-offs and decision
- [ ] Step 6: Validate against decision framework

Pattern Selection Guide

By Project Size

Size	Recommended Pattern
Small (<10K LOC)	Simple MVC/Layered
Medium (10K-100K)	Clean Architecture
Large (>100K)	Modular Monolith or Microservices

By Team Size

Team	Recommended
1-3 devs	Monolith with clear modules
4-10 devs	Modular Monolith
10+ devs	Microservices (if justified)

Common Patterns

1. Layered Architecture

┌─────────────────────────────┐
│       Presentation          │  ← UI, API Controllers
├─────────────────────────────┤
│       Application           │  ← Use Cases, Services
├─────────────────────────────┤
│         Domain              │  ← Business Logic, Entities
├─────────────────────────────┤
│      Infrastructure         │  ← Database, External APIs
└─────────────────────────────┘

Use when: Simple CRUD apps, small teams, quick prototypes

2. Clean Architecture

┌─────────────────────────────────────┐
│            Frameworks & Drivers      │
│  ┌─────────────────────────────┐    │
│  │     Interface Adapters       │    │
│  │  ┌─────────────────────┐    │    │
│  │  │   Application       │    │    │
│  │  │  ┌─────────────┐    │    │    │
│  │  │  │   Domain    │    │    │    │
│  │  │  └─────────────┘    │    │    │
│  │  └─────────────────────┘    │    │
│  └─────────────────────────────┘    │
└─────────────────────────────────────┘

Use when: Complex business logic, long-lived projects, testability is key

3. Hexagonal (Ports & Adapters)

        ┌──────────┐
        │ HTTP API │
        └────┬─────┘
             │ Port
    ┌────────▼────────┐
    │                 │
    │   Application   │
    │     Core        │
    │                 │
    └────────┬────────┘
             │ Port
        ┌────▼─────┐
        │ Database │
        └──────────┘

Use when: Need to swap external dependencies, multiple entry points

4. Event-Driven Architecture

Producer → Event Bus → Consumer
              │
              ├─→ Consumer
              │
              └─→ Consumer

Use when: Loose coupling needed, async processing, scalability

5. CQRS (Command Query Responsibility Segregation)

┌─────────────┐      ┌─────────────┐
│  Commands   │      │   Queries   │
│  (Write)    │      │   (Read)    │
└──────┬──────┘      └──────┬──────┘
       │                    │
       ▼                    ▼
  Write Model          Read Model
       │                    │
       └────────┬───────────┘
                ▼
           Event Store

Use when: Different read/write scaling, complex domains, event sourcing

Directory Structure Patterns

Feature-Based (Recommended for medium+)

src/
├── features/
│   ├── users/
│   │   ├── api/
│   │   ├── components/
│   │   ├── hooks/
│   │   ├── services/
│   │   └── types/
│   └── orders/
│       ├── api/
│       ├── components/
│       └── ...
├── shared/
│   ├── components/
│   ├── hooks/
│   └── utils/
└── app/
    └── ...

Layer-Based (Simple apps)

src/
├── controllers/
├── services/
├── models/
├── repositories/
└── utils/

Decision Framework

When making architectural decisions, evaluate against these criteria:

Simplicity - Start simple, evolve when needed
Team Skills - Match architecture to team capabilities
Requirements - Let business needs drive decisions
Scalability - Consider growth trajectory
Maintainability - Optimize for change

Trade-off Analysis Template

Use this template to document architectural decisions:

markdown

## Decision: [What we're deciding]

### Context

[Why this decision is needed now]

### Options Considered

1. Option A: [Description]
2. Option B: [Description]

### Trade-offs

| Criteria         | Option A | Option B |
| ---------------- | -------- | -------- |
| Complexity       | Low      | High     |
| Scalability      | Medium   | High     |
| Team familiarity | High     | Low      |

### Decision

We chose [Option] because [reasoning].

### Consequences

- [What this enables]
- [What this constrains]

Validation Checklist

After selecting an architecture, validate against:

Architecture Validation:
- [ ] Matches project size and complexity
- [ ] Aligns with team skills and experience
- [ ] Supports current requirements
- [ ] Allows for anticipated growth
- [ ] Dependencies flow inward (core has no external deps)
- [ ] Clear boundaries between modules/layers
- [ ] Testing strategy is feasible
- [ ] Trade-offs are documented

If validation fails, reconsider the pattern selection or adjust the implementation approach.

Files

Just SKILL.md in skills/designing-architecture of CloudAI-X/claude-workflow-v2.

Open the folder on GitHubat commit 3b5a89e

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in CloudAI-X/claude-workflow-v2, which our catalogue first saw on October 7, 2026.

aiskillstore/marketplaceskills/cloudai-x/designing-architecture

Compare with similar skills

Designing Architecture next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Designing Architecture compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Designing Architecture this skillCloudAI-X/claude-workflow-v2	1.4k	1 repos	~1.4k	Automated safety check: Pass	MIT	3 days ago
Evolutionary Modular Architecturetech-leads-club/agent-skills	7k	—	~3.7k	Automated safety check: Pass	CC-BY-4.0	yesterday
Architect ReviewAratKruglik/claude-laravel	155	8 repos	~2.2k	Automated safety check: Pass	None	5 mo ago
Architecturemanagedcode/dotnet-skills	486	—	~659	Automated safety check: Pass	MIT	today
NestJS Modular Monolith Architecttech-leads-club/agent-skills	7k	—	~3.9k	Automated safety check: Pass	CC-BY-4.0	yesterday
Microservices ArchitectJeffallan/claude-skills	12k	—	~1.8k	Automated safety check: Pass	MIT	6 days ago

Similar skills

Evolutionary Modular Architecture
tech-leads-club/agent-skills
Guides design of modular-monolith platforms with DDD, flat-by-aggregate modules, anti-corruption layers, outbox events and resilience, plus an architecture document with SVG diagrams.
7k GitHub stars~3.7k tokensUpdated yesterday
DevelopmentAuto-check passed
Architect Review
AratKruglik/claude-laravel
Master software architect specializing in modern architecture patterns, clean architecture, microservices, event-driven systems, and DDD.
155 GitHub starsUsed in 8 repos~2.2k tokens
DevelopmentAuto-check passed
Architecture
managedcode/dotnet-skills
Design or review .NET solution architecture across modular monoliths, clean architecture, vertical slices, microservices, DDD, CQRS, and cloud-native boundaries without over-engineering.
486 GitHub stars~659 tokensUpdated today
DevelopmentAuto-check passed
NestJS Modular Monolith Architect
tech-leads-club/agent-skills
Designs scalable NestJS modular monoliths with domain-driven design, Clean Architecture layers and optional CQRS, defining bounded contexts and strict module boundaries.
7k GitHub stars~3.9k tokensUpdated yesterday
Backend & APIsAuto-check passed
Microservices Architect
Jeffallan/claude-skills
Designs distributed systems: bounded-context service boundaries, sync and async communication, data ownership, resilience, tracing and rollout strategy.
12k GitHub stars~1.8k tokensUpdated 6 days ago
Backend & APIsAuto-check passed
Architecture Selection
rsmdt/the-startup
System architecture patterns including monolith, microservices, event-driven, and serverless, with C4 modeling, scalability strategies, and technology selection criteria.
557 GitHub stars~1.2k tokensUpdated 2 mo ago
Backend & APIsAuto-check passed

Questions about Designing Architecture

What does Designing Architecture do?

Designs software architecture and selects appropriate patterns for projects. Designing Architecture is an agent skill from CloudAI-X/claude-workflow-v2. Designs software architecture and selects appropriate patterns for projects.

When should I use Designing Architecture?

Designing Architecture fits situations like: designing systems; choosing architecture patterns; structuring projects; making technical decisions.

How do I install Designing Architecture in Claude Code?

Run `npx skills add CloudAI-X/claude-workflow-v2 --skill designing-architecture -a claude-code`. Or copy the skill folder (skills/designing-architecture in CloudAI-X/claude-workflow-v2) into .claude/skills/designing-architecture in your project. Claude Code loads it when a task matches its description.

How do I install Designing Architecture in Codex?

Run `npx skills add CloudAI-X/claude-workflow-v2 --skill designing-architecture -a codex`. Or copy the skill folder (skills/designing-architecture in CloudAI-X/claude-workflow-v2) into .agents/skills/designing-architecture in your project. Codex loads it when a task matches its description.

Can I use Designing Architecture in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add CloudAI-X/claude-workflow-v2 --skill designing-architecture -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/designing-architecture, .gemini/skills/designing-architecture, .github/skills/designing-architecture and .opencode/skills/designing-architecture in your project.

What does Designing Architecture need to run?

SKILL.md names no scripts, command-line tools or credentials: Designing Architecture is instructions for the agent only.

Does Designing Architecture access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Designing Architecture safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Designing Architecture use?

Designing Architecture is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Designing Architecture use?

About 1.4k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Designing Architecture?

Skills that share tags, products or a category with Designing Architecture: Evolutionary Modular Architecture (tech-leads-club/agent-skills, 7k stars), Architect Review (AratKruglik/claude-laravel, 155 stars), Architecture (managedcode/dotnet-skills, 486 stars) and NestJS Modular Monolith Architect (tech-leads-club/agent-skills, 7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Designing Architecture?

CloudAI-X (a GitHub user) maintains it in CloudAI-X/claude-workflow-v2, which has 1,418 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 6, 2026.

Source: CloudAI-X/claude-workflow-v2 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Designing Architecture

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Designing Architecture

When to Load

Architecture Decision Workflow

Pattern Selection Guide

By Project Size

By Team Size

Common Patterns

1. Layered Architecture

2. Clean Architecture

3. Hexagonal (Ports & Adapters)

4. Event-Driven Architecture

5. CQRS (Command Query Responsibility Segregation)

Directory Structure Patterns

Feature-Based (Recommended for medium+)

Layer-Based (Simple apps)

Decision Framework

Trade-off Analysis Template

Validation Checklist

Files

Used in 1 other repository

Compare with similar skills

Similar skills

More from CloudAI-X/claude-workflow-v2

Related

Questions about Designing Architecture