Review a proposed or completed cloakbrowser-mcp change only when the user explicitly requests code review, quality review, or a pre-merge assessment. Evaluate strict TypeScript, CLI and transport contracts, upstream-tool parity, child-process and session boundaries, tests, docs, packaging, workflows, security, and…
Simplify existing cloakbrowser-mcp code only when the user explicitly requests a behavior-preserving clarity refactor. Apply to strict TypeScript bridge, CLI, Streamable HTTP, tests, scripts, workflows, or documentation while preserving public CLI, environment, MCP, transport, package, and test behavior; do not use…
Improve cloakbrowser-mcp agent instructions, skill routing, durable decisions, task context, or handoffs only when the user explicitly requests context optimization, migration, stale-guidance repair, or recoverable session handoff. Align guidance with current bridge code, tests, configuration, docs, and delivery…
Write or revise cloakbrowser-mcp technical documentation or record a settled architecture decision only when the user explicitly requests documentation, an ADR, or documentation required by an authorized public-contract change. Use for bridge architecture, CLI and environment configuration, stdio or Streamable HTTP…
Perform an adversarial, evidence-based challenge of a named high-risk cloakbrowser-mcp product or technical decision only when the user explicitly requests doubt-driven review, red-teaming of a decision, or a go/no-go challenge. Use for public contracts, upstream parity, process and HTTP isolation, unsafe browser…
Refine a cloakbrowser-mcp product, architecture, tooling, documentation, security, packaging, or workflow idea only when the user explicitly asks to ideate, compare directions, explore alternatives, or stress-test an early proposal. Use repository evidence and Prompt MCP for material user selections; do not silently…
Implement exactly one self-contained, explicitly authorized cloakbrowser-mcp task packet per invocation, verify it, update its checklist and handoff, then stop. Use for substantial TypeScript, MCP bridge, CLI, Streamable HTTP, packaging, Docker, CI, security, or documentation work planned under docs/specs; do not use…
Run a structured cloakbrowser-mcp requirements or decision interview only when the user explicitly asks to be interviewed, grilled, or guided through unresolved choices. Inspect repository evidence first and use the globally installed Prompt MCP for all material questions across bridge behavior, CLI/configuration…
Diagnose or improve cloakbrowser-mcp performance only when the user explicitly requests optimization or provides a measured regression in startup, MCP call latency, Streamable HTTP sessions, memory, package or image size, build, tests, or CI. Establish a reproducible Node.js baseline before editing and preserve…
Author the authoritative /plan workflow for substantial cloakbrowser-mcp work when the user invokes /plan or explicitly requests implementation planning, decomposition, milestones, or review-gated task packets. Require an approved specification, use Prompt MCP for unresolved material planning and authorization…
Maintain, organize, consolidate, or audit the cloakbrowser-mcp documentation set only when the user explicitly requests project documentation maintenance or an authorized public change requires it. Use for README, localized MkDocs pages, generated CLI and compatibility content, configuration, tools, Docker, security…
Create, update, prepare, or review a cloakbrowser-mcp GitHub Pull Request only when the user explicitly requests PR work. Follow the repository's branch, base/head, assignee, title, template, check, security, and reporting rules; review remains read-only, and commit, push, PR creation/update, readiness changes, merge…
Prepare, publish, verify, or recover a cloakbrowser-mcp release only when the user explicitly requests release work. Require a Prompt MCP-confirmed target version and stability, follow the repository's version, changelog, PR, GitHub Release, npm, Docker, MCP Registry, and docs process, and never tag, publish…
Audit or harden a concrete cloakbrowser-mcp trust boundary only when the user explicitly requests security work, threat analysis, or a fix for an identified security defect. Cover MCP and HTTP input, upstream child processes, generated config and temporary files, browser profiles, filesystem/network access, unsafe…
Author the authoritative /spec workflow for a substantial cloakbrowser-mcp change when the user invokes /spec, explicitly requests a specification, or authorizes specification work that lacks a durable contract. Establish repository facts, use the globally installed Prompt MCP for every material decision, persist…