agentleFS
ww-w-aiww-w-ai/bkit-gemini/skills/phase-9-deployment/SKILL.md

phase-9-deployment

Skill66 starsChanged 7 months agoApache-2.0View on GitHub

Skill for deploying to production environment. Covers CI/CD, environment configuration, and deployment strategies.

  • Reads credentials
  • Installs packages

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Phase 9: Deployment

Ship to production

Deployment Options

Starter Level: Vercel/Netlify

# Vercel deployment
npm i -g vercel
vercel deploy --prod

# Or connect GitHub for auto-deploy

Dynamic Level: Docker + Platform

# Dockerfile
FROM node:20-alpine AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci
COPY . .
RUN npm run build

FROM node:20-alpine AS runner
WORKDIR /app
COPY --from=builder /app/.next ./.next
COPY --from=builder /app/node_modules ./node_modules
COPY --from=builder /app/package.json ./
EXPOSE 3000
CMD ["npm", "start"]

Enterprise Level: Kubernetes

# kubernetes/deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: app
spec:
  replicas: 3
  selector:
    matchLabels:
      app: myapp
  template:
    metadata:
      labels:
        app: myapp
    spec:
      containers:
      - name: app
        image: myapp:latest
        ports:
        - containerPort: 3000

CI/CD Pipeline

# .github/workflows/deploy.yml
name: Deploy

on:
  push:
    branches: [main]

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '20'
      - run: npm ci
      - run: npm run build
      - run: npm run test
      - uses: amondnet/vercel-action@v25
        with:
          vercel-token: ${{ secrets.VERCEL_TOKEN }}
          vercel-org-id: ${{ secrets.ORG_ID }}
          vercel-project-id: ${{ secrets.PROJECT_ID }}
          vercel-args: '--prod'

Environment Variables

# Production .env
DATABASE_URL=postgres://...
NEXT_PUBLIC_API_URL=https://api.example.com
AUTH_SECRET=<generated-secret>

Deployment Checklist

  • All tests passing
  • Environment variables set
  • Database migrations run
  • SSL certificates configured
  • Monitoring set up
  • Backup strategy in place

Post-Deployment

After successful deployment:

  1. Verify functionality
  2. Monitor logs
  3. Check performance
  4. Generate completion report: /pdca report {feature}

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.