Use when handling form submissions, mutations, or server-side logic with type safety in Astro via defineAction / astro:actions.

Use when adding React, Vue, Svelte, Solid, Preact, or another UI framework to an Astro project via @astrojs/* integrations.

Use when adding interactivity to Astro pages via client:* directives or rendering dynamic server content with server:defer.

Use when designing an Android screen or flow — deliverable is a device-framed HTML mockup and developer handoff spec, never Compose code.

Use when starting any design task — resolves register, sets the 3 dials, locks Gate 0, and routes to the right move and target skill.

Use when adding or reviewing motion on an already-settled layout or component — never to hide or compensate for an unfinished one.

Goroutines, channels, `context`, and `errgroup` for Go 1.27 — plus the number-one documented pitfall: **leaking goroutines on an unbuffered channel + early return.**

Use when laying out a new Go service, choosing an HTTP router or DB layer, or wiring dependencies. Not for concurrency (go-concurrency) or language idioms (go-core-idioms).

Use when setting up Go modules/workspaces, configuring golangci-lint v2, running govulncheck, or building a Go CI quality gate. Not for app logic or non-Go audits.

Use when configuring how a Hermes Agent spawns subagents - delegation.* keys (model, provider, max_spawn_depth, max_concurrent_children, reasoning_effort, timeouts), delegation.backend with the advanced-delegation plugin (model_map, profile_routes), manager/worker topologies and their cost. Not for scheduled jobs (hermes-cron), separate long-lived agents on their own channels (hermes-core profiles, hermes-gateways), or approval policy (hermes-security).

iOS-specific development with XcodeBuildMCP automation tools.

Use when migrating Eloquent models, Jobs, Console commands, Controllers, API Resources, Validation, Factories or Seeders to Laravel 13 PHP attributes.

Use when implementing semantic/vector search in Laravel 13 with PostgreSQL + pgvector.

Use when you are the LEAD (main session) and an owner request arrives that needs agents -- intake, routing, briefs, follow-up, blocks, verification, learning, report. Canonical procedure from request to verified report; not for sub-agents executing a brief.

Use when converting existing code to modular architecture (Laravel, Next.js, React). Triggers: "modularize", "convert to modules", "migrate to modular", "restructure modules".

Use when a film needs product visuals — capturing real screenshots at a fixed DPR, the real OS pointer, masking sensitive data with labeled example data, avoiding third-party brand look-alikes, and recording provenance in .motion/assets.json.

Use when starting or resuming any motion film (launch video, product promo, social ad, README GIF, social loop) — locks the six-block brief (inputs, direction, structure, build, gotchas, start = G0; genre ad|demo), builds the dense beat map (a gesture every 0.5-1 s, ≤ 0.75 s gesture-free, CTA still ≤ 1.2 s), routes the G0 art-direction board, and runs the staged pipeline (one still per beat) with its owner gates.