
Use when explicitly evaluating task complexity, required skills, risk level, or work scale using the vendored SkillTrust task-analysis reference.
Use when a task involves architecture decisions, migrations, rollout planning, system boundaries, technical tradeoffs, or rollback risk.
Use when creating or reviewing PRDs, ADRs, design docs, UI specs, or work plans and a documentation template or document-type decision is needed.
Use when evaluating OpenCLI from Codex with strict read-only constraints, especially for HackerNews, local GitHub CLI status, or Codex Desktop CDP reachability checks.
Use when explicitly running a frontend review recipe against React or TypeScript UI work and the operator wants the vendored SkillTrust reference flow.
Use when the user explicitly mentions Google Stitch and wants design tokens, CSS custom properties, Tailwind theme guidance, or code-level design-system artifacts.
Use when the user explicitly mentions Google Stitch and asks to convert Stitch designs into Vite, CRA, or generic React components.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when a task involves backend services, API routes, database writes, auth, permissions, error semantics, or service contracts.
Use when the task involves front-end page or component design quality, Figma or screenshot translation, spacing or typography refinement, responsive behavior, UI state validation, or visual polish before merge.
Use when a task involves user experience, product flow, onboarding, conversion, user journeys, friction points, or UI acceptance criteria.
Add or refresh repository-level Codex scaffolding such as .codex/config.toml and AGENTS.md. Use when a repo needs lightweight Codex defaults, repo-specific instructions, or a repeatable project bootstrap.
Run the minimum useful verification after repository bootstrap or small setup changes, then produce a concise change summary. Use when a repo has just been initialized or had Codex scaffolding added and the user wants a quick verification-and-summary pass.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Capture an external webpage into a reusable local markdown note. Use when the user wants a rendered page saved locally, preserved for later reference, or turned into a markdown source artifact rather than only summarized in chat.
Safely operate in repositories that use Git worktrees or live inside a meta-workspace with multiple repos. Use when a task involves git roots, linked worktrees, pointer directories, or avoiding the wrong repository context.
Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads, date/time mocking, WebSockets, geolocation, permissions, multi-tab/popup flows, mobile/responsive layouts, touch gestures, GraphQL, error handling, offline mode, multi-user collaboration, third-party services (payments, email verification), console error monitoring, global setup/teardown, test annotations (skip, fixme, slow), test tags (@smoke, @fast, @critical, filtering with --grep), project dependencies, security testing (XSS, CSRF, auth), performance budgets (Web Vitals, Lighthouse), iframes, component testing, canvas/WebGL, service workers/PWA, test coverage, i18n/localization, Electron apps, or browser extension testing. Covers E2E, component, API, visual, accessibility, security, Electron, and extension testing.
Use when explicitly reviewing or designing tests, TDD flow, coverage expectations, or TypeScript/Vitest/RTL/Playwright testing guidance from the vendored reference.
Use when the user explicitly mentions Google Stitch and wants a Stitch-derived DESIGN.md or design-language reference synthesized from Stitch project screens.
Use when the user explicitly mentions Google Stitch and asks to convert Stitch designs into Next.js App Router components.
Use when the user explicitly mentions Google Stitch and wants a structured Stitch-ready UI prompt or prompt refinement from rough product/design ideas.
Use when explicitly reviewing, generating, refactoring, or migrating Terraform/OpenTofu IaC and checking failure modes such as identity churn, secrets, blast radius, CI drift, or compliance gates.
Use when handing work between Codex, Cursor, or other agents, before pausing or switching tools, to refresh docs/agent-handoff.md with branch, changed files, verification evidence, and an explicit next step.