This skill should be used when the user asks about "ArchiMate naming conventions", "model quality", "EA smells", "anti-patterns", "ArchiMate best practices", "model review", "abstraction levels", "viewpoints", "model organization", or needs guidance on creating high-quality ArchiMate models.
From archimatenpx claudepluginhub thomasrohde/marketplace --plugin archimateThis skill uses the workspace's default tool permissions.
references/framework-integration.mdreferences/viewpoints.mdGuides browser automation with Playwright, Puppeteer, Selenium for e2e testing and scraping. Teaches reliable selectors, auto-waits, isolation to fix flaky tests.
Provides checklists to review code for functionality, quality, security, performance, tests, and maintainability. Use for PRs, audits, team standards, and developer training.
Enforces A/B test setup with gates for hypothesis locking, metrics definition, sample size calculation, assumptions checks, and execution readiness before implementation.
This skill provides guidance on creating high-quality, maintainable ArchiMate models.
| Element Category | Convention | Examples |
|---|---|---|
| Structural Elements | Singular Noun Phrases | Customer Portal, Data Warehouse |
| Behavioral Elements | Verb Phrases | Manage Applications, Process Payments |
| Processes | Present-tense Verb + Noun | Handle Claim, Submit Order |
| Services | Noun or Gerund Phrase | Customer Information Service, Payment Processing |
| Capabilities | Compound Noun/Gerund | Risk Management, Customer Onboarding |
| Value Streams | Verb-Noun Active | Acquire Insurance Product |
[Business Systems][Customer System]ASIS_ApplicationLandscape, TOBE_Integration| EA Smell | Description | Correction |
|---|---|---|
| Lonely Component | Element with no relations | Connect or remove orphans |
| Strict Layers Violation | Business directly linked to Technology | Add Application layer intermediation |
| Dead Element | Element not in any view | Review for deletion or include |
| God Component | One element with too many responsibilities | Decompose into focused components |
| Chatty Interface | Too many fine-grained relationships | Consolidate at appropriate abstraction |
| Missing Relationship | Implicit dependencies not modeled | Make relationships explicit |
| Circular Dependencies | Cyclic relationships | Restructure to eliminate cycles |
| Purpose | Abstraction Level | Audience |
|---|---|---|
| Informing | High (Overview) | CxOs, broad stakeholders |
| Deciding | Medium (Coherence) | Managers, analysts |
| Designing | Low (Details) | Subject matter experts |
| Element Type | Right Level | Over-Modeling Signs |
|---|---|---|
| Business Processes | Level 2-3 decomposition | Every task modeled |
| Applications | Logical components | Individual modules as components |
| Technology | Platform/service level | Individual servers |
| Capabilities | 2-3 levels deep | Operational activities |
| Stakeholder Type | Recommended Viewpoints |
|---|---|
| CxOs, Business Managers | Strategy, Capability Map, Motivation |
| Enterprise Architects | Layered, Application Cooperation, Implementation |
| Process Architects | Business Process Cooperation, Service Realization |
| Application Architects | Application Usage, Implementation and Deployment |
| Infrastructure Architects | Technology, Technology Usage, Physical |
| Architecture Pattern | Primary Viewpoints |
|---|---|
| Microservices | Application Cooperation, Layered, Technology Usage |
| API/Integration | Application Cooperation, Service Realization |
| Cloud Infrastructure | Technology, Deployment, Layered |
| Data Architecture | Information Structure, Application Cooperation |
| Capability Mapping | Capability Map, Strategy, Resource Map |
Model
├── Strategy
├── Business
├── Application
├── Technology
├── Physical
├── Motivation
├── Implementation & Migration
├── Relations
└── Views
Model
├── Customer Domain
│ ├── Business
│ ├── Application
│ └── Technology
├── Finance Domain
└── Shared Services
For detailed viewpoint guidance and framework integration:
references/viewpoints.md - Complete ArchiMate viewpoints catalogreferences/framework-integration.md - TOGAF, BPMN, IT4IT integration patterns