senior-architect

Design architecture decisions and generate Mermaid, PlantUML, or ASCII diagrams.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/AgLyx3/My-Note-App-Not-Just-a-Note-App --skill senior-architect-aglyx3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: senior-architect
Source: https://github.com/AgLyx3/My-Note-App-Not-Just-a-Note-App/tree/main/.cursor/skills/engineering-team/senior-architect
Command: npx skills add https://github.com/AgLyx3/My-Note-App-Not-Just-a-Note-App --skill senior-architect-aglyx3

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill helps teams design robust system architectures, evaluate trade-offs, and generate clear diagrams to inform technical decisions.

Core Features & Use Cases

  • Architecture Diagram Generator: Mermaid, PlantUML, or ASCII to visualize system components and relationships.
  • Dependency & ADR Support: Assess dependencies, capture Architecture Decisions Records, and document rationale.
  • System Design Assessments: Evaluate patterns (monolith, microservices, hexagonal, etc.) and propose scalable architectures for complex projects.

Quick Start

Provide a high-level architectural plan and generate diagrams for a given project.

Frequently Asked Questions about senior-architect

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

FAQPage Schema
How do I generate system design diagrams for a complex project?

Generate architecture diagrams in Mermaid, PlantUML, or ASCII by providing a high-level architectural plan to visualize system components and relationships for technical decisions.

What is an ADR and how do I document architecture decisions?

An Architecture Decision Record (ADR) captures design decisions and rationale. You can document trade-offs and reasoning to maintain clear technology evaluations across varying project sizes.

How do I assess dependencies when evaluating a tech stack?

Assess dependencies by analyzing the technology evaluations within your system design, capturing impacts in ADRs to document the rationale and trade-offs of your tech stack decisions.

Does this approach work for evaluating microservices versus monolithic architecture patterns?

Yes, system design assessments evaluate patterns like monolith, microservices, and hexagonal architectures to propose scalable structures tailored to the specific scale and context of complex projects.

What is the best way to document trade-offs for technology evaluations?

Document trade-offs by capturing Architecture Decision Records (ADRs) alongside dependency analyses, ensuring the rationale behind complex system design choices is clearly recorded.