Help us improve
Share bugs, ideas, or general feedback.
From makesmith
Use when a project needs DevOps targets for building Docker images, pushing to registries (GCR/ECR/ACR), and deploying via Helm, kubectl, or Docker Compose
npx claudepluginhub jugrajsingh/skillgarden --plugin makesmithHow this skill is triggered — by the user, by Claude, or both
Slash command
/makesmith:generating-deployThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generate Makefile.deploy with DevOps targets for Docker and Kubernetes deployments.
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Share bugs, ideas, or general feedback.
Generate Makefile.deploy with DevOps targets for Docker and Kubernetes deployments.
basename $(pwd)
git describe --tags --always 2>/dev/null || echo "latest"
Present via AskUserQuestion:
Which container registry will you use?
○ GCR (Google Container Registry)
○ ECR (AWS Elastic Container Registry)
○ ACR (Azure Container Registry)
○ DockerHub
○ Custom registry
Present via AskUserQuestion:
How will you deploy?
○ Helm (Kubernetes via Helm charts)
○ kubectl (direct Kubernetes manifests)
○ Docker Compose (remote server)
○ None (just build and push)
Only if deployment target is Helm or kubectl:
Does this project deploy the same image as multiple releases?
○ Single deployment (one release)
○ Multiple deployments (e.g., service-type1, service-type2, service-type3)
If multiple, ask for deployment names.
Read ONLY the reference file matching the user's deployment target choice:
| Deployment Target | Reference File |
|---|---|
| Helm | references/helm.md |
| kubectl | references/kubectl.md |
| Docker Compose | references/compose.md |
| None | No reference needed |
Read references/common-template.makefile for the base structure (header, build, push, utilities).
Customize the template:
{project_name} with detected project nameAppend deploy commands to the CLAUDE.md Commands section. If the Commands section already exists (from generating-local), add a Deploy subsection. If it doesn't exist, create the full section.
**Deploy:**
```bash
make -f Makefile.deploy build-image # Build Docker image
make -f Makefile.deploy push-image # Push to registry
make -f Makefile.deploy deploy # Deploy via Helm
make -f Makefile.deploy build-push-deploy # Full CI/CD
make -f Makefile.deploy status # Pod status
make -f Makefile.deploy logs # Tail pod logs
```
For multi-deployment projects, list the per-deployment targets:
```bash
make -f Makefile.deploy deploy SOURCE=retail # Deploy retail
make -f Makefile.deploy deploy-retail # Alias
make -f Makefile.deploy deploy-runway # Deploy runway
```
Created Makefile.deploy:
Configuration:
- Image: {project}:{version}
- Registry: {registry_type}
- Deployment: {deployment_type}
Targets:
Build:
build-image - Build Docker image (local tag)
push-image - Push to default registry
build-and-push - Build and push
Deploy:
{deployment_targets_summary}
Utilities:
{utility_targets_summary}
Usage:
make -f Makefile.deploy build-push-deploy
| Registry | Command |
|---|---|
| GCR | gcloud auth configure-docker gcr.io --quiet |
| ECR | aws ecr get-login-password --region REGION | docker login --username AWS --password-stdin ACCOUNT.dkr.ecr.REGION.amazonaws.com |
| ACR | az acr login --name REGISTRY |
| DockerHub | docker login |