docker-cloud
Skill2 starsChanged 31 days agoMITView on GitHub
Implements Dockerfiles, Compose, preview deploys, health checks, and rollback-safe cloud configuration
- Reads credentials
In this repository52 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/00-core-operating-model.mdcCursor rule
- .cursor/rules/01-plan-approval-gate.mdcCursor rule
- .cursor/rules/02-git-worktree-policy.mdcCursor rule
- .cursor/rules/03-validation-definition-of-done.mdcCursor rule
- .cursor/rules/04-documentation-memory.mdcCursor rule
- accessibility-reviewSkill
- agent-skills-packagingSkill
- autonomy-budgetSkill
- bounded-autonomySkill
- candidate-promotionSkill
- capability-planningSkill
- code-reviewerSkill
- code-structure-cleanupSkill
- compass-evaluatorSkill
- context-inodesSkill
- dependency-supply-chainSkill
- embedding-providersSkill
- execution-telemetrySkill
- experience-routingSkill
- experience-skill-trainingSkill
- external-knowledge-ingestSkill
- github-integrationSkill
- goose-agent-orchestrationSkill
- harness-gcSkill
- hosted-vector-dbSkill
- implementation-planningSkill
- ios-engineeringSkill
- knowledge-stewardSkill
- linear-integrationSkill
- node-engineeringSkill
- northstar-connected-routineSkill
- notion-integrationSkill
- package-registry-tiSkill
- persistent-role-promotionSkill
- playwright-browser-validationSkill
- postgres-prismaSkill
- procedure-playbooksSkill
- project-overseerSkill
- pull-request-preparationSkill
- python-mlSkill
- react-engineeringSkill
- repository-discoverySkill
- review-fix-loopSkill
- security-audit-proceduresSkill
- security-reviewSkill
- skill-learning-loopSkill
- skill-lifecycleSkill
- source-code-contextSkill
- technology-intelligence-liveSkill
- testing-validationSkill
- worktree-orchestrationSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 20
Prefer the project's existing container and cloud conventions.
- Distinctive: line 21
Keep images minimal and reproducible (pinned base tags when practical).
- Distinctive: line 23
Add health checks and sensible restart policies for services that need them.
- Very specific: line 26
Document required env vars in .env.example and TESTING.md / PROJECT_CONTEXT.md.
- Distinctive: line 27
Write rollback steps (previous image tag, compose down, redeploy prior revision).
- Distinctive: line 35
Do not deploy to production or run destructive cloud operations without Captain approval.
- Very specific: line 36
Do not commit cloud credentials, kubeconfigs, or .env files.
- Distinctive: line 37
Do not expose debug ports or disable TLS "temporarily" in shared environments.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Docker and Cloud Previews
Use this Skill when
Working on Dockerfiles, Docker Compose, container health checks, preview deployments, deployment manifests, or cloud configuration for non-production environments.
Inputs
- Approved IMPLEMENTATION_PLAN.md (deployment + rollback sections)
- Existing Dockerfile / Compose / cloud config
- Environment separation from PROJECT_CONTEXT.md
Procedure
- Prefer the project's existing container and cloud conventions.
- Keep images minimal and reproducible (pinned base tags when practical).
- Separate build-time and runtime secrets; never bake secrets into images.
- Add health checks and sensible restart policies for services that need them.
- For cloud previews: create/update preview environments only; do not touch production without explicit Captain approval.
- Capture deploy logs and URLs under
.agent/evidence/deployment/when available. - Document required env vars in
.env.exampleand TESTING.md / PROJECT_CONTEXT.md. - Write rollback steps (previous image tag, compose down, redeploy prior revision).
Output
Dockerfile/Compose/cloud config changes, evidence paths, and rollback notes for the First Mate.
Prohibited actions
- Do not deploy to production or run destructive cloud operations without Captain approval.
- Do not commit cloud credentials, kubeconfigs, or
.envfiles. - Do not expose debug ports or disable TLS "temporarily" in shared environments.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.