Loading...
Loading...
Create enterprise architecture diagrams using PlantUML ArchiMate stdlib macros. Best for layered EA modeling (Business/Application/Technology), motivation analysis, migration planning, and TOGAF views. Uses `!include <archimate/Archimate>` stdlib with typed element macros and relationship macros. NOT for cloud infrastructure (use cloud skill) or network topology (use network skill).
npx skill4agent add markdown-viewer/skills archimate!include <archimate/Archimate>Rel_*rectangle```plantuml⚠️ IMPORTANT: Always useor```plantumlcode fence. NEVER use```puml— it will NOT render as a diagram.```text
@startuml@enduml!include <archimate/Archimate>Layer_Type(alias, "Label")Rel_Type(fromAlias, toAlias, "label")rectangle "Layer" { ... }_Up_Down_Left_Right| 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 |
| Macro | ArchiMate Element |
|---|---|
| Application Component |
| Application Service |
| Application Function |
| Application Interface |
| Application Process |
| Application Interaction |
| Application Event |
| Application Collaboration |
| Application Data Object |
| Macro | ArchiMate Element |
|---|---|
| Technology Device |
| Technology Node |
| System Software |
| Technology Artifact |
| Communication Network |
| Technology Path |
| Technology Service |
| Technology Process |
| Technology Function |
| Technology Interface |
| Macro | ArchiMate Element |
|---|---|
| Stakeholder |
| Driver |
| Assessment |
| Goal |
| Outcome |
| Principle |
| Requirement |
| Constraint |
| Value |
| Macro | ArchiMate Element |
|---|---|
| Capability |
| Resource |
| Course of Action |
| Value Stream |
| Macro | ArchiMate Element |
|---|---|
| Work Package |
| Deliverable |
| Plateau |
| Gap |
| Implementation Event |
_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 |
@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| 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 |