using-maestro

Coordinate Kubernetes-based Maestro development workflows with Tilt, k3d, and GKE.

1|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/89jobrien/dotfiles --skill using-maestro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-maestro
Source: https://github.com/89jobrien/dotfiles/tree/main/dot-claude/skills/using-maestro
Command: npx skills add https://github.com/89jobrien/dotfiles --skill using-maestro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maestro developers often juggle Kubernetes-centric local development with Tilt, GKE deployments, and Go+Rust tooling, making it hard to keep environments deterministic and workflows fast.

Core Features & Use Cases

  • Orchestrates Tilt-based local dev for Maestro projects, coordinating pod lifecycles and service orchestration.
  • Provides context switching between local k3d/Tilt and GKE clusters for testing and deployment workflows.
  • Guides Go API and Rust CLI development with standardized conventions and workflow automation for Maestro.

Quick Start

Install and run Tilt to boot the local Maestro environment and connect to your cluster.

Frequently Asked Questions about using-maestro

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate a local Kubernetes dev environment with Tilt and k3d?

Orchestrating a local Kubernetes dev environment with Tilt and k3d involves coordinating pod lifecycles and service orchestration to spin up local clusters. It manages container orchestration and automates workflows for end-to-end development tasks.

What is the best way to switch between local k3d and GKE Kubernetes contexts?

Switching between local k3d and GKE Kubernetes contexts is handled through guided context switching for testing and deployment workflows. It allows developers to move between local Tilt environments and cloud clusters to keep configurations deterministic.

Does this workflow support development for both Go API and Rust CLI components?

Yes, this workflow supports development for both Go API and Rust CLI components. It provides standardized conventions and workflow automation specifically tailored for Maestro developers working across these languages.

How do I manage pods and run common kubectl workflows during Maestro development?

Managing pods and running common kubectl workflows during Maestro development is supported through built-in guidance and automation. It coordinates pod lifecycles and integrates standard Kubernetes commands directly into the development workflow.

Why does coordinating Kubernetes-based development with Tilt and GKE make environments hard to manage?

Coordinating Kubernetes-based development with Tilt, GKE, and Go+Rust tooling makes environments hard to manage because developers must juggle multiple contexts. This workflow solves the problem by keeping environments deterministic and making workflows fast.