software-architect
Skill0 starsChanged 24 days agoMITView on GitHub
Design or review software architecture, bounded contexts, dependencies, ADRs, failure modes and compatibility across services. Use for consequential system changes.
16 other projects use a version of this.
Adopted by
Most recently taken up by
- JuankCadavid/akili-specstheir own version, first seen Nov 2, 2026
- paulopestanajunior/agents-configtheir own version, first seen Oct 15, 2026
- wonderslife/pdd-skills-v3their own version, first seen Oct 13, 2026
- beelabstudio/aitheir own version, first seen Sep 20, 2026
- poorvith-mp/skills-developertheir own version, first seen Aug 19, 2026
- darker2016/WorkbuddySkillGroups4DSHtheir own version, first seen Aug 14, 2026
Used with
Projects with it also use software-engineer and code-review.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
nek1987Skillsoftware-engineer
Builds and refactors code safely; prefers small diffs, clear validation steps, and testable outcomes.
Also in 3 projects that use this
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 3 projects that use this
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- wonderslife/pdd-skills★ 41same name
- firatcand/founder-skills★ 37same name
- Hassaan146/claude-skills★ 18same name
- jshearin01/agent-skills★ 16same name
- wonderslife/pdd-skills-v3★ 15same name
- JuankCadavid/akili-specs★ 10same name
- u1pns/skills-entrepeneur★ 8same name
- darker2016/WorkbuddySkillGroups4DSH★ 6same name
- eligapris/software-architect★ 4same name
- EmersonBraun/skills★ 4same name
6 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository28 other files it gives its agents.
- agent-skill-security-auditorSkill
- backend-api-engineerSkill
- backend-debuggingSkill
- backup-disaster-recoverySkill
- code-review-prSkill
- database-transaction-integritySkill
- dependency-supply-chain-auditorSkill
- devops-ci-cdSkill
- documentation-handoverSkill
- frontend-design-directionSkill
- llm-api-integrationSkill
- load-resilience-testingSkill
- mcp-integration-builderSkill
- observability-monitoringSkill
- performance-accessibilitySkill
- playwright-webapp-testingSkill
- privacy-data-governanceSkill
- product-business-analystSkill
- project-bootstrap-environmentsSkill
- qa-release-gatekeeperSkill
- qa-test-strategySkill
- react-artifacts-builderSkill
- security-authorization-auditorSkill
- skill-authoring-toolkitSkill
- skill-evaluation-benchmarkSkill
- technical-project-orchestratorSkill
- theme-design-systemSkill
- visual-assets-designSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
3
Distinctive
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 8
Read the repository, ADRs and contracts before describing the current architecture.
- Distinctive: line 11
Consider 2-3 concrete alternatives only when a meaningful trade-off exists.
- Distinctive: line 18
Never treat a speculative improvement as an authorized rewrite.
“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Software architecture
- Read the repository, ADRs and contracts before describing the current architecture. Label unknown areas; do not invent diagrams.
- Identify functional needs and operational requirements: latency, availability, security, growth, auditability, recovery, localization and team capacity.
- Draw logical boundaries, data ownership, sync/async interactions and failure containment. Preserve existing public contracts unless explicitly approved.
- Consider 2-3 concrete alternatives only when a meaningful trade-off exists; compare complexity, operational cost, reversibility and migration risk.
- Evaluate failure modes (timeouts, duplicate requests, partial writes, unhealthy dependencies) and what the system does during degradation.
- Specify a proposed ADR: context, decision, rejected options, consequences, date and evidence.
- Sequence rollout: compatibility, feature flags when useful, migration, tests, telemetry and rollback trigger.
Handoff: data changes to database-transaction-integrity; permissions to security-authorization-auditor; release risk to qa-release-gatekeeper. Output: observed architecture, decision, affected contracts, proposed ADR, delivery slices and unanswered questions. Never treat a speculative improvement as an authorized rewrite.
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.