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.

Use when choosing, running or repairing storage and backups - block vs file vs object, ZFS (pools, vdev layouts, datasets, snapshots, send/receive, scrub, ARC), Ceph (cephadm, MON/MGR/OSD/MDS, pools, CRUSH, RBD/CephFS/RGW, health, OSD replacement, capacity), NFS and iSCSI basics, S3-compatible object storage (MinIO status, Garage, SeaweedFS, Ceph RGW), Kubernetes storage pointers (CSI, Rook-Ceph, Longhorn), backup strategy (3-2-1-1-0, RPO/RTO, retention, immutability, encryption, off-site), restic, BorgBackup/borgmatic, Velero, rclone, Proxmox Backup Server pointer, restore testing, disaster-recovery runbooks, capacity monitoring and SMART. Not for LVM and single-host filesystems (devops-linux), database dumps and PITR (devops-databases), Proxmox PBS jobs and vzdump (devops-proxmox), PV/PVC basics (devops-kubernetes) or public-cloud storage services.

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 scheduling Hermes Agent work - hermes cron create/edit/list/pause/resume/run/cancel/remove, schedule formats, --workdir (so .hermes.md loads), --timezone, --reasoning-effort, --catch-up, --grace-minutes, model pinning, delivery targets, preflight (blocked_config), failure alerts, daily/weekly/monthly job recipes. Not for what the jobs should say (hermes-rhythm), subagent limits (hermes-delegation) or messaging adapter setup (hermes-gateways).

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".