harness-emphasis
Claude Code plugin: [[Done]], [[Failed]] and [[Needs you]] pills and known headings gain a glyph in the terminal, and the model is taught to write them. Display-only.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/hongmd--harness-emphasis)HTML
<a href="/listings/hongmd--harness-emphasis"><img src="/api/listings/hongmd--harness-emphasis/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
Add this repository as a marketplace and install from it:
/plugin marketplace add hongmd/harness-emphasis /plugin install emphasis@harness-emphasis
From a shell:
claude plugin marketplace add hongmd/harness-emphasis claude plugin install emphasis@harness-emphasis
Then start a new session. For a local checkout, point the marketplace at the folder instead: `claude plugin marketplace add /path/to/harness-emphasis`. To try it without installing:
claude --plugin-dir /path/to/harness-emphasis
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
.claude-plugin/marketplace.json · Manifest · 5 lines
- {
- "name": "harness-emphasis",
- "owner": { "name": "Hong Tran" },
- "plugins": [{ "name": "emphasis", "source": "./" }]
- }
README.md · README · 140 lines
- # Emphasis
- [](https://github.com/hongmd/harness-emphasis/actions/workflows/ci.yml)
- [](https://github.com/hongmd/harness-emphasis/releases/latest)
- [](LICENSE)
- Replies you can scan. This Claude Code plugin turns `[[Done]]`, `[[Failed]]` and `[[Needs you]]` into glyph pills drawn as inline code, gives known headings and lead labels an icon from their word, and teaches the model to write them.
- ```text
- ## Verdict → ## ⇒ Verdict
- [[Done]] 12/12 → `[✓ Done 12/12]` (inline code)
- **Cause:** the lock → **∆ Cause:** the lock
- ```
- It changes only what is drawn. The stored message, ctrl+o, copied text and the model's own view of the conversation keep the original Markdown.
- ## Why glyphs and not colors
- Claude Code draws an assistant reply through its own Markdown renderer. `MessageDisplay` can replace the text shown while a reply streams, but that text is drawn as Markdown with control characters stripped, so a plugin cannot set a color of its own. Emphasis therefore carries tone with a one-cell glyph inside an inline code span, which takes the renderer's own code color and reads apart in any terminal — bold alone disappears where a font's bold face is weak. Bold is still used for lead labels and headings, where the glyph is the thing to spot.
- Every glyph comes from the arrows, geometric shapes and math operators even the plainest monospace font carries. The blocks outside those (`☑`, `※`, `✎`, `⤳`) were checked against JetBrains Mono Nerd Font and are absent, so they fall back to another font and may be two cells wide — which shifts a whole reply when it wraps. If a glyph still draws as a box, your font and its fallbacks lack it; the word is still readable beside it.
- ### Two hooks draw the same text
- `classic.MessageDisplay` draws a reply as it streams, and a `ui.render` hook on `AssistantMessage` draws the transcript's own row from the same tables. Both are needed: the interactive renderer drops a `MessageDisplay` hook's `displayContent` (anthropics/claude-code#83957), so the streaming hook alone shows nothing on screen. Keeping both means a build that fixes that bug draws the row either way — `decorate` leaves an already-drawn line as it is, so no glyph doubles.
- ## Install
- Add this repository as a marketplace and install from it:
- ```sh
- /plugin marketplace add hongmd/harness-emphasis
- /plugin install emphasis@harness-emphasis
- ```
- From a shell:
- ```sh
- claude plugin marketplace add hongmd/harness-emphasis
- claude plugin install emphasis@harness-emphasis
- ```
- Then start a new session. For a local checkout, point the marketplace at the folder instead: `claude plugin marketplace add /path/to/harness-emphasis`. To try it without installing:
- ```sh
- claude --plugin-dir /path/to/harness-emphasis
- ```
- ## Pills
- Write `[[Word]]` beside the thing it describes. The word chooses the glyph.
- | Glyph | Meaning | Words |
- |---|---|---|
- | `✓` | Settled | Done, Passed, Observed, Fixed, Live, Recommended, Keep |
- | `✗` | Something is wrong | Failed, Blocked, Broken, Unsafe |
- | `?` | Look here | Needs you, Decision, Unverified, Partial, Skipped, In progress, Pending, At risk |
- | `‼` | Consequences | Costs money, Destructive, Irreversible |
- | `◇` | Kind of work | Brainstorm, Investigate, Preview, Implement, Qualify |
- | `●` | Ownership, owned | Owned |
- | `◩` | Ownership, shared | Shared |
- | `◔` | Ownership, foreign | Foreign |
- | `◌` | Context, inferred | Inferred |
- | `⊕` | Context, new | New |
- | `∆` | Context, changed | Changed |
- | `◈` | Context, optional | Optional |
- Some words carry their own glyph instead: Fixed `⊞`, Observed `◉`, Live `▶`, Recommended `⋆`, Rejected `⊘`, Blocked `■`, Unverified `▲`, In progress `◕`, Partial `◔`, Pending `○`, Todo `□`, Draft `▫`, Skipped `↦`, Stale `↭`. Every glyph is drawn from the arrows, geometric shapes and math operators a monospace font is expected to carry, one cell wide, and none collides with another pill's in its table. The full table is `PILL_ICONS` in `src/emphasis.ts`.
- - **Detail.** A word replies are told to write may be followed by detail: `[[Passed 12/12]]`, `[[Failed: 3 tests]]`, `[[In progress 40%]]`. An accepted spelling only counts as its word when it is the whole label, so `[[down for maintenance]]` is an unknown label in the error tone, not the word "Down".
- - **Synonyms.** Completed, Complete, OK and Finished display as Done. Fail, Failing and Error display as Failed. Pass displays as Passed, Waiting as Pending, and Needs review as Review.
- - **Unknown words.** Any other short label still reads as a pill with its tone's glyph, so nothing is left as raw brackets.
- - **Length.** A label can be up to 32 characters. Longer ones are left as typed.
- ## Labels
- - **Headings.** A `##` heading takes an icon when its word is one of: Finding, Result, Status, Evidence, Cause, Effect, Fix, Risk, Limits, Cost, Decision, Options, Plan, Next, Why, How, Rule, Example, Checked, Verdict, Rollback, Undo, Review, Scoreboard, Terminal, Folder, File, Branch, Ideas, Pills, Colors, Icons.
- - **Lead labels.** Bold text that opens a line, list item, blockquote or table cell takes the same icon: `**Cause:** the lock`. A table cell after the first is left alone. A lead label with no colon takes the action words too, so `- **Check** the log` keeps the check the two-colon form has.
- - **Action lead-ins.** Bold **Check:**, **Do:**, **Next:**, **Unblock:**, **Left:**, **Run:**, **Guard:**, **Undo:** and **See:** take an icon anywhere in a line, so the action that follows a pill is easy to find.
- Your own messages, inline code, fenced code and escaped brackets are left alone. Pills inside a fence are never drawn, and a fence opened in one streaming flush and closed in the next is respected.
- ## The rules come with it
- An agent writes pills only when it is told how. The plugin adds a `emphasis:reply_style` section to the system prompt, so there is nothing to paste into `CLAUDE.md`. The section tells the model:
- - which words to use for each tone, and that every failure, ask and unchecked claim needs its pill
- - to open a reply with the kind of work it understood, and to mark consequences and ownership
- - to follow each attention pill with the action it calls for, such as the fastest check after `[[Unverified]]`
- - to write labels as plain words, because the terminal adds the icons
- The word lists in that section are read from the same tables that draw the pills, so the rules and the drawing cannot drift apart. Print, JSON and headless runs get no section, since nothing there draws pills.
- ## Settings
- Set them from `/plugin` → Emphasis, or in `~/.claude/settings.json` under `pluginConfigs`:
- | Field | Default | Effect |
- |---|---|---|
- | `display` | on | Draw pills and label glyphs in the reply on screen |
- | `guidance` | on | Add the reply-style section to the system prompt |
- To keep the drawing and write your own rules, turn `guidance` off.
- ## Limits
- - The drawing replaces text on screen only. The stored message, ctrl+o, copied text and the model's view keep the original Markdown.
- - Color cannot be set directly; a pill takes the renderer's inline-code color, and a label keeps bold. A terminal theme that draws code spans in the body color gives the glyph alone.
- - A pill is inline code, so a terminal's mouse copy or `/copy` of the reply carries its backticks. The stored message and ctrl+o do not.
- - The no-break spaces inside a pill keep its words together on one line when the reply wraps.
- - Checked on macOS; tests run in CI on Linux. Claude Code 2.1.330.
- ## Development
- ```sh
- mise install
- mise run check # everything CI runs: typecheck, test, validate, changelog
- mise run test # the rules, without Claude Code running
- mise run validate # what the engine will refuse
- ```
- `src/` imports nothing outside the standard library, so `mise run typecheck` checks it with no config file. `hooks/register.ts` imports the engine's types and is checked by `mise run validate` instead. CI runs the same four steps on every push and pull request.
- The rules all live in `src/emphasis.ts` and are tested without Claude Code running. `src/guidance.ts` holds the prompt section and reads its word lists from the same tables.
- ### Releases
- Each release is listed in [CHANGELOG.md](CHANGELOG.md). The version lives in `.claude-plugin/plugin.json` (and is mirrored in `package.json`). Bump both, add a CHANGELOG section for that version, push to `main`, and CI tags that commit `v<version>` and publishes a release whose notes are that section, verbatim. `mise run changelog` fails if the file has no section for the current version, an empty section, or a link to a tag the file does not cover — so bad notes fail the build before they can ship. A version that already has a release is left alone, so merging does not re-tag.
- ```sh
- npm version --no-git-tag-version patch # or minor / major
- jq -r .version package.json # copy it into .claude-plugin/plugin.json
- $EDITOR CHANGELOG.md # add the section for the new version
- mise run changelog # catches a missing section or link before the push
- git commit -am "Release v<version>" && git push
- ```
- ## Credits
- An idea taken from [pi-emphasis](https://github.com/johnlindquist/pi-emphasis), rewritten for Claude Code's plugin API. The vocabulary, the placement rules and the action lead-ins are theirs; the glyph-only rendering is this plugin's.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.