cast-codes

Use this skill when helping users add MCP servers to their CastCodes configuration.

Customize CastCodes keyboard shortcuts (keybindings, keymappings) by editing the user's keybindings.yaml file. Use when the user asks to remap a key combination, rebind an action, change a shortcut, or remove a default keybinding (e.g. "change ctrl+space to ctrl+s", "rebind the command palette to cmd+p", "remove the default for X").

Create new CastCodes tab config TOML files from natural-language requests. Use when the user wants a new tab config, a new tab layout, or asks for a slash command to generate a tab config.

View or modify CastCodes application settings using the bundled JSON schema for guidance

Reference the CastCodes tab config schema, validation rules, and examples. Use when creating or updating CastCodes tab config TOML files or when another tab-config skill needs the canonical schema details.

Update existing CastCodes tab config TOML files from natural-language edit requests. Use when the user wants to modify a tab config that already exists or when editing a tab config file already open in CastCodes.

Create a pull request in the CastCodes repository (OpenCoven/cast-codes) for the current branch. Use when the user mentions opening a PR, creating a pull request, submitting changes for review, or preparing code for merge. Covers the CastCodes-specific gates (rebrand + AI-attribution), Conventional-Commit titling, template selection, GitHub-issue linking, and test coverage.

Work on CastCodes plugin host, skill, MCP, CLI-agent plugin manager, native or WASM plugin host, app plugin, and plugin-related command behavior. Use when editing plugin support or adding plugin-facing capability while preserving the public OSS hosted-service boundary.

Preserve CastCodes fork-local OSS behavior. Use when touching auth, cloud or Oz flows, telemetry, crash reporting, billing, autoupdate, release feeds, shared sessions, feedback, upstream URLs, hosted API clients, or any feature that could call Warp-owned infrastructure from the public CastCodes build.

Choose and run CastCodes local development, build, rebrand, and packaging checks. Use when building or verifying the app, selecting focused Rust checks, running the public OSS binary, validating release or bundle behavior, or interpreting CastCodes-specific local development failures.

Guard CastCodes public rebrand surfaces. Use when changing user-visible naming, app IDs, binary/package slugs, URL schemes, public config paths, bundle metadata, docs, release assets, installer metadata, or when deciding whether an inherited Warp name should remain internal compatibility state.

Implement or review CastCodes UI changes. Use when editing UI, settings, menus, onboarding, command palettes, unavailable hosted-service states, public copy, or visual affordances in the CastCodes app while preserving shared Warp UI conventions and CastCodes OSS boundaries.

Write a TECH.md spec for a significant Warp feature after researching the current codebase and implementation constraints. Use when the user asks for a technical spec, implementation plan, or architecture doc tied to a product spec.

Repo-specific review guidance for warp. Only the categories declared overridable by the core review-pr skill may be specialized here.