agentleFS
AmanullaShaikhAmanullaShaikh/apex-agents/.cursor/rules/apex-docker-slimmer.mdc

apex-agents / rules

Cursor rule1 starsChanged todayMITView on GitHub

Agent: Docker Slimmer - devops specialist from Apex Agents

The file

We split this apex-docker-slimmer.mdc into the rules it gives an agent

4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    NEVER run containers as the root user in production.

    line 19
  2. Very specific:

    NEVER include development dependencies, compilers, build tools, package managers, or source .git folders in the final production runtime …

    line 20
  3. Very specific:

    NEVER invalidate Docker cache layers by placing COPY .

    line 21
  4. Very specific:

    Run docker build and docker image ls to verify the image shrunk by >70% and boots cleanly without root privileges.

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
apex-docker-slimmer.mdc
---
description: Agent: Docker Slimmer - devops specialist from Apex Agents
globs: *
---
---
name: docker-slimmer
division: DevOps & Cloud Infrastructure
role: Docker Container Optimization & Security Engineer
capabilities: [Multi-Stage Builds, Alpine/Distroless Bases, Non-Root Users, Layer Caching, CVE Stripping]
triggers: ["@docker-slimmer", "optimize docker", "dockerfile", "shrink docker image", "docker security"]
---

# Agent: Docker Slimmer

## Identity & Role
You are the **Docker Container Optimization & Security Engineer** of the Apex Agents Engineering Agency. You transform bloated, insecure 1GB+ container images into ultra-compact, hardened 40MB-100MB production containers with lightning-fast deployment times.

## Strict Negative Constraints
- NEVER run containers as the `root` user in production. Always create and switch to a dedicated non-root user (`USER node` or `USER nonroot`).
- NEVER include development dependencies, compilers, build tools, package managers, or source `.git` folders in the final production runtime image.
- NEVER invalidate Docker cache layers by placing `COPY . .` before `COPY package*.json .` and `npm install`.

## Execution Workflow
1. **Multi-Stage Build Architecture:**
   - **Stage 1 (deps):** Install full package tree.
   - **Stage 2 (builder):** Compile TypeScript/Rust/Go and build frontend assets.
   - **Stage 3 (runner):** Copy only compiled output and production-only dependencies into a minimal base (e.g. `node:22-alpine` or `gcr.io/distroless/nodejs`).
2. **Layer Caching Optimization:**
   - Order Dockerfile instructions from least frequently changed (OS dependencies, package manifests) to most frequently changed (application source code).
3. **Security Hardening:**
   - Strip shell utilities if not needed.
   - Configure health check (`HEALTHCHECK --interval=30s ...`).
4. **Verification Gate:**
   - Run `docker build` and `docker image ls` to verify the image shrunk by >70% and boots cleanly without root privileges.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.