/create-chart
Generate a Helm chart for deploying an application to Kubernetes.
$ npx -y skills add rohitg00/awesome-claude-code-toolkit --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/create-chart
Context preview
What this command does when you run it.
Generate a Helm chart for deploying an application to Kubernetes.
Command definition
create-chart.mdname: create-chart
description: Generate a Helm chart for deploying an application to Kubernetes.
/create-chart - Create Helm Chart
Generate a Helm chart for deploying an application to Kubernetes.
Steps
1. Ask the user for the application name, type (web app, API, worker, cronjob), and container image 2. Create the chart directory structure with `helm create` 3. Configure Chart.yaml with name, version, appVersion, and description 4. Customize the Deployment template: replicas, resources, probes, env vars 5. Configure the Service template: type (ClusterIP, LoadBalancer, NodePort), ports 6. Add Ingress template with host, path, TLS configuration 7. Create ConfigMap and Secret templates for application configuration 8. Add HorizontalPodAutoscaler template with CPU/memory scaling rules 9. Configure PodDisruptionBudget for high-availability deployments 10. Set up ServiceAccount with appropriate RBAC permissions 11. Define values.yaml with sensible defaults for all configurable parameters 12. Validate the chart with `helm lint` and `helm template`
Rules
- Always include resource limits and requests in deployment templates
- Configure liveness and readiness probes for all containers
- Use values.yaml for all configurable parameters; do not hardcode in templates
- Include pod anti-affinity rules for high-availability deployments
- Set security context: non-root user, read-only filesystem, drop capabilities
- Use chart hooks for database migrations or pre-deployment checks
- Pin container image tags; never use 'latest' in production values
Read more
name: create-chart description: Generate a Helm chart for deploying an application to Kubernetes.
/create-chart - Create Helm Chart
Generate a Helm chart for deploying an application to Kubernetes.
Steps
1. Ask the user for the application name, type (web app, API, worker, cronjob), and container image 2. Create the chart directory structure with `helm create` 3. Configure Chart.yaml with name, version, appVersion, and description 4. Customize the Deployment template: replicas, resources, probes, env vars 5. Configure the Service template: type (ClusterIP, LoadBalancer, NodePort), ports 6. Add Ingress template with host, path, TLS configuration 7. Create ConfigMap and Secret templates for application configuration 8. Add HorizontalPodAutoscaler template with CPU/memory scaling rules 9. Configure PodDisruptionBudget for high-availability deployments 10. Set up ServiceAccount with appropriate RBAC permissions 11. Define values.yaml with sensible defaults for all configurable parameters 12. Validate the chart with `helm lint` and `helm template`
Rules
- Always include resource limits and requests in deployment templates
- Configure liveness and readiness probes for all containers
- Use values.yaml for all configurable parameters; do not hardcode in templates
- Include pod anti-affinity rules for high-availability deployments
- Set security context: non-root user, read-only filesystem, drop capabilities
- Use chart hooks for database migrations or pre-deployment checks
- Pin container image tags; never use 'latest' in production values
The most comprehensive toolkit for Claude Code -- 135 agents, 35 curated skills (+400,000 via SkillKit), 42 commands, 176+ plugins, 20 hooks, 15 rules, 7 templates, 15 MCP configs, 26 companion apps, 53 ecosystem entries, and more.
Repo: rohitg00/awesome-claude-code-toolkit
Other commands on rohitg00-claude-code-toolkit.
- /adr
Write an Architecture Decision Record documenting a significant technical decision.
Open command - /design-review
Conduct a structured design review of a module, feature, or system component.
Open command - /diagram
Generate Mermaid diagrams from codebase analysis or description.
Open command - /migrate
Plan and execute a framework or library migration incrementally.
Open command - /plan
Create a structured implementation plan for the requested feature or change.
Open command - /refactor
Perform a systematic refactoring of the specified code area.
Open command

