llms.txt is an open proposal for a short Markdown file that lists a project's key docs and links, so AI tools can find them without crawling every page.

Where should llms.txt be deployed?

At /llms.txt on your documentation site, or in your repository root. Tools read it when they fetch it; nothing loads it automatically.

# Production Docker & Containerization Engineer

> Production containerization standards. Enforces multi-stage builds, non-root runtime users, layer caching, and health checks.

## Quick Reference

- **Framework**: Docker / Kubernetes / GitHub Actions

- **Language**: Dockerfile / Bash / YAML

- **Styling & UI**: None

- **Database / Persistence**: PostgreSQL / Redis Containers

- **Architectural Philosophy**: strict

## Core Architectural Invariants

- **Clean Layered Architecture**: Decouple presentation, business logic, and data access layers via interfaces.

- **Guard Clauses & Early Returns**: Exit early from functions to eliminate deeply nested if-else pyramids.

## Operational Guardrails & Prohibited Patterns

- **Inspect Before Acting**: Always read and understand existing code and imports before suggesting changes.

- **Dependency Caution**: Never introduce new third-party libraries or packages without explicit approval.

- **Propose Verification Steps**: With every modification, specify concrete commands or tests to verify correctness.

## Mandatory Project Directives

- Never run production application containers as root.

- Never include development tooling (compilers, git) in final runtime images.

## Implementation Reference

### Preferred Patterns

```bash

# Good: Lean multi-stage build with non-root user

FROM node:20-alpine AS builder

WORKDIR /app

COPY package*.json ./

RUN npm ci

COPY . .

RUN npm run build

FROM node:20-alpine AS runner

WORKDIR /app

ENV NODE_ENV=production

RUN addgroup -g 1001 -S nodejs && adduser -S nextjs -u 1001

COPY --from=builder --chown=nextjs:nodejs /app/dist ./dist

USER nextjs

EXPOSE 3000

CMD ["node", "dist/index.js"]

```

### Discouraged Anti-Patterns

```bash

# Discouraged: Bloated single-stage build running as root

FROM node:20

WORKDIR /app

COPY . .

RUN npm install

CMD ["npm", "start"]

```

## Verification Commands & Workflows

1. Always construct multi-stage Dockerfiles with separate build and minimal runtime stages.

2. Create and switch to a dedicated non-root user (e.g. USER node or USER app).

3. Copy dependency lockfiles before source files to maximize Docker layer caching.

4. Add HEALTHCHECK instruction to verify container readiness in production.

## Context Documents & Specs

- [System Architecture](ARCHITECTURE.md): Authoritative system design, data flows, and state machine invariants.

- [AI Multi-Agent Spec](AGENTS.md): Universal specification for autonomous coding agent operations.

DevOps & Tooling · Any LLM tool that fetches it

Docker & CI/CD llms.txt

An llms.txt for a Docker & CI/CD project: a short Markdown map of what it is and where the key docs and code live.

Path: llms.txt
Loads: Fetched on request
Format: Markdown index (.txt)
Used by: Any LLM tool that fetches it

All llms.txt presets and how llms.txt works

What this file tells the agent

An llms.txt gives language models and agents a short Markdown map of your Docker & CI/CD project: what it is and where the key docs and code live, so a tool that fetches it can go straight to the right files.

Always use multi-stage Docker builds to separate builder tools from the lean production image.
Never run containers as root; create and switch to a non-privileged user (`USER node` or `USER app`).
Pin base image versions explicitly; avoid mutable `:latest` tags.
Leverage layer caching by copying package manifests before source code.

Install it in one command

01
Go to your project root
The file goes at llms.txt, relative to the root.
02
Download the file
Run the command on the right. It downloads this preset and writes the file.
03
Make sure it gets used
Nothing loads llms.txt automatically. Serve it at your site root, or point agents to it from CLAUDE.md or AGENTS.md.

$ curl -fsSL "https://www.devscratchpad.tech/api/raw/llms-txt/docker-devops" -o "llms.txt"

writes llms.txt

path

llms.txt

To write the file from your own code instead, use Read your code or Convert Legacy Rules in the editor above.

More for Docker & CI/CD

Other formats

Other llms.txt presets

Questions

What is llms.txt?: llms.txt is an open proposal for a short Markdown file that lists a project's key docs and links, so AI tools can find them without crawling every page.
Where should llms.txt be deployed?: At /llms.txt on your documentation site, or in your repository root. Tools read it when they fetch it; nothing loads it automatically.

Target Standard & File Format

Identity & Activation Rules

Technology Stack Context

Engineering Philosophy

Architectural & Code Quality Conventions

Agent Behavioral Guardrails

Step-by-Step Workflow Procedures

Target File Location

Docker & CI/CD llms.txt

What this file tells the agent

Install it in one command

Go to your project root

Download the file

Make sure it gets used

More for Docker & CI/CD

Other formats

Other llms.txt presets

Questions