tilt-setup

Tilt Setup

Install Tilt and scaffold or audit Tiltfile + tilt/ configurations for local Kubernetes development with ecosystem-aware templates.

Pre-flight

Run the detection script to understand current state:

python3 ${CLAUDE_SKILL_DIR}/scripts/detect_tilt.py <project-root>

The detector reports: tilt/kubectl binaries, current kubectl context (with production-pattern matching), existing Tiltfile and tilt/ modular layout (also recognizes legacy .tilt/), .tiltignore, tilt_config.json, ecosystems detected (Java/Gradle, Next.js, Python, infra), local cluster tools available, and audit violations (TILT001–TILT025) when a Tiltfile exists.

Decision Flow

Run detector
    |
    ├── tilt_binary.installed = false → Install Tilt first
    |
    ├── kubectl_context.is_production_pattern = true → STOP and warn user
    |
    ├── tiltfile.exists = true → Phase 1: Audit
    |
    └── tiltfile.exists = false → Phase 2: Scaffold

Phase 1: Audit (Existing Tiltfile)

1. Summarize findings — show a status table:

   Component	Status	Detail
   tilt binary	installed/missing	version, path
   kubectl context	safe/production	current context, classification
   Tiltfile	found/not found	path, line count
   Modular layout	yes/no	tilt/ files (config.star, services.star, *.yaml)
   Ecosystems	N detected	java-gradle, nextjs, python, infra
   Service count	N services	k8s_resource calls
   Safety guard	yes/no	allow_k8s_contexts or manual guard
   .tiltignore	yes/no	path

2. Present audit violations grouped by severity (ERROR > WARNING > INFO):

   • Show rule ID, message, fix hint
   • Rules cover: missing safety guard, deprecated restart_container, missing live_update, no watch_settings, no update_settings, missing resource_deps/labels/port_forwards, monolithic Tiltfile, etc.

3. Use AskUserQuestion (multiSelect: true) — ask which violations to fix.