How do I install the Architecture skill?

Run npx skillmds@latest add sahilkhan30/architecture in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Architecture safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Architecture?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Architecture free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Architecture?

SahilKhan30 (@sahilkhan30) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Architecture by sahilkhan30 — Agent Skill

Name: Architecture
Author: SahilKhan30

File contents

Architecture & System Design Skill

Purpose

Standardize architectural reasoning, assumption extraction, ADR creation, and trade-off tracking for financial platform development.

1. Guideline Classification & Rules

MANDATORY

Entry Point: Read docs/project-status.md first before designing architecture.
Decision Budget: Limit initial HLD/LLD design to max 5–7 core ADRs in docs/decisions.md to prevent analysis paralysis.
Record explicit assumptions in docs/assumptions.md (AS-xxx) with impact ratings (LOW, MEDIUM, HIGH, CRITICAL).

STARTING HYPOTHESIS & CONDITIONAL PATTERNS

Modular Monolith Starting Hypothesis: Modular Monolith is a starting hypothesis to evaluate against scale, deployment independence, and isolation constraints rather than a default decision.
Asynchronous Workers: Evaluate async processing (@Async, Spring Events, messaging) when high throughput or latency isolation is justified by requirements/assumptions.

2. Ambiguity Escalation Levels

Level 1 (Low): Minor detail -> Make explicit assumption (AS-xxx) in docs/assumptions.md and proceed.
Level 2 (Medium): Technical/API choice -> Make assumption (AS-xxx), record decision (DEC-xxx), proceed.
Level 3 (High / Critical): Major business rule or architectural fork -> Record AS-xxx with HIGH/CRITICAL impact, STOP & prompt user immediately.

3. ADR Template (`docs/decisions.md`)

### DEC-xxx: [Decision Title]
- **Status**: Accepted
- **Context**: [Problem requirement REQ-xxx or constraint driving this decision]
- **Options Evaluated**:
  1. [Option A] - [Pros / Cons]
  2. [Option B] - [Pros / Cons]
- **Chosen Option & Rationale**: [Justification for choice]
- **Trade-offs & Risks**: [Consequences and operational trade-offs accepted]
- **Related Assumptions**: [AS-xxx]

---name: architecturedescription: Use when designing system architecture, extracting assumptions, creating ADRs, establishing domain boundaries, and mapping requirements to design choices.---# Architecture & System Design Skill## PurposeStandardize architectural reasoning, assumption extraction, ADR creation, and trade-off tracking for financial platform development.---## 1. Guideline Classification & Rules### MANDATORY- **Entry Point**: Read `docs/project-status.md` first before designing architecture.- **Decision Budget**: Limit initial HLD/LLD design to **max 5–7 core ADRs** in `docs/decisions.md` to prevent analysis paralysis.- Record explicit assumptions in `docs/assumptions.md` (`AS-xxx`) with impact ratings (`LOW`, `MEDIUM`, `HIGH`, `CRITICAL`).### STARTING HYPOTHESIS & CONDITIONAL PATTERNS- **Modular Monolith Starting Hypothesis**: Modular Monolith is a starting hypothesis to evaluate against scale, deployment independence, and isolation constraints rather than a default decision.- **Asynchronous Workers**: Evaluate async processing (`@Async`, Spring Events, messaging) when high throughput or latency isolation is justified by requirements/assumptions.---## 2. Ambiguity Escalation Levels- **Level 1 (Low)**: Minor detail -> Make explicit assumption (`AS-xxx`) in `docs/assumptions.md` and proceed.- **Level 2 (Medium)**: Technical/API choice -> Make assumption (`AS-xxx`), record decision (`DEC-xxx`), proceed.- **Level 3 (High / Critical)**: Major business rule or architectural fork -> Record `AS-xxx` with `HIGH`/`CRITICAL` impact, **STOP & prompt user immediately**.---## 3. ADR Template (`docs/decisions.md`)```markdown### DEC-xxx: [Decision Title]- **Status**: Accepted- **Context**: [Problem requirement REQ-xxx or constraint driving this decision]- **Options Evaluated**: 1. [Option A] - [Pros / Cons] 2. [Option B] - [Pros / Cons]- **Chosen Option & Rationale**: [Justification for choice]- **Trade-offs & Risks**: [Consequences and operational trade-offs accepted]- **Related Assumptions**: [AS-xxx]```

Frequently asked questions

Architecture