--- name: c4-container description: "C4 Container Level: System Deployment workflow skill. Use this skill when the user needs Expert C4 Container-level documentation specialist and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off." version: "0.0.1" category: devops tags: ["c4-container", "expert", "container-level", "documentation", "specialist", "devops"] complexity: intermediate risk: caution tools: ["codex-cli", "claude-code", "cursor", "gemini-cli", "opencode"] source: community author: "sickn33" date_added: "2026-04-14" date_updated: "2026-04-25" --- # C4 Container Level: System Deployment ## Overview This public intake copy packages `plugins/antigravity-awesome-skills-claude/skills/c4-container` from `https://github.com/sickn33/antigravity-awesome-skills` into the native Omni Skills editorial shape without hiding its origin. Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow. This intake keeps the copied upstream files intact and uses the `external_source` block in `metadata.json` plus `ORIGIN.md` as the provenance anchor for review. # C4 Container Level: System Deployment Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Containers, Purpose, Components, Interfaces, Dependencies, Infrastructure. ## When to Use This Skill Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request. - Working on c4 container level: system deployment tasks or workflows - Needing guidance, best practices, or checklists for c4 container level: system deployment - The task is unrelated to c4 container level: system deployment - You need a different domain or tool outside this scope - Use when the request clearly matches the imported source intent: Expert C4 Container-level documentation specialist. - Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch. ## Operating Table | Situation | Start here | Why it matters | | --- | --- | --- | | First-time use | `metadata.json` | Confirms repository, branch, commit, and imported path through the `external_source` block before touching the copied workflow | | Provenance review | `ORIGIN.md` | Gives reviewers a plain-language audit trail for the imported source | | Workflow execution | `SKILL.md` | Starts with the smallest copied file that materially changes execution | | Supporting context | `SKILL.md` | Adds the next most relevant copied source file without loading the entire package | | Handoff decision | `## Related Skills` | Helps the operator switch to a stronger native skill when the task drifts | ## Workflow This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow. 1. Clarify goals, constraints, and required inputs. 2. Apply relevant best practices and validate outcomes. 3. Provide actionable steps and verification. 4. If detailed examples are required, open resources/implementation-playbook.md. 5. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task. 6. Read the overview and provenance files before loading any copied upstream support files. 7. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request. ### Imported Workflow Notes #### Imported: Instructions - Clarify goals, constraints, and required inputs. - Apply relevant best practices and validate outcomes. - Provide actionable steps and verification. - If detailed examples are required, open `resources/implementation-playbook.md`. #### Imported: Containers ### [Container Name] - **Name**: [Container name] - **Description**: [Short description of container purpose and deployment] - **Type**: [Web Application, API, Database, Message Queue, etc.] - **Technology**: [Primary technologies: Node.js, Python, PostgreSQL, Redis, etc.] - **Deployment**: [Docker, Kubernetes, Cloud Service, etc.] ## Examples ### Example 1: Ask for the upstream workflow directly ```text Use @c4-container to handle . Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer. ``` **Explanation:** This is the safest starting point when the operator needs the imported workflow, but not the entire repository. ### Example 2: Ask for a provenance-grounded review ```text Review @c4-container against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why. ``` **Explanation:** Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection. ### Example 3: Narrow the copied support files before execution ```text Use @c4-container for . Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding. ``` **Explanation:** This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default. ### Example 4: Build a reviewer packet ```text Review @c4-container using the copied upstream files plus provenance, then summarize any gaps before merge. ``` **Explanation:** This is useful when the PR is waiting for human review and you want a repeatable audit packet. ### Imported Usage Notes #### Imported: Example Interactions - "Synthesize all components into containers based on deployment definitions" - "Map the API components to containers and document their APIs as OpenAPI specs" - "Create container-level documentation for the microservices architecture" - "Document container interfaces as Swagger/OpenAPI specifications" - "Analyze Kubernetes manifests and create container documentation" #### Imported: Output Examples When synthesizing containers, provide: - Clear container boundaries with deployment rationale - Descriptive container names and deployment characteristics - Complete API documentation with OpenAPI/Swagger specifications - Links to all contained components - Mermaid container diagrams showing deployment architecture - Links to deployment configurations (Dockerfiles, K8s manifests, etc.) - Infrastructure requirements and scaling considerations - Consistent documentation format across all containers ## Best Practices Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution. - Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support. - Prefer the smallest useful set of support files so the workflow stays auditable and fast to review. - Keep provenance, source commit, and imported file paths visible in notes and PR descriptions. - Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate. - Treat generated examples as scaffolding; adapt them to the concrete task before execution. - Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant. ## Troubleshooting ### Problem: The operator skipped the imported context and answered too generically **Symptoms:** The result ignores the upstream workflow in `plugins/antigravity-awesome-skills-claude/skills/c4-container`, fails to mention provenance, or does not use any copied source files at all. **Solution:** Re-open `metadata.json`, `ORIGIN.md`, and the most relevant copied upstream files. Check the `external_source` block first, then restate the provenance before continuing. ### Problem: The imported workflow feels incomplete during review **Symptoms:** Reviewers can see the generated `SKILL.md`, but they cannot quickly tell which references, examples, or scripts matter for the current task. **Solution:** Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it. ### Problem: The task drifted into a different specialization **Symptoms:** The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. **Solution:** Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind. ## Related Skills - `@00-andruia-consultant` - Use when the work is better handled by that native specialization after this imported skill establishes context. - `@00-andruia-consultant-v2` - Use when the work is better handled by that native specialization after this imported skill establishes context. - `@10-andruia-skill-smith` - Use when the work is better handled by that native specialization after this imported skill establishes context. - `@10-andruia-skill-smith-v2` - Use when the work is better handled by that native specialization after this imported skill establishes context. ## Additional Resources Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding. | Resource family | What it gives the reviewer | Example path | | --- | --- | --- | | `references` | copied reference notes, guides, or background material from upstream | `references/n/a` | | `examples` | worked examples or reusable prompts copied from upstream | `examples/n/a` | | `scripts` | upstream helper scripts that change execution or validation | `scripts/n/a` | | `agents` | routing or delegation notes that are genuinely part of the imported package | `agents/n/a` | | `assets` | supporting assets or schemas copied from the source package | `assets/n/a` | ### Imported Reference Notes #### Imported: Purpose [Detailed description of what this container does and how it's deployed] #### Imported: Components This container deploys the following components: - [Component Name]: [Description] - Documentation: c4-component-name.md #### Imported: Interfaces ### [API/Interface Name] - **Protocol**: [REST/GraphQL/gRPC/Events/etc.] - **Description**: [What this interface provides] - **Specification**: [Link to OpenAPI/Swagger/API Spec file] - **Endpoints**: - `GET /api/resource` - [Description] - `POST /api/resource` - [Description] #### Imported: Dependencies ### Containers Used - [Container Name]: [How it's used, communication protocol] ### External Systems - [External System]: [How it's used, integration type] #### Imported: Infrastructure - **Deployment Config**: [Link to Dockerfile, K8s manifest, etc.] - **Scaling**: [Horizontal/vertical scaling strategy] - **Resources**: [CPU, memory, storage requirements] #### Imported: Container Diagram Use proper Mermaid C4Container syntax: ```mermaid C4Container title Container Diagram for [System Name] Person(user, "User", "Uses the system") System_Boundary(system, "System Name") { Container(webApp, "Web Application", "Spring Boot, Java", "Provides web interface") Container(api, "API Application", "Node.js, Express", "Provides REST API") ContainerDb(database, "Database", "PostgreSQL", "Stores data") Container_Queue(messageQueue, "Message Queue", "RabbitMQ", "Handles async messaging") } System_Ext(external, "External System", "Third-party service") Rel(user, webApp, "Uses", "HTTPS") Rel(webApp, api, "Makes API calls to", "JSON/HTTPS") Rel(api, database, "Reads from and writes to", "SQL") Rel(api, messageQueue, "Publishes messages to") Rel(api, external, "Uses", "API") ``` ```` **Key Principles** (from [c4model.com](https://c4model.com/diagrams/container)): - Show **high-level technology choices** (this is where technology details belong) - Show how **responsibilities are distributed** across containers - Include **container types**: Applications, Databases, Message Queues, File Systems, etc. - Show **communication protocols** between containers - Include **external systems** that containers interact with ```` #### Imported: API Specification Template For each container API, create an OpenAPI/Swagger specification: ```yaml openapi: 3.1.0 info: title: [Container Name] API description: [API description] version: 1.0.0 servers: - url: https://api.example.com description: Production server paths: /api/resource: get: summary: [Operation summary] description: [Operation description] parameters: - name: param1 in: query schema: type: string responses: '200': description: [Response description] content: application/json: schema: type: object ```` #### Imported: Key Distinctions - **vs C4-Component agent**: Maps components to deployment units; Component agent focuses on logical grouping - **vs C4-Context agent**: Provides container-level detail; Context agent creates high-level system diagrams - **vs C4-Code agent**: Focuses on deployment architecture; Code agent documents individual code elements #### Imported: Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.