Browser automation through the agent-browser CLI for websites, local web apps, forms, screenshots, scraping, QA, and exploratory testing. Use when Codex needs real browser interaction, visual evidence, accessibility snapshots, video recording, or browser-based checks.
Distinctive, production-grade frontend design for web components, pages, applications, dashboards, and interactive tools. Use when Codex needs to build or revise a user-facing UI with strong visual direction, polished interaction states, and non-generic aesthetics.
Structured plan interrogation that asks one sharp question at a time until the design is clear. Use when the user says "grill me", asks to stress-test a plan, or needs dependencies, assumptions, and tradeoffs surfaced before implementation.
Safe edits to Klimkit's repo-managed Codex harness pack, including shared AGENTS guidance, model config, subagents, hooks, and bundled skills. Use when the user asks to change packs/codex/ behavior or kk apply projections, not for normal plugin-only workflow use.
Klimkit's evidence-first Codex workflow for implementation, debugging, review, and release tasks. Use when a user asks for Klimkit, wants checklist/proof-driven work, needs .klimkit task artifacts, or expects verification, reflection, and final review before handoff.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a…
Convert an implementation, debugging, release, UI, backend, security, or research request into a concrete pass/fail acceptance checklist before code changes start. Use when Codex needs blocking success criteria, scope boundaries, verification targets, or a task note for Klimkit-managed work.
Spawn Claude Opus 5 or Fable 5 as an external subagent through the Claude Code CLI, supervised by exactly one GPT-5.6 Sol low-effort babysitter. Use automatically when the user says "spawn Opus 5", "spawn Fable 5", asks for an Opus 5 or Fable 5 sub-agent, or asks Codex to delegate a task to either Claude model.
Trace repository behavior across files before implementation without making edits. Use when Codex needs to understand unfamiliar code, execution paths, architecture, dependencies, tests, ownership boundaries, or contradictory patterns before deciding what to change.
Drive OpenAI Codex through the codex CLI and Codex desktop app from any agent or script. Use when Codex needs to spawn sessions, resume or connect to existing sessions, send live desktop messages, read transcripts, orchestrate many Codex agents, use the Codex app-server WebSocket protocol, or find active Codex…
Create isolated Git worktrees for Klimkit agent work, including simple branch worktrees and feature branches from a base branch that is first updated by merging another branch. Use when the user asks to create a worktree, make a new branch checkout, start isolated feature work, or prepare a dev-synced worktree.
Diagnose bugs, failures, flaky behavior, broken tests, CI failures, or unexpected production signals with a reproduce-first workflow and Klimkit proof. Use when the user asks to debug, investigate, root-cause, fix a failure, or explain why behavior changed.
Perform a fresh-context final acceptance review of the exact draft response against the original request, checklist, changed files, verification evidence, reflection, and proof artifacts. Use as the last gate before telling the human work is complete; especially use from fresh subagents when klimkit-implement requests…
Interview the user relentlessly about a plan, design, architecture, product decision, workflow, or release choice until shared understanding is reached, using repo and web research to prioritize the most important unresolved questions while recording the considered question shortlist, each asked question, and each…
Audit and clean Codex and Claude Code customization across local computers, SSH hosts, containers, and VMs with a two-phase approval gate. Use when the user asks to inventory, compare, reset, consolidate, quarantine, remove, or troubleshoot agents, skills, instructions, hooks, MCP servers, plugins, worktrees, caches…
Run Klimkit's full implementation workflow for code, docs, release, configuration, UI, backend, security-sensitive, or proof-producing changes. Use when the user asks Codex to implement, fix, refactor, release, migrate, wire up, or complete non-trivial repository work with checklist, verification, reflection, and…
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
Write a concise cross-task reflection note after verification and before final review for non-trivial Klimkit work. Use when Codex should connect the current task to prior work history, patterns, risks, or future process improvements.
Set up Claude Code Remote Control on a VM or server so a project folder stays drivable from claude.ai/code and the Claude mobile app after the laptop closes. Use when asked to install, supervise, harden, resize, or debug remote control, keep agent sessions alive across disconnects and reboots, or diagnose why a…
Check, explain, or set up Klimkit static proof-report serving for docs/work HTML reports and Tailscale URLs. Use as the fallback when native hosted publishing (Claude Code Artifacts, Codex Sites) is unavailable and a task needs report-server readiness, /reports/ links, Tailscale Serve verification, or troubleshooting…
Review auth, authorization, secrets, data exposure, input validation, sandboxing, infrastructure, compliance-sensitive flows, and unsafe defaults before completion. Use when a change touches security boundaries, credentials, deployment, containers, permissions, user data, or network exposure.
Set up Klimkit's docs-first repo context for agent work. Use when adding the docs/work/ journal layout, repo skill pointers, config state, or onboarding instructions to a project that should use Klimkit workflows.
Implement behavior changes with narrow red-green-refactor loops and Klimkit proof. Use when adding features, fixing bugs with clear expected behavior, changing shared contracts, or when the user asks for TDD or test-first work.