depgen-k8s

Generate Dockerfile and Kubernetes manifests from CLAUDE.md and SPECIFICATION.md.

3|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/rashidee/co2-skills --skill depgen-k8s
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: depgen-k8s
Source: https://github.com/rashidee/co2-skills/tree/main/skills/depgen-k8s
Command: npx skills add https://github.com/rashidee/co2-skills --skill depgen-k8s

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates deployment artifacts (Dockerfile and Kubernetes manifests) tailored to a given application, saving time and reducing manual configuration errors.

Core Features & Use Cases

  • Generates a production-ready multi-stage Dockerfile for Java, Laravel, or Node.js stacks, based on detected project files.
  • Creates Kubernetes manifests for a single target environment in the app's k8s/ folder, including namespace, configmap, secret, deployment, service, and optional ingress, aligned with CLAUDE.md data.
  • Automatically reads CLAUDE.md and SPECIFICATION.md to determine dependencies, environment variables, and health checks, then outputs versioned container images and environment-specific values.

Quick Start

Provide the application name and optional environment to generate a Dockerfile and Kubernetes manifests in the app's k8s/ folder.

Frequently Asked Questions about depgen-k8s

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate Kubernetes manifests and Dockerfiles automatically for my Spring Boot app?

You generate Kubernetes manifests and Dockerfiles automatically by reading CLAUDE.md and SPECIFICATION.md to auto-detect your Spring Boot stack, then outputting environment-specific namespace, configmap, secret, deployment, service, and ingress manifests into the k8s/ folder.

What is the best way to automate containerization for Laravel or Node.js projects?

Automate containerization for Laravel or Node.js by auto-detecting the stack from project files to generate a production-ready, multi-stage Dockerfile tailored to the specific stack dependencies and environment variables.

Do I need CLAUDE.md and SPECIFICATION.md files to generate deployment artifacts?

Yes, you need CLAUDE.md and SPECIFICATION.md files because the generator reads them to determine dependencies, environments, and stack details, using this data to tailor versioned container images and environment-specific Kubernetes values.

Can I generate Kubernetes manifests for a specific target environment?

Yes, you can generate Kubernetes manifests for a specific target environment by providing the application name and optional environment parameter, which outputs versioned container images and environment-specific values into the app's k8s/ folder.

Does automated Kubernetes manifest generation support ingress configuration?

Yes, automated Kubernetes manifest generation supports optional ingress configuration, creating it alongside namespace, configmap, secret, deployment, and service manifests based on the environment data specified in your CLAUDE.md file.

Why does the generated Dockerfile use a multi-stage build for Java or Node.js?

The generated Dockerfile uses a multi-stage build for Java, Laravel, or Node.js to produce production-ready container images, reducing final image size and separating build dependencies from runtime environments based on detected project files.