skills/0xbigboss/tilt/SKILL.md
Manages Tilt development environments via CLI and Tiltfile authoring. Must use when working with Tilt or Tiltfiles.
npx skillsauth add aiskillstore/marketplace tiltInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Tilt live-reloads aggressively. Never suggest restarting tilt up or manually refreshing resources—Tilt handles this automatically in nearly all cases.
| Change Type | What Happens | Your Action |
|------------|--------------|-------------|
| Tiltfile edits | Tilt re-evaluates the entire Tiltfile on save | Just save the file |
| Source code with live_update | Files sync to container without rebuild | Just save the file |
| Source code without live_update | Full image rebuild triggers automatically | Just save the file |
| Kubernetes manifests | Resources re-apply automatically | Just save the file |
| Frontend with HMR | Browser updates via Hot Module Replacement | Just save the file |
| Backend with watch tools | Process restarts via nodemon/air/watchexec | Just save the file |
Restarting tilt up is required only for:
Instead of restarting, verify updates propagated:
# Check resource status after saving
tilt get uiresource/<name> -o json | jq '.status.updateStatus'
# Watch for update completion
tilt wait --for=condition=Ready uiresource/<name> --timeout=60s
# Check recent logs for reload confirmation
tilt logs <resource> --since 1m
tilt logs <resource> --since 5m | rg -i "reload|restart|updated|synced"
Always run tilt up in a tmux session using send-keys. This ensures:
SESSION=$(basename $(git rev-parse --show-toplevel 2>/dev/null) || basename $PWD)
# Start tilt in tmux (idempotent, send-keys for proper shell init)
if ! tmux has-session -t "$SESSION" 2>/dev/null; then
tmux new-session -d -s "$SESSION" -n tilt
tmux send-keys -t "$SESSION:tilt" 'tilt up' Enter
echo "Started tilt in tmux session: $SESSION"
elif ! tmux list-windows -t "$SESSION" -F '#{window_name}' | grep -q "^tilt$"; then
tmux new-window -t "$SESSION" -n tilt
tmux send-keys -t "$SESSION:tilt" 'tilt up' Enter
echo "Added tilt window to session: $SESSION"
else
echo "Tilt already running in session: $SESSION"
fi
To check tilt output:
SESSION=$(basename $(git rev-parse --show-toplevel 2>/dev/null) || basename $PWD)
tmux capture-pane -p -t "$SESSION:tilt" -S -50
To stop tilt:
SESSION=$(basename $(git rev-parse --show-toplevel 2>/dev/null) || basename $PWD)
tmux send-keys -t "$SESSION:tilt" C-c
Never run tilt up directly in foreground or with run_in_background. Always use tmux.
tilt get uiresources -o json to query resource status programmaticallytilt get uiresource/<name> -o json for detailed single resource statetilt logs with --since, --tail, --json flags for log retrievaltilt trigger <resource> to force updates when auto-reload didn't triggertilt wait to block until resources reach ready statetilt get uiresources -o json | jq '.items[] | {name: .metadata.name, runtime: .status.runtimeStatus, update: .status.updateStatus}'
tilt wait --for=condition=Ready uiresource/<name> --timeout=120s
tilt logs <resource> # Current logs
tilt logs <resource> --since 5m # Logs from last 5 minutes
tilt logs <resource> --tail 100 # Last 100 lines
tilt logs --json # JSON Lines output
tilt trigger <resource>
tilt up # Start Tilt
tilt down # Stop and clean up
tilt ci # CI/batch mode
unknown, none, pending, ok, error, not_applicablenone, pending, in_progress, ok, error, not_applicabledevelopment
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.