Skip to main content
ZICQ

Skills ZICQ category:DevOps & Cloud devcontainer-setup

Devcontainer Setup

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.

176 installs

Official URL:skills.sh

What this skill does

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.

Devcontainer Setup SkillAuthorized ScopeContractInformation GatheringRequired InformationFile Structure to CreateTemplatesPackage Manager ReferenceImplementation StepsExample Usage

Source category:skills.sh agent-skill

SKILL.md & Agent activation

Official spec ↗
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.
  1. DiscoverThe client exposes names and descriptions to the agent.
  2. ActivateYour request or the task context selects the skill and loads its instructions.
  3. 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.

Invocation syntax and available tools depend on your Agent client. Client integration guide ↗

Install this skill

Skills CLI ↗

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.

Full package on GitHub ↗

Install from the terminal · Skills CLI

Requires Node.js and npx. First inspect the repository's skill list to confirm the name.

npx skills add 'https://github.com/shipshitdev/skills' --list

npx skills add 'https://github.com/shipshitdev/skills' --skill 'devcontainer-setup'

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.

Readable layout

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

  1. Project Name: What is the project/container name? (e.g., my-project, shipshitdev-api)

  2. 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
  3. Package Manager: Which package manager?

    • bun - Bun (default for Bun projects)
    • npm - npm
    • pnpm - pnpm
    • yarn - Yarn
  4. Ports: What ports need to be forwarded? (comma-separated, e.g., 3000, 3001, 5432)

  5. Port Labels (optional): Labels for each port (e.g., 3000=Web, 5432=Postgres)

  6. 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
  7. Claude Code Support: Include Claude Code CLI setup?

    • Yes - Install Claude Code and fix symlinks for container use
    • No - Skip Claude Code setup
  8. VS Code Extensions (optional): Additional extensions to install (comma-separated extension IDs)

  9. Monorepo Structure (if applicable):

    • Is this a monorepo with nested package.json files?
    • What are the app/package directories? (e.g., apps/*, packages/*)

File Structure to Create

.devcontainer/
├── devcontainer.json      # VS Code dev container config
├── Dockerfile             # Container image definition
├── docker-compose.yml     # Docker compose config
├── setup.sh               # Post-create setup script
└── README.md              # Documentation

Templates

Generate all five files from the gathered information:

  • devcontainer.json — build config, mounts, features, VS Code extensions/settings, forwarded ports, postCreateCommand
  • 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
  • README.md — quick start, mount/port tables, directory structure, troubleshooting

See references/templates.md for the full fill-in-the-blank text of each file ({{PLACEHOLDER}} values come from the gathered information above).

Package Manager Reference

| Package Manager | Lock File | Install Command | Dev Command | |-----------------|-----------|-----------------|-------------| | bun | bun.lock* | bun install --frozen-lockfile | bun run dev | | npm | package-lock.json | npm ci | npm run dev | | pnpm | pnpm-lock.yaml | pnpm install --frozen-lockfile | pnpm run dev | | yarn | yarn.lock | yarn install --frozen-lockfile | yarn dev |

Implementation Steps

  1. Ask the user the required questions above using AskUserQuestion
  2. Create the .devcontainer directory
  3. Generate each file with the gathered configuration
  4. Make setup.sh executable
  5. Provide summary of what was created and how to use it

Example Usage

User: "Set up devcontainer for my Next.js project"

  1. Gather info: Project uses Bun, ports 3000, needs Claude Code support
  2. Create all 5 files in .devcontainer/
  3. Output: "Created devcontainer configuration. Open in VS Code and click 'Reopen in Container'."

Related skills

DevOps & Cloud

Docker Essentials

Essential Docker commands and workflows for container management, image operations, and debugging.

DevOps & Cloud

Find Skills

Discover and install skills from the open agent skills ecosystem. Use when: (1) user asks "how do I do X" where X might have an existing ski…

DevOps & Cloud

Microsoft Foundry

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd a…

DevOps & Cloud

Azure Deploy

Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT us…