← ClaudeAtlas

load-bearinglisted

Design a system's architecture for the agent-assisted era: choose the architecture style, the stack, the module boundaries, the contracts, and the data model — concentrating scarce human judgment on the irreversible decisions and letting agents move fast behind the reversible ones. Use when the user is designing or restructuring a system, choosing between monolith and microservices, picking a tech stack or database, defining APIs or module boundaries, deciding how to realize non-functional requirements (scale, availability, security), writing an ADR, or about to build something structurally non-trivial. Triggers on "design the architecture", "what stack should I use", "monolith or microservices", "how should I structure this", "design the data model / API", "system design".
IamK77/Skill · ★ 1 · AI & Automation · score 77
Install: claude install-skill IamK77/Skill
<!-- Copyright 2026 IamK77 — Licensed under the Apache License, Version 2.0. See ./LICENSE and ./NOTICE · https://www.apache.org/licenses/LICENSE-2.0 --> # load-bearing !`checklist init ${CLAUDE_SKILL_DIR} --force` Architecture is the set of decisions that are **expensive to reverse**. That definition is the whole skill — and it is exactly what the agent-assisted era changes the calculus of. When an agent (or a fleet of them) writes the code, the cost of *reversible* decisions — how the internal code is organized, which library you reached for, even a full rewrite — collapses toward zero. The cost of *irreversible* decisions — a production data schema, a public contract others depend on, the trust/security model, the line where you split into separate deployables — does **not** budge. Agents make code cheap to change; they do not make data migrations, broken API contracts, or breaches cheap. So the master move of this skill is a triage: **spend your scarce human judgment on the one-way doors, and let agents move fast and refactor freely behind the two-way doors.** Most of the classic "decide it carefully up front" advice was written when *all* code was expensive to change. Half of it now applies only to the durable layer. **Speak the owner's language, or the one-way door isn't theirs.** This skill works by spending the user's judgment where you cannot reverse it — validating an inherited decision, approving or vetoing an ADR — and they can only judge a decision they foll