tilt
Tilt local development and e2e testing. Triggers on tilt, kind cluster, e2e tests, test/tilt, local dev cluster.
What this skill does
# Tilt Local Development ## Rules - **NEVER run `tilt up` or `tilt down`** - Tilt is interactive, runs in the user's terminal - Ask the user to start Tilt when needed - Ask the user to verify Tilt shows all services ready before running tests ## Checking Tilt Status ```bash # Check if Tilt is running tilt get uiresources # Check if all services are ready (non-zero exit = not ready) tilt wait --timeout 5s --for=condition=Ready uiresource/<resource> ``` If Tilt is not running, ask the user: > "Please start Tilt (`tilt up` or `tilt ci`) and wait for all services to be ready." ## Running test/tilt Tests These are e2e tests that run against the Tilt-managed kind cluster. ```bash # All tilt tests cd test/tilt && go test -v ./... # Specific test cd test/tilt && go test -v -run TestSpecificFunction ./... # With log file for easier reading cd test/tilt && go test -v ./... 2>&1 | sed 's/\x1b\[[0-9;]*m//g' > test.log ``` ## Running envtests (no Tilt needed) Controller integration tests use envtest, independent of Tilt: ```bash # Setup (one-time) go install sigs.k8s.io/controller-runtime/tools/setup-envtest@latest # Run envtests KUBEBUILDER_ASSETS=$(setup-envtest use -p path 1.34.1) go test -v ./cmd/... # Run specific controller tests KUBEBUILDER_ASSETS=$(setup-envtest use -p path 1.34.1) go test -short -v ./cmd/<controller>/internal/reconcilers/... ``` ## Prerequisites If the user needs to set up Tilt from scratch: **Install:** ```bash brew install kind ko tilt tilt-dev/tap/ctlptl docker colima ``` **Start colima (Docker):** ```bash colima start --cpu 4 --memory 6 export DOCKER_HOST=unix://$HOME/.colima/default/docker.sock ``` **Symlink dependent repos into .cache/:** ```bash mkdir -p .cache ln -s <path-to-api-machinery-backend> .cache/backend ln -s <path-to-dgxc-admission-controller> .cache/admission-controller ln -s <path-to-platform-apis> .cache/apis ``` **Start cluster and Tilt:** ```bash ctlptl apply -f ctlptl.yml tilt up # opens web UI on space bar ``` ## Troubleshooting - **Pod failures with taggedPointer errors**: Use colima, not Rancher Desktop - **Tilt not finding repos**: Check .cache/ symlinks point to correct locations - **Tests fail connecting to cluster**: Verify Tilt shows all services ready - **Stale cluster**: `kind delete cluster && ctlptl apply -f ctlptl.yml`
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.