solution-architecture
Skill0 starsChanged 8 days agoApache-2.0View on GitHub
Produce and review Solution Architect (SA) artifacts for Solo Empire systems — context and container architecture, tech-stack and ADR decisions, NFR targets, security and data boundaries, API and data-model TRDs, sequence diagrams, deployment topology, migration plans, and runbooks. Use when designing or documenting how a system is built, deployed, scaled, secured, or migrated, or when a docpack needs architecture, nfr-security, runbook, or trd-api-data documents.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- hangljoe/AI-PreSales-Skillstheir own version, first seen Sep 28, 2026
- chinthakat/agent-skillstheir own version, first seen Sep 21, 2026
- gootf/software-agent-soptheir own version, first seen Aug 30, 2026
- SuShuheng/making-thingstheir own version, first seen Jul 16, 2026
- patonkikh/APEStheir own version, first seen Jul 3, 2026
- xmllint/sre-project-pipeline-skillstheir own version, first seen Jun 5, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- patonkikh/APES★ 3same name
- gootf/software-agent-sop★ 2same name
- hangljoe/AI-PreSales-Skills★ 1same name
- SuShuheng/making-things★ 1same name
- chinthakat/agent-skills★ 0same name
- xmllint/sre-project-pipeline-skills★ 0same name
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 repository27 other files it gives its agents.
- ai-agentsSkill
- ai-agent-workflowsSkill
- ai-native-estimationSkill
- ai-product-deliverySkill
- book-dev-engineering-loopSkill
- business-analysisSkill
- client-discovery-and-proposalsSkill
- content-distributionSkill
- data-engineeringSkill
- flow-videoSkill
- game-engineeringSkill
- govern-ai-skillsSkill
- graphic-designSkill
- lead-research-and-crmSkill
- main-only-developmentSkill
- product-managementSkill
- product-ownerSkill
- project-managementSkill
- qa-testingSkill
- security-and-privacySkill
- skill-templateSkill
- solo-empire-operatorSkill
- subagent-orchestrationSkill
- system-docpackSkill
- unused-file-cleanupSkill
- ux-reviewSkill
- xr-engineeringSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
1
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 31
Write the runbook: environments, build/deploy, variable names, health checks, rollback, backup/restore, incident steps.
“Common” is measured: kept by at least 6 in 10 of the 6 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
Solution Architecture
Turn requirements and existing code into a defensible, evidence-backed architecture that delivery, operations, and the client can act on.
Workflow
- Read
dashboard/CURRENT-STATE.md,docs/ARCHITECTURE.md,systems/architecture/repository-boundaries.md, and the system's rows inrepository-catalog/registries/runtime-boundaries.yamlandservice-deployments.yaml. - Inventory the as-built system from code: entry points, routes/controllers, models and migrations, integrations, config variable names, build and deploy files (Dockerfile, railway.toml, vercel.json, CI).
- Model it: context diagram, containers/components, data stores, trust boundaries, deployment topology (mermaid flowchart/sequence/erDiagram).
- Record decisions as ADR-xx (context, options, decision, consequences) using
templates/development-cycle/system-architecture-decision.mdwhen a standalone record is needed. - Set measurable NFR-xx targets (latency, availability, RPO/RTO, capacity,
security controls, observability) with
templates/development-cycle/non-functional-requirements.md; unknown targets become owner questions, not guesses. - For APIs and data, produce the TRD: endpoint table (method, path, auth,
purpose), entity/ER model, integration contracts — see
templates/development-cycle/api-contract.mdandtechnical-design.md. - Write the runbook: environments, build/deploy, variable names, health checks, rollback, backup/restore, incident steps.
- Review with
templates/positions/solution-architect/architecture-review-record.mdand hand security/privacy questions tosecurity-and-privacy.
Decision rules
- Describe the as-built system first; label target or proposed designs [สมมติฐาน] until approved.
- Hosting follows the recorded decision (Railway primary PaaS, Vercel for frontends) unless a client contract says otherwise; never invent a target.
- Secrets: variable names only, never values or provider IDs that grant access.
- Production changes, migrations, spending, or provider switches → explicit owner approval before acting; documents only describe the plan.
Handoff
Report diagrams and ADRs produced, NFR targets with their source, open architecture questions, risks (R-xx), and the verification run.
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.