Individual skill
software-architect
Use when the user is deciding, reviewing, or second-guessing a software architecture or tech-stack choice — monolith vs microservices vs serverless vs event-driven, backend language, database type, caching, CQRS/event sourcing, polyglot, or a migration like Strangler Fig. Triggers on "should I use microservices", "which database", "tech stack for", "system design", or "architecture review". For how to deploy, operate, and scale that design (CI/CD, cloud, Kubernetes, IaC), use devops.
software-architect/SKILL.md
Source commit d4d207119b9affb3cd653805c9807598841e90f2
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 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)
- 44
- Repository last updated
- Jul 2, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- anthropic Repository topic
- claude-code Repository topic
- copywriting Repository topic
- devops Repository topic
- gtm Repository topic
- marketing Repository topic
- product-management Repository topic
- prompt-engineering Repository topic
- sales Repository topic
- skill-md Repository topic
- devops Derived category
- engineering Derived category
- design Derived category
- data Derived category
- data-databases Derived category
- devops-containers 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 · 3,849 bytesreferences/architectural-styles.mddoc · 5,184 bytesreferences/backend-runtimes.mddoc · 4,240 bytesreferences/data-layer.mddoc · 6,633 bytes
Read excerpt
# Software Architect
An evidence-based decision framework for software architecture and technology selection. Grounded in practitioner literature, not hype cycles.
## Output discipline
Deliver only what the user will actually use. Never leak internal scaffolding into the output:
- No reference citations the reader can't see ("§3.2", "per the knowledge base", "KB §1.4").
- No mode or process narration ("Mode: Generate", "I have everything I need", "following the skill's methodology").
- No skill-handoff chatter inside the deliverable.
Apply frameworks silently — name one only when it helps the reader, not to show your work. When context is missing, state your assumption in one line and proceed; don't interrogate.
## Core Principles