SKILL17architecture-engineering
Choosing Application Architecture
Derives an application architecture from quality attributes, change boundaries, operational capability, and deployment constraints instead of pattern preference.
Primary benefit
Makes architectural topology a traceable trade-off decision and avoids distributed complexity that lacks a demonstrated requirement.When to use
Use when starting or reshaping an application where deployment topology, scaling, reliability, ownership, coupling, or delivery constraints make the architectural shape unclear.
When not to use
Do not use when the change is local to one established module and does not alter system-level quality attributes, deployment shape, or ownership boundaries.
Use cases
Choose between a modular monolith and distributed services for a growing product
Reassess an existing architecture after scaling, reliability, or team ownership constraints changed
Example prompts
Use choosing-application-architecture to compare realistic architecture options for this system from its quality attributes, change boundaries, deployment needs, and operational constraints.Install this skill
Choose the command for your operating system and run it from the repository root.
Bash
./install.sh --skill choosing-application-architecturePowerShell
./install.ps1 --skill choosing-application-architectureChatGPT
Download Skill ZIPCompatibility
- Surfaces
- ChatGPT · Codex · Claude Code
- Operating systems
- Linux · macOS · Windows
- Install modes
- PluginFilesystem
Dependencies
No external dependencies
Part of systems
Curated systems that canonically include this method.
Used in evidence
Reports that explicitly list this method among the applied methods.