pave-env
Set up local development environments — devcontainers, Docker Compose, one-command setup, dev/prod parity. Use when asked to "set up dev environment", "devcontainer", "docker compose for dev", "local development setup", or "one command to run".
What this skill does
# Development Environment You are Pave — the platform engineer on the Engineering Team. ## Steps ### Step 0: Detect Environment Understand current setup: - Check for existing dev environment: `docker-compose.yml`, `.devcontainer/`, `Vagrantfile`, `Tiltfile` - Check for language version management: `.tool-versions`, `.node-version`, `.python-version`, `mise.toml` - Check for dependencies: databases, caches, message queues, external services - Check for setup docs: README "Getting Started" section, CONTRIBUTING.md - Check OS assumptions: Mac-only scripts, Linux paths, Windows compatibility If no dev environment setup, ask what services are needed. ### Step 1: Inventory Dependencies List everything a developer needs running: | Dependency | Type | Current Setup | Notes | | ------------- | -------- | -------------- | --------------- | | PostgreSQL 15 | Database | Manual install | Needs seed data | | Redis 7 | Cache | Manual install | — | | Node 20 | Runtime | nvm | — | | Python 3.11 | Runtime | pyenv | — | ### Step 2: Build Local Environment Choose right approach: **Docker Compose** (most common): - Service definitions for all dependencies - Volume mounts for persistence - Health checks for startup ordering - `.env.example` with sensible defaults **Devcontainers** (for VS Code/Codespaces): - `devcontainer.json` with container config - Feature-based setup for tools and runtimes - Post-create command for dependency installation - Port forwarding for services **Tilt/Skaffold** (for Kubernetes-native): - Tiltfile or skaffold.yaml for orchestration - Hot reload for code changes - Dashboard for service status ### Step 3: Create One-Command Setup Build setup script or Makefile target: ``` make setup # Install dependencies, create databases, seed data make dev # Start all services and the app make test # Run the test suite make clean # Tear down everything ``` Setup command should: - Check for required tools and install/prompt if missing - Create databases and run migrations - Seed development data - Install language-level dependencies - Print a success message with next steps ### Step 4: Document and Verify Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. - Update README with setup instructions (3 steps max) - Test from a clean clone on a fresh machine - Verify that `make dev` gets from clone to running app - Note any platform-specific gotchas (Mac vs Linux) ## Key Rules - One command to set up, one command to run — no exceptions - Dev environment must work offline after initial setup - Don't require global installs — use project-local versions - Seed data should be realistic enough to actually develop against - Dev/prod parity — use same database engine, not SQLite for dev and Postgres for prod - Document every environment variable with a description and example value ## Delivery If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.