Standards for authoring SDD plugin agents — frontmatter, self-containment, skill references, and no-user-interaction rules.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrates local Kubernetes development environment management.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Manage local Kubernetes development environments for SDD projects.
Invoked by sdd-run.md with:
action — The local-env action to performargs — Remaining arguments after the actionbrew install kind) - recommendedbrew install minikube)| Action | Description |
|---|---|
create | Create cluster + install infra |
destroy | Delete cluster entirely |
start | Resume stopped cluster |
stop | Pause cluster (preserves state) |
status | Show cluster and workload status |
deploy | Set up databases, run migrations, deploy helm charts |
undeploy | Remove helm deployments (databases persist) |
forward | Manage port forwards |
infra | Install/reinstall observability infrastructure |
When invoked without an action, display usage:
⚠ Missing required action argument.
USAGE:
/sdd-run local-env <action> [args] [options]
ACTIONS:
create Create local k8s cluster + install infra
destroy Delete cluster entirely 🔴 destructive
start Resume stopped cluster
stop Pause cluster (preserves state)
status Show cluster and workload status
deploy Set up databases, run migrations, deploy helm charts
undeploy Remove helm deployments 🟡 caution
forward Manage port forwards (start|stop|list)
infra Install/reinstall observability infrastructure
EXAMPLES:
/sdd-run local-env create
/sdd-run local-env deploy
/sdd-run local-env forward start
/sdd-run local-env status
/sdd-run local-env create [--name=cluster-name] [--provider=kind|minikube|docker-desktop] [--skip-infra]
Creates a local k8s cluster and installs the observability stack (Victoria Metrics + Victoria Logs).
Options:
--name: Cluster name (default: sdd-local)--provider: Cluster provider (default: auto-detected)
kind: Kubernetes IN Docker (fast, lightweight)minikube: Full-featured local k8sdocker-desktop: Uses Docker Desktop's built-in Kubernetes--skip-infra: Skip installing observability stackImplementation:
<plugin-root>/fullstack-typescript/system/system-run.sh local-env create [--name=cluster-name] [--provider=kind|minikube|docker-desktop] [--skip-infra]
/sdd-run local-env destroy [--name=cluster-name]
Completely removes the local cluster (not available for docker-desktop).
Implementation:
<plugin-root>/fullstack-typescript/system/system-run.sh local-env destroy [--name=cluster-name]
/sdd-run local-env start [--name=cluster-name]
/sdd-run local-env stop [--name=cluster-name]
Pause and resume the cluster. State is preserved when stopped.
Implementation:
<plugin-root>/fullstack-typescript/system/system-run.sh local-env start [--name=cluster-name]
<plugin-root>/fullstack-typescript/system/system-run.sh local-env stop [--name=cluster-name]
/sdd-run local-env status [--name=cluster-name]
Shows cluster status, node health, and deployed workloads.
Implementation:
<plugin-root>/fullstack-typescript/system/system-run.sh local-env status [--name=cluster-name]
/sdd-run local-env deploy [chart-name] [--namespace=<app-name>] [--skip-db] [--skip-migrate] [--exclude=name,...]
Deploys the full application stack in order:
type: database componentcomponents/helm_charts/Options:
--namespace: Override namespace (default: app name from sdd-settings.yaml)--skip-db: Skip database setup (useful for redeploying apps only)--skip-migrate: Skip running migrations--exclude: Comma-separated list of charts to skip (for hybrid development)Implementation:
<plugin-root>/fullstack-typescript/system/system-run.sh local-env deploy [chart-name] [--namespace=<app-name>] [--skip-db] [--skip-migrate] [--exclude=name,...]
/sdd-run local-env undeploy [chart-name] [--namespace=<app-name>]
Removes deployed applications (keeps infrastructure).
Implementation:
<plugin-root>/fullstack-typescript/system/system-run.sh local-env undeploy [chart-name] [--namespace=<app-name>]
/sdd-run local-env forward [start|stop|list] [--namespace=<app-name>]
Manages port forwards for local access to services.
Implementation:
<plugin-root>/fullstack-typescript/system/system-run.sh local-env forward [start|stop|list] [--namespace=<app-name>]
/sdd-run local-env infra [--reinstall]
Install or reinstall the observability infrastructure stack.
Implementation:
<plugin-root>/fullstack-typescript/system/system-run.sh local-env infra [--reinstall]
| Provider | Best For | Create Time | Notes |
|---|---|---|---|
kind | CI/CD, disposable clusters | ~30 seconds | Default, recommended |
minikube | Feature-rich local dev | ~60 seconds | Supports addons |
docker-desktop | Simple local dev | Already running | Uses existing cluster |
Auto-detection order:
docker-desktopminikubekindThe telemetry namespace contains:
| Namespace | Contents |
|---|---|
telemetry | Observability stack |
<app-name> | Application deployments (from sdd-settings.yaml name field) |
The deploy action reads sdd/sdd-settings.yaml (delegate to the techpack-settings skill for the settings schema — it returns the project name, component list with types, and per-component settings) to:
name (used as the Kubernetes namespace)type: database components to set uptype: helm components to deployRun most services in k8s while developing one locally:
# Deploy everything except the service you're working on
/sdd-run local-env deploy --exclude=main-server-api
# Start port forwards so your local service can reach k8s
/sdd-run local-env forward start
# Run your service locally
cd components/servers/main-server
npm run dev
Your local service connects to:
# Check Docker is running
docker ps
# Check kind clusters
kind get clusters
# Delete and recreate
/sdd-run local-env destroy
/sdd-run local-env create
# Check pod status
kubectl get pods -A
# Check pod logs
kubectl logs <pod-name> -n <namespace>
# Describe pod for events
kubectl describe pod <pod-name> -n <namespace>
# List active forwards
/sdd-run local-env forward list
# Stop all and restart
/sdd-run local-env forward stop
/sdd-run local-env forward start
Returns the system CLI output for the requested action.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Standards for authoring SDD plugin agents — frontmatter, self-containment, skill references, and no-user-interaction rules.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffolds Node.js/TypeScript backend components with CMDO architecture, driven by component settings.
日本語の概要は準備中です。原文の説明を表示しています。
CMDO architecture standards for Node.js/TypeScript backends with strict layer separation.
日本語の概要は準備中です。原文の説明を表示しています。
Intent-to-command mappings for fullstack-typescript tech pack features.
日本語の概要は準備中です。原文の説明を表示しています。
Create change specification and implementation plan with dynamic phase generation. Supports feature, bugfix, refactor, and epic types.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrates the full change lifecycle — routes actions to phase-specific sub-files.
日本語の概要は準備中です。原文の説明を表示しています。