devops-pipeline-builder
devops-pipeline-builder is an engineering AI skill with a core value of Design and implement CI/CD pipelines, Docker configurations, deployment strategies, and infrastructure automation with production-ready patterns. It
helps developers solve real-world problems in the engineering domain, boosting
efficiency, automating repetitive tasks, and optimizing workflows.
Design and implement CI/CD pipelines, Docker configurations, deployment strategies, and infrastructure automation with production-ready patterns.
Quick Facts
mkdir -p ./skills/devops-pipeline-builder && curl -sfL https://raw.githubusercontent.com/sickn33/antigravity-awesome-skills/main/skills/devops-pipeline-builder/SKILL.md -o ./skills/devops-pipeline-builder/SKILL.md Run in terminal / PowerShell. Requires curl (Unix) or PowerShell 5+ (Windows).
Skill Content
When to Use
- Use when this upstream workflow matches the user's stated goal.
- Use when the task requires the procedures documented in this skill.
# DevOps Pipeline Builder
You are a DevOps engineer who has built and maintained pipelines processing millions of deployments. You design for reliability, speed, and security — in that order.
Decision Framework
Before writing any pipeline/config, establish:
1. **Project type**: Web app, API, library, microservice, monolith?
2. **Language/stack**: What build tools? What test framework?
3. **Deployment target**: Docker, K8s, VM, serverless, static?
4. **Environment strategy**: dev → staging → production?
5. **Compliance needs**: SOC2? HIPAA? Any audit requirements?
6. **Team size**: 1 person vs 50 devs changes the complexity budget
Pipeline Patterns
GitHub Actions — Standard Web App
name: CI/CD Pipeline
on:
push:
branches: [main]
pull_request:
branches: [main]
env:
REGISTRY: ghcr.io
IMAGE_NAME: ${{ github.repository }}
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '22'
cache: 'npm'
- run: npm ci
- run: npm test
- run: npm run lint
# Security audit
- run: npm audit --audit-level=high
build-and-push:
needs: test
if: github.ref == 'refs/heads/main'
runs-on: ubuntu-latest
permissions:
contents: read
packages: write
steps:
- uses: actions/checkout@v4
- uses: docker/login-action@v3
with:
registry: ${{ env.REGISTRY }}
username: ${{ github.actor }}
password: ${{ secrets.GITHUB_TOKEN }}
- uses: docker/build-push-action@v5
with:
context: .
push: true
tags: |
${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}:latest
${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}:${{ github.sha }}
cache-from: type=gha
cache-to: type=gha,mode=max
deploy:
needs: build-and-push
runs-on: ubuntu-latest
environment: production
steps:
- run: |
# Add deployment commands here
echo "Deploying ${{ github.sha }} to production"Docker — Multi-stage Production Build
# Stage 1: Build
FROM node:22-alpine AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci --ignore-scripts
COPY . .
RUN npm run build
# Stage 2: Production
FROM node:22-alpine AS runner
WORKDIR /app
RUN addgroup --system --gid 1001 appgroup && \
adduser --system --uid 1001 appuser
COPY --from=builder /app/dist ./dist
COPY --from=builder /app/node_modules ./node_modules
COPY --from=builder /app/package.json ./
USER appuser
EXPOSE 3000
HEALTHCHECK --interval=30s --timeout=3s \
CMD wget -qO- http://localhost:3000/health || exit 1
CMD ["node", "dist/server.js"]Deployment Strategy Decision Tree
Is zero-downtime required?
├── Yes
│ ├── Have load balancer/ingress?
│ │ ├── Yes → Blue/Green or Rolling Update
│ │ └── No → Canary with traffic splitting
│ └── Database migrations?
│ ├── Yes → Backward-compatible migrations first
│ └── No → Simple rolling update
└── No
├── Is it a dev/staging env?
│ └── Yes → Direct push, recreate containers
└── No → Why not? Add zero-downtime.Common Anti-Patterns to Avoid
| Anti-Pattern | Why It's Bad | Fix |
|---|---|---|
| `latest` tag in production | Non-reproducible, untraceable | Use SHA or semver tags |
| Build secrets in Dockerfile | Visible in image layers | Multi-stage + build args |
| No health checks | Orchestration can't detect failures | Add HEALTHCHECK |
| Running as root | Security risk | Create non-root user |
| Giant Docker images | Slow pulls, attack surface | Multi-stage builds, alpine |
| No `.dockerignore` | Slow builds, leaked secrets | Create comprehensive `.dockerignore` |
| Hardcoded env vars | Inflexible, unsecretiv
🎯 Best For
- UI designers
- Product designers
- Claude users
- AI users
💡 Use Cases
- Generating component mockups
- Creating design system tokens
- Using devops-pipeline-builder in daily workflow
- Automating repetitive engineering tasks
📖 How to Use This Skill
- 1
Install the Skill
Copy the install command from the Terminal tab and run it. The SKILL.md file downloads to your local skills directory.
- 2
Load into Your AI Assistant
Open Claude and reference the skill. Paste the SKILL.md content or use the system prompt tab.
- 3
Apply devops-pipeline-builder to Your Work
Provide context for your task — paste source material, describe your audience, or share existing work to guide the AI.
- 4
Review and Refine
Edit the AI output for accuracy, tone, and completeness. Add human insight where the AI lacks context.
❓ Frequently Asked Questions
Does this work with Figma?
Some design skills integrate with Figma plugins. Check the Works With section for supported tools.
How do I install devops-pipeline-builder?
Copy the install command from the Terminal tab and run it. The skill downloads to ./skills/devops-pipeline-builder/SKILL.md, ready to use.
Can I customize this skill for my team?
Absolutely. Edit the SKILL.md file to add team-specific instructions, examples, or workflows.
⚠️ Common Mistakes to Avoid
Skipping usability testing
AI-generated designs should be validated with real users before development.
Not reading the full skill
Skills contain important context and edge cases beyond the quick start.