sickn33/agentic-awesome-skills / plugins/aasb-architecture-design/skills/senior-architect
senior-architect
VerifiedPlan and review system architecture using explicit requirements, tradeoffs and evidence; bundled scripts are incomplete stubs.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.4 KB |
| references/architecture_patterns.md | markdown | 1.3 KB |
| references/system_design_workflows.md | markdown | 1.1 KB |
| references/tech_decision_guide.md | markdown | 1014 B |
| scripts/architecture_diagram_generator.py | script | 1.9 KB |
| scripts/dependency_analyzer.py | script | 1.9 KB |
| scripts/project_architect.py | script | 1.9 KB |
references/architecture_patterns.md
View on GitHub# Architecture pattern selection
Start with the current simple design. Patterns are alternatives, not a maturity ladder.
| Candidate | Useful when | Cost/failure to examine |
| --- | --- | --- |
| Modular monolith | Shared transactions and a small team dominate | Internal module coupling and release coordination |
| Independent service | Ownership/scaling/failure isolation has evidence | Network failures, consistency and operational load |
| Queue worker | Work exceeds request budget or needs controlled concurrency | Duplicate delivery, idempotency, retries, DLQ and visibility |
| Cache | Repeat reads and acceptable freshness are measured | Tenant keys, invalidation, stale values and stampedes |
| Read projection | Read shape differs materially from transactional writes | Rebuilds, lag, schema versions and source-of-truth recovery |
Record the actual flow, data owner and trust boundary. For a queue, show producer → durable broker → authorized consumer → output, plus retry/dead-letter and deduplication paths. For a cache, define scope, TTL, version and authoritative fallback. A diagram does not implement those guarantees.
Validate with a workload and failure scenario that can distinguish options, then capture the evidence in a decision record. Do not infer production capacity from a conceptual pattern.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |