Skills archimate
Create ArchiMate enterprise architecture diagrams using PlantUML stdlib macros. Best for TOGAF viewpoints, layered EA modeling (Business/Application/Technology), motivation analysis, and migration planning.
install
source · Clone the upstream repo
git clone https://github.com/markdown-viewer/skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/markdown-viewer/skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/archimate" ~/.claude/skills/markdown-viewer-skills-archimate && rm -rf "$T"
manifest:
archimate/SKILL.mdsource content
Enterprise Architecture Diagram Generator (ArchiMate)
Quick Start: Add
!include <archimate/Archimate> → Declare typed elements → Connect with Rel_* macros → Group into layers with rectangle → Wrap in ```plantuml fence.
⚠️ IMPORTANT: Always use
or```plantumlcode fence. NEVER use```puml— it will NOT render as a diagram.```text
Critical Rules
- Every diagram starts with
and ends with@startuml@enduml - Must include
before using any macros!include <archimate/Archimate> - Element syntax:
Layer_Type(alias, "Label") - Relationship syntax:
Rel_Type(fromAlias, toAlias, "label") - Use
to group elements into ArchiMate layersrectangle "Layer" { ... } - Directional suffixes
,_Up
,_Down
,_Left
control relationship direction_Right
Element Macros
Business Layer
| Macro | ArchiMate Element |
|---|---|
| Business Actor |
| Business Role |
| Business Process |
| Business Function |
| Business Service |
| Business Event |
| Business Interface |
| Business Collaboration |
| Business Object |
| Business Product |
| Business Contract |
| Business Representation |
Application Layer
| Macro | ArchiMate Element |
|---|---|
| Application Component |
| Application Service |
| Application Function |
| Application Interface |
| Application Process |
| Application Interaction |
| Application Event |
| Application Collaboration |
| Application Data Object |
Technology Layer
| Macro | ArchiMate Element |
|---|---|
| Technology Device |
| Technology Node |
| System Software |
| Technology Artifact |
| Communication Network |
| Technology Path |
| Technology Service |
| Technology Process |
| Technology Function |
| Technology Interface |
Motivation Layer
| Macro | ArchiMate Element |
|---|---|
| Stakeholder |
| Driver |
| Assessment |
| Goal |
| Outcome |
| Principle |
| Requirement |
| Constraint |
| Value |
Strategy Layer
| Macro | ArchiMate Element |
|---|---|
| Capability |
| Resource |
| Course of Action |
| Value Stream |
Implementation Layer
| Macro | ArchiMate Element |
|---|---|
| Work Package |
| Deliverable |
| Plateau |
| Gap |
| Implementation Event |
Relationship Macros
All relationships support directional suffixes:
_Up, _Down, _Left, _Right.
| Macro | ArchiMate Relationship | Line Style |
|---|---|---|
| Composition | Solid + filled diamond |
| Aggregation | Solid + open diamond |
| Assignment | Solid + circle→triangle |
| Realization | Dotted + hollow triangle |
| Serving | Solid + arrow |
| Triggering | Solid + filled triangle |
| Flow | Dashed + filled triangle |
| Access | Dotted line |
| Access (read) | Dotted + arrow |
| Access (write) | Dotted + reverse arrow |
| Influence | Dashed + arrow |
| Association | Solid line |
| Specialization | Solid + hollow triangle |
Quick Example
@startuml !include <archimate/Archimate> rectangle "Business" { Business_Actor(customer, "Customer") Business_Process(order, "Order Process") Business_Service(orderSvc, "Order Service") } rectangle "Application" { Application_Component(orderApp, "Order System") Application_Service(orderAPI, "Order API") } rectangle "Technology" { Technology_Node(server, "App Server") Technology_Device(db, "Database Server") } Rel_Triggering(customer, order, "places order") Rel_Realization(order, orderSvc, "realizes") Rel_Serving(orderAPI, orderSvc, "serves") Rel_Realization(orderApp, orderAPI, "realizes") Rel_Assignment(server, orderApp, "runs on") Rel_Serving(db, server, "stores data") @enduml
Diagram Types
| Type | Purpose | Key Macros | Example |
|---|---|---|---|
| Enterprise Landscape | Full B/A/T layered view | All layers | enterprise-landscape.md |
| Application Integration | App-to-app data flows | | application-integration.md |
| Technology Infrastructure | Infrastructure stack | | technology-infrastructure.md |
| Business Capability | Capability map | , | business-capability.md |
| Migration Planning | Plateau-based roadmap | | migration-planning.md |
| Security Architecture | Security controls | , | security-architecture.md |
| Data Architecture | Data flow & ownership | , | data-architecture.md |
| DevOps Pipeline | CI/CD delivery chain | , | devops-pipeline.md |