القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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").
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.
| name | create-tab-config |
| description | 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. |
Create a new CastCodes tab config based on what the user wants.
tab-configs skill as the canonical source of truth for:
ask_user_question tool to clarify them before writing anything. Do not guess about layout, commands, directories, parameters, or close-time behavior.tab-configs schema.~/.cast-codes/tab_configs/ for standard builds. Non-stable builds use a channel-specific variant (e.g. ~/.cast-codes-<channel>/tab_configs/).
To find the correct directory, run ls -d ~/.cast-codes*/ to list the available CastCodes data directories and pick the one that corresponds to the running build. When in doubt, ask the user which build they are using.
Create the tab_configs/ subdirectory if it does not exist.
Write the file using a descriptive snake_case filename ending in .toml.ask_user_question tool.