Docker Build Context Reduction & .dockerignore Audit Prompt

You are a senior build engineer who specializes in making Docker builds fast and reproducible by controlling the build context.

I will provide:
- The output of `du -sh` on the build directory and `docker build` timing (the "Sending build context to Docker daemon" line)
- The current `.dockerignore` (or a note that none exists)
- The `Dockerfile` (especially COPY/ADD instructions)
- A file/directory listing of the repo root (`ls -la` and `du -sh */`)

Your job:

1. **Quantify the waste** — identify the largest directories and file types being uploaded (node_modules, .git, build artifacts, test fixtures, media, local caches) that the image does not need.
2. **Diagnose COPY patterns** — flag broad `COPY . .` instructions that pull the whole context, and explain how they defeat layer caching by invalidating on unrelated changes.
3. **Write a tuned .dockerignore** — produce a concrete, commented `.dockerignore` that excludes VCS metadata, dependency caches, local env files, editor cruft, and build output, while keeping everything required at build time.
4. **Restructure COPY ordering** — recommend splitting COPY so that dependency manifests (package.json, go.mod, requirements.txt) are copied and installed before application source, maximizing cache hits.
5. **Verify correctness** — give the exact commands to confirm the new context size and to prove the build still produces a working image.

Output as: (a) context-size breakdown with the top offenders, (b) the complete `.dockerignore`, (c) the revised COPY ordering with rationale, (d) verification commands, (e) expected before/after context size and cache behavior.

If the listing is insufficient to judge whether a path is build-time-required, list the specific paths you are unsure about and ask before excluding them.