npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

terminal-legibility

v0.1.0

Published

Agent Skill that makes terminal/TUI coding-agent sessions scannable. Audits and sets up a legible theme + font, readable git diffs (delta/difftastic/bat), glamorous markdown rendering (glow/gum), and agent verbosity — then applies a self-formatting output

Readme

The two problems it fixes

  1. The view — theme, font, git diffs, rendering, and agent verbosity that fight the reader.
  2. The throw-back — agent responses and raw markdown with no clear next step and no way to see what just happened.

Install

Pick one:

# Command Code / any Agent-Skills tool: install from GitHub
cmd skills add rosh100yx/terminal-legibility

# or copy the directory into your skills dir
cp -R terminal-legibility ~/.commandcode/skills/

# or install as a versioned package
npm install terminal-legibility

Use

Just talk to it:

"this is too hard to read", "squint", "make the output readable", "readable diffs", "tame the firehose", "set up my terminal theme/font"

It runs five phases:

  1. Detect — scripts/detect.sh identifies your terminal, shell, diff tools, and agent configs.
  2. Audit — flags the contrast / font / diff / render / verbosity weak spots.
  3. Emit — a legibility profile: one recommended default + one alternative per layer.
  4. Apply — copy-paste snippets, or write to config files that already exist (diff-only, never clobbers).
  5. Self-format — applies a 10-rule output style so its own responses lead with the next action and end with Next Actions + Reflective Questions.

The legibility profile (defaults)

| Layer | Default | Alternative | |-------|---------|-------------| | Theme | Catppuccin Mocha (~12:1 contrast) | Gruvbox Dark (warm, low glare) | | Font | JetBrains Mono (tallest x-height) | Commit Mono (smart kerning) | | Diff | delta as core.pager | difftastic as a difft alias | | Render | glow - for docs / agent output | gum format -t code | | Output | outputStyle: Concise (Claude Code) | viewMode: focus |

Full, copy-pasteable config lives in references/ — exact ANSI hexes, font flags per terminal, delta/difftastic/bat gitconfig, glow/gum rendering, and Claude Code / Codex / aider settings. Attributions for all of the above are in CREDITS.md.

The output rules (what the skill makes every agent do)

  1. Lead with the next action — command, path, or snippet first.
  2. Number multi-step tasks; one bounded action per step.
  3. End with one concrete <2-min next action.
  4. Cap lists at 5; group and rank.
  5. Structure over prose — tables, ASCII trees, checklists.
  6. No preamble, recap, or pleasantries.
  7. Matter-of-fact errors: cause + fix, never "Uh oh".
  8. Restate state every turn ("Step 3 of 5 done").
  9. Close open work with ## Next Actions + ## Reflective Questions.
  10. Pre-send test: reading only the first and last line, do you know what to do next and what just happened?

Layout

terminal-legibility/
├── SKILL.md            # the skill (frontmatter + phased body + ruleset)
├── scripts/
│   ├── detect.sh       # read-only terminal/shell/tool detection
│   └── verify.sh       # validates SKILL.md before publish
├── references/
│   ├── themes.md       # Catppuccin Mocha, Gruvbox Dark, Tokyo Night + contrast rules
│   ├── fonts.md        # fonts, size, line-height, ligatures
│   ├── diff-tooling.md # delta, difftastic, bat config
│   ├── rendering.md    # glow, gum, Lip Gloss/Glamour style
│   └── agent-settings.md # Claude Code / Codex / aider verbosity + theming
├── assets/             # cover + before/after images
├── .github/workflows/  # CI + npm release on tag
├── CREDITS.md          # attributions & source links
└── LICENSE             # MIT

License

MIT — free core, forever. See LICENSE.