Terminal Title

Updates terminal window title to: $TERMINAL_TITLE_EMOJI ProjectName - Topic

When to Invoke

You MUST actively monitor conversation flow and invoke this skill whenever the topic materially shifts. Do not wait for explicit permission.

DO invoke:

• Session start (default topic: "Claude Code")
• "let's talk about X" / "can you tell me about Y" → invoke immediately
• User switches domains: debugging → docs, frontend → backend, feature → tests
• User starts working on different module/component after sustained discussion
• User asks about completely unrelated topic

Do NOT invoke:

• Follow-up questions on same topic ("add a comment to that function")
• Small refinements to current work ("make it blue")
• Clarifications about current task

Workflow

1. Determine project name — Use human-friendly name from context (git repo, package.json, README heading, or directory basename as fallback). Capitalize properly ("OneOnOne" not "oneonone").

2. Determine topic — Short description (2-4 words) from current conversation context. Default to "Claude Code" at session start.

3. Execute script — Use the skill base directory from the skill loading message:

   Unix/macOS/Linux:

   bashCopy

   bash <skill-base-dir>/scripts/set_title.sh "ProjectName" "Topic"
   

   Windows:

   bashCopy

   pwsh -NoProfile -ExecutionPolicy Bypass -File <skill-base-dir>/scripts/set_title.ps1 "ProjectName" "Topic"
   

   The script reads $TERMINAL_TITLE_EMOJI from environment (defaults to 🎉) and sends terminal escape sequences.

4. Continue silently — Don't mention the title update unless user asks.

Example

User starts Claude Code in /Users/dev/work/oneonone/hosting with TERMINAL_TITLE_EMOJI=💼, conversation is about Firebase config:

bash <skill-base-dir>/scripts/set_title.sh "OneOnOne" "Firebase Config"
# Result: 💼 OneOnOne - Firebase Config