senior-architect

Guide architectural decisions for scalable software systems across modern stacks.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ksrae/tag-diary-app --skill senior-architect-ksrae
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: senior-architect
Source: https://github.com/ksrae/tag-diary-app/tree/main/.agents/skills/senior-architect
Command: npx skills add https://github.com/ksrae/tag-diary-app --skill senior-architect-ksrae

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineering teams design scalable, maintainable architectures by guiding architectural decisions, patterns, and organizational practices aligned with business goals.

Core Features & Use Cases

  • System Design Guidance: Evaluate trade-offs between microservices and monoliths, apply event-driven patterns, and craft data models for relational and NoSQL stores.
  • Code Organization in Monorepo: Define shared packages, encapsulate features as modules, and enforce clear dependency boundaries.
  • Cross-Cutting Concerns: Establish observability, security posture, and scalable infrastructure considerations; provide decision frameworks for technology choices.
  • Use Case: Plan a multi-team project architecture and generate a high-level blueprint with rationale.

Quick Start

Provide a starter architecture outline for a given project and specify the reasoning behind each choice.

Frequently Asked Questions about senior-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design scalable software architecture for a multi-team project?

Design scalable software architecture by applying a structured framework that evaluates system design, tech-stack selection, and module boundaries. This generates a high-level architectural blueprint with rationale, guiding organizational practices to align with business goals.

What is the best way to organize a monorepo to maintain clear dependency boundaries?

Organize a monorepo by defining shared packages and encapsulating features as distinct modules. This approach enforces clear dependency boundaries and establishes code organization patterns that keep multi-team projects maintainable as they scale.

How do I evaluate trade-offs between microservices and monoliths for my system design?

Evaluate microservices and monoliths by applying an architectural decision framework that assesses scalability, maintainability, and cross-cutting concerns. This process evaluates trade-offs based on your specific business goals and modern stack requirements.

Can I use this architectural guidance for modern stacks like ReactJS, NodeJS, and FastAPI?

Yes, architectural guidance applies to modern stacks including ReactJS, NextJS, NodeJS, FastAPI, and Flutter. The framework guides system design, tech-stack selection, and plan-driven refactoring across these technologies for multi-team projects.

How do I establish observability and security posture when planning system design?

Establish observability and security posture by addressing cross-cutting concerns within your architectural framework. This ensures scalable infrastructure considerations and security requirements are integrated during system design rather than added retroactively.

When should I apply event-driven patterns and NoSQL data models in software architecture?

Apply event-driven patterns and NoSQL data models when evaluating system design trade-offs for scalable architectures. The framework guides these decisions by assessing specific data requirements and architectural constraints against your business goals.