--- name: vibeid description: VibeID — personality test for AI coding agent users based on Claude Code usage behavior. Use when the user says /vibeid, /vibecoding, "run VibeID test", "personality test", or similar. Analyzes the user's Claude Code /insights report across 4 axes (pace, craft, arc, flow) and reveals their Vibetype (one of 16 archetypes), then injects a persona card into the report. --- # VibeID — VibeCoding Personality Test Analyze the user's Claude Code `/insights` report and reveal their **Vibetype**: a 4-letter code (one of 16 combinations) mapped to a distinct persona with low-poly character art. The skill keeps deterministic logic (HTML parsing, axis thresholds, HTML injection) in Node.js scripts, and reserves Claude for the one thing it is uniquely good at: generating personalized copy from the user's actual behavioral data. ## When to Activate - User types `/vibeid`, `/vibecoding`, `/vibe` - User asks for "VibeID", "VibeCoding test", "personality test", or equivalent phrasing - Coffee CLI launches Claude Code with an initial prompt matching any of the above ## Prerequisites 1. Claude Code installed; user has run `/insights` at least once (produces `~/.claude/usage-data/report.html`) 2. Node.js available on PATH (for `analyze.js` / `inject.js`) 3. Network access to `https://coffeecli.com/CC-VibeID-test/matrix.json` ## Execution Steps Follow in order. Do not skip. Do not fabricate numbers. ### Step 0 — Detect the user's dominant language (any language, worldwide) **Do this FIRST, before any user-visible output.** The `/vibeid` slash command itself is English, so the invocation tells you nothing. VibeID is a **global** product — any language must render correctly. Detection priority (use the FIRST source that works): #### Priority 1 (preferred): `.user_lang` hint from Coffee CLI When the user clicks "Personality Test" in Coffee CLI, the app writes the UI locale to `~/.claude/skills/vibeid/.user_lang`. This is the **most reliable** signal — the user explicitly picked their UI language. Use the **Read tool** (Claude Code built-in, NOT `node -e fs.readFileSync` which double-converts `/c/...` into `C:\c\...` on Windows Git Bash): ``` Read ~/.claude/skills/vibeid/.user_lang ``` The file contains one of: `zh-CN`, `zh-TW`, `en`, `ja`, `ko`, `fr`, `de`, `es`, `pt`, `ru`, `vi`. Normalize to an ISO 639-1 code: `zh-CN` and `zh-TW` → `zh`; others stay as-is. Set `target_language` and skip to Step 1. #### Priority 2 (fallback): scan session jsonl If `.user_lang` doesn't exist (user ran /vibeid from a raw CC shell, not Coffee CLI), scan the user's chat history: 1. List recent session files with the Bash tool: ```bash ls -t ~/.claude/projects/*/*.jsonl 2>/dev/null | head -5 ``` 2. For each of the top 3-5 files, use the **Read tool** (NOT `node -e`) to read the last ~200 lines. Extract lines containing `"role":"user"` — those are the user's own typed messages. 3. Infer the dominant natural language and set `target_language` to the ISO 639-1 code: - `zh` — Chinese (simplified or traditional) - `en` — English - `ja` — Japanese - `ko` — Korean - `fr` — French - `de` — German - `es` — Spanish - `pt` — Portuguese - `ru` — Russian - `vi` — Vietnamese - `ar` — Arabic, `tr` — Turkish, `it` — Italian, or any other ISO 639-1 code matching the evidence #### Priority 3 (last resort): default to `en` If neither source gives a signal (empty jsonl, unreadable files), default to `en`. **All subsequent user-visible output in Steps 1, 5, 7 uses `target_language` consistently.** The persona analysis, the "generating report" note, and the final summary are all written in the same language. **Never switch mid-response.** ### Step 1 — Verify the insights report exists Check whether `~/.claude/usage-data/report.html` exists (expand `~` to the user's home directory). - **Present**: Continue directly to Step 2. Do NOT print any "generating report" message — Coffee CLI's Personality Test launcher already ran `/insights` in a dedicated pre-run tab before spawning this vibeid tab, so the report is already fresh. You can proceed silently to the analysis. - **Missing**: Do NOT attempt to run `claude -p "/insights"` yourself. Nested `claude` invocations with slash commands are unreliable across platforms (Windows Git Bash mangles `/insights` into `C:/Program Files/Git/insights`, and `-p` print-mode strips some slash commands). Instead, emit a short helpful message in `target_language` asking the user to launch via Coffee CLI, then STOP. Message template (translate naturally into `target_language`): - `zh`: 还没有生成使用报告。请关闭这个 Tab，从 Coffee CLI 的"人格测试"卡片重新启动（它会自动先跑 /insights）。或者先在 Claude Code 里手动执行 `/insights`，完成后再重试 `/vibeid`。 - `en`: No usage report yet. Please close this tab and launch from Coffee CLI's "Personality Test" card (it auto-runs `/insights` first). Or run `/insights` in a Claude Code tab first, then retry `/vibeid`. - `ja`: 使用状況レポートがまだ生成されていません。このタブを閉じて、Coffee CLI の「性格診断」カードから起動してください（自動的に `/insights` が先に実行されます）。または、Claude Code タブで先に `/insights` を実行してから `/vibeid` を再試行してください。 - other ISO-639-1 codes: translate appropriately into that language After emitting the message, stop execution — do not fabricate data, do not continue to Step 2. ### Step 2 — Load the persona matrix Prefer the **local** copy at `/matrix.json` (use Read). If the local file is missing, fall back to WebFetch `https://coffeecli.com/CC-VibeID-test/matrix.json`. The matrix contains: - `axes` — meaning of each axis letter (P/T, F/S, V/A, L/H) - `thresholds` — numeric cutoffs to classify each axis - `families` — the 4 family color palettes (Ember / Sunward / Tidal / Starlit) - `personas` — 16 entries keyed by 4-letter code - `image_base_url` — CDN root for persona PNGs Hold this data in memory. If both local and remote reads fail, report the error honestly and stop — do not fall back to fabricated persona data. ### Step 3 — Extract behavioral signals from the report Run: ``` node /scripts/analyze.js ``` It prints a JSON object on stdout: ``` { "signals": { "messages": 2850, "sessions": 262, "median_response_seconds": 56.2, "top_tool": "Bash", "craft_ratio": 2.13, "ship_intent_share": 0.38, "build_intent_share": 0.22, "multi_clauding_pct": 16 } } ``` Parse stdout as JSON. If the script exits non-zero, report the error and stop. ### Step 4 — Derive the 4-letter VibeID code Using thresholds from `matrix.json` and signals from Step 3: - **Mind**: `R` (Rational) if `rational_share >= thresholds.mind_rational_share_min`, else `E` (Expressive). Rational dominates when analytical / corrective / shipping intents (bug fix, refactor, release) outweigh generative / aesthetic intents (feature, UI, visual). - **Craft**: `D` (Design) if `design_share >= thresholds.craft_design_share_min`, else `T` (Technical). Design leans on Read + Grep + Write (investigate + create new); Technical leans on Bash + Edit (execute + modify). - **Arc**: `V` (Voyager) if `ship_intent_share > build_intent_share`, else `A` (Architect). - **Flow**: `H` (Hive) if `multi_clauding_pct >= thresholds.flow_multiclaud_pct`, else `L` (Lone). Concatenate to form the VibeID code (e.g. `RTAH`). Look it up in `personas` to get the record. ### Step 5 — Generate a rich, multi-section personality analysis Write **500–800 words** of personalized analysis across **5 distinct sections**, separated by **blank lines (`\n\n`)**. Users read this like an MBTI 16Personalities profile — they want depth, specificity, and a little flattery grounded in real numbers. **Language**: Write the entire 500-800 word analysis in `target_language` detected in Step 0. This supports **any language**, not just Chinese/English: - If `target_language == "zh"`: write in Simplified Chinese and use `name_cn` / `profession_cn` / `tagline_cn` / family `name_cn` from the matrix (pre-translated by us) - If `target_language == "en"`: write in English and use the English fields (`name` / `profession` / `tagline` / `family`) - **For any other language** (ja / ko / fr / de / es / pt / ru / vi / ar / etc.): write the analysis in that language, and **translate `name` / `profession` / `tagline` from the matrix's English fields on the fly** into the same language. Keep the 4-letter code (e.g. `TFAH`) unchanged — it's a brand identifier like `INFJ`, pronounced locally but spelled the same globally. Tone is consistent across all languages: confident, specific, lightly flattering, grounded in real numbers. **Required sections** (each a separate paragraph, roughly 100–160 words): 1. **核心画像 / Core Archetype** — Open with their 4-letter code and persona name in bold. Explain why this archetype fits them, connecting to their family's vibe (Ember fast+hands-on / Sunward fast+curious / Tidal deep+hands-on / Starlit deep+reflective). 2. **节奏与专注 / Tempo & Focus** — Analyze their median response time, total messages, and multi-clauding %. What does this say about how they think — sprint mode, deep marathons, or parallel-wielding? Tie to Eysenck / Jungian cognitive style where natural. 3. **工艺与姿态 / Craft & Stance** — Compare their tool mix (Bash/Edit vs Read/Grep ratio). Hands-on forger or careful observer? What does the top tool reveal about their instinct? Reference specific numbers. 4. **成就弧线 / Achievement Arc** — Ship-intent vs Build-intent balance. Are they a shipper (release cadence dominant) or a builder (feature expansion dominant)? Mention commits / files / lines changed if present in signals. 5. **建议与盲点 / Advice & Blind Spot** — 1–2 concrete suggestions leveraging their strengths, and 1 honest blind spot the data suggests (e.g. "潮汐族深度优秀，但 Tide 节奏可能让快速迭代的同伴难以同步"). Constructive, not harsh. **Tone**: Confident, specific, lightly flattering but grounded in real numbers. **Never fabricate numbers** — only use what Step 3 extracted or the report explicitly states. Bold the persona name once and the 4-letter code once. **Formatting**: Plain text with `\n\n` between paragraphs. No headers / bullets / markdown bold (the injector renders each paragraph as a `

` tag; bold comes from surrounding a phrase with `**...**` which the injector will convert). **CRITICAL — quoting rule (must follow or Step 6 JSON will break)**: Never use straight ASCII double quotes (`"`) inside the analysis text. When this string becomes a value in the persona JSON of Step 6, every `"` must be escaped as `\"`, and missing even one escape kills the whole injection (seen in production: `invalid persona JSON: Expected ',' or '}' ...`). Safe alternatives for emphasis / quoting: - Chinese quotes `“……”` or `「……」` (Chinese / Japanese output) - French guillemets `« … »` (French output) - German `„ … "` (German output) - For English: use single quotes `'…'` or **markdown bold** (`**phrase**`) instead of `"…"`. - To strongly emphasize a persona code or key term, use `**RTAH**` (the injector converts `**…**` to bold). Quick self-check before finalizing Step 5 output: search your draft for any `"`; if you find one, replace it with one of the alternatives above. ### Step 6 — Inject the persona card into the report **Do NOT create any temporary JSON files** (writing to disk triggers user-level fact-forcing hooks and degrades UX). Pipe the persona JSON to `inject.js` via stdin in a single Bash call using a heredoc: ```bash node "/scripts/inject.js" "" << 'VEOF' { "code": "TFVH", "name": "星海统帅", "family": "潮汐族", "profession": "星域元帅", "tagline": "指挥多支深空舰队同步出击。", "copy": "", "image_url": "../skills/vibeid/images/TFVH.png", "palette": { "bg": "#C6D8E0", "costume": "#2E7D87", "accent": "#C0C8D0" } } VEOF ``` **Populate `name` / `profession` / `tagline` / `family` with the localized values** matching the user's detected language (English → `name` etc; Chinese → `name_cn` / `profession_cn` / `tagline_cn` / family `name_cn`). The `copy` field is the multi-paragraph narrative from Step 5 with `\n\n` between sections. **Key rules**: - Use a single-quoted heredoc marker (`'VEOF'`) so shell doesn't expand `$` or backticks inside the JSON - `inject.js` accepts persona JSON via stdin (preferred), argv[3] file path (legacy), or argv[3] inline string (fallback) - One Bash call, zero file writes = minimum gateguard friction ``` { "code": "TFVH", "name": "星海统帅", "family": "潮汐族", "profession": "星域元帅", "tagline": "指挥多支深空舰队同步出击。", "copy": "你是 **TFVH · 星海统帅** ...\n\n在节奏上...\n\n工艺姿态方面...\n\n成就弧线...\n\n建议与盲点...", "image_url": "/TFVH.png", "palette": { "bg": "#C6D8E0", "costume": "#2E7D87", "accent": "#C0C8D0" } } ``` **Image URL construction** — CRITICAL: `image_url = matrix.image_base_url_remote + '/' + persona.code + '.png'` Example: for code `RTAH` → `https://coffeecli.com/CC-VibeID-test/personas/images/RTAH.png`. Each PNG filename equals the 4-letter code + `.png` (matrix v3+). **Do NOT** construct a `file:///...` URL, ever. Use the CDN URL from matrix — it works in shared screenshots, on mobile, and when report.html is copied to another machine. Both `image_base_url` and `image_base_url_remote` in matrix v3 hold the same CDN URL for belt-and-suspenders protection; use either. The injector rewrites `report.html` in place, inserting a VibeID card just after the `

Claude Code Insights

` header. If the report already has a VibeID card (idempotency marker ``), the injector replaces it with the new one. A backup is written to `report.html.bak` before modification. ### Step 7 — Confirm to the user Print a concise summary: - VibeID code (e.g. `TFVH`) - Persona name and profession - Family - One sentence of personalized insight - Path to the updated `report.html` - Suggest they open the report to see the full card Respond in the language the user is using. ## Validation Checkpoints The skill succeeded if: 1. `matrix.json` fetched and parsed 2. `analyze.js` exited 0 with valid signals JSON 3. A valid 4-letter VibeID code was derived 4. `inject.js` exited 0 and `report.html` now contains the `` marker 5. The user sees a clear summary ## Error Handling - Missing `report.html` → stop, ask user to run `/insights` - Missing Node.js → report clearly, suggest install - `matrix.json` fetch fails → stop, report network issue - Analyzer parse failure → stop, show script stderr - Injector failure → do not partially modify the report; restore from `report.html.bak` ## Notes - Persona images, family palettes, and taglines live in the remote `matrix.json` — edit that file to tune the experience without redeploying the skill - 16 persona codes: PFVL, PFVH, PFAL, PFAH, PSVL, PSVH, PSAL, PSAH, TFVL, TFVH, TFAL, TFAH, TSVL, TSVH, TSAL, TSAH - Inspired by public-domain typologies (Jung 1921 Psychological Types, classical Four Temperaments, Big Five / HEXACO). No MBTI trademarks used.