Maintenance in progress: we are upgrading our database. Some skill downloads may fail for a moment. If one does, please try again in a minute.
coder
- 47 skills
- 0 followers
- 23 hours ago last updated
- ▌ Verify Claudecode Nvim · coder bundleDrive the real claudecode.nvim plugin in a real Neovim (an agent-tty terminal) while a scripted WebSocket client (scripts/ws-client.mjs) plays the Claude Code CLI over the plugin's WebSocket MCP server, and capture screen text, PNG screenshots, WebM video, JSON-RPC traffic, and file state as evidence. Use to prove a claudecode.nvim feature works end to end (openDiff accept/reject, openFile, selection tracking, :ClaudeCodeSend at-mentions, closing diffs, the Claude terminal commands, the editor-state tools, server start/stop) without the claude CLI or network. Also use it to reproduce a bug report, and for any change that can raise a prompt or change the editor mode.
- ▌ Verify Diff Lifecycle · coder bundleModel-check the claudecode.nvim openDiff answer lifecycle (TLA+/TLC) against guards read from the current Lua code. Use after a change to how diffs are resolved, replaced, closed, or answered, or to how openDiff is called (lua/claudecode/diff.lua, diff_inline.lua, server/init.lua, server/client.lua, tools/init.lua, tools/open_diff.lua, tools/close_tab.lua, tools/close_all_diff_tabs.lua, the :ClaudeCodeCloseAllDiffs command in init.lua), and before trusting such a change.
- ▌ Frontend Review 2 · coderDiff-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.
- ▌ Pull Requests 4 · coderGuide 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.
- ▌ Deep Review 3 · coderSub-agent powered code reviews spanning correctness, tests, consistency, and fit
- ▌
- ▌
- ▌
- ▌ Dogfood 2 · coder bundleSystematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
- ▌ Electron 2 · coderAutomate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
- ▌ Deep Review 2 · coderSub-agent powered code reviews spanning correctness, tests, consistency, and fit
- ▌
- ▌ Dev Server Sandbox 2 · coderRun multiple isolated xum dev-server instances (temp XUM_ROOT + free ports)
- ▌ Dev Desktop Sandbox 2 · coderRun isolated xum desktop (Electron) instances (temp XUM_ROOT + free ports)
- ▌ Generate Readme Screenshots 2 · coderRegenerate 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 regressions in readme screenshot stories, changes to App.readmeScreenshots.stories.tsx, changes to mockFactory.ts that affect screenshot stories, or explicit user request to update README images.
- ▌ Agent Browser · coder bundleBrowser 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 button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
- ▌ Vercel Sandbox · coderRun agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.
- ▌ Agent Tty 2 · coderTerminal 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 CLI workflow with reviewable artifacts.
- ▌ Balatrobot · coderRun 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/ using only the balatrobot CLI (no curl, no uvx).
- ▌ Coder Modules · coderCreates and updates Coder Registry modules with proper scaffolding, Terraform testing, README frontmatter, and version management
- ▌ Coder Templates · coderCreates and updates Coder Registry workspace templates with agent setup, infrastructure provisioning, and module consumption
- ▌
- ▌ Setup · coder bundleInstall, 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 use for upgrades, debugging an existing deployment, editing an existing template, or configuring OAuth/OIDC on a running deployment.
- ▌ Modules · coder bundleAdd 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", "install Claude Code in this template", or "pin module versions". Do not use for installing or upgrading Coder itself (use the setup skill), authoring a brand-new template from scratch (use the templates skill), or publishing a custom module to the registry.
- ▌ Templates · coder bundleCreate, 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 template to add JetBrains", or "deprecate this template version". Do not use for installing or upgrading Coder itself (use the setup skill), adding a single module to a template that already builds (use the modules skill), or authoring custom Terraform providers unrelated to Coder.
- ▌ Agent Tty · coderTerminal 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 CLI workflow with reviewable artifacts.
- ▌ Triage · coder bundleMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.
- ▌ Improve · coder bundleSurvey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.
- ▌ Eval Guide · coderGuide for running statistically meaningful agent-tty evals with trials, parallelism, and A/B comparison. Covers non-determinism baseline, recommended sample sizes, and result interpretation.
- ▌ Dogfood Tui · coderStructured TUI dogfooding and QA workflow using agent-tty. Use for exploratory testing, bug hunting, release-readiness validation, and UX review of terminal applications.
- ▌ Domain Modeling · coder bundleBuild and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
- ▌ Release Maintainer · coderInternal maintainer SOP for version bumps, release PRs, tagging, publishing, and post-publish verification in this repository.
- ▌ Agent Terminal · coderTerminal 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 CLI workflow with reviewable artifacts.
- ▌
- ▌
- ▌ Electron · coderAutomate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
- ▌ Dev Server Sandbox · coderRun multiple isolated xum dev-server instances (temp XUM_ROOT + free ports)
- ▌ Dev Desktop Sandbox · coderRun isolated xum desktop (Electron) instances (temp XUM_ROOT + free ports)
- ▌ Generate Readme Screenshots · coderRegenerate 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 regressions in readme screenshot stories, changes to App.readmeScreenshots.stories.tsx, changes to mockFactory.ts that affect screenshot stories, or explicit user request to update README images.
- ▌ Frontend Review · coderDiff-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.
- ▌ Pull Requests · coderGuide 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.
- ▌ Dogfood · coder bundleRun 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.
- ▌ Coder Agents Review · coderUse 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 until the app comments `approved`.
- ▌ Deep Review · coder bundleMulti-reviewer code review. Spawns domain-specific reviewers in parallel, cross-checks findings, posts a single structured GitHub review.
- ▌ Refine Plan · coderIteratively refine development plans using TDD methodology. Ensures plans are clear, actionable, and include red-green-refactor cycles with proper test coverage.
- ▌ Write Docs · coderAuthoring 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. Counterpart to the doc-check skill, which reviews changes for documentation needs.
- ▌