Skip to content

fix: render favicon as legible npm-style n - #19

Merged
kodingkin merged 1 commit into
mainfrom
fix/favicon-n-glyph
Aug 11, 2026
Merged

fix: render favicon as legible npm-style n#19
kodingkin merged 1 commit into
mainfrom
fix/favicon-n-glyph

Conversation

@kodingkin

Copy link
Copy Markdown
Owner

Summary

  • Favicon (frontend/app/icon.svg) rendered as an illegible blob at tab size — the rect-based "n" had a stepped arch that dissolved into anti-aliasing noise at 16px. Replaced with a single rounded <path>: two full-height stems + top arch, verified by pixel-sampling at 16px/64px.
  • Gitignore the ClawHub skill lock (**/.clawhub/) and include the auto-generated Next.js agent-rules doc block in frontend/CLAUDE.md.

Test plan

  • Dev server serves /icon.svg → 200 image/svg+xml
  • Homepage <head> declares <link rel="icon" href="/icon.svg?...">
  • Rendered shape reads as "n" at 16px favicon size

The rect-based glyph's stepped arch dissolved into anti-aliasing noise at favicon size, so it read as a blob instead of an n. Replace with a single rounded path: two full-height stems plus a top arch. Also gitignore the ClawHub skill lock and include the Next.js-generated agent rules doc.
@vercel

vercel Bot commented Aug 11, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
npmatch Ready Ready Preview Aug 11, 2026 11:44am
npmatch-backend Ready Ready Preview Aug 11, 2026 11:44am

@kodingkin
kodingkin merged commit d666b5f into main Aug 11, 2026
4 checks passed
@kodingkin
kodingkin deleted the fix/favicon-n-glyph branch August 11, 2026 11:45
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