silo

silo

Use this Skill when a project uses silo.toml or the user asks about silo commands, profiles, port isolation, or k3d/Tilt integration.

Instructions

1. Prefer bundled docs for authoritative behavior: silo doc <topic> (see topics below).
2. Use CLI commands directly; keep changes minimal and aligned with current config:
   • silo up [name] starts an instance (k3d optional, Tilt starts).
   • silo down stops Tilt; --delete-cluster removes k3d; --clean removes env/lockfile.
   • silo env [name] generates env + lockfile only.
   • silo profiles lists profile names.
   • silo status reports current instance.
   • silo version prints CLI version.
3. Profiles:
   • Resolution order: --profile > SILO_PROFILE > lockfile > base config.
   • Switching profiles requires --force.
4. Hosts and URLs:
   • Prefer *.localhost hostnames for cookie isolation (avoid localhost:PORT).
5. k3d:
   • If k3d.registry.enabled = true, ensure K3D_REGISTRY_PORT is defined in [ports].
6. Do not edit .silo.lock by hand; rerun silo up or silo down --clean instead.

Bundled Docs

Use silo doc [topic] (or --list / --json for discovery):

Examples

silo up dev
silo up --profile testnet --force
silo doc profiles