senior-architect
Senior Architect guides system design through structured phases: requirements analysis, architecture evaluation, and decision documentation. It produces Architecture Decision Records, trade-off analyses, and scalability blueprints grounded in proven patterns.
Senior Architect evaluates architectural styles and selects the best approach with explicit trade-offs documented.
AI-generated summary based on this skill's SKILL.md
Install
Pixel-Process-UG/superkit-agents/senior-architect · repository language: TypeScript
git clone https://github.com/Pixel-Process-UG/superkit-agents
cp -r superkit-agents/templates/skills/senior-architect ~/.claude/skills/senior-architectnpx skillfed install Pixel-Process-UG/superkit-agents/senior-architectFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How does Senior Architect help with system design for scaling?
Senior Architect guides you through structured scaling design by analyzing your system's growth requirements, evaluating architectural patterns, and documenting trade-offs. It helps define non-functional requirements and SLOs, then produces scalability blueprints with horizontal scaling strategies tailored to your constraints and performance targets.
What is an architecture decision records template and how do I create one?
Senior Architect provides ADR creation process guidance to document your architectural choices systematically. Each record captures the decision context, alternatives considered, chosen solution, and explicit trade-offs. Senior Architect structures these records to ensure consistency across your system design choices and makes future architectural decisions traceable and justified.
What are the microservices vs monolith trade-offs I should evaluate?
Senior Architect evaluates both approaches by analyzing deployment complexity, team autonomy, data consistency, operational overhead, and scalability patterns. It documents trade-offs explicitly: monoliths offer simpler initial deployment but limit independent scaling; microservices enable fine-grained scaling and team independence but increase infrastructure and coordination costs.
How do I plan non-functional requirements for my system?
Senior Architect helps define non-functional requirements by establishing clear SLOs for performance, reliability, availability, and latency. It guides you through analyzing your system's constraints, user expectations, and operational capabilities, then translates these into measurable targets that drive architectural decisions and technology selection.
How should I approach technology selection for a new system?
Senior Architect analyzes technology options by mapping them against your non-functional requirements, team expertise, and operational context. It evaluates service boundaries, integration patterns, and long-term maintenance costs, then documents the selection rationale with trade-offs so your technology choices remain justified as systems evolve.
What scalability analysis and planning should I do upfront?
Senior Architect guides scalability planning by identifying bottlenecks, defining growth scenarios, and designing horizontal scaling patterns. It helps you establish SLOs for throughput and latency, evaluate caching and partitioning strategies, and document how each architectural component scales, ensuring your system design anticipates future demand.
SKILL.md
rendered from the published skill — quoted content, verbatim
Senior Architect
Overview
Provide architecture-level guidance for system design decisions. This skill produces Architecture Decision Records (ADRs), trade-off analyses, scalability blueprints, and non-functional requirements specifications. Every recommendation includes explicit trade-offs and is grounded in proven patterns.
Announce at start: "I'm using the senior-architect skill for system design and architecture decisions."
Phase 1: Requirements Analysis
Goal: Capture all functional and non-functional requirements before designing.
Actions
- Identify functional requirements (capabilities)
- Define non-functional requirements (quality attributes)
- Identify constraints (budget, team, timeline, compliance)
- Map integration points with existing systems
- Establish success criteria and SLOs
STOP — Do NOT
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
templates/skills/senior-architect/SKILL.md