Scaffolds a complete VS Code Dev Container configuration with Docker, docker-compose, and optional Claude Code CLI support. Activates when asked to "set up devcontainer", "add docker development environment", "configure dev container", or containerize a development workflow.
Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.
What it does
Scaffolds a complete VS Code Dev Container configuration with Docker, docker-compose, and optional Claude Code CLI support. Activates when asked to "set up devcontainer", "add docker development environment", "configure dev container", or containerize a development workflow.
When to use it
The official description does not include a separate “Use when”. Per the spec, agents activate this skill when the task matches keywords in that description.
How agents load it
Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Devcontainer Setup Skill; Authorized Scope; Contract; Information Gathering; Required Information; File Structure to Create. It includes spec-recommended sections: step-by-step instructions, input/output examples.
File analysis
File analysis: besides SKILL.md, the body references references/templates.md. Those resources load on demand.
Scaffolds a complete VS Code Dev Container configuration with Docker, docker-compose, and optional Claude Code CLI support. Activates when asked to "set up devcontainer", "add docker development environment", "configure dev container", or containerize a development workflow.
DiscoverThe client exposes names and descriptions to the agent.
ActivateYour request or the task context selects the skill and loads its instructions.
Load resourcesReferenced scripts, documentation and assets are used when needed.
Files referenced by the instructions · 1
references/templates.md
These paths are extracted from the text. Check the upstream package to verify the files exist.
Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.
This skill references supporting files. Retrieve the complete directory from the source; copying SKILL.md alone may leave missing dependencies.
Ask your Agent to install
Copy these instructions to a compatible agent and confirm the target directory matches your client.
Install the agent skill "devcontainer-setup" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-e39d3f75c1a6ebcd-Devcontainer-Setup.html
Save it as .cursor/skills/devcontainer-setup/SKILL.md or .claude/skills/devcontainer-setup/SKILL.md and keep the frontmatter name and description exactly as-is.
This skill also ships scripts/, references/, or assets/ — fetch the whole folder from https://github.com/shipshitdev/skills instead of creating only a SKILL.md.
The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.
name: devcontainer-setup
description: Scaffolds a complete VS Code Dev Container configuration with Docker, docker-compose, and optional Claude Code CLI support. Activates when asked to "set up devcontainer", "add docker development environment", "configure dev container", or containerize a development workflow.
metadata:
version: "1.1.0"
tags: "devcontainer, docker, setup"
Devcontainer Setup Skill
Authorized Scope
Apply this engine only within the user's requested task and existing explicit
authorization. Loading or delegating to it grants no additional authority.
Preserve report-only restrictions and the caller's target, host, provider, and
cost limits. Existing approval satisfies a gate only for the same actions and
scope; obtain approval before expanding them. Forward these limits to delegates.
Contract
Inputs:
Project runtime, existing container configuration, and requested development setup
Approved directory mounts and optional tooling
Outputs:
Dev Container configuration and startup instructions
Creates/Modifies:
.devcontainer/ files within the authorized setup scope
External Side Effects:
Image pulls, package installs, or container startup only when requested
Confirmation Required:
Before overwriting existing configuration or mounting directories outside the
selected project
Before adding tooling or starting containers outside the approved setup
Delegates To:
docker-expert for container configuration details
Information Gathering
Before creating the devcontainer, gather the following information from the user:
Required Information
Project Name: What is the project/container name? (e.g., my-project, shipshitdev-api)
Base Image: What runtime does this project use?
oven/bun:1.3.5 - Bun projects (recommended for speed)
node:20-slim - Node.js projects
node:20 - Node.js with more tools
Custom image path
Package Manager: Which package manager?
bun - Bun (default for Bun projects)
npm - npm
pnpm - pnpm
yarn - Yarn
Ports: What ports need to be forwarded? (comma-separated, e.g., 3000, 3001, 5432)
Port Labels (optional): Labels for each port (e.g., 3000=Web, 5432=Postgres)
Parent Directory Mount: Should the parent directory be mounted for cross-repo access?
Yes - Mount parent as /workspace (good for monorepos, shared libraries)
No - Only mount this project
Claude Code Support: Include Claude Code CLI setup?
Yes - Install Claude Code and fix symlinks for container use
No - Skip Claude Code setup
VS Code Extensions (optional): Additional extensions to install (comma-separated extension IDs)
Monorepo Structure (if applicable):
Is this a monorepo with nested package.json files?
What are the app/package directories? (e.g., apps/*, packages/*)
Dockerfile — base image, workdir, dependency install (monorepo-aware), dev tools, exposed ports
docker-compose.yml — service definition, volumes (parent mount + node_modules caching), ports, dev command
setup.sh — installs dependencies; if Claude Code support is requested, also fixes host-to-container Claude config symlinks and prints API key setup instructions