nhouseholder/senior-architect
.claude/skills/senior-architect/SKILL.md
Architecture audit and system design skill. When invoked, evaluates the overall architecture — service boundaries, data flow, dependency graph, tech stack choices, scalability risks. Also guides system design for new features. Use when asked to review architecture, design a system, evaluate tech stack, or plan infrastructure.
$ install --global
skillsauthnpx skillsauth add nhouseholder/nicks-claude-code-superpowers senior-architectInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 9, 2026, 3:01 AM18.9s7 files scanned
SKILL.md
- name:
- senior-architect
- description:
- Architecture audit and system design skill. When invoked, evaluates the overall architecture — service boundaries, data flow, dependency graph, tech stack choices, scalability risks. Also guides system design for new features. Use when asked to review architecture, design a system, evaluate tech stack, or plan infrastructure.
- weight:
- heavy
Senior Architect — Architecture Review & Design Protocol
When This Fires
- User says "review the architecture", "design the system", "evaluate tech stack"
- User says "is this scalable", "should we split this", "what's the right approach"
- Hook routes to this skill for architecture-related work
Architecture Audit Protocol (When Reviewing)
Step 1: Map the System
- Identify all services/layers (frontend, backend, database, cache, CDN, workers)
- Map data flow: user → frontend → API → database → response
- Identify third-party integrations (auth providers, payment, analytics)
- Check deployment target (Cloudflare, Vercel, AWS, etc.) and its constraints
Step 2: Structural Assessment
- [ ] Separation of concerns: Business logic mixed with routing/UI?
- [ ] Dependency direction: Do lower layers depend on higher layers? (bad)
- [ ] Circular dependencies: A imports B imports A?
- [ ] God modules: Single file doing everything? (>500 lines = split candidate)
- [ ] Configuration management: Hardcoded values vs. env vars vs. config files?
Step 3: Scalability Assessment
- [ ] Stateless services: Can horizontally scale? Or tied to local state/filesystem?
- [ ] Database bottlenecks: Single DB? Read replicas? Connection pooling?
- [ ] Caching strategy: What's cached? What should be? TTL appropriate?
- [ ] Background jobs: Long tasks blocking request handlers?
- [ ] Rate limits: External API calls rate-limited? Queued?
Step 4: Tech Stack Fit
- [ ] Platform constraints: Using node:fs on serverless? Expecting persistent storage on workers?
- [ ] Over-engineering: Microservices for a team of 1? K8s for 100 users?
- [ ] Under-engineering: Monolith hitting scaling walls? Missing caching layer?
- [ ] Dependency risk: Critical deps unmaintained? Single points of failure?
Step 5: Output
Architecture summary with:
- Current architecture diagram (ASCII or description)
- Issues ranked by severity
- Recommended changes with effort estimates (small/medium/large)
System Design Protocol (When Designing New Features)
- Clarify requirements (use spec-interview if complex)
- Identify bounded contexts — what data/logic belongs together?
- Choose patterns — MVC, event-driven, CQRS, etc.
- Evaluate trade-offs — document what you're choosing and what you're giving up
- Design for the current scale — not 10x ahead (that's over-engineering)
- Output: design document with data flow, API contracts, and migration path
Related Skills
nhouseholder/compactor
tools
VerifiedTrustedCommunity
Unified context management and session continuity skill. Combines total-recall, strategic-compact, /ledger, and session continuity. Runs in background to preserve critical context across compaction and sessions.
1SKILL.mdUpdated Apr 21, 2026
nhouseholder/webapp-testing
tools
VerifiedTrustedCommunity
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
1SKILL.mdUpdated Apr 17, 2026
nhouseholder/using-ultraplan
tools
VerifiedTrustedCommunity
Suggest /ultraplan for complex planning tasks on Claude Code CLI (2.1.91+ only). Research preview.
1SKILL.mdUpdated Apr 17, 2026
nhouseholder/ui-ux-pro-max
tools
VerifiedTrustedCommunity
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.
1SKILL.mdUpdated Apr 17, 2026