SuperAPI AI Directory

devcontainer-dev

General & other

View repository

Updated 10-15 23:43

About this skill

Devcontainer Dev

Workflow

  1. In the current-state investigation, read references/inspection.md and check.devcontainer/devcontainer.json, post-create scripts, language-specific manifests, lockfiles, and workspace settings.
  2. For design or improvement proposals, read references/design.md and separate the responsibilities of the runtime, CLI, editor extensions, ports, cache, monorepo detection, and project dependencies.
  3. In post-change verification, read references/validation.md and choose a verification policy that includes syntax checks and lightweight setup confirmation while avoiding heavy processing.

Operating Rules

  • If the user asks you to "propose", present the shortcomings and options before directly applying configuration changes.
  • Before globally installing all tools on the devcontainer side, check whether they should be resolved as project dependencies.
  • For UI/E2E test environment checks, assume Playwright.
  • For Node.js projects, prefer pnpm, and use pre-commit for pre-commit hooks. Do not adopt Husky.
  • In a monorepo, avoid double installation of the root workspace and individual packages.
  • Unless the user explicitly says so, do not commit for reviews or template creation alone.

Expected Output

  • Report handled items, unhandled items, and optional improvements separately.
  • For unhandled items, clarify what should go into the devcontainer and what should go into project dependencies.
  • If changes were made, briefly report the files touched and the verification performed.