Skip to content

docs: marketplace-first install, first-party plugin sections, palette comment fixes#13

Open
fielding wants to merge 2 commits into
mainfrom
fable/fresh-eyes
Open

docs: marketplace-first install, first-party plugin sections, palette comment fixes#13
fielding wants to merge 2 commits into
mainfrom
fable/fresh-eyes

Conversation

@fielding

@fielding fielding commented Jul 2, 2026

Copy link
Copy Markdown
Owner

What

A fresh-eyes writing pass on the README and palette.

  • Marketplace-first VS Code install. The README still said to build the extension from source with a .vsix pinned at 1.0.0; the extension has been on the VS Code Marketplace and Open VSX since January (verified live before writing). Now leads with code --install-extension fielding.human-plus-plus.
  • Install sections for Neovim, Vim, and Zed. All three shipped in v1.5/v1.6 but the README's only trace was "Vim / Neovim — via tinty". The lazy.nvim snippet is headless-verified (colorscheme humanplusplus + setup() both load). Zed gets dev-extension instructions since the registry query comes back empty — no false availability claims.
  • palette.toml comment fixes. Five of eight quiet-accent role comments described roles the templates don't use (base12 said strings; strings are base17). Comments now match the actual VS Code template assignments and the README table. No hex changes.
  • Marker example leads with sigils (!! ?? >>) instead of the legacy TODO/NOTE aliases it's supposed to be replacing.
  • Site app cards updated to match (first-party plugins, Zed).

Verification

  • make check passes (palette valid, build clean, analysis passes)
  • README.md regenerated from the template via make build — no drift
  • nvim --headless install-path smoke test passes

🤖 Generated with Claude Code

https://claude.ai/code/session_01Xan5eRiAXvcnAVvXHejdTz

fielding and others added 2 commits July 2, 2026 11:47
Five of the eight base24 slot comments described roles the templates
don't actually use (base12 said strings; strings are base17, etc.).
Align the comments with the real assignments in the VS Code template
and the README palette table. No hex changes.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Xan5eRiAXvcnAVvXHejdTz
The README still told people to build the VS Code extension from
source with a version pinned at 1.0.0, while the extension has been
on the Marketplace and Open VSX since January. Lead with the
one-line install instead.

The first-party Neovim plugin, vanilla Vim colorscheme, and Zed
extension shipped in v1.5/v1.6 but the README never mentioned them
('Vim / Neovim — via tinty' was the only trace). Add install
sections for all three — the lazy.nvim snippet is headless-verified
— and update the app table and site app cards to match.

Also switch the marker example to lead with the sigils rather than
the legacy TODO/NOTE aliases, and align the base13 role in the
palette table with actual usage (diff added, CSS classes).

README.md regenerated via make build; make check passes.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Xan5eRiAXvcnAVvXHejdTz
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant