Immediate result: A small multi-stage Dockerfile and .dockerignore for your app, with each line explained.
Problem it solvesHand-written Dockerfiles end up huge, slow to build and running as root.
Next.js 15 app, npm run build then npm start, port 3000
FROM node:22-alpine AS deps … FROM node:22-alpine AS run
USER node — the app never runs as root.
Build: docker build -t web . · Run: docker run -p 3000:3000 web
Hand-written Dockerfiles tend to be huge, slow to rebuild and run as root. This skill writes a multi-stage Dockerfile for your language and framework that caches dependencies separately from source, uses a slim pinned base image, runs as a non-root user and includes a health check. It adds a matching .dockerignore, explains each line and gives the build and run commands. It never bakes secrets into the image and never uses the latest tag, so your builds stay reproducible. It's a sound starting point you can tune for your own registry and deployment.
# Skill: Dockerfile generator
You are running the "Dockerfile generator" skill for me. I work as: DevOps engineer. What I need from you: a small multi-stage Dockerfile and .dockerignore for my app, with each line explained.
## When I send you my language and framework, how I build and start the app, and the port it listens on
1. Pick a slim, pinned base image.
2. Use a multi-stage build that caches dependencies separately from source.
3. Run as a non-root user and add a health check.
4. Write a matching .dockerignore.
## Reply in this format
- Dockerfile (code)
- .dockerignore (code)
- Line-by-line notes
- Build and run commands
## Rules
- Pin versions; never use :latest.
- Never bake secrets into the image.
- Use only the facts I give you; mark anything you had to assume with [ASSUMPTION].
- If something essential is missing, ask me one short question, then continue.
- No preamble or filler: start with the result.
Confirm you're ready in one line, then wait for me to send my language and framework, how I build and start the app, and the port it listens on.Then sendYour language and framework, how you build and start the app, and the port it listens on. For example: Next.js 15 app, npm run build then npm start, port 3000
Upload it to Claude, add it to ChatGPT's Codex app, clone it into Claude Code, or download the SKILL.md for any agent. Full guide with screenshots →
Download the ZIP and upload it in Claude. Claude then uses the skill on its own whenever a request matches.
Download ZIP
OpenAI's Codex app reads the same SKILL.md format. Copy the skill into your Codex skills folder:
$ git -c http.version=HTTP/1.1 clone https://scienceofapps.com/skills/ai-skills.git
$ cp -r ai-skills/dockerfile-generator ~/.codex/skills/
Clone the library and copy this skill into your Claude Code skills folder.
$ git -c http.version=HTTP/1.1 clone https://scienceofapps.com/skills/ai-skills.git
$ cp -r ai-skills/dockerfile-generator ~/.claude/skills/~/.claude/skills/ for all projects, or .claude/skills/ inside one project.Download the skill file and put it in a folder named after the skill.
Download SKILL.md~/.claude/skills/dockerfile-generator/SKILL.md.Repositoryscienceofapps.com/skills/ai-skills.git · all 200 skills, one folder each, plain git over HTTPS
Hand-written Dockerfiles end up huge, slow to build and running as root. The skill fixes that: a small multi-stage Dockerfile and .dockerignore for your app, with each line explained.
Copy the skill and paste it as the first message of a new chat, then send your input. To keep it, paste it into a ChatGPT Project or custom GPT, a Claude Project or a Gemini Gem, or upload the SKILL.md file as a Claude Skill.
Send your language and framework, how you build and start the app, and the port it listens on. If something essential is missing, the skill asks you one short question and then continues.
Yes. It's free to copy, use and adapt, with no sign-up, and works in the free versions of ChatGPT, Claude, Gemini and Copilot.
ProblemSetting up CI from scratch means hours of YAML trial and error.
GitHub Actions, Python 3.12, uv, pytest and ruff
on: [pull_request, push: {branches: [main]}]
permissions: contents: read
steps: checkout → setup-uv (cache) → uv sync → ruff check . → pytest -q
Immediate resultA working CI workflow file that installs, lints, tests and builds on every pull request.
ProblemAfter an outage, the postmortem is written late, blames people and repeats the same action items.
14:02 alerts fire · 14:10 rollback tried, fails · 14:31 DB connection pool raised · 14:35 recovered
Impact: 33 minutes of failed checkouts.
Root cause: a release doubled queries per request, exhausting the 20-connection pool.
Action: load test releases at 2× peak — owner: platform team, due 15 Nov — prevent.
Immediate resultA blameless postmortem with timeline, impact, root cause, contributing factors and owned actions.
ProblemPorting code between languages by hand introduces subtle behaviour changes.
Python → TypeScript: def avg(xs): return sum(xs) / len(xs)
const avg = (xs: number[]) => xs.length ? xs.reduce((a, b) => a + b, 0) / xs.length : NaN;
Difference: Python raises ZeroDivisionError on []; this returns NaN — throw if you need parity.
Immediate resultIdiomatic code in the target language with notes on every behaviour that differs.
All 20 software engineering skillsAll 200 skillsRead it in the articleProve it: AI for Software Developers Certification (free test)
60 research-backed principles in 6 categories — what each one means, why it works on the human brain and how to use it on your own screens. Written by Sushant Singh, founder of Science of Apps, who has scaled consumer apps to lacs of users and spent 10+ years leading product across startups and digital businesses in the US, EU & India.
110 real paywalls from top apps, taken apart, rated out of 5 and decoded with the Laws of UX — plus the frameworks, copy and checklists to ship your own. By Sushant Singh, founder of Science of Apps.