senior-architect

Guide system architecture design with pattern selection and ADR documentation.

5|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/lidge-jun/cli-jaw-skills --skill senior-architect-lidge-jun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: senior-architect
Source: https://github.com/lidge-jun/cli-jaw-skills/tree/main/senior-architect
Command: npx skills add https://github.com/lidge-jun/cli-jaw-skills --skill senior-architect-lidge-jun

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides guidance and structured approaches for making critical system architecture decisions, documenting them effectively, and analyzing dependencies to ensure maintainable and scalable software systems.

Core Features & Use Cases

  • Architecture Decision Records (ADRs): Helps document significant design choices with context, decision, and consequences.
  • Pattern Selection: Offers guidance on choosing appropriate architectural patterns (e.g., Microservices, Monolith, CQRS) based on requirements.
  • Dependency Analysis: Aids in identifying and resolving unhealthy circular dependencies.
  • Tech Stack & Database Selection: Provides matrices for choosing suitable technologies.
  • Use Case: When starting a new project or refactoring an existing one, use this Skill to document the initial architectural decisions and select the most appropriate patterns and technologies.

Quick Start

Use the senior-architect skill to generate a template for an Architecture Decision Record.

Frequently Asked Questions about senior-architect

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

FAQPage Schema
How do I write an Architecture Decision Record for system design?

An Architecture Decision Record (ADR) documents significant system design choices by outlining the context, decision, and consequences. This Skill generates structured templates to help you record architectural decisions effectively.

How do I choose between microservices and monolithic architecture patterns?

Selecting architectural patterns like microservices or monoliths requires evaluating trade-offs based on project requirements. This Skill provides guidance and matrices to help you choose appropriate patterns for scalability and maintainability.

What is the best way to analyze circular dependencies in a software project?

Analyzing circular dependencies involves identifying and resolving unhealthy structural relationships in your codebase. This Skill aids in dependency analysis to ensure your software architecture remains maintainable.

How do I select a technology stack and database for a new project?

Tech stack and database selection requires evaluating suitable technologies against your project needs. This Skill provides decision matrices to help you evaluate trade-offs and plan for system scalability.

When do I need to document architectural decisions for software engineering projects?

You need to document architectural decisions when starting a new project or refactoring an existing one. This facilitates structured decision-making by offering workflows for evaluating trade-offs and recording consequences.

Does this Skill support evaluating trade-offs for system scalability?

Yes, evaluating trade-offs for system scalability is a core function. It provides structured workflows and matrices to facilitate decision-making and planning for maintainable and scalable software systems.