Individual skill
architecture-first
Decide module boundaries before the first file: what modules exist, which way dependencies point, who owns state, and what each module may know. Use when starting a project, service, site, API, or subsystem; adding a feature with no obvious home; resolving a circular import or inverted framework dependency; or writing an ARCHITECTURE.md or ADR. Do not use for a one-file script, throwaway experiment, bug fix inside an established seam, naming/function-shape cleanup (use code-complexity), an existing oversized module (use refactoring-safely), or capacity/data scaling decisions (use system-and-data-design). This defines earned boundaries; it does not license speculative layers.
skills/development/architecture-first/SKILL.md
Source commit 849719987d9c0d6ed973bdbce8ed37b266d3b1f3
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 7, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 214
- Repository last updated
- Nov 7, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- claude Repository topic
- claude-code Repository topic
- llm Repository topic
- machine-learning Repository topic
- prompt-engineering Repository topic
- skills Repository topic
- mcp Repository topic
- agent-harness Repository topic
- harness Repository topic
- engineering Derived category
- design Derived category
- writing Derived category
- data Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 8,036 bytesSKILL.mdcore · 8,036 bytesreferences/clean-architecture-original.mddoc · 13,599 bytesreferences/clean-architecture/boundaries-and-layers.mddoc · 54,535 bytesreferences/clean-architecture/details-and-code-organization.mddoc · 46,033 bytesreferences/clean-architecture/python-implementation.mddoc · 69,710 bytesreferences/clean-architecture/solid-and-components.mddoc · 47,862 bytesreferences/domain-driven-design-original.mddoc · 19,122 bytesreferences/domain-driven-design/bounded-contexts.mddoc · 13,416 bytesreferences/domain-driven-design/building-blocks.mddoc · 13,401 bytesreferences/domain-driven-design/domain-events.mddoc · 12,063 bytesreferences/domain-driven-design/repositories-factories.mddoc · 15,387 bytesreferences/domain-driven-design/strategic-design.mddoc · 14,536 bytesreferences/domain-driven-design/ubiquitous-language.mddoc · 12,660 bytes
Read excerpt
# Architecture first — the shape before the first file
Most bad structure is not a bad decision. It is an absent one: code goes where the
smallest diff puts it, and the smallest diff is always "next to the last thing". This
skill exists to make the layout an explicit, cheap, early decision.
## Scope guard — read first
Match the ceremony to the problem. Over-applying this is its own failure mode.
| Situation | What this skill asks of you |
|---|---|
| Script, spike, one file, throwaway | Nothing. Skip. |
| One module, <500 lines, one reason to change | Name the module and its one job. Stop. |