Stats
Actions
Tags
How this command is triggered — by the user, by Claude, or both
Slash command
/archimate:pattern [architecture type, e.g., microservices, cloud, API gateway]This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# ArchiMate Pattern Lookup Help the user find the right ArchiMate pattern for their architecture scenario. ## Process 1. Identify the architecture pattern from the user's query 2. Load the archimate-patterns skill if needed for detailed patterns 3. Present the pattern with: - Element mappings (what ArchiMate elements to use) - Relationship patterns (how to connect them) - Notation examples - Variations for different detail levels ## Common Patterns Quick Reference ### Microservices - Services → Application Component - APIs → Application Interface - Docker images → Artifact...
Help the user find the right ArchiMate pattern for their architecture scenario.
[Application Component: Service Name] → [realizes] → [Application Service: Capability]
→ [composition] → [Application Function: Internal Behavior]
→ [serves] → [Application Interface: API]
[Technology Node: API Gateway]
→ [realization] → [Technology Service: API Management]
→ [serves] → [Application Component: Backend]
[Application Component: Producer] → [triggers] → [Application Event: Event Name]
[Application Event] → [flow] → [Application Component: Consumer]
[Capability] → [realized by] → [Business Process]
[Capability] → [realized by] → [Application Component]
[Value Stream] → [composition] → [Value Stream Stage]
[Value Stream Stage] ← [served by] ← [Capability]
If user asks generally, offer categories:
Present patterns as both:
Include:
npx claudepluginhub thomasrohde/marketplace --plugin archimate/architectDesigns system architecture evaluating patterns (monolith, microservices, serverless, event-driven, CQRS, hexagonal) with trade-offs, C4 diagrams, bounded contexts, and ADRs. Outputs docs, commits changes. Supports comparisons, migrations, validation.
/create-architecture-documentationGenerates architecture documentation covering system context, containers, components, data flows, security models, and quality attributes using C4 Model, Arc42, ADRs, Mermaid, and PlantUML.
/diagramGenerates C4 architecture diagrams (context, container, component levels) from design documents in Mermaid, PlantUML, or C4 format. Outputs to docs/architecture/diagrams/. Supports --format, --level, --diagram_type options.
/architect-systemDesign complete system architecture from requirements. Produces C4 diagrams, bounded contexts, and integration specifications.
/flow-architecture-evolutionOrchestrates architecture evolution workflow with ADR management, architecture review, breaking change analysis, and migration planning.