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

designer-notes

v1.8.2

Published

Figma-style feedback commenting for AI-generated UI. Pin comments to HTML elements, then hand off to Claude Code, Cursor, or Codex for implementation.

Downloads

1,977

Readme

designer-notes

Pin comments to HTML elements, just like Figma. Then hand off to Claude Code, Cursor, or Codex to apply the changes.

Learn more at arturnbull.github.io/designer-notes-landing-page

Install

Claude Code

npx designer-notes

This installs two Claude Code skills and the tool files to ~/.claude/skills/.

Cursor (experimental)

npx designer-notes --cursor

This installs tool files to ~/.cursor/designer-notes/ and slash commands to your project's .cursor/commands/ directory. Cursor support is experimental — the core commenting workflow works, but Claude Code-specific features (model directives, skill invocations, parallel processing) are not available.

Codex CLI (experimental)

npx designer-notes --codex

This installs skill files to ~/.agents/skills/ for use with OpenAI's Codex CLI. Codex support is experimental — setup runs inline from the skill prompt (no hooks), and model directives map to OpenAI models (#o3, #gpt-4o, #o4-mini).

Update

npx designer-notes@latest --force

Quick start

  1. Open Claude Code in any project with HTML files
  2. Run /designer-notes — it adds the script and starts the dev server
  3. Press C to comment on elements, or T to edit text directly
  4. Run /submit-feedback — Claude reads your feedback and edits the code

What it does

designer-notes is a browser-based commenting tool for reviewing AI-generated UI. It gives you a Figma-like workflow for leaving design feedback directly on rendered HTML pages.

Every comment is saved with its CSS selector and click position into a structured markdown file. When you run /submit-feedback, Claude reads that file and applies each change to the source code.

Features

  • Pin notes to any element — click a heading, button, or card to attach feedback
  • Inline text editing — click any text element to edit it directly in the browser, Figma-style. Before/after changes are exported as structured diffs and applied automatically
  • Batch reviews — leave all your notes first, submit once
  • Slash commands — use your environment's existing Claude skills
  • Model directives — use #opus, #sonnet, or #haiku per comment
  • Effort directives — use #high-effort, #medium-effort, or #low-effort
  • Auto-save — comments and text edits persist and export to markdown automatically
  • Viewport tracking — feedback includes window size so changes target the right breakpoint
  • Changelog — cumulative HTML changelog generated after each feedback round

Keyboard shortcuts

| Key | Action | |-----|--------| | C | Toggle comment mode | | T | Toggle text edit mode | | ⌘\ | Open / close sidepanel | | ⌘. | Show / hide all UI |

Manual install

If you don't have npm, download the files directly:

mkdir -p ~/.claude/skills/designer-notes ~/.claude/skills/submit-feedback

# Tool files
curl -fsSL https://raw.githubusercontent.com/arturnbull/designer-notes/main/designer-notes.js \
  -o ~/.claude/skills/designer-notes/designer-notes.js
curl -fsSL https://raw.githubusercontent.com/arturnbull/designer-notes/main/serve.js \
  -o ~/.claude/skills/designer-notes/serve.js
curl -fsSL https://raw.githubusercontent.com/arturnbull/designer-notes/main/changelog-template.html \
  -o ~/.claude/skills/designer-notes/changelog-template.html

# Skill files
curl -fsSL https://raw.githubusercontent.com/arturnbull/designer-notes/main/skills/designer-notes/SKILL.md \
  -o ~/.claude/skills/designer-notes/SKILL.md
curl -fsSL https://raw.githubusercontent.com/arturnbull/designer-notes/main/skills/submit-feedback/SKILL.md \
  -o ~/.claude/skills/submit-feedback/SKILL.md

Then restart Claude Code.

How it works

  1. /designer-notes adds a <script> tag to your HTML and starts a local dev server
  2. The server auto-finds an open port (defaults to 3847, increments if in use)
  3. Three floating buttons appear in the bottom-right: text edit (pencil), comment (speech bubble), and panel (ellipsis)
  4. Press C to enter comment mode — click elements to place numbered pins and type feedback
  5. Press T to enter text edit mode — click any text element to edit it inline. Accept with Enter, dismiss with Esc. Re-editing the same element updates the existing entry
  6. Use /skills and #directives in comment popovers for advanced control
  7. All feedback auto-saves to feedback-YYYY-MM-DD.md in your project directory
  8. /submit-feedback parses the markdown, locates each element in source, and applies changes. Text edits are applied via haiku for speed
  9. After changes are applied, the browser clears automatically for the next review round

Requirements

Uninstall

Claude Code:

rm -rf ~/.claude/skills/designer-notes ~/.claude/skills/submit-feedback

Cursor:

rm -rf ~/.cursor/designer-notes
rm .cursor/commands/designer-notes.md .cursor/commands/submit-feedback.md

Codex:

rm -rf ~/.agents/skills/designer-notes ~/.agents/skills/submit-feedback

Links

License

MIT