How does this skill handle non-functional requirements?

It treats NFRs like performance, security, and scalability as first-class concerns, systematically mapping them to specific architectural decisions like caching strategies, auth models, or load balancing.

Can it validate existing architectures?

Yes, the /validate-architecture command allows you to review current designs against project requirements and industry best practices to identify gaps or risks.

What is the 'Phase 3' solutioning specialist role?

It represents the critical stage in the development lifecycle where conceptual requirements (Phase 2) are turned into concrete technical designs (Phase 3) before implementation (Phase 4) starts.

What documentation format does the skill generate?

It generates standardized Markdown documentation containing component boundaries, interface definitions, data models, and the rationale behind specific architectural trade-offs.

System Architect

Name: System Architect
Author: delorenj

bydelorenj

•

クラウドインフラストラクチャ

Designs robust system architectures and technical blueprints by mapping functional and non-functional requirements to scalable technology stacks.

概要

The System Architect skill acts as a specialized solutioning specialist for Claude Code, bridging the gap between product requirements and implementation. It systematically evaluates functional and non-functional requirements to produce comprehensive architectural designs, including data models, API specifications, and component boundaries. By utilizing proven patterns—such as microservices, modular monoliths, or serverless—and explicitly documenting trade-offs, this skill ensures that development teams have a clear, secure, and maintainable roadmap before coding begins.

主な機能

Technology stack selection with architectural justification
Systematic mapping and validation of non-functional requirements (NFRs)
5 GitHub stars
Automated architecture validation against Product Requirement Documents (PRDs)
Comprehensive system architecture design and documentation
Creation of detailed data models and API specifications

ユースケース

Reviewing and validating existing system architectures for scalability and security bottlenecks
Transforming a PRD into a detailed technical blueprint before starting a new development phase
Standardizing architectural decision records (ADRs) and design documentation across a project

概要

主な機能

Technology stack selection with architectural justification
Systematic mapping and validation of non-functional requirements (NFRs)
5 GitHub stars
Automated architecture validation against Product Requirement Documents (PRDs)
Comprehensive system architecture design and documentation
Creation of detailed data models and API specifications

ユースケース

Reviewing and validating existing system architectures for scalability and security bottlenecks
Transforming a PRD into a detailed technical blueprint before starting a new development phase
Standardizing architectural decision records (ADRs) and design documentation across a project