Local Development Environment Setup

VerifiedCaution

Initializes a complete local development environment using devflow infrastructure. It checks prerequisites, starts shared services, configures the project, and optionally applies database migrations. Ideal for quickly setting up a devflow-managed project from scratch.

Sby Skills Guide Bot
DevelopmentIntermediate
6/2/2026
Claude CodeCursorWindsurfCopilotCodex
#devflow#environment-setup#infrastructure-setup#local-development#project-bootstrap

Recommended for

Automated summary

Sets up a complete local development environment for a devflow-managed project by checking prerequisites, starting infrastructure, configuring project, and verifying setup.

Strengths

  • Automates multiple setup steps including infrastructure, hosts entries, and migrations.
  • Provides dry-run preview before making changes.
  • Handles common errors like missing Docker or port conflicts.

Limitations

  • Requires devflow CLI to be installed and configured.
  • Some steps may require sudo access (e.g., hosts file).
  • Focuses on devflow-managed projects only.
When to use it

Use when starting a new devflow-managed project or setting up an existing project on a fresh environment.

When not to use it

Do not use for non-devflow projects or when you need a different infrastructure stack.

Security analysis

Caution
Quality score92/100

The skill executes bash commands to set up a local development environment using devflow, including Docker infrastructure, host file modifications, and database migrations. No destructive or malicious commands are present. The use of Docker and sudo for host entries is legitimate but warrants caution due to elevated privileges and container orchestration.

No concerns found

How this analysis is made

Examples

Standard setup
Set up the local development environment for this devflow project.
Full setup with migrations
Set up the local development environment with full infrastructure and database migrations.
Minimal setup
Set up only the project services without shared infrastructure.

name: setup description: Initialize and set up local development environment with devflow infrastructure allowed-tools: Bash, Read, Write disable-model-invocation: true argument-hint: [--full|--minimal]

Local Development Setup

Set up a complete local development environment for a devflow-managed project.

Usage

  • /devflow-setup - Standard setup (infrastructure + project)
  • /devflow-setup --full - Full setup including database migrations
  • /devflow-setup --minimal - Project only, skip shared infrastructure

Prerequisites Check

First, verify the environment:

devflow doctor

If any tools are missing, inform the user what needs to be installed before proceeding.

Setup Steps

Step 1: Verify Configuration

Check that devflow.yml exists in the current directory:

devflow config validate

If missing, ask the user which preset to use (aocodex, aosentry, or custom).

Step 2: Start Shared Infrastructure (unless --minimal)

devflow infra status --json

If infrastructure is not running:

devflow infra up

Step 3: Configure Project for Shared Infrastructure

Check if project is already configured:

devflow infra status --json

If not registered, configure it:

devflow infra configure . --dry-run

Show the user what changes will be made. If they approve:

devflow infra configure .

Step 4: Set Up Hosts Entries

devflow infra hosts list --json

If domains are missing, inform user they need to run with sudo:

sudo devflow infra hosts add

Step 5: Start Project Services

devflow dev start

Step 6: Apply Local Migrations (if --full)

devflow db status --env local --json

If migrations are pending:

devflow db migrate --env local

Step 7: Verify Setup

Run a final status check:

devflow infra status
devflow db status --env local

Output

Provide a summary showing:

  • Infrastructure status (Traefik dashboard URL)
  • Project domains configured
  • Services running
  • Database migration state
  • Any manual steps remaining (like hosts file if sudo wasn't available)

Error Handling

  • If Docker is not running, instruct user to start Docker Desktop or daemon
  • If mkcert CA is not installed, provide installation instructions
  • If ports are in use, identify conflicting processes
  • If compose file has issues, show specific validation errors

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/local-development-environment-setup-mm8o51q5/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/local-development-environment-setup-mm8o51q5' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/local-development-environment-setup-mm8o51q5/download' --output '.skill-downloads/local-development-environment-setup-mm8o51q5/SKILL.md.part' && mv '.skill-downloads/local-development-environment-setup-mm8o51q5/SKILL.md.part' '.skill-downloads/local-development-environment-setup-mm8o51q5/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Bash, Read, Write

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/local-development-environment-setup-mm8o51q5/SKILL.md' && test -s '.skill-downloads/local-development-environment-setup-mm8o51q5/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/setup' && cp -R '.skill-downloads/local-development-environment-setup-mm8o51q5' '.claude/skills/setup'

Cursor
test -f '.skill-downloads/local-development-environment-setup-mm8o51q5/SKILL.md' && test -s '.skill-downloads/local-development-environment-setup-mm8o51q5/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/setup' && cp -R '.skill-downloads/local-development-environment-setup-mm8o51q5' '.cursor/skills/setup'

Codex
test -f '.skill-downloads/local-development-environment-setup-mm8o51q5/SKILL.md' && test -s '.skill-downloads/local-development-environment-setup-mm8o51q5/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/setup' && cp -R '.skill-downloads/local-development-environment-setup-mm8o51q5' '.agents/skills/setup'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/local-development-environment-setup-mm8o51q5'

openskills read 'local-development-environment-setup-mm8o51q5'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/local-development-environment-setup-mm8o51q5/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills