senior-architect

Generate ADRs and Mermaid-based C4 diagrams for large-scale system architecture.

13|2|Updated Jan 5, 2026
One-click install
npx skills add https://github.com/kriscard/kriscard-claude-plugins --skill senior-architect-kriscard
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: senior-architect
Source: https://github.com/kriscard/kriscard-claude-plugins/tree/main/plugins/architecture/skills/senior-architect
Command: npx skills add https://github.com/kriscard/kriscard-claude-plugins --skill senior-architect-kriscard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture: Use when designing system architecture, creating C4 diagrams, evaluating tech trade-offs, or writing ADRs. NOT for implementation details or coding.

Core Features & Use Cases

  • Comprehensive system design toolkit: decision records, C4 diagrams, ADRs, and trade-off analysis.
  • Guidance for patterns like monolith vs microservices, API design choices, database patterns, and system design processes.
  • Use Case: When starting a new large-scale product, produce ADRs and a high-level architecture plan to align teams.

Quick Start

Provide a high-level system design sketch and ADRs for the given problem.

Frequently Asked Questions about senior-architect

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

FAQPage Schema
What is the best way to document system design decisions for a large-scale project?▼

System design decisions are best documented using Architecture Decision Records (ADRs) to capture trade-offs and context. This Skill generates ADRs alongside high-level architecture plans to align teams on monolith versus microservices choices and API specifications.

How do I create C4 diagrams using Mermaid for my software architecture?▼

You can create C4 diagrams using Mermaid by providing a high-level system design sketch. This Skill generates Mermaid-based C4 diagrams as design artifacts to visually communicate scalable architecture structures and component relationships.

When do I need architecture decision records for monolith versus microservices trade-offs?▼

Architecture decision records are needed when evaluating monolith versus microservices trade-offs to ensure scalable architecture. This Skill provides trade-off analysis and guidance to formalize these system design decisions for large-scale products.

Does this system design Skill help with API design patterns and data storage strategies?▼

Yes, this system design Skill provides comprehensive guidance on API design choices and data storage strategies. It helps evaluate patterns and produces high-level design artifacts that satisfy requirements for robust API specifications.

Can I use this for implementation details and coding tasks?▼

No, this Skill is explicitly not for implementation details or coding tasks. It focuses strictly on high-level system architecture, evaluating tech trade-offs, producing ADRs, and generating C4 diagrams.

How do I evaluate tech trade-offs when designing scalable system architectures?▼

You evaluate tech trade-offs in scalable system architecture by analyzing decision records and high-level design artifacts. This Skill provides a comprehensive toolkit for trade-off analysis covering database patterns, API design, and architectural styles.