architecture-design

A set of guidelines for planning a software system’s structure, data, security, and performance. It favors simple, loosely connected parts and explains common designs such as Clean Architecture and event-driven systems.

In plain words
What is it for?
Use it when designing a new system, defining its database tables and relationships, planning migrations, choosing components, or documenting architectural decisions.
Why use it?
It helps prevent overcomplicated designs, unclear boundaries, and data or security problems that are expensive to fix later.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/matrixfounder/agentic-development/architecture-design
Any agent
npx skills add MatrixFounder/Agentic-development --skill architecture-design
Clone the repo
git clone --depth 1 https://github.com/MatrixFounder/Agentic-development

Made for: Claude Code, Codex.

Per session 13 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 562 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00013 $0.00562
Opus 5 $0.00006 $0.00281
Sonnet 5 $0.00003 $0.00112
Haiku 4.5 $0.00001 $0.00056

Measured 2d ago against content hash 60718c6bbf39, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

architecture-design scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agent/skills/architecture-design/SKILL.md · 69 lines

How it starts

The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Architecture Design

1. Core Principles

Simplicity Above All

  • Goal: Solve the task maximally simply.
  • Avoid Overengineering: Complex architecture and heavy libraries complicate maintenance.
  • Zero-Dependency: Add only truly necessary components.
  • No-ORM Preference: Do not use ORM if simple SQL queries are easier.
  • Frameworks: Do not use frameworks if API is easier on lower-level libraries.

Modularity

  • Loose coupling, high cohesion.
  • Clear interface definitions between components.

Common Patterns

If building a complex system, refer to these standard patterns:

  • Clean Architecture: references/clean_architecture.md (Layers, Dependency Rule).
  • Event-Driven: references/event_driven.md (Async, Brokers, Idempotency).

2. Requirements for Architecture Components

Data Model

  1. Design Detailedly:
    • All entities, attributes with types.
    • All relationships (1:1, 1:N, M:N).
    • All constraints and indexes.
  2. Think about Migrations:
    • How data will migrate with changes.
    • Backward compatibility.
  3. Consider Performance:
    • Frequent queries -> Indexes.
    • Denormalization if necessary.

Security

  • Built-in: Security must be designed, not patched.
  • Auth: OAuth2/JWT/Session strategies defined.
  • Protection: OWASP Top 10 consideration.

Scalability

  • Horizontal: Stateless services.
  • Database: Partitioning, Replication strategies.

3. Important Rules

✅ DO:

  1. Base on TASK: Justify every decision by requirements from TASK.
  2. Consider Existing: Structure new components to fit existing patterns.
  3. Be Specific: Indicate specific technologies (e.g., "PostgreSQL 14"), not just "SQL DB".
  4. Link to Use Cases: Map components to the UC they fulfill.

❌ DO NOT:

  1. Write Code: You design architecture, not implementation.
  2. Ignore Legacy: Study existing project before designing.
  3. Leave Decisions for Later: Key technologies must be selected now.
  4. Accumulate Debt: If refactoring is needed, record it.

Read the full file on GitHub · 69 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 69 lines · 13 tokens per session scan A 60718c6bbf39

Subscribe to this mod's changes

architecture-design is a skill published in the GitHub repository MatrixFounder/Agentic-development (5 stars, last pushed 20d ago), licensed Apache-2.0. It adds 13 tokens to every session and 562 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

batch

Execute batch operations on multiple files in parallel. Automatically discovers files, splits into chunks, and processes with parallel worker agents. Use /batch followed by operation and file pattern.

QwenLM/qwen-code · 37 tokens

extension-creator

Create, scaffold, customize, validate, and locally test Qwen Code extensions. Use when the user wants a new Qwen Code extension, needs help choosing an extension template, wants to add QWEN.md context, commands, skills, agents, MCP servers, settings, hooks, channels, or LSP servers, or asks how to link and test an…

QwenLM/qwen-code · 96 tokens

notion

Notion API for creating and managing pages, databases, and blocks. Use when the user wants to create a Notion page, query a Notion database, update Notion properties, search Notion, add content to Notion, manage Notion blocks, or interact with Notion data sources and workspaces via the API.

elizaOS/eliza · 69 tokens

pr-feedback

Fetches PR review feedback and inline comments, categorizes them, and presents options to the user. Use when the user asks to get, read, address, or fix review comments on a pull request.

strands-agents/harness-sdk · 44 tokens

argent-native-profiler

Native profiling for CPU hotspots, UI hangs, memory issues. iOS via xctrace; Android via Perfetto. Use when diagnosing native-level performance issues.

software-mansion/argent · 37 tokens

argent-tv-interact

Control and inspect TV apps via argent — Apple TV (tvOS), Android TV (leanback), and Amazon Fire TV (Vega). Boot the target, read focus, navigate with the D-pad remote, type, screenshot, and on Vega debug the JS runtime (evaluate, console logs, network inspector). Use when a task targets a TV (runtimeKind "tv", or…

software-mansion/argent · 107 tokens