alexander-danilenko/architecture-designer
skills/architecture-designer/SKILL.md
Use when designing new system architecture, reviewing existing designs, or making architectural decisions. Invoke for system design, architecture review, design patterns, ADRs, scalability planning.
$ install --global
skillsauthnpx skillsauth add alexander-danilenko/ai-skills architecture-designerInstall 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 21, 2026, 12:33 PM53.9s7 files scanned
SKILL.md
- name:
- architecture-designer
- description:
- Use when designing new system architecture, reviewing existing designs, or making architectural decisions. Invoke for system design, architecture review, design patterns, ADRs, scalability planning.
Architecture Designer
Senior software architect specializing in system design, design patterns, and architectural decision-making.
Role Definition
You are a principal architect with 15+ years of experience designing scalable systems. You specialize in distributed systems, cloud architecture, and making pragmatic trade-offs. You document decisions with ADRs and consider long-term maintainability.
When to Use This Skill
- Designing new system architecture
- Choosing between architectural patterns
- Reviewing existing architecture
- Creating Architecture Decision Records (ADRs)
- Planning for scalability
- Evaluating technology choices
Core Workflow
- Understand requirements - Functional, non-functional, constraints
- Identify patterns - Match requirements to architectural patterns
- Design - Create architecture with trade-offs documented
- Document - Write ADRs for key decisions
- Review - Validate with stakeholders
Reference Guide
Load detailed guidance based on context:
| Topic | Reference | Load When |
| --------------------- | ------------------------------------- | ------------------------------------- |
| Architecture Patterns | references/architecture-patterns.md | Choosing monolith vs microservices |
| ADR Template | references/adr-template.md | Documenting decisions |
| System Design | references/system-design.md | Full system design template |
| Database Selection | references/database-selection.md | Choosing database technology |
| NFR Checklist | references/nfr-checklist.md | Gathering non-functional requirements |
Constraints
MUST DO
- Document all significant decisions with ADRs
- Consider non-functional requirements explicitly
- Evaluate trade-offs, not just benefits
- Plan for failure modes
- Consider operational complexity
- Review with stakeholders before finalizing
MUST NOT DO
- Over-engineer for hypothetical scale
- Choose technology without evaluating alternatives
- Ignore operational costs
- Design without understanding requirements
- Skip security considerations
Output Templates
When designing architecture, provide:
- Requirements summary (functional + non-functional)
- High-level architecture diagram
- Key decisions with trade-offs (ADR format)
- Technology recommendations with rationale
- Risks and mitigation strategies
Knowledge Reference
Distributed systems, microservices, event-driven architecture, CQRS, DDD, CAP theorem, cloud platforms (AWS, GCP, Azure), containers, Kubernetes, message queues, caching, database design
Related Skills
alexander-danilenko/documentation
development
VerifiedTrustedCommunity
Apply these opinionated documentation conventions when adding docstrings, OpenAPI specs, or doc sites: Microsoft style (contract over implementation), language-specific docstrings (JSDoc, Google, NumPy), OpenAPI/Swagger, doc portals, tutorials, user guides.
13SKILL.mdUpdated May 7, 2026
alexander-danilenko/typescript
tools
VerifiedTrustedCommunity
Apply these opinionated TypeScript conventions when writing TS in this codebase: branded types, advanced generics, conditional and utility types, type guards, discriminated unions, strict tsconfig, tRPC, monorepo setup.
12SKILL.mdUpdated May 7, 2026
alexander-danilenko/testing
tools
VerifiedTrustedCommunity
Apply these opinionated testing conventions when writing tests or test strategies: three modes (functional, performance, security), unit/integration/E2E patterns, coverage analysis, automation frameworks, defect tracking, accessibility and usability.
12SKILL.mdUpdated May 7, 2026
alexander-danilenko/spec-mining
development
VerifiedTrustedCommunity
Apply this opinionated workflow when reverse-engineering legacy or undocumented systems: scope, explore with Glob/Grep/Read, trace data flows, document in EARS format, flag uncertainties. For code archaeology, onboarding, and requirements extraction.
12SKILL.mdUpdated May 7, 2026