メニュー
Install the Tokyo Night statusline in Claude Code (one-time; Claude Code only — sets settings.json statusLine to point at the statusline shipped with this skill)
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when the Kickbacks/vibe-ads ad extension owns the Claude Code statusline and the user wants the Yuumi Tokyo Night statusline back WITHOUT removing the ad — installs a combined HUD+ad statusline and locks it against the extension's rewrites (Claude Code only; macOS/Linux)
Agree on domain, package location, responsibility, and function signatures before implementing — sketch the skeleton, record a design note, hand off code to yuumi:implement. Invoke by hand.
Use when a document carries inline {curly-brace} edit notes to apply in place, or when scattered edits across long drafts or multiple files must stay consistent — no copy-paste round-trips
Use when a file, endpoint, module, system, concept, or change (a PR, branch, or diff) needs to be genuinely understood, not skimmed — renders a single-file Anthropic-style HTML explainer that installs a mental model in one read; add a comprehension quiz when the user wants their understanding verified ("a quiz I must pass")
Use when implementing a spec whose reviewer will need the decision trail — resolved ambiguities, deviations, tradeoffs, open questions — not just the diff; keeps a running single-file HTML decision log alongside the code
Use when a plan or spec needs pressure-testing before you build it — finds the holes through an in-depth interview rather than a passive review
| name | yuumi:statusline-setup |
| description | Install the Tokyo Night statusline in Claude Code (one-time; Claude Code only — sets settings.json statusLine to point at the statusline shipped with this skill) |
| version | 1.6.4 |
Install the Tokyo Night powerline statusline for Claude Code. This is a one-time step after installing yuumi with npx skills add -g heeseon87/yuumi.
Claude Code only. Other agents (Codex, Cursor, …) have no statusline concept — this skill is a no-op there. For diagnosing an existing install, use
/yuumi-statusline-doctor.
The statusline (statusline.mjs) ships inside this skill's assets/, so npx skills already placed it at a stable path. Setup just wires Claude Code to it:
statusline.mjs (the skills-CLI copy drops it) so its #!/usr/bin/env node shebang keeps node resolution dynamic — fnm / nvm friendly.settings.json statusLine.command directly at the installed assets/statusline.mjs (on Windows: an absolute node.exe + the path, since there is no shebang).settings.json to ~/.claude/hud/backup/.SessionStart auto-sync hook from the old marketplace-era install.There is no SessionStart hook and no ~/.claude/hud/ copy — the skill-dir path is stable, so npx skills update refreshes the statusline in place with nothing to re-sync.
assets/. It must be the global install (~/.claude/skills/…) because the statusline is a user-level setting; the script refuses a project-local install and tells the user to re-run npx skills add -g heeseon87/yuumi.node -e "var fs=require('fs'),p=require('path'),os=require('os');var roots=[p.join(process.env.CLAUDE_CONFIG_DIR||p.join(os.homedir(),'.claude'),'skills'),p.join(process.cwd(),'.claude','skills')];for(var r of roots){try{for(var d of fs.readdirSync(r)){var a=p.join(r,d,'assets');if(fs.existsSync(p.join(a,'setup.mjs'))&&fs.existsSync(p.join(a,'statusline.mjs'))){require('child_process').execFileSync(process.execPath,[p.join(a,'setup.mjs')],{stdio:'inherit'});process.exit(0)}}}catch(e){}}console.error('yuumi statusline-setup assets not found. Install globally first: npx skills add -g heeseon87/yuumi');process.exit(1)"
No re-run needed. npx skills update refreshes statusline.mjs at its stable skill-dir path; the next statusline refresh picks it up. If something looks off, run /yuumi-statusline-doctor.
The statusline shows:
Requires a Nerd Font terminal and truecolor (24-bit) support.