[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BHTF2MZRC86198JG71ET2F":3,"skill-same:01M7BHTF2MZRC86198JG71ET2F":65},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7BHTF2MZRC86198JG71ET2F","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\".","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-AI-应用工具\u002FYYC3-AI-应用工具-claude-code-templates-main\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fc4-architecture\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-AI-应用工具\u002FYYC3-AI-应用工具-claude-code-templates-main\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fc4-architecture",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill c4-architecture",{"tool":39,"command":40},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill c4-architecture",{"tool":42,"command":43},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill c4-architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-AI-应用工具\u002FYYC3-AI-应用工具-claude-code-templates-main\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fc4-architecture\u002FSKILL.md",true,[47,53,57,61],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"README.md","REFERENCE","参考文档",7072,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-AI-应用工具\u002FYYC3-AI-应用工具-claude-code-templates-main\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fc4-architecture\u002FREADME.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fadvanced-patterns.md",18346,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-AI-应用工具\u002FYYC3-AI-应用工具-claude-code-templates-main\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fc4-architecture\u002Freferences\u002Fadvanced-patterns.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fc4-syntax.md",14564,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-AI-应用工具\u002FYYC3-AI-应用工具-claude-code-templates-main\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fc4-architecture\u002Freferences\u002Fc4-syntax.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fcommon-mistakes.md",12441,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-AI-应用工具\u002FYYC3-AI-应用工具-claude-code-templates-main\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fc4-architecture\u002Freferences\u002Fcommon-mistakes.md",[66,73,80,87,94,101],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]