Prompt

Software EngineeringPromptIn a pack

Dockerfile Hardening and Multi-Stage Build for Any Language

Rewrites a Dockerfile into a small, cached, reproducible multi-stage build that runs as non-root, with a .dockerignore, health check and a scan step in CI.

  • Role-Based
  • Step-by-Step
  • Constraints
  • Structured Output

Opening lines · ~298 words in full

ROLE: You are a container security and build engineer. You make images small because small images build faster and expose less, you order layers for caching, and you never ship compilers or secrets to production.

CONTEXT: The current Dockerfile: [DOCKERFILE]. Language, framework and package …

Written by the PromptCorrectly team© 2026 PromptCorrectly · All rights reserved

How to use it

  1. Read it, then replace anything in [BRACKETS] with your details — the more concrete the context, the sharper the answer.
  2. Copy it (or download the .md) and paste it into the AI you already use — it knows your work, so that is where the prompt does the most.
  3. Want a sharper answer? Ask the AI to check its own draft against your brief before it replies — that is self-critique prompting.

Techniques in this prompt

Role-Based

Assigns the model an expert persona so it adopts the right vocabulary, depth, and standards for the task.

Learn this technique
Step-by-Step

Forces explicit intermediate reasoning instead of jumping to a conclusion, which improves accuracy on hard tasks.

Learn this technique
Constraints

Sets the rules and boundaries — tone, length, what to avoid — that keep the output on-target.

Learn this technique
Structured Output

Pins the response to a defined structure so it drops straight into your workflow.

Learn this technique

Works with

Any chat AI — ChatGPT, Claude, Gemini, Copilot, Grok, Mistral or a local model. The structure does the work, so you are not tied to one vendor or one model version.

New to structured prompts? Start with how to prompt AI, the RCTCO prompt framework this prompt is built on, and role prompting examples.

More in Software Engineering

Production Incident Root Cause AnalysisDrives a disciplined RCA from symptoms to root cause and prevention, separating contributing factors from the true trigger.Security-Focused Code Review For Pull RequestsReviews a diff specifically for security vulnerabilities, mapping findings to severity, exploit path, and concrete fixes.Legacy Code Refactoring StrategistPlans a safe, incremental refactor of tangled legacy code with characterization tests and reversible seams.API Contract Designer With OpenAPI OutputDesigns a consistent, versioned REST resource and emits a ready-to-use OpenAPI 3.1 fragment plus error model.