architecting-systems

architecting-systems is a skill for Claude Code from rileyhilliard/claude-essentials. It costs 43 tokens per session (587 once invoked), scanned A, original, MIT.

A guide for designing the structure of software systems as they grow, including modules, boundaries, dependencies, asynchronous work, and operational visibility.

In plain words
What is it for?
Use it when organizing files and modules, defining interfaces and domain boundaries, separating responsibilities, designing concurrent workflows, or adding logging, health checks, metrics, and tracing.
Why use it?
It helps prevent tightly coupled code and unclear ownership from making future changes difficult. The guidance also helps control the complexity introduced by architectural decisions.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the ce plugin — 17 skills, 1 command, 4 agents shipped together

Good fit Use it when organizing files and modules, defining interfaces and domain boundaries, separating responsibilities, designing concurrent workflows, or adding logging, health checks, metrics, and tracing.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rileyhilliard/claude-essentials/architecting-systems
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.

Any agent
npx skills add rileyhilliard/claude-essentials --skill architecting-systems
Clone the repo
git clone --depth 1 https://github.com/rileyhilliard/claude-essentials

Made for: Claude Code.

Or install ce, the plugin that ships this one along with the rest of its 17 skills, 1 command, 4 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for architecting-systems

README.md
[![agentmods](https://agentmods.dev/badge/skills/rileyhilliard/claude-essentials/architecting-systems/github.svg)](https://agentmods.dev/skills/rileyhilliard/claude-essentials/architecting-systems)
Your own site
<a href="https://agentmods.dev/skills/rileyhilliard/claude-essentials/architecting-systems"><img src="https://agentmods.dev/badge/skills/rileyhilliard/claude-essentials/architecting-systems/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for architecting-systems

Your own site · 80×15
<a href="https://agentmods.dev/skills/rileyhilliard/claude-essentials/architecting-systems"><img src="https://agentmods.dev/badge/skills/rileyhilliard/claude-essentials/architecting-systems.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 587 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00043 $0.00587
Opus 5 $0.00022 $0.00293
Sonnet 5 $0.00009 $0.00117
Haiku 4.5 $0.00004 $0.00059

Measured 9d ago against content hash 7353e87a8027, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

architecting-systems 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 9d 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.

plugins/ce/skills/architecting-systems/SKILL.md · 56 lines

How it starts

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

Architecting Systems

Core principle: Small decisions made early compound into either clean systems or massive technical debt. Get the structure right and the system stays maintainable as it grows. Get it wrong and every change gets harder.

Topic Selection

Load the relevant reference based on what you're working on:

Working on... Load File
Layers, vertical slices, file organization Structure references/structure.md
Interfaces, dependency inversion, contracts Coupling references/coupling.md
Bounded contexts, API design, module boundaries Boundaries references/boundaries.md
Async patterns, race conditions, queues Concurrency references/concurrency.md
Logging, health checks, metrics, tracing Observability references/observability.md

Load multiple references when the task spans topics. For most greenfield work, start with Structure and Coupling.


Core Principles (All Topics)

Complexity budget

Every architectural decision has a complexity cost. Spend that budget where it matters.

Worth the complexity Not worth it
Separation between domains that change independently Abstracting code that only has one implementation
Event-driven for genuinely async workflows Event-driven for simple request-response flows
Caching for measured performance bottlenecks Caching "just in case"
Microservices for teams that deploy independently Microservices for a small team's monolith

The rule: Don't add indirection until you need it. Premature abstraction is as costly as premature optimization. Two similar code blocks are better than a wrong abstraction.


Quick Reference

Problem Response
"Where does this code go?" If the answer isn't obvious, the structure needs work
"Changing X requires touching Y" Missing boundary between X and Y
"This module does too many things" Split along separate reasons to change
"We can't test this in isolation" Hidden dependencies; inject them instead
"New devs take weeks to be productive" Conventions are too weak or too novel
"Every PR touches 10 files" Feature code is scattered; colocate it
"The shared folder keeps growing" Boundaries are in the wrong place

Read the full file on GitHub · 56 lines

Files

What ships with it

5 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. 9d ago First seen · 56 lines · 43 tokens per session scan A 7353e87a8027

Subscribe to this mod's changes

architecting-systems is a skill published in the GitHub repository rileyhilliard/claude-essentials (128 stars, last pushed 21d ago), licensed MIT. It adds 43 tokens to every session and 587 once invoked, about $0.0002 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-30.

Related

Other skills, from other repositories

mem0-oss-to-platform

Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…

mem0ai/mem0 · 273 tokens

agui-dotnet-protobuf

Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…

ag-ui-protocol/ag-ui · 162 tokens

azure-mgmt-botservice-dotnet

Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".

microsoft/skills · 78 tokens

fastapi-router-py

Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.

microsoft/skills · 46 tokens

migrate-segw-to-rap

Reverse-engineer a SEGW-built OData V2 service (MPC/DPC/MPCEXT/DPCEXT) into a modern RAP V4 service — tables, CDS views (interface + projection), behavior definitions, draft entities, service definition + binding. Use when asked to "migrate this SEGW service to RAP", "convert OData V2 to V4 RAP", "modernize this…

arc-mcp/arc-1 · 106 tokens

telnyx-messaging-hosted-curl

Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.

team-telnyx/ai · 45 tokens