Use when building or restyling strike's TUI — views, panels, modals, pickers, badges, dashboards, status rows, or any layout work in internal/frontend/tui. Covers the internal/frontend/tui/ui component catalog and internal/frontend/tui/theme tokens. Do not…
Use when running tests, validation, CI checks, coverage, race detection, vet, build, or verifying strike-cli changes. Trigger on make test, go test, lint, verify, validate, regression, or before claiming work done.
Use when adding or extending Go tests in strike-cli — *_test.go, table-driven cases, fixtures, httptest, tool Ask helpers, TUI harnesses, coverage gaps. Do not use for running tests only (use test-and-validate).
Drive open GitHub issues on strike-cli to merge via parallel worktrees — parse wave/depends/blocks/conflicts headers, dispatch issue-handler agents, prefer bugs-first, never parallelize conflicting issues. Use when asked to orchestrate issues, farm the…
Offline product happy-path checks for strike-cli — boot, echo turn, interrupt, session resume. Use when verifying user-visible CLI/TUI/session/auth changes, before release, or when issue-handler tier B/C touches cmd/, engine, tui input/keymap, session, or…
Own a GitHub issue end-to-end in strike-cli — worktree, implement, test, PR, spawn review agents that comment on the PR, address feedback in a loop, CI, merge. Use when asked to handle/fix/close an issue, ship a PR from an issue, or babysit issue work through…
Discovered from skills/ not contributions
Say hello