Automated summary
Builds a Docker image for the local platform using predefined recipes.
Strengths
- Guided process with image and tag selection
- Automatic prerequisite checks (Docker, dependencies)
- Clear success/failure messages with actionable steps
Limitations
- Only supports images listed in the menu
- Builds only for the local platform (not multi-arch)
- Does not push the image to any registry
Use this skill to quickly build a predefined Docker image locally during development or local testing.
Avoid this skill when you need to build for multiple architectures, push to a registry, or use a custom image not in the list.
Security analysis
SafeThe skill builds Docker images from a fixed set of predefined local directories. It does not execute external scripts, exfiltrate data, or perform destructive actions. The only potential risk is from the Dockerfiles themselves, but they are intended to be trusted local files.
No concerns found
How this analysis is madeExamples
/build
Select netshoot
Select tag: local/build
Select node
Select tag: custom
Enter custom tag: master-headBuild Docker Image (Local Platform)
Description
Build a single Docker image for the current platform. This is the fastest way to build and test images locally.
Instructions
Follow these steps to build a Docker image:
1. Gather Required Information
Use the AskUserQuestion tool to prompt the user for:
Question 1: Which image to build?
- Header: "Image"
- Options:
- bookworm: "Base Debian Bookworm image with Docker client and common utilities"
- go-operator: "Go 1.25 development environment for Kubernetes operators with tools like controller-gen, ginkgo, helm, kind, and golangci-lint"
- netshoot: "Network troubleshooting container with comprehensive networking tools (tcpdump, wireshark, iperf, nmap, etc.)"
- node: "Node.js v20.18.3 development environment built on top of bookworm base"
- server-base: "SUSE BCI base image with tini, curl, and NFS client"
Question 2: What tag to use?
- Header: "Tag"
- Options:
- local: "Tag as 'local' for quick local testing (Recommended)"
- latest: "Tag as 'latest'"
- custom: "Specify a custom tag"
If the user selects "custom", ask them to provide the custom tag name in the "Other" field.
2. Validate Prerequisites
Before building, check:
-
Docker is running:
docker infoIf this fails, inform the user that Docker is not running and they need to start Docker Desktop or the Docker daemon.
-
Image directory exists: Verify that the directory for the selected image exists (e.g.,
bookworm/,netshoot/, etc.) -
Handle node dependency: If the user selected "node", check if the bookworm:master-head image exists:
docker images futuretea/bookworm:master-head --format "{{.Repository}}:{{.Tag}}"If it doesn't exist, warn the user:
"⚠️ The node image depends on futuretea/bookworm:master-head, which doesn't exist locally. You should build bookworm first with tag 'master-head', or this build will fail."
Ask if they want to continue anyway or build bookworm first.
3. Build the Image
Execute the docker build command:
docker build -t futuretea/<image-name>:<tag> <image-name>/
Replace <image-name> with the selected image and <tag> with the selected/custom tag.
4. Report Results
After the build completes:
On Success:
✅ Successfully built futuretea/<image-name>:<tag>
You can now run the image with:
docker run -it futuretea/<image-name>:<tag>
To see the image details:
docker images futuretea/<image-name>:<tag>
On Failure:
❌ Build failed for futuretea/<image-name>:<tag>
Common issues:
- Check the Dockerfile syntax in <image-name>/Dockerfile
- Ensure base images are available
- Check Docker daemon logs for more details
Example Usage
User: /build
Claude: [Prompts for image selection]
User: [Selects netshoot]
Claude: [Prompts for tag]
User: [Selects "local"]
Claude: [Runs docker build -t futuretea/netshoot:local netshoot/]
Claude: ✅ Successfully built futuretea/netshoot:local
Notes
- This skill only builds for the current platform (typically linux/amd64 on most development machines)
- For multi-platform builds, use the
/build-multiplatformskill instead - The build output will show all Docker build steps and any errors
- Built images are stored locally and not pushed to any registry
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/build-docker-image-local-platform-mm5t8biu/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/build-docker-image-local-platform-mm5t8biu' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/build-docker-image-local-platform-mm5t8biu/download' --output '.skill-downloads/build-docker-image-local-platform-mm5t8biu/SKILL.md.part' && mv '.skill-downloads/build-docker-image-local-platform-mm5t8biu/SKILL.md.part' '.skill-downloads/build-docker-image-local-platform-mm5t8biu/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/build-docker-image-local-platform-mm5t8biu/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.