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.

# Kubernetes & Helm Manifest Validation Specialist

> Cloud-native Kubernetes and Helm rules. Enforces container resource limits, non-root security contexts, readiness probes, and valid YAML indentation.

## Quick Reference

- **Framework**: Kubernetes 1.30+ / Helm 3

- **Language**: YAML / Go Templates

- **Styling & UI**: None / Infrastructure

- **Database / Persistence**: etcd / Cloud Native

- **Architectural Philosophy**: architect

## Core Architectural Invariants

- **Self-Documenting Naming**: Expressive function and variable names over verbose redundant comments.

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

- **Schema-Driven Boundaries**: Validate all external data (API, forms, env) with Zod or Pydantic schemas; on failure, reject with a typed error and never pass unvalidated data onward.

## Operational Guardrails & Prohibited Patterns

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

- **Minimal Surgical Diffs**: Touch only lines relevant to prompt. Preserve existing comments and formatting.

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

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

## Mandatory Project Directives

- Never deploy containers using mutable :latest image tags.

- Always include standard app.kubernetes.io/* metadata labels.

## Implementation Reference

### Preferred Patterns

```go

apiVersion: apps/v1

kind: Deployment

metadata:

name: api-service

labels:

app.kubernetes.io/name: api-service

spec:

replicas: 3

template:

spec:

securityContext:

runAsNonRoot: true

runAsUser: 10001

containers:

- name: api

image: registry.example.com/api:v1.4.0

securityContext:

allowPrivilegeEscalation: false

readOnlyRootFilesystem: true

resources:

requests: { cpu: 100m, memory: 128Mi }

limits: { cpu: 500m, memory: 512Mi }

readinessProbe:

httpGet: { path: /healthz, port: 8080 }

```

### Discouraged Anti-Patterns

```go

apiVersion: apps/v1

kind: Deployment

metadata:

name: bad-service

spec:

template:

spec:

containers:

- name: app

image: myapp:latest # No resource limits, root container, missing probes!

```

## Verification Commands & Workflows

1. Always specify explicit resources.requests and resources.limits on every container.

2. Enforce strict securityContext: runAsNonRoot: true, allowPrivilegeEscalation: false, readOnlyRootFilesystem: true.

3. Configure both livenessProbe and readinessProbe with realistic timeouts and initialDelaySeconds.

4. Format Helm template interpolations using nindent filters to preserve valid YAML indentation.

## 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

Kubernetes & Helm Charts llms.txt

An llms.txt for a Kubernetes & Helm Charts 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 Kubernetes & Helm Charts 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 specify explicit resources.requests and resources.limits (both CPU and memory) on every container.
Enforce strict security contexts: readOnlyRootFilesystem: true, runAsNonRoot: true, and allowPrivilegeEscalation: false.
Mandate both livenessProbe and readinessProbe with appropriate initialDelaySeconds on deployment workloads.
Validate Helm template indentation using nindent filters (e.g. toYaml . | nindent 8) to eliminate YAML formatting corruption.
Configure PodDisruptionBudgets (PDB) and topology spread constraints for multi-node high availability.

Code to avoid, and what to write instead

The rule steers the agent away from the left and toward the right.

avoid

# Dangerous: No resource constraints, root container, missing probes
apiVersion: apps/v1
kind: Deployment
metadata:
  name: bad-service
spec:
  template:
    spec:
      containers:
        - name: app
          image: myapp:latest # Mutable tag and unconstrained limits!

write instead

apiVersion: apps/v1
kind: Deployment
metadata:
  name: api-service
  labels:
    app.kubernetes.io/name: api-service
spec:
  replicas: 3
  template:
    spec:
      securityContext:
        runAsNonRoot: true
        runAsUser: 10001
      containers:
        - name: api
          image: registry.example.com/api:v1.4.0
          securityContext:
            allowPrivilegeEscalation: false
            readOnlyRootFilesystem: true
          resources:
            requests:
              cpu: 100m
              memory: 128Mi
            limits:
              cpu: 500m
              memory: 512Mi
          readinessProbe:
            httpGet:
              path: /healthz
              port: 8080
            initialDelaySeconds: 5

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/kubernetes-helm" -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 Kubernetes & Helm Charts

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

Kubernetes & Helm Charts llms.txt

What this file tells the agent

Code to avoid, and what to write instead

Install it in one command

Go to your project root

Download the file

Make sure it gets used

More for Kubernetes & Helm Charts

Other formats

Other llms.txt presets

Questions