tilt-dev
Tilt Development Environment Management
Manage and troubleshoot local development stacks orchestrated by Tilt.
Quick Start
Script paths shown as scripts/... assume your current working directory is skills/tilt-dev/. From repo root, use skills/tilt-dev/scripts/....
Check if Services Are Running
Always check before starting Tilt:
# Run status check script
scripts/check_tilt_status.sh [port]
# Or manually
tilt get uiresources --port <PORT>
Check Service Health
# Run health check script
scripts/get_service_health.sh
# Or manually check endpoints
curl http://localhost:3000/health # Backend
curl http://localhost:3001/ # Frontend
curl http://localhost:4111/swagger-ui # Mastra
Start Tilt
Only if services are not already running:
tilt up --port <PORT>
Common ports: 10102, 10301, 10350
View Logs
tilt logs --port <PORT> <resource>
# Follow logs
tilt logs --port <PORT> <resource> --follow
Stop Tilt
tilt down
Important Principles
Always Check First
Services are likely already running with hot reload. Never blindly run tilt up without checking status first.
Prefer Health Checks Over Restarts
Check health endpoints and logs before restarting services. Tilt hot-reloads changes automatically.
Use the Tilt UI
Access at http://localhost:<PORT> for:
- Real-time resource status
- Build logs
- Service restarts
- Error messages
Common Workflows
Debug Service Not Responding
- Check Tilt UI resource status
- View resource logs:
tilt logs --port <PORT> <resource> - Check health endpoint with curl
- Review error messages in logs
View Recent Errors
# Tail logs for specific service
tilt logs --port <PORT> <resource> | tail -50
# Follow logs in real-time
tilt logs --port <PORT> <resource> --follow
Diagnose Tilt Issues
tilt doctor
Reference
See references/tilt_commands.md for:
- Complete command reference
- Tiltfile (Starlark) syntax guidelines
- Project-specific examples
- Troubleshooting guide
- Port conventions
Scripts
scripts/check_tilt_status.sh [port]- Check if Tilt is running and list resourcesscripts/get_service_health.sh- Check health endpoints for common services
More from liatrio-labs/ai-prompts
git-commit-conventional
Create Conventional Commit messages and execute safe git commits from working tree changes. Use when users ask to create a commit, write a conventional commit message, split broad changes into multiple commits, stage only parts of files, run pre-commit before committing, or perform a quick commit-time quality review with severity guardrails.
24create-pull-request
Generate a reviewer-ready pull request or merge request title and description from branch changes. Use when a user asks to draft PR/MR content, summarize branch deltas against a base branch, or optionally create the PR with gh/glab after approval.
23create-mermaid-diagrams
Create, validate, and repair Mermaid diagrams for technical documentation with a deterministic CLI feedback loop. Use when an AI needs to create Mermaid diagrams, improve Mermaid diagram quality, validate Mermaid fences in markdown, diagnose Mermaid rendering failures, or fix Mermaid syntax and formatting issues.
21liatrio-brand-guidelines
Applies Liatrio brand guidelines to UI design, brand audits, and asset selection. Use when users request Liatrio styling, logo variants, typography or color decisions, visual polish, or formal brand compliance checks.
21branch-surgery-pr-split
Split oversized or mixed-concern branches into smaller, reviewable PR stacks with safety refs, topology selection, parity audits, and merge sequencing. Use when a PR or branch is too large, difficult to review, mixed across concerns, conflict-prone, or needs to be decomposed without losing net changes.
21uv-usage
Provides concise guidance for using uv (Python package manager), including project workflows, pip-compatible commands, Python version management, and PEP 723 inline script dependencies. Use when users mention uv, uv run, inline dependencies, PEP 723, or Python dependency/project management.
16