[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NT46B4WB89N3NF34R44RPK":3,"skill-same:01M6NT46B4WB89N3NF34R44RPK":83},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M6NT46B4WB89N3NF34R44RPK","c4-architecture",null,"Generate architecture documentation using C4 model Mermaid diagrams. Use when asked to create architecture diagrams, document system architecture, visualize software structure, create C4 diagrams, or generate context\u002Fcontainer\u002Fcomponent\u002Fdeployment diagrams. Triggers include \"architecture diagram\", \"C4 diagram\", \"system context\", \"container diagram\", \"component diagram\", \"deployment diagram\", \"document architecture\", \"visualize architecture\".","mattonweb\u002Fai-assistant-foundry","mattonweb","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2309734?v=4","01M6NQYCY846TKYN2ZCRS71WQ7","Matt Johnson","01M6NQYD2NPAQEFVD8TW9W0SVX",1,"MIT","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fcode-mermaid\u002Fsoftaworks\u002Fc4-architecture\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"architecture","c4 architecture","create","architecture documentation","software","structure","diagrams","context","model","system","c4 diagrams","generate","visualize","deployment","architecture diagram","architecture diagrams","mermaid","diagram","documentation","component","2026-11-10 10:12:30",false,"---\nname: c4-architecture\ndescription: Generate architecture documentation using C4 model Mermaid diagrams. Use when asked to create architecture diagrams, document system architecture, visualize software structure, create C4 diagrams, or generate context\u002Fcontainer\u002Fcomponent\u002Fdeployment diagrams. Triggers include \"architecture diagram\", \"C4 diagram\", \"system context\", \"container diagram\", \"component diagram\", \"deployment diagram\", \"document architecture\", \"visualize architecture\".\n---\n\n# C4 Architecture Documentation\n\nGenerate software architecture documentation using C4 model diagrams in Mermaid syntax.\n\n## Workflow\n\n1. **Understand scope** - Determine which C4 level(s) are needed based on audience\n2. **Analyze codebase** - Explore the system to identify components, containers, and relationships\n3. **Generate diagrams** - Create Mermaid C4 diagrams at appropriate abstraction levels\n4. **Document** - Write diagrams to markdown files with explanatory context\n\n## C4 Diagram Levels\n\nSelect the appropriate level based on the documentation need:\n\n| Level | Diagram Type | Audience | Shows | When to Create |\n|-------|-------------|----------|-------|----------------|\n| 1 | **C4Context** | Everyone | System + external actors | Always (required) |\n| 2 | **C4Container** | Technical | Apps, databases, services | Always (required) |\n| 3 | **C4Component** | Developers | Internal components | Only if adds value |\n| 4 | **C4Deployment** | DevOps | Infrastructure nodes | For production systems |\n| - | **C4Dynamic** | Technical | Request flows (numbered) | For complex workflows |\n\n**Key Insight:** \"Context + Container diagrams are sufficient for most software development teams.\" Only create Component\u002FCode diagrams when they genuinely add value.\n\n## Quick Start Examples\n\n### System Context (Level 1)\n```mermaid\nC4Context\n  title System Context - Workout Tracker\n\n  Person(user, \"User\", \"Tracks workouts and exercises\")\n  System(app, \"Workout Tracker\", \"Vue PWA for tracking strength and CrossFit workouts\")\n  System_Ext(browser, \"Web Browser\", \"Stores data in IndexedDB\")\n\n  Rel(user, app, \"Uses\")\n  Rel(app, browser, \"Persists data to\", \"IndexedDB\")\n```\n\n### Container Diagram (Level 2)\n```mermaid\nC4Container\n  title Container Diagram - Workout Tracker\n\n  Person(user, \"User\", \"Tracks workouts\")\n\n  Container_Boundary(app, \"Workout Tracker PWA\") {\n    Container(spa, \"SPA\", \"Vue 3, TypeScript\", \"Single-page application\")\n    Container(pinia, \"State Management\", \"Pinia\", \"Manages application state\")\n    ContainerDb(indexeddb, \"IndexedDB\", \"Dexie\", \"Local workout storage\")\n  }\n\n  Rel(user, spa, \"Uses\")\n  Rel(spa, pinia, \"Reads\u002Fwrites state\")\n  Rel(pinia, indexeddb, \"Persists\", \"Dexie ORM\")\n```\n\n### Component Diagram (Level 3)\n```mermaid\nC4Component\n  title Component Diagram - Workout Feature\n\n  Container(views, \"Views\", \"Vue Router pages\")\n\n  Container_Boundary(workout, \"Workout Feature\") {\n    Component(useWorkout, \"useWorkout\", \"Composable\", \"Workout execution state\")\n    Component(useTimer, \"useTimer\", \"Composable\", \"Timer state machine\")\n    Component(workoutRepo, \"WorkoutRepository\", \"Dexie\", \"Workout persistence\")\n  }\n\n  Rel(views, useWorkout, \"Uses\")\n  Rel(useWorkout, useTimer, \"Controls\")\n  Rel(useWorkout, workoutRepo, \"Saves to\")\n```\n\n### Dynamic Diagram (Request Flow)\n```mermaid\nC4Dynamic\n  title Dynamic Diagram - User Sign In Flow\n\n  ContainerDb(db, \"Database\", \"PostgreSQL\", \"User credentials\")\n  Container(spa, \"Single-Page App\", \"React\", \"Banking UI\")\n\n  Container_Boundary(api, \"API Application\") {\n    Component(signIn, \"Sign In Controller\", \"Express\", \"Auth endpoint\")\n    Component(security, \"Security Service\", \"JWT\", \"Validates credentials\")\n  }\n\n  Rel(spa, signIn, \"1. Submit credentials\", \"JSON\u002FHTTPS\")\n  Rel(signIn, security, \"2. Validate\")\n  Rel(security, db, \"3. Query user\", \"SQL\")\n\n  UpdateRelStyle(spa, signIn, $textColor=\"blue\", $offsetY=\"-30\")\n```\n\n### Deployment Diagram\n```mermaid\nC4Deployment\n  title Deployment Diagram - Production\n\n  Deployment_Node(browser, \"Customer Browser\", \"Chrome\u002FFirefox\") {\n    Container(spa, \"SPA\", \"React\", \"Web application\")\n  }\n\n  Deployment_Node(aws, \"AWS Cloud\", \"us-east-1\") {\n    Deployment_Node(ecs, \"ECS Cluster\", \"Fargate\") {\n      Container(api, \"API Service\", \"Node.js\", \"REST API\")\n    }\n    Deployment_Node(rds, \"RDS\", \"db.r5.large\") {\n      ContainerDb(db, \"Database\", \"PostgreSQL\", \"Application data\")\n    }\n  }\n\n  Rel(spa, api, \"API calls\", \"HTTPS\")\n  Rel(api, db, \"Reads\u002Fwrites\", \"JDBC\")\n```\n\n## Element Syntax\n\n### People and Systems\n```\nPerson(alias, \"Label\", \"Description\")\nPerson_Ext(alias, \"Label\", \"Description\")       # External person\nSystem(alias, \"Label\", \"Description\")\nSystem_Ext(alias, \"Label\", \"Description\")       # External system\nSystemDb(alias, \"Label\", \"Description\")         # Database system\nSystemQueue(alias, \"Label\", \"Description\")      # Queue system\n```\n\n### Containers\n```\nContainer(alias, \"Label\", \"Technology\", \"Description\")\nContainer_Ext(alias, \"Label\", \"Technology\", \"Description\")\nContainerDb(alias, \"Label\", \"Technology\", \"Description\")\nContainerQueue(alias, \"Label\", \"Technology\", \"Description\")\n```\n\n### Components\n```\nComponent(alias, \"Label\", \"Technology\", \"Description\")\nComponent_Ext(alias, \"Label\", \"Technology\", \"Description\")\nComponentDb(alias, \"Label\", \"Technology\", \"Description\")\n```\n\n### Boundaries\n```\nEnterprise_Boundary(alias, \"Label\") { ... }\nSystem_Boundary(alias, \"Label\") { ... }\nContainer_Boundary(alias, \"Label\") { ... }\nBoundary(alias, \"Label\", \"type\") { ... }\n```\n\n### Relationships\n```\nRel(from, to, \"Label\")\nRel(from, to, \"Label\", \"Technology\")\nBiRel(from, to, \"Label\")                        # Bidirectional\nRel_U(from, to, \"Label\")                        # Upward\nRel_D(from, to, \"Label\")                        # Downward\nRel_L(from, to, \"Label\")                        # Leftward\nRel_R(from, to, \"Label\")                        # Rightward\n```\n\n### Deployment Nodes\n```\nDeployment_Node(alias, \"Label\", \"Type\", \"Description\") { ... }\nNode(alias, \"Label\", \"Type\", \"Description\") { ... }  # Shorthand\n```\n\n## Styling and Layout\n\n### Layout Configuration\n```\nUpdateLayoutConfig($c4ShapeInRow=\"3\", $c4BoundaryInRow=\"1\")\n```\n- `$c4ShapeInRow` - Number of shapes per row (default: 4)\n- `$c4BoundaryInRow` - Number of boundaries per row (default: 2)\n\n### Element Styling\n```\nUpdateElementStyle(alias, $fontColor=\"red\", $bgColor=\"grey\", $borderColor=\"red\")\n```\n\n### Relationship Styling\n```\nUpdateRelStyle(from, to, $textColor=\"blue\", $lineColor=\"blue\", $offsetX=\"5\", $offsetY=\"-10\")\n```\nUse `$offsetX` and `$offsetY` to fix overlapping relationship labels.\n\n## Best Practices\n\n### Essential Rules\n\n1. **Every element must have**: Name, Type, Technology (where applicable), and Description\n2. **Use unidirectional arrows only** - Bidirectional arrows create ambiguity\n3. **Label arrows with action verbs** - \"Sends email using\", \"Reads from\", not just \"uses\"\n4. **Include technology labels** - \"JSON\u002FHTTPS\", \"JDBC\", \"gRPC\"\n5. **Stay under 20 elements per diagram** - Split complex systems into multiple diagrams\n\n### Clarity Guidelines\n\n1. **Start at Level 1** - Context diagrams help frame the system scope\n2. **One diagram per file** - Keep diagrams focused on a single abstraction level\n3. **Meaningful aliases** - Use descriptive aliases (e.g., `orderService` not `s1`)\n4. **Concise descriptions** - Keep descriptions under 50 characters when possible\n5. **Always include a title** - \"System Context diagram for [System Name]\"\n\n### What to Avoid\n\nSee [references\u002Fcommon-mistakes.md](references\u002Fcommon-mistakes.md) for detailed anti-patterns:\n- Confusing containers (deployable) vs components (non-deployable)\n- Modeling shared libraries as containers\n- Showing message brokers as single containers instead of individual topics\n- Adding undefined abstraction levels like \"subcomponents\"\n- Removing type labels to \"simplify\" diagrams\n\n## Microservices Guidelines\n\n### Single Team Ownership\nModel each microservice as a **container** (or container group):\n```mermaid\nC4Container\n  title Microservices - Single Team\n\n  System_Boundary(platform, \"E-commerce Platform\") {\n    Container(orderApi, \"Order Service\", \"Spring Boot\", \"Order processing\")\n    ContainerDb(orderDb, \"Order DB\", \"PostgreSQL\", \"Order data\")\n    Container(inventoryApi, \"Inventory Service\", \"Node.js\", \"Stock management\")\n    ContainerDb(inventoryDb, \"Inventory DB\", \"MongoDB\", \"Stock data\")\n  }\n```\n\n### Multi-Team Ownership\nPromote microservices to **software systems** when owned by separate teams:\n```mermaid\nC4Context\n  title Microservices - Multi-Team\n\n  Person(customer, \"Customer\", \"Places orders\")\n  System(orderSystem, \"Order System\", \"Team Alpha\")\n  System(inventorySystem, \"Inventory System\", \"Team Beta\")\n  System(paymentSystem, \"Payment System\", \"Team Gamma\")\n\n  Rel(customer, orderSystem, \"Places orders\")\n  Rel(orderSystem, inventorySystem, \"Checks stock\")\n  Rel(orderSystem, paymentSystem, \"Processes payment\")\n```\n\n### Event-Driven Architecture\nShow individual topics\u002Fqueues as containers, NOT a single \"Kafka\" box:\n```mermaid\nC4Container\n  title Event-Driven Architecture\n\n  Container(orderService, \"Order Service\", \"Java\", \"Creates orders\")\n  Container(stockService, \"Stock Service\", \"Java\", \"Manages inventory\")\n  ContainerQueue(orderTopic, \"order.created\", \"Kafka\", \"Order events\")\n  ContainerQueue(stockTopic, \"stock.reserved\", \"Kafka\", \"Stock events\")\n\n  Rel(orderService, orderTopic, \"Publishes to\")\n  Rel(stockService, orderTopic, \"Subscribes to\")\n  Rel(stockService, stockTopic, \"Publishes to\")\n  Rel(orderService, stockTopic, \"Subscribes to\")\n```\n\n## Output Location\n\nWrite architecture documentation to `docs\u002Farchitecture\u002F` with naming convention:\n- `c4-context.md` - System context diagram\n- `c4-containers.md` - Container diagram\n- `c4-components-{feature}.md` - Component diagrams per feature\n- `c4-deployment.md` - Deployment diagram\n- `c4-dynamic-{flow}.md` - Dynamic diagrams for specific flows\n\n## Audience-Appropriate Detail\n\n| Audience | Recommended Diagrams |\n|----------|---------------------|\n| Executives | System Context only |\n| Product Managers | Context + Container |\n| Architects | Context + Container + key Components |\n| Developers | All levels as needed |\n| DevOps | Container + Deployment |\n\n## References\n\n- [references\u002Fc4-syntax.md](references\u002Fc4-syntax.md) - Complete Mermaid C4 syntax\n- [references\u002Fcommon-mistakes.md](references\u002Fcommon-mistakes.md) - Anti-patterns to avoid\n- [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) - Microservices, event-driven, deployment\n","# C4 Architecture Documentation\n\nGenerate software architecture documentation using C4 model diagrams in Mermaid syntax.\n\n## Workflow\n\n1. **Understand scope** - Determine which C4 level(s) are needed based on audience\n2. **Analyze codebase** - Explore the system to identify components, containers, and relationships\n3. **Generate diagrams** - Create Mermaid C4 diagrams at appropriate abstraction levels\n4. **Document** - Write diagrams to markdown files with explanatory context\n\n## C4 Diagram Levels\n\nSelect the appropriate level based on the documentation need:\n\n| Level | Diagram Type | Audience | Shows | When to Create |\n|-------|-------------|----------|-------|----------------|\n| 1 | **C4Context** | Everyone | System + external actors | Always (required) |\n| 2 | **C4Container** | Technical | Apps, databases, services | Always (required) |\n| 3 | **C4Component** | Developers | Internal components | Only if adds value |\n| 4 | **C4Deployment** | DevOps | Infrastructure nodes | For production systems |\n| - | **C4Dynamic** | Technical | Request flows (numbered) | For complex workflows |\n\n**Key Insight:** \"Context + Container diagrams are sufficient for most software development teams.\" Only create Component\u002FCode diagrams when they genuinely add value.\n\n## Quick Start Examples\n\n### System Context (Level 1)\n```mermaid\nC4Context\n  title System Context - Workout Tracker\n\n  Person(user, \"User\", \"Tracks workouts and exercises\")\n  System(app, \"Workout Tracker\", \"Vue PWA for tracking strength and CrossFit workouts\")\n  System_Ext(browser, \"Web Browser\", \"Stores data in IndexedDB\")\n\n  Rel(user, app, \"Uses\")\n  Rel(app, browser, \"Persists data to\", \"IndexedDB\")\n```\n\n### Container Diagram (Level 2)\n```mermaid\nC4Container\n  title Container Diagram - Workout Tracker\n\n  Person(user, \"User\", \"Tracks workouts\")\n\n  Container_Boundary(app, \"Workout Tracker PWA\") {\n    Container(spa, \"SPA\", \"Vue 3, TypeScript\", \"Single-page application\")\n    Container(pinia, \"State Management\", \"Pinia\", \"Manages application state\")\n    ContainerDb(indexeddb, \"IndexedDB\", \"Dexie\", \"Local workout storage\")\n  }\n\n  Rel(user, spa, \"Uses\")\n  Rel(spa, pinia, \"Reads\u002Fwrites state\")\n  Rel(pinia, indexeddb, \"Persists\", \"Dexie ORM\")\n```\n\n### Component Diagram (Level 3)\n```mermaid\nC4Component\n  title Component Diagram - Workout Feature\n\n  Container(views, \"Views\", \"Vue Router pages\")\n\n  Container_Boundary(workout, \"Workout Feature\") {\n    Component(useWorkout, \"useWorkout\", \"Composable\", \"Workout execution state\")\n    Component(useTimer, \"useTimer\", \"Composable\", \"Timer state machine\")\n    Component(workoutRepo, \"WorkoutRepository\", \"Dexie\", \"Workout persistence\")\n  }\n\n  Rel(views, useWorkout, \"Uses\")\n  Rel(useWorkout, useTimer, \"Controls\")\n  Rel(useWorkout, workoutRepo, \"Saves to\")\n```\n\n### Dynamic Diagram (Request Flow)\n```mermaid\nC4Dynamic\n  title Dynamic Diagram - User Sign In Flow\n\n  ContainerDb(db, \"Database\", \"PostgreSQL\", \"User credentials\")\n  Container(spa, \"Single-Page App\", \"React\", \"Banking UI\")\n\n  Container_Boundary(api, \"API Application\") {\n    Component(signIn, \"Sign In Controller\", \"Express\", \"Auth endpoint\")\n    Component(security, \"Security Service\", \"JWT\", \"Validates credentials\")\n  }\n\n  Rel(spa, signIn, \"1. Submit credentials\", \"JSON\u002FHTTPS\")\n  Rel(signIn, security, \"2. Validate\")\n  Rel(security, db, \"3. Query user\", \"SQL\")\n\n  UpdateRelStyle(spa, signIn, $textColor=\"blue\", $offsetY=\"-30\")\n```\n\n### Deployment Diagram\n```mermaid\nC4Deployment\n  title Deployment Diagram - Production\n\n  Deployment_Node(browser, \"Customer Browser\", \"Chrome\u002FFirefox\") {\n    Container(spa, \"SPA\", \"React\", \"Web application\")\n  }\n\n  Deployment_Node(aws, \"AWS Cloud\", \"us-east-1\") {\n    Deployment_Node(ecs, \"ECS Cluster\", \"Fargate\") {\n      Container(api, \"API Service\", \"Node.js\", \"REST API\")\n    }\n    Deployment_Node(rds, \"RDS\", \"db.r5.large\") {\n      ContainerDb(db, \"Database\", \"PostgreSQL\", \"Application data\")\n    }\n  }\n\n  Rel(spa, api, \"API calls\", \"HTTPS\")\n  Rel(api, db, \"Reads\u002Fwrites\", \"JDBC\")\n```\n\n## Element Syntax\n\n### People and Systems\n```\nPerson(alias, \"Label\", \"Description\")\nPerson_Ext(alias, \"Label\", \"Description\")       # External person\nSystem(alias, \"Label\", \"Description\")\nSystem_Ext(alias, \"Label\", \"Description\")       # External system\nSystemDb(alias, \"Label\", \"Description\")         # Database system\nSystemQueue(alias, \"Label\", \"Description\")      # Queue system\n```\n\n### Containers\n```\nContainer(alias, \"Label\", \"Technology\", \"Description\")\nContainer_Ext(alias, \"Label\", \"Technology\", \"Description\")\nContainerDb(alias, \"Label\", \"Technology\", \"Description\")\nContainerQueue(alias, \"Label\", \"Technology\", \"Description\")\n```\n\n### Components\n```\nComponent(alias, \"Label\", \"Technology\", \"Description\")\nComponent_Ext(alias, \"Label\", \"Technology\", \"Description\")\nComponentDb(alias, \"Label\", \"Technology\", \"Description\")\n```\n\n### Boundaries\n```\nEnterprise_Boundary(alias, \"Label\") { ... }\nSystem_Boundary(alias, \"Label\") { ... }\nContainer_Boundary(alias, \"Label\") { ... }\nBoundary(alias, \"Label\", \"type\") { ... }\n```\n\n### Relationships\n```\nRel(from, to, \"Label\")\nRel(from, to, \"Label\", \"Technology\")\nBiRel(from, to, \"Label\")                        # Bidirectional\nRel_U(from, to, \"Label\")                        # Upward\nRel_D(from, to, \"Label\")                        # Downward\nRel_L(from, to, \"Label\")                        # Leftward\nRel_R(from, to, \"Label\")                        # Rightward\n```\n\n### Deployment Nodes\n```\nDeployment_Node(alias, \"Label\", \"Type\", \"Description\") { ... }\nNode(alias, \"Label\", \"Type\", \"Description\") { ... }  # Shorthand\n```\n\n## Styling and Layout\n\n### Layout Configuration\n```\nUpdateLayoutConfig($c4ShapeInRow=\"3\", $c4BoundaryInRow=\"1\")\n```\n- `$c4ShapeInRow` - Number of shapes per row (default: 4)\n- `$c4BoundaryInRow` - Number of boundaries per row (default: 2)\n\n### Element Styling\n```\nUpdateElementStyle(alias, $fontColor=\"red\", $bgColor=\"grey\", $borderColor=\"red\")\n```\n\n### Relationship Styling\n```\nUpdateRelStyle(from, to, $textColor=\"blue\", $lineColor=\"blue\", $offsetX=\"5\", $offsetY=\"-10\")\n```\nUse `$offsetX` and `$offsetY` to fix overlapping relationship labels.\n\n## Best Practices\n\n### Essential Rules\n\n1. **Every element must have**: Name, Type, Technology (where applicable), and Description\n2. **Use unidirectional arrows only** - Bidirectional arrows create ambiguity\n3. **Label arrows with action verbs** - \"Sends email using\", \"Reads from\", not just \"uses\"\n4. **Include technology labels** - \"JSON\u002FHTTPS\", \"JDBC\", \"gRPC\"\n5. **Stay under 20 elements per diagram** - Split complex systems into multiple diagrams\n\n### Clarity Guidelines\n\n1. **Start at Level 1** - Context diagrams help frame the system scope\n2. **One diagram per file** - Keep diagrams focused on a single abstraction level\n3. **Meaningful aliases** - Use descriptive aliases (e.g., `orderService` not `s1`)\n4. **Concise descriptions** - Keep descriptions under 50 characters when possible\n5. **Always include a title** - \"System Context diagram for [System Name]\"\n\n### What to Avoid\n\nSee [references\u002Fcommon-mistakes.md](references\u002Fcommon-mistakes.md) for detailed anti-patterns:\n- Confusing containers (deployable) vs components (non-deployable)\n- Modeling shared libraries as containers\n- Showing message brokers as single containers instead of individual topics\n- Adding undefined abstraction levels like \"subcomponents\"\n- Removing type labels to \"simplify\" diagrams\n\n## Microservices Guidelines\n\n### Single Team Ownership\nModel each microservice as a **container** (or container group):\n```mermaid\nC4Container\n  title Microservices - Single Team\n\n  System_Boundary(platform, \"E-commerce Platform\") {\n    Container(orderApi, \"Order Service\", \"Spring Boot\", \"Order processing\")\n    ContainerDb(orderDb, \"Order DB\", \"PostgreSQL\", \"Order data\")\n    Container(inventoryApi, \"Inventory Service\", \"Node.js\", \"Stock management\")\n    ContainerDb(inventoryDb, \"Inventory DB\", \"MongoDB\", \"Stock data\")\n  }\n```\n\n### Multi-Team Ownership\nPromote microservices to **software systems** when owned by separate teams:\n```mermaid\nC4Context\n  title Microservices - Multi-Team\n\n  Person(customer, \"Customer\", \"Places orders\")\n  System(orderSystem, \"Order System\", \"Team Alpha\")\n  System(inventorySystem, \"Inventory System\", \"Team Beta\")\n  System(paymentSystem, \"Payment System\", \"Team Gamma\")\n\n  Rel(customer, orderSystem, \"Places orders\")\n  Rel(orderSystem, inventorySystem, \"Checks stock\")\n  Rel(orderSystem, paymentSystem, \"Processes payment\")\n```\n\n### Event-Driven Architecture\nShow individual topics\u002Fqueues as containers, NOT a single \"Kafka\" box:\n```mermaid\nC4Container\n  title Event-Driven Architecture\n\n  Container(orderService, \"Order Service\", \"Java\", \"Creates orders\")\n  Container(stockService, \"Stock Service\", \"Java\", \"Manages inventory\")\n  ContainerQueue(orderTopic, \"order.created\", \"Kafka\", \"Order events\")\n  ContainerQueue(stockTopic, \"stock.reserved\", \"Kafka\", \"Stock events\")\n\n  Rel(orderService, orderTopic, \"Publishes to\")\n  Rel(stockService, orderTopic, \"Subscribes to\")\n  Rel(stockService, stockTopic, \"Publishes to\")\n  Rel(orderService, stockTopic, \"Subscribes to\")\n```\n\n## Output Location\n\nWrite architecture documentation to `docs\u002Farchitecture\u002F` with naming convention:\n- `c4-context.md` - System context diagram\n- `c4-containers.md` - Container diagram\n- `c4-components-{feature}.md` - Component diagrams per feature\n- `c4-deployment.md` - Deployment diagram\n- `c4-dynamic-{flow}.md` - Dynamic diagrams for specific flows\n\n## Audience-Appropriate Detail\n\n| Audience | Recommended Diagrams |\n|----------|---------------------|\n| Executives | System Context only |\n| Product Managers | Context + Container |\n| Architects | Context + Container + key Components |\n| Developers | All levels as needed |\n| DevOps | Container + Deployment |\n\n## References\n\n- [references\u002Fc4-syntax.md](references\u002Fc4-syntax.md) - Complete Mermaid C4 syntax\n- [references\u002Fcommon-mistakes.md](references\u002Fcommon-mistakes.md) - Anti-patterns to avoid\n- [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) - Microservices, event-driven, deployment\n",{"name":5,"description":7},"main","d8518247cb8ab8b2dac57a6be33543ffd23b97c5","code-mermaid\u002Fsoftaworks\u002Fc4-architecture",0,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry","https:\u002F\u002Fgithub.com\u002Fmattonweb","2026-05-29 08:42:23",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add mattonweb\u002Fai-assistant-foundry --skill c4-architecture",{"tool":57,"command":58},"bunx","bunx skills add mattonweb\u002Fai-assistant-foundry --skill c4-architecture",{"tool":60,"command":61},"pnpm","pnpm dlx skills add mattonweb\u002Fai-assistant-foundry --skill c4-architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fcode-mermaid\u002Fsoftaworks\u002Fc4-architecture\u002FSKILL.md",true,[65,71,75,79],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"README.md","REFERENCE","参考文档",7072,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fcode-mermaid\u002Fsoftaworks\u002Fc4-architecture\u002FREADME.md",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fadvanced-patterns.md",18346,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fcode-mermaid\u002Fsoftaworks\u002Fc4-architecture\u002Freferences\u002Fadvanced-patterns.md",{"path":76,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fc4-syntax.md",14564,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fcode-mermaid\u002Fsoftaworks\u002Fc4-architecture\u002Freferences\u002Fc4-syntax.md",{"path":80,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fcommon-mistakes.md",12443,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fcode-mermaid\u002Fsoftaworks\u002Fc4-architecture\u002Freferences\u002Fcommon-mistakes.md",[84,120,134,154,175,199],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":100,"publishedAt":39},"01M6P02DENRHN6KVGYC55FKASJ","writing-clearly-and-concisely","Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fwriting-clearly-and-concisely\u002FSKILL.md",[90,95],{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":96,"categoryName":97,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,37,119],"writing clearly and concisely","writing","concisely","text","for","more","timeless","error","professional","prose","reports","use","read","Rules","commit messages","messages","error messages","ui","commit",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":39},"01M6P0286HZ8RWMFCCPC8HF7SC","crafting-effective-readmes","Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fcrafting-effective-readmes\u002FSKILL.md",[],[127,128,102,129,130,112,131,132,133],"crafting effective readmes","README","templates","type","project","guidance","files",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":143,"publishedAt":39},"01M6P025A41BBTPWVTZ3GFQVG6","wiki-architect","You are a documentation architect that produces structured wiki catalogues and onboarding guides from codebases.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsickn33\u002Fwiki-architect\u002FSKILL.md",[140],{"categoryNo":141,"categoryName":142,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000038","人力资源",[144,145,146,147,148,149,150,151,152,153,37],"wiki","architect","wiki architect","unknown","you","documentation architect","guides","structured","community","onboarding",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":39},"01M6P01NSKPXP77NWB4K0PXRK5","readme","You are an expert technical writer creating comprehensive project documentation. Your goal is to write a README.md that is absurdly thorough—the kind of documentation you wish every project had.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsickn33\u002Freadme\u002FSKILL.md",[],[128,161,162,163,148,164,165,131,166,167,44,168,169,170,171,172,37,173,174],"project documentation","tree","kind","expert","github","wish","writer","goal","write","technical writer","technical","https","write a readme","safe",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":39},"01M6P01GP0NEN8KT3A3SA6ZFVE","ubiquitous-language","Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions \"domain model\" or \"DDD\".","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fmattpocock\u002Fubiquitous-language\u002FSKILL.md",[],[182,183,112,184,185,186,27,187,188,21,189,190,191,192,193,194,195,196,197,198],"ubiquitous language","language","extract","user","glossary","terms","ddd","build","true","canonical","style","define","harden","domain model","domain","terminology","conversation",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":207,"publishedAt":39},"01M6P01BJBP9XP4TDRT7QD1ZVA","technical-writing-style","Enforce clear, direct writing in software development documents including OKRs, PRDs, tech specs, architecture decision records (ADRs), git commit messages, PR descriptions, READMEs, changelogs, runbooks, incident postmortems, API docs, and onboarding guides. Trigger whenever a user asks to write, edit, revise, or review any of these document types. Also trigger when the user says writing \"sounds like AI\", \"feels robotic\", \"needs polish\", or asks to \"make it sound more natural\" in the context of technical or professional prose. Do not trigger for fiction, poetry, creative writing, academic papers, or legal documents unless the user explicitly asks for a more natural tone.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fmattnebr\u002Ftechnical-writing-style\u002FSKILL.md",[205,206],{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},{"categoryNo":96,"categoryName":97,"taxonomyType":98,"taxonomyTypeDesc":99},[208,209,192,171,102,210,109,211,212,213,214,215,216,217,218,116,219,19,119,220],"writing style","technical writing style","technical writing","papers","types","runbooks","software development","incident","Poetry","decision","api","documents","review"]