菜单
Atmos compositions: named service groupings, compositions.<name>.services, components.container[*].composition, composition validate, and service contract checks
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Component architecture: Terraform root modules, remote source provisioning, abstract components, component inheritance, versioning, mixins, catalog patterns
Atmos emulator components: local AWS/GCP/Azure/Kubernetes/Vault/OpenBao/registry emulators, components.emulator, !emulator, identities, persistence, health checks, and emulator commands
YAML functions: !terraform.state, !terraform.output, !store, !store.get, !secret, !emulator, !env, !exec, !include, !template, !append, !unset, !literal, !random, !aws.*, !git.*, !cwd, !repo-root
JSON Schema for Atmos: stack-manifest and atmos.yaml config schemas, IDE auto-completion, validate stacks/schema/config, SchemaStore integration
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations
Run one full merge-readiness pass on the current branch's PR right now: sync with origin/main, check CI, address CodeRabbit threads, lint, and test coverage — fixing what's safely fixable. Mirrors `atmos fix --all` at the CLI, plus the agent-delegated fixing atmos itself can't do. This is exactly what pr-maintenance-loop runs every hour; invoke this directly for an on-demand check without starting a recurring loop. Invoke on explicit requests like "fix all" / "check this PR" / "is this PR merge-ready".
| name | atmos-compositions |
| description | Atmos compositions: named service groupings, compositions.<name>.services, components.container[*].composition, composition validate, and service contract checks |
| metadata | {"copyright":"Copyright Cloud Posse, LLC 2026","version":"1.0.0"} |
Use this skill for compositions: named groupings of component instances that form a system. Compositions define the service contract; components fulfill services by referencing the composition.
| Need | Load |
|---|---|
| Container components that fulfill services | atmos-container |
| Stack manifest structure | atmos-stacks |
| Workflow orchestration across services | atmos-workflows |
Declare composition service contracts at stack scope:
compositions:
app:
description: Application runtime
services:
- api
- worker
- db
components:
container:
api:
composition: app
worker:
composition: app
The composition describes expected services. Components declare which composition they fulfill.
Use atmos composition validate to inspect whether a stack provides all services for a composition.
atmos composition validate app -s plat-ue2-dev
Validation reports fulfilled and not-provided services. Use this before running workflows that assume a complete multi-service system.
ATMOS_PROFILE.