dust-hive
Tool for running multiple isolated Dust development environments using git worktrees and Docker.
Install
mkdir -p .claude/skills/dust-hive && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2373" && unzip -o skill.zip -d .claude/skills/dust-hive && rm skill.zipInstalls to .claude/skills/dust-hive
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Information about dust-hive, a CLI tool for running multiple isolated Dust development environments. ALWAYS enable this skill when the working directory is under ~/dust-hive/. Use for understanding port allocation, running tests, and working with the environment.Key capabilities
- →Run multiple isolated Dust development environments simultaneously
- →Check the current state of a dust-hive environment
- →Automatically load environment variables using direnv
- →Understand port allocation for different services within an environment
- →Run linters, type checks, and builds for Dust apps
- →Execute front tests in cold environments using shared test containers
How it works
dust-hive is a CLI tool that creates isolated Dust development environments, each with its own Git worktree, port range, Docker containers, and database instances, managed via direnv for environment variables.
Inputs & outputs
When to use dust-hive
- →Checking environment status
- →Managing port conflicts
- →Running tests in isolated environments
About dust-hive
Provides management for isolated dev environments including port allocation, database instances, and Docker containers. Detects environments automatically via workspace path.
Information about dust-hive, a CLI tool for running multiple isolated Dust development environments. ALWAYS enable this skill when the working directory is under ~/dust-hive/. Use for understanding port allocation, running tests, and working with the environment.
Prerequisites
Limitations
- →Node modules structure uses shallow copy with symlinks
- →SDK watcher may not detect changes after git rebase or pull
- →Requires manual cleanup for `npm install` due to node_modules structure
How it compares
This tool provides isolated development environments with automatic port and database management, simplifying concurrent development compared to a single, shared setup.
Compared to similar skills
dust-hive side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| dust-hive (this skill) | 1 | 10mo | Review | Intermediate |
| supabase-local-dev-loop | 0 | 4mo | Caution | Beginner |
| manage-infra | 0 | 9mo | Review | Beginner |
| fly-io-deployer | 0 | 6mo | Caution | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by dust-tt
View all by dust-tt →You might also like
supabase-local-dev-loop
jeremylongshore
Configure Supabase local development with hot reload and testing. Use when setting up a development environment, configuring test workflows, or establishing a fast iteration cycle with Supabase. Trigger with phrases like "supabase dev setup", "supabase local development", "supabase dev environment", "develop with supabase".
manage-infra
jpmolinamatute
Starts or stops the Docker Compose infrastructure (Postgres 17).
fly-io-deployer
LeoYeAI
Deploy and operate Node, Python, Go, Rust, Elixir, and Docker apps on Fly.io with production-grade fly.toml authoring, Machines API orchestration, region selection (latency vs sovereignty vs egress), Fly Postgres clustering, LiteFS for SQLite replication, Upstash Redis bindings, Tigris object storag
test-with-postgres
storj
Run unit tests that require PostgreSQL. Use this skill when the user wants to run tests with PostgreSQL database backend. Automatically handles checking for and configuring a PostgreSQL Docker container.
local-env
dailydotdev
Local environment management - run SQL queries, set up fake payments, reset test data. Use when the user needs help with local database operations or test data setup.
supabase-multi-env-setup
jeremylongshore
Configure Supabase across development, staging, and production environments. Use when setting up multi-environment deployments, configuring per-environment secrets, or implementing environment-specific Supabase configurations. Trigger with phrases like "supabase environments", "supabase staging", "supabase dev prod", "supabase environment setup", "supabase config by env".