About

Imported from shipshitdev/skills (skills/devcontainer-setup/SKILL.md). Install upstream with npx skills add shipshitdev/skills --skill devcontainer-setup. Copyright stays with the author.

Devcontainer Setup Skill

Name: devcontainer-setup
Author: shipshitdev

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/*)

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

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

Example Usage

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

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

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml

targets:
  - https://api.opensmartroute.ai/api/v1/registry/shipshitdev-skills-devcontainer-setup/manifest   # or paste the manifest below

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

shipshitdev-skills-devcontainer-setup.ocm.jsonjson

{
  "ocm": "1",
  "id": "shipshitdev-skills-devcontainer-setup",
  "kind": "skill",
  "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.",
  "publisher": "shipshitdev",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "coding"
    ],
    "tags": [
      "skill-md",
      "devcontainer",
      "docker",
      "setup",
      "skills-sh"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "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."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "skills.sh",
      "repository": "https://github.com/shipshitdev/skills",
      "path": "skills/devcontainer-setup/SKILL.md",
      "ref": "HEAD",
      "url": "https://github.com/shipshitdev/skills/blob/HEAD/skills/devcontainer-setup/SKILL.md",
      "key": "shipshitdev/skills/skills/devcontainer-setup/SKILL.md"
    }
  },
  "instructions": "# Devcontainer Setup Skill\n\n## Authorized Scope\n\nApply this engine only within the user's requested task and existing explicit\nauthorization. Loading or delegating to it grants no additional authority.\nPreserve report-only restrictions and the caller's target, host, provider, and\ncost limits. Existing approval satisfies a gate only for the same actions and\nscope; obtain approval before expanding them. Forward these limits to delegates.\n\n## Contract\n\nInputs:\n\n- Project runtime, existing container configuration, and requested development setup\n- Approved directory mounts and optional tooling\n\nOu",
  "cost": {
    "context_tokens": 1160
  }
}

Fetch it by URL: GET /api/v1/registry/shipshitdev-skills-devcontainer-setup/manifest?version=1.0.0

Reviews

Star ratings from people who tried it. One review per account; edit yours any time.

No reviews yet. Install it, try it, and be the first to rate it.