How does this skill handle architectural decisions?

It uses the Architecture Decision Record (ADR) methodology to capture the context, options, and consequences of significant choices, organizing them by their respective C4 level.

Does this support data modeling?

Yes, it prioritizes LinkML for canonical domain definitions and supports OpenAPI, AsyncAPI, and Protobuf for message contracts.

What is the C4 model in this skill?

The C4 model defines four levels of abstraction—Context, Container, Component, and Code—allowing you to zoom in and out of a system's architecture to communicate with different stakeholders.

When should I use ArchiMate vs. UML?

This skill uses ArchiMate for high-level architectural facts and system boundaries (L1-L2) and UML for detailed internal software design and implementation patterns (L3-L4).

Solution Architecture & Modeling

Name: Solution Architecture & Modeling
Author: meaningfy-ws

bymeaningfy-ws

•

API Development

Develops rigorous system architecture models using C4, ArchiMate, and UML through a contract-first approach.

About

This skill empowers Claude to act as a senior solution architect, guiding users through the creation of comprehensive system models and formal documentation. By utilizing the C4 abstraction levels alongside ArchiMate and UML notations, it ensures that architectural decisions are well-structured, justified via Architecture Decision Records (ADRs), and translated into actionable artifacts like LinkML schemas and OpenAPI specifications. It is an essential tool for engineering teams that prioritize rigorous design, clear system boundaries, and documentation-first development workflows before committing to code.

Key Features

Traceable mapping from business requirements to architectural drivers
Automated Architectural Decision Record (ADR) generation and management
Structured C4 abstraction levels (Context, Container, Component, Code)
Contract-first data modeling with LinkML, OpenAPI, and AsyncAPI
1 GitHub stars
Dual-notation modeling using ArchiMate for facts and UML for design

Use Cases

Establishing a documentation-first workflow for enterprise-grade software projects
Modernizing legacy systems by reverse-engineering formal architectural models
Designing complex microservices ecosystems with clear container and service boundaries

About

Key Features

Traceable mapping from business requirements to architectural drivers
Automated Architectural Decision Record (ADR) generation and management
Structured C4 abstraction levels (Context, Container, Component, Code)
Contract-first data modeling with LinkML, OpenAPI, and AsyncAPI
1 GitHub stars
Dual-notation modeling using ArchiMate for facts and UML for design

Use Cases

Establishing a documentation-first workflow for enterprise-grade software projects
Modernizing legacy systems by reverse-engineering formal architectural models
Designing complex microservices ecosystems with clear container and service boundaries