Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
jwynia avatar

Devcontainer

  • 297 installs
  • 133 repo stars
  • Updated February 24, 2026
  • jwynia/agent-skills

devcontainer is a Claude Code skill that configures and uses devcontainers so Claude-assisted development runs in a reproducible, dependency-complete environment for developers who need consistent setups across machines

About

devcontainer is an agent skill from jwynia/agent-skills for configuring VS Code/Cursor devcontainers so AI-assisted development runs inside a reproducible Docker-based environment. It helps developers define devcontainer.json, Dockerfile references, feature packs, and post-create commands so every contributor gets the same language runtimes, CLIs, and extensions. Teams reach for it when onboarding is slow, local dependency drift breaks agent workflows, or remote-container development must mirror CI. The skill focuses on environment parity for coding agents, not production deployment pipelines.

  • Standardizes reproducible dev environments
  • Reduces onboarding and dependency drift
  • Works with containerized project setups
  • Improves cross-machine parity for agents
  • Supports consistent tooling in Codespaces-like flows

Devcontainer by the numbers

  • 297 all-time installs (skills.sh)
  • +3 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #334 of 1,435 DevOps & CI/CD skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/jwynia/agent-skills --skill devcontainer

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs297
repo stars133
Last updatedFebruary 24, 2026
Repositoryjwynia/agent-skills

How do you set up reproducible devcontainers for AI coding?

Configure and use devcontainers so Claude-assisted development runs in a reproducible, dependency-complete environment across machines and contributors.

Who is it for?

Developers standardizing local and remote dev environments for Claude Code or Cursor across a team repository.

Skip if: Operators who only need production Kubernetes manifests or one-off local installs without containerized dev parity.

When should I use this skill?

User asks to configure devcontainers, devcontainer.json, reproducible dev environments, or containerized Claude development setups.

What you get

devcontainer.json configuration, Dockerfile or image reference, feature pack selections, and post-create setup steps.

  • devcontainer.json
  • Container build configuration
  • Post-create setup script guidance

Files

SKILL.mdMarkdownGitHub ↗

Devcontainer Diagnostic

Diagnose devcontainer and Docker development environment problems. Help create reproducible, fast-starting development environments that work consistently across VS Code, GitHub Codespaces, and team members.

When to Use This Skill

Use this skill when:

  • Setting up a new devcontainer
  • Container startup is too slow
  • Configuration errors or conflicts
  • Different behavior in VS Code vs Codespaces
  • Multi-service development environment needed

Do NOT use this skill when:

  • Writing application code
  • Deploying to production
  • Configuring CI/CD pipelines

Core Principle

Development containers should provide instant productivity. Every configuration choice affects startup time, reproducibility, and team onboarding. Make these trade-offs explicit.

Diagnostic States

DV0: No Devcontainer Strategy

Symptoms: Manual setup, "check the README", works on one machine fails on others

Interventions:

  • Start with pre-built devcontainer base image
  • Use assets/devcontainer-simple.md template

DV1: Slow Container Startup

Symptoms: 5+ minute startup, heavy postCreateCommand, avoiding rebuilds

Key Questions:

  • How long does startup actually take?
  • What's in postCreateCommand?
  • Are you using prebuilds?

Interventions:

  • Move npm install/pip install to Dockerfile (cached)
  • Use mcr.microsoft.com/devcontainers/* base images
  • Configure prebuilds for team repos
  • Run scripts/analyze-devcontainer.ts

DV2: Configuration Problems

Symptoms: JSON errors, VS Code won't connect, features conflicting

Checklist:

  • [ ] devcontainer.json passes JSON validation
  • [ ] Using only ONE of: image, build.dockerfile, dockerComposeFile
  • [ ] Features are compatible and ordered correctly
  • [ ] Extensions use correct publisher.extension-name format

DV3: Environment Parity Issues

Symptoms: Works in VS Code, fails in Codespaces (or vice versa)

Common Issues:

IssueLocal VS CodeCodespaces
Docker socketUsually availableDocker-in-Docker needed
Secrets.env files workUse Codespaces secrets
File watchingNativeMay need polling

DV4: Multi-Service Complexity

Symptoms: Need database/cache/queue, services can't communicate

Interventions:

  • Use Docker Compose integration
  • Named volumes for persistence
  • Health checks for service readiness
  • Use assets/devcontainer-compose.md template

DV5: Dockerfile Issues

Symptoms: Build failures, huge images, no caching

Best Practices:

FROM mcr.microsoft.com/devcontainers/base:ubuntu

# Dependencies first (cached)
RUN apt-get update && apt-get install -y \
    build-essential && rm -rf /var/lib/apt/lists/*

# Copy deps then install (cached if deps unchanged)
COPY package*.json ./
RUN npm install

# Code last (changes frequently)
COPY . .

DV6: Devcontainer Validated

Indicators:

  • Startup under 2 minutes
  • Works in VS Code and Codespaces
  • New developers productive in 30 minutes

Available Scripts

ScriptPurposeUsage
analyze-devcontainer.tsFind issues and optimizationsdeno run --allow-read scripts/analyze-devcontainer.ts
validate-dockerfile.tsCheck Dockerfile best practicesdeno run --allow-read scripts/validate-dockerfile.ts
scan-image.tsVulnerability scanning (wraps Trivy)deno run --allow-run scripts/scan-image.ts [image]

Anti-Patterns

The Kitchen Sink

Installing every tool "just in case" - 10+ minute startups. Fix: Start minimal. Add only when needed.

The postCreateCommand Overload

Everything in postCreateCommand - runs every time. Fix: Move stable operations to Dockerfile.

The Snowflake Container

Manual changes inside running containers. Fix: ALL changes go in config files.

Templates

  • assets/devcontainer-simple.md - Basic single-container setup
  • assets/devcontainer-dockerfile.md - Custom Dockerfile approach
  • assets/devcontainer-compose.md - Multi-service setup

Related Skills

  • system-design - Multi-service architecture informs Compose config
  • pwa-development - Consistent environment for PWA toolchain

Related skills

FAQ

What does the devcontainer skill configure?

The devcontainer skill configures devcontainer.json and related Docker settings so Claude-assisted development runs in a reproducible, dependency-complete container shared across machines and contributors.

When should developers use the devcontainer skill?

Use the devcontainer skill when local setups drift, onboarding is inconsistent, or you want Cursor or Claude Code to run inside a standardized container with the same runtimes and tools as CI.

DevOps & CI/CDdevopsintegrations

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.