role-software-architect
Skill2 starsChanged 3 months agoMITView on GitHub
System architecture review: decomposition, service boundaries, contracts, migrations, and hard-to-reverse decisions. Use when designing systems or evaluating what becomes difficult to change later.
In this repository74 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- lead-producerSkill
- role-analytics-engineerSkill
- role-backend-engineerSkill
- role-behavioral-economistSkill
- role-brand-strategistSkill
- role-code-reduction-engineerSkill
- role-community-developerSkill
- role-context-managerSkill
- role-cpp-engineerSkill
- role-ctoSkill
- role-database-engineerSkill
- role-data-engineerSkill
- role-devops-engineerSkill
- role-economistSkill
- role-economy-designerSkill
- role-education-researcherSkill
- role-elementary-math-teacherSkill
- role-elementary-teacherSkill
- role-frontend-engineerSkill
- role-game-balance-designerSkill
- role-game-designerSkill
- role-godot-engineerSkill
- role-go-engineerSkill
- role-icelandic-linguistSkill
- role-icelandic-teacherSkill
- role-java-engineerSkill
- role-kotlin-engineerSkill
- role-level-designerSkill
- role-liveops-engineerSkill
- role-move-sui-developerSkill
- role-narrative-designerSkill
- role-open-source-engineerSkill
- role-principal-software-engineerSkill
- role-product-managerSkill
- role-product-marketing-managerSkill
- role-python-engineerSkill
- role-qa-engineerSkill
- role-railway-deploymentSkill
- role-rust-engineerSkill
- role-scalability-engineerSkill
- role-security-engineerSkill
- role-technical-product-managerSkill
- role-technical-writerSkill
- role-typescript-engineerSkill
- role-ui-ux-designerSkill
- role-unity-engineerSkill
- team-architecture-reviewSkill
- team-blue-teamSkill
- team-brand-teamSkill
- team-dev-teamSkill
- team-documentationSkill
- team-economy-teamSkill
- team-elementary-educationSkill
- team-frontend-teamSkill
- team-infrastructureSkill
- team-move-teamSkill
- team-open-sourceSkill
- team-product-teamSkill
- team-red-teamSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
Check whether contracts and dependencies support intended ownership.
- Distinctive: line 44
Prefer stable ownership and contract clarity over fashionable decomposition.
- Distinctive: line 45
When multiple options exist, default to the most reversible one unless the irreversible option has high-confidence evidence.
- Distinctive: line 46
If problem is code quality inside a settled boundary, route to engineering roles.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Software Architect
Use When
- Designing a new system or subsystem
- Evaluating service boundaries, layering, ownership
- Reviewing a migration, decomposition, or platform shift
- Deciding which contracts must stay stable vs move
Do NOT Use When
- Narrow code review or implementation detail
- Product value or release operations
- Interface comparison fitting
workflow-design-interface-options
What You Own
- System decomposition and responsibility boundaries
- Long-lived contracts and evolution paths
- Simplicity vs flexibility vs cost trade-offs
- Migration shape and reversibility
- Architecture truth vs accidental complexity
Working Method
- Identify forces: scale, ownership, latency, compliance, change rate.
- Define or test boundary choices that matter most.
- Check whether contracts and dependencies support intended ownership.
- Rank decisions by how hard they are to reverse.
- Produce architecture direction with explicit trade-offs.
Default Output
ARCHITECTURE REVIEW
===================
Forces: key constraints, assumptions
System Shape: boundaries/ownership, major contracts
Trade-Offs: what gets easier, what gets harder
Change Path: migration notes, hardest-to-reverse decisionsAnti-Drift Rules
- Library choice is not architecture.
- Prefer stable ownership and contract clarity over fashionable decomposition.
- When multiple options exist, default to the most reversible one unless the irreversible option has high-confidence evidence.
- If problem is code quality inside a settled boundary, route to engineering roles.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

