القائمة
This skill should be used when the user asks to "set up deployment", "configure CI/CD", "create a Dockerfile", "choose a hosting platform", or discusses deployment and infrastructure decisions. Provides pragmatic DevOps guidance for indie developers.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
This skill should be used when the user asks to "pre-flight check", "validate before commit", "validate before PR", "validate before deploy", "is this ready to ship", "check readiness", "run pre-flight", "validate project state", or wants context-aware validation across commit/PR/release/deploy boundaries. Orchestrates universal validators (lint, tests, types, version sync, stale refs, docs, hook conflicts) and supports generating new custom validators.
This skill should be used when a command's --refine flag is set, or the user asks to "refine my prompt", "optimize this prompt", "make this request sharper" — rewrites a vague natural-language request into a specific, well-structured prompt using project context, shows before/after, and confirms before the caller proceeds. Replaces the deprecated /craft:refine command.
This skill should be used when the user asks to "release", "create a release", "ship it", "publish a new version", "bump version and release", "cut a release", or mentions releasing to GitHub/npm/PyPI. Orchestrates the full release pipeline from pre-flight checks through GitHub release creation.
ADHD-friendly session and task workflow for craft users — captures context at session end, restores it at session start, picks the next task, breaks through blockers, holds focus on one task, reviews a craft spec, or refines a vague craft prompt. Use when wrapping up or resuming a coding session, when deciding what to work on next (also "what's next", "pick a task for me", "give me something to do"), when stuck or in decision paralysis, when focusing on a single craft task, or when reviewing/refining a craft spec or prompt. The full intent-to-operation map is in the "When to Use" table below.
This skill should be used when the user asks to "init a repo", "set up git", "manage branches", "switch branch", "create a worktree", "list worktrees", "clean merged branches", "sync with remote", "git activity", "git recap", "protect main", "apply branch protection", "bypass protection", "undo a commit", "fix a git mistake", or mentions git lifecycle, worktrees, branch protection, GitHub-side baseline protection, safety rails, or learning git workflows. Covers craft's full git lifecycle — repo init, branch and worktree management, remote sync, status/recap, local and GitHub-side branch protection, and the learning/safety reference docs.
This skill should be used when the user asks "what's my friction", "session insights", "friction report", "what patterns am I hitting", "analyze my sessions", "generate insights report", "aggregate facets", or "show CLAUDE.md suggestions". Aggregates session facet history into a friction/goals report. Formerly bundled with the brainstorm skill (ideation); split out because the two operations share no input or output. Directory name kept as brainstorm-insights for path stability — tests and references/insights.md reference it.
| name | devops-helper |
| description | This skill should be used when the user asks to "set up deployment", "configure CI/CD", "create a Dockerfile", "choose a hosting platform", or discusses deployment and infrastructure decisions. Provides pragmatic DevOps guidance for indie developers. |
Auto-activated when: User discusses deployment, CI/CD, Docker, testing automation, or infrastructure decisions.
Ship Fast Principles:
Right-Sized DevOps:
Anti-Patterns to Avoid:
When analysis is needed, I will:
devops-engineer agent for pipeline optimizationexperienced-engineer agent for testing strategyperformance-engineer agent for build performancerun_in_background: trueUser: "I need to set up deployment for my Next.js app with a PostgreSQL database"
Skill activates and provides:
1. Platform recommendation (Vercel for Next.js + Supabase for PostgreSQL)
2. CI/CD setup (GitHub Actions for tests, Vercel auto-deploys)
3. Environment variables strategy (.env.local, Vercel env vars)
4. Database migrations approach (Drizzle or Prisma)
5. Delegates infrastructure review to devops-engineer agent (background)
6. Returns with complete deployment setup plan
When activated, I provide:
| Need | Recommended Platform | Monthly Cost |
|---|---|---|
| Static site | GitHub Pages / Netlify | Free |
| Next.js/React | Vercel | Free tier → $20/mo |
| Full-stack app | Render / Railway | $7-20/mo |
| Python/Django | Fly.io / Render | $5-15/mo |
| Database | Supabase / PlanetScale | Free tier → $25/mo |
| Background jobs | Render Cron / Railway | Included |
I'll provide templates for:
# Basic CI workflow for testing + deployment
name: CI/CD
on: [push, pull_request]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Run tests
run: npm test
deploy:
needs: test
if: github.ref == 'refs/heads/main'
runs-on: ubuntu-latest
steps:
- name: Deploy to Vercel
# Vercel auto-deploys via GitHub integration
# Build stage
FROM node:18-alpine AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci
COPY . .
RUN npm run build
# Production stage
FROM node:18-alpine
WORKDIR /app
COPY --from=builder /app/dist ./dist
COPY package*.json ./
RUN npm ci --production
CMD ["node", "dist/index.js"]
/brainstorm for deployment discussions/next (suggests DevOps implementation steps)/done (captures deployment decisions, configs used)Free Tier Strategy:
Total: $0/month for MVP, scales to ~$50/month at 1K users
Remember: This skill auto-activates based on keywords. Keep recommendations indie-friendly (managed platforms, reasonable costs, minimal complexity). Ship fast, scale later.