From ghostty-your-turn
Interactively change the "your turn" (waiting for your reply) background color of the ghostty-your-turn plugin. Use for: change the your-turn color, turn color, stop color, the waiting color, change the ghostty background color, update-your-turn-color. Decide it by live-previewing on the actual pane, then persist it once confirmed. Do NOT use for non-Ghostty terminal settings, or enabling/disabling the color change (the Hook itself). Always follow the steps in the body.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ghostty-your-turn:update-your-turn-colorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Interactively decide the `ghostty-your-turn` "your turn" color **by previewing it live on the actual pane**,
Interactively decide the ghostty-your-turn "your turn" color by previewing it live on the actual pane,
then persist it to the config file once confirmed.
Config file: ${XDG_CONFIG_HOME:-$HOME/.config}/ghostty-your-turn/color.conf (line 1 holds #rrggbb).
Default when unset: #6b5b95 (a mid-tone readable with either white or black text).
The Bash in this skill is run by Claude. Claude's Bash child process has no controlling tty, so the preview must be written to the tty resolved from
$PPID(writing to/dev/ttydirectly orprintfto stdout will not reach it).
CONFIG_FILE="${XDG_CONFIG_HOME:-$HOME/.config}/ghostty-your-turn/color.conf"
if [ -f "$CONFIG_FILE" ]; then
echo "Current your-turn color: $(head -n1 "$CONFIG_FILE" | tr -d ' \t\r\n')"
else
echo "Current your-turn color: (unset -> default #6b5b95)"
fi
Tell the user the result.
Use AskUserQuestion to offer candidates. Each option is just an example; the user can specify any
#rrggbb via "Other". Add a note about whether it stays readable with either white or black text
(very bright/dark colors become hard to read). Example candidates:
#6b5b95 (calm purple / default / works with white or black)#2d6e6e (teal / suited to white text)#7d5a2d (amber brown / suited to white text)#444a55 (slate gray / suited to white text)If the user already has a specific color, skip Step 2 and use that value.
Apply the chosen color to this pane right now (replace <HEX> with the actual value).
HEX="<HEX>" # e.g. #2d6e6e
resolve_pane_tty() {
local pid="$PPID" i=0 t
while [ "$i" -lt 8 ]; do
i=$((i + 1))
t=$(ps -o tty= -p "$pid" 2>/dev/null | tr -d ' ')
case "$t" in
"" | "?" | "??") : ;;
*) printf '/dev/%s\n' "$t"; return 0 ;;
esac
pid=$(ps -o ppid= -p "$pid" 2>/dev/null | tr -d ' ')
{ [ -z "$pid" ] || [ "$pid" = "0" ] || [ "$pid" = "1" ]; } && return 1
done
return 1
}
DEV=$(resolve_pane_tty) && printf '\033]11;%s\007' "$HEX" >"$DEV" && echo "Preview applied: $HEX -> $DEV"
Ask the user "It's this color now. How does it look?"
Use AskUserQuestion to ask "Confirm this color" vs "Try another color".
Write the confirmed color to the config file (replace <HEX> with the confirmed value).
HEX="<HEX>"
CONFIG_DIR="${XDG_CONFIG_HOME:-$HOME/.config}/ghostty-your-turn"
mkdir -p "$CONFIG_DIR"
printf '%s\n' "$HEX" >"$CONFIG_DIR/color.conf"
echo "Saved: $HEX"
The preview already shows this color, so no reset is needed (future your-turn states use this color too). Report that it was saved and finish.
#rrggbb). Do not use color names or the rgb: form.Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub brbranch/claude-ghostty-your-turn --plugin ghostty-your-turn