Use whenever you need to GENERATE or EDIT a raster image — a mockup graphic, logo, sprite, icon, illustration, banner, product shot, or any "make me a picture of…" request. Always use `beckett image`; never scaffold an image project or call codex/python/SVG…
Use whenever you spec, cast, or build frontend/UI work — a page, component, dashboard, marketing site, app screen, or "make it look good." Encodes the house aesthetic and a Tailwind-first, source-before-hand-roll workflow (21st.dev → shadcn/ui → build).…
Use before planning, answering questions about people/projects/environment, or staffing — to pull what you already know from your memory knowledge graph. Use whenever a task names a person, project, team, or your own setup.
Use for ANY browser / computer-use work — a live-site lookup, a signup, a login-and-do-something. Long tasks go to the dedicated BACKGROUND browser agent via `beckett browser` (watch it, steer it mid-run, stop it); a genuinely one-shot read can run inline via…
Use to post the final result of a piece of work in channel, in voice. Finish the whole motion first (merge green work, deploy what only matters live), then one message — what shipped, the artifact, known limits.
Use whenever you touch GitHub — creating a repo, pushing a branch, opening/merging/reviewing a PR, filing or answering an issue, or getting installed on someone's repo. Always go through `beckett gh ...`; never call raw `gh`/`git push` and never run `gh auth`.
Use the moment a new @beckett mention arrives, before any work. Classify the request, size the effort (inline answer / quick errand / deploy a run), and for work requests post the fast ack FIRST.
Use for creating, storing, or using credentials for an external account without exposing passwords or TOTP seeds in the transcript. Drive the installed `jingle` vault by subprocess injection; never print or transmit a secret.