architecture-models-4plus1listed

Produce Philippe Kruchten's 4+1 architectural view model for a software system, with rendered diagrams (Mermaid primary, PlantUML fallback for deployment) AND Miro RISEN prompts for each view. Use this skill whenever the user mentions "4+1", "architecture views", "architectural documentation", "logical view", "process view", "development view", "physical view", or "deployment view" — and also whenever the user asks to document system architecture, produce architecture blueprints, generate architecture diagrams, or prepare architecture content for review with non-developer stakeholders, even if they don't say "4+1" explicitly. Works with zero-input (user gives a paragraph, skill drafts a full architecture), interview mode (user has detailed context), or partial mode (user wants only one or two views). Flexes notation to audience — UML-flavoured for dev-only audiences, BPMN-style swimlanes for cross-functional audiences, simplified C4 for executives.
MarieLynneBlock/arcanum-artifex · ★ 2 · AI & Automation · score 66

Install: claude install-skill MarieLynneBlock/arcanum-artifex

# 4+1 Architecture Models Generates Kruchten's 4+1 View Model for any software system. Each deliverable per view is two artefacts: 1. **A rendered architectural drawing** — Mermaid (primary) or PlantUML (for deployment-heavy physical views). 2. **A Miro RISEN prompt** — ready to paste into Miro AI Sidekick to recreate the same view on a Miro board. Plus a prose view document that wraps both and explains the architecture decisions, quality attributes, and concerns. This skill is portable by design: the same SKILL.md works natively in Claude Code, via a Cursor rule (`shims/cursor/`), and via a Copilot custom prompt (`shims/copilot/`). Change logic here; the shims will pick it up. ## The five views at a glance | View | Who reads it | What it answers | Primary notation | |------|-------------|-----------------|------------------| | Logical | End-users, analysts, architects | What components exist and how they relate | Mermaid class / component / C4 Container | | Process | Integrators, performance engineers, operations, BAs | How the system behaves at runtime | Mermaid sequenceDiagram (dev) / flowchart with swimlanes (cross-functional) | | Development | Developers, software managers | How the codebase is organised | Mermaid flowchart / C4 Component | | Physical | SRE, infrastructure engineers | How it's deployed and operated | PlantUML deployment + AWS/Azure/GCP stdlib (primary) / Mermaid C4Deployment (fallback) | | Scenarios (+1) | All stakeholders | Key use cases that exer