coder

Guidelines for creating and managing Pull Requests in this repo

Sub-agent powered code reviews spanning correctness, tests, consistency, and fit

Run isolated xum desktop (Electron) instances (temp XUM_ROOT + free ports)

Run multiple isolated xum dev-server instances (temp XUM_ROOT + free ports)

Regenerate high-resolution README screenshots from Storybook stories. Use this skill when visual diffs are detected in any story under "Docs/README Screenshots", or when story data/layout changes require updated documentation assets. Triggers on: visual…

Guidelines for when to use (and avoid) useEffect in React components

Terminal-Bench integration for Xum agent benchmarking and failure analysis

Testing doctrine, commands, and test layout conventions

Diff-scoped self-review of frontend changes under site/src against the FE pattern rules (FE1-FE10) before creating or updating a PR. Use whenever a branch diff touches site/src files.

Checks if code changes require documentation updates

Authoring workflow and guardrails for writing, moving, or restructuring Coder documentation under docs/. Points at the canonical content guidelines and prose style guide, then walks research, routing, Diátaxis mode, structure, pedagogy, and validation.…

Multi-reviewer code review. Spawns domain-specific reviewers in parallel, cross-checks findings, posts a single structured GitHub review.

Reviews code changes for bugs, security issues, and quality problems

Run a Coder PR dogfood instance: inspect PR context, check out the right branch or stack, start Coder with scripts/develop.sh using agent-safe dev-instance practices, validate the changed functionality with UI evidence when needed, and report findings.

Guide for creating, updating, and following up on pull requests in the Coder repository. Use when asked to open a PR, update a PR, rewrite a PR description, or follow up on CI/check failures.

Use this skill when a repository already has an open pull request and you need to run the Coder Agents Review loop: request review with `/coder-agents-review` when needed, wait for feedback from the `coder-agents-review` GitHub app, fix issues, and repeat…

Terminal and TUI automation CLI for AI agents. Use when the user needs to create a terminal session, run a command in a terminal, automate an interactive CLI or TUI, wait for terminal output, capture a TUI screenshot, export a terminal recording, or test a…

Structured TUI dogfooding and QA workflow using agent-tty. Use for exploratory testing, bug hunting, release-readiness validation, and UX review of terminal applications.

Terminal and TUI automation CLI for AI agents. Use when the user needs to create a terminal session, run a command in a terminal, automate an interactive CLI or TUI, wait for terminal output, capture a TUI screenshot, export a terminal recording, or test a…

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module…

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.

Internal maintainer SOP for version bumps, release PRs, tagging, publishing, and post-publish verification in this repository.

Guide for running statistically meaningful agent-tty evals with trials, parallelism, and A/B comparison. Covers non-determinism baseline, recommended sample sizes, and result interpretation.

Sub-agent powered code reviews spanning correctness, tests, consistency, and fit

Terminal-Bench integration for Mux agent benchmarking and failure analysis

Regenerate high-resolution README screenshots from Storybook stories. Use this skill when visual diffs are detected in any story under "Docs/README Screenshots", or when story data/layout changes require updated documentation assets. Triggers on: visual…

Run isolated mux desktop (Electron) instances (temp MUX_ROOT + free ports)

Run multiple isolated mux dev-server instances (temp MUX_ROOT + free ports)

Guidelines for creating and managing Pull Requests in this repo

Testing doctrine, commands, and test layout conventions

Per-workspace KIND clusters for coder-k8s dev + demos.

Sub-agent powered code reviews spanning correctness, tests, consistency, and fit

Index + offline snapshot of coder/coder documentation (progressive disclosure).

Guidelines for creating and managing Pull Requests in this repo

Install, deploy, or bootstrap a new Coder (coder/coder) deployment end-to-end. Use for first-time setup on Docker, Kubernetes/Helm, a VM, cloud, HTTPS/domain setup, creating the first admin, pushing a starter template, or building the first workspace. Do not…

Create, edit, push, or version a Coder template. Use for requests like "scaffold a Docker template", "build a Kubernetes template", "add a coder_parameter for the Git repo URL", "push my template to this Coder deployment", "update the existing aws-linux…

Add a Coder module from registry.coder.com/modules to an existing Coder template, or update one that is already there. Use for requests like "add the Cursor IDE to my template", "give workspaces JetBrains access", "set up code-server", "wire in dotfiles",…

Creates and updates Coder Registry modules with proper scaffolding, Terraform testing, README frontmatter, and version management

Creates and updates Coder Registry workspace templates with agent setup, infrastructure provisioning, and module consumption

Run and debug BalatroBot locally. Use when you need to start Balatro with the BalatroBot Lua mod, manually test or reproduce issues via the JSON-RPC HTTP API, inspect the newest session logs under logs/, and capture screenshots into logs/<session>/artifacts/…

Guide for creating, updating, and following up on pull requests in the aibridge repository. Use when asked to open a PR, update a PR, rewrite a PR description, or follow up on CI/check failures.

Pull request submission and review lifecycle. Use when creating, pushing, or monitoring PRs to ensure all CI checks pass and Codex review comments are resolved before declaring a PR ready.