Canonical browser-testing workflow for the psynk.ai app — test, debug, investigate, and improve the product through a Chrome DevTools Protocol browser session plus local codebase access. Use when the user wants to manually test or verify a UI flow, starts or references a CDP-enabled browser/remote debugging port, and wants the assistant to propose test scenarios, watch their browser activity, drive browser steps on request, collect console/network/DOM/storage/screenshot evidence, investigate frontend/backend issues in the code, record findings, fix small issues immediately, or delegate larger issues while continuing exploratory testing. Default mode attaches to a browser the user is already driving; it can also bring up a fresh self-driven headless stack (see references/local-stack.md).
Build me merge-confidence on a PR I have checked out locally by collaboratively authoring a "visual book" — a single self-contained HTML file that tells the story of the problem the PR solves and then explains the change level by level, diagram-first, anticipating the questions I'd ask. Not a bug hunt and not a back-and-forth transcript: the book is the artifact, and finishing it together is how I come to understand the PR. Use when I want to walk through / understand / get confidence on a PR or branch before merging, rather than have it reviewed.
Use the `fj` Forgejo CLI to interact with Forgejo/Gitea forges from the terminal: repos, issues, pull requests, releases, actions, wikis, users, and orgs. Use when the user wants to open/list/merge PRs, file or search issues, clone/create repos, cut releases, or otherwise operate on a Forgejo instance without the web UI.
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (TERMINOLOGY.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Use when creating a new project from scratch that needs Nix flake setup with devshell
Use when the user wants to submit a markdown file (.md) as a task to the shepherd task system, or mentions sending work to shepherd