Skip to content

cbbkrd-tech/jl-finishes / .claude/skills/ln-730-devops-setup

ln-730-devops-setup

Verified

Coordinates Docker, CI/CD, and environment configuration setup via auto-detection

Paths: File paths (shared/, references/, ../ln-*) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.

ln-730-devops-setup

Type: L2 Domain Coordinator Category: 7XX Project Bootstrap Parent: ln-700-project-bootstrap

Coordinates DevOps infrastructure setup by delegating to specialized workers.


Purpose & Scope

Orchestrates the complete DevOps setup for a project:

  • Does: Auto-detect stack, delegate to workers, verify configuration
  • Does NOT: Generate files directly (delegates to ln-731, ln-732, ln-733)

Overview

AspectDetails
InputProject directory with source code
OutputDocker, CI/CD, environment configuration
Workersln-731 (Docker), ln-732 (CI/CD), ln-733 (Environment)
ModeAuto-detect (no user prompts)

Supported Stacks

ComponentOption 1Option 2
FrontendReact/Vite + Nginx-
Backend.NET 8/9Python (FastAPI/Django)
DatabasePostgreSQL-
CI/CDGitHub Actions-

Workflow

Phase 1: Pre-flight Validation

Check required tools and project structure:

  • Verify Docker is installed (docker --version)
  • Verify docker-compose is available
  • Check for existing DevOps files (warn if overwriting)

Output: Validation report or STOP with instructions

Phase 2: Project Analysis (Auto-detect)

Detect project stack automatically:

DetectionMethodFiles to Check
FrontendPackage.json presencesrc/frontend/package.json, package.json
Backend .NET.csproj/.sln presence*.sln, src/**/*.csproj
Backend Pythonrequirements.txt/pyproject.tomlrequirements.txt, pyproject.toml
DatabaseConnection strings in codeappsettings.json, .env.example
Existing CI/CDWorkflow files.github/workflows/, azure-pipelines.yml

Version Detection:

  • Node.js: Read from package.json engines or use node -v
  • .NET: Read from *.csproj TargetFramework
  • Python: Read from pyproject.toml or runtime.txt
  • PostgreSQL: Default to latest stable (17)

Output: Stack configuration object with detected versions

Phase 3: Worker Delegation

Delegate to workers in parallel (independent tasks):

ln-730 (Coordinator)
    |
    +---> ln-731-docker-generator (via Task tool)
    |         Input: stack config, versions
    |         Output: Dockerfile.*, docker-compose.yml, .dockerignore
    |
    +---> ln-732-cicd-generator (via Task tool)
    |         Input: stack config, detected commands
    |         Output: .github/workflows/ci.yml
    |
    +---> ln-733-env-configurator (via Task tool)
              Input: detected environment variables
              Output: .env.example, .env.development, .gitignore updates

Error Handling:

  • If worker fails, log error and continue with others
  • Report all failures at the end
  • Suggest manual fixes for failed components

Phase 4: Configuration Verification

Verify generated configuration:

  • Run docker-compose config to validate syntax
  • Check all referenced files exist
  • Verify no secrets in committed files

Output: Verification report

Phase 5: Completion Report

Generate summary:

  • List all created files
  • Show detected stack configuration
  • Provide next steps for user

Generated Files

Docker (ln-731)

  • Dockerfile.frontend - Multi-stage build for frontend
  • Dockerfile.backend - Multi-stage build for backend
  • docker-compose.yml - Service orchestration
  • docker-compose.override.yml - Development overrides (optional)
  • .dockerignore - Build context exclusions

CI/CD (ln-732)

  • .github/workflows/ci.yml - Main CI pipeline

Environment (ln-733)

  • .env.example - Template with all variables
  • .env.development - Development defaults
  • .env.production - Production template (placeholders)
  • .gitignore updates - Secrets protection

Critical Notes

  1. Auto-detect Only: No interactive prompts. Uses detected values or sensible defaults.
  2. Idempotent: Check file existence before creation. Warn before overwriting.
  3. Parallel Execution: Workers are independent, can run in parallel.
  4. Error Recovery: Continue on partial failures, report all issues at end.
  5. Version Pinning: Use detected versions, not hardcoded values.

Definition of Done

  • Pre-flight validation passed
  • Stack auto-detected successfully
  • All workers completed (or failures documented)
  • docker-compose config validates successfully
  • No secrets in generated files
  • Completion report displayed

Reference Files

  • Worker: ../ln-731-docker-generator/SKILL.md
  • Worker: ../ln-732-cicd-generator/SKILL.md
  • Worker: ../ln-733-env-configurator/SKILL.md

Version: 1.1.0 Last Updated: 2026-01-10

writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 319kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 117kUpdated Claude CodeCodexVerifiedInstall