H
HusainMain/cursorfit
Fit the cursor to your site: audit the repo's design character, pick one cursor family, implement it in your…
○checked 2026-11-20 - the package in the command does not match this entry, so it is not shown as a copyable command.
updated 2026-11-19
View on GitHub ↗Direct link · no redirect page
After install: how to tell it works
- What you see after install — The command exits 0 and the terminal shows no "command not found" or "permission denied".
- One-line self-check — Run the smallest usage example from that repository's README. If the output matches what the README describes, it is working.
- If that does not work — This project has no troubleshooting notes. Search its issues for "install".
The install command comes from the repository; these checks describe observable results only and do not replace the project's own docs.
- Star count
- 0 ★ · HusainMain/cursorfit · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 1 sources
- Score
- score 103 · 1 sources · repo
- Install
- see Install & config above
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: Open Source. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
HusainMain/cursorfit;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# cursorfit
Excerpted from the repository README (abridged)
### Fit the cursor to the site, not the site to the cursor.
Your site has a typeface, a palette, a spacing rhythm and a speed. The cursor is still the
system arrow. So you go looking for a cursor, find forty of them, and have no way to choose
except taste — which is exactly the thing that made the rest of the site good in the first
place.
cursorfit reads your repo, scores its design character, and picks one cursor for it. Then
it writes the code into the project, in your own colour token, at your own tempo.
It will also tell you when the right answer is no cursor at all.
## The part everyone skips
A custom cursor is a usability decision with a design budget attached. It replaces a control
the visitor has used since they were six. That costs something, and the cost is specific:
It has to survive over text, images, glass, video, and a disabled button.
It has to disappear on touch, and calm down under reduced-motion.
It has to keep working when JavaScript loads late or not at all.
And it has to look like it belongs to this site — not to the skill that generated it.
Most cursor skills sell the effect and leave you with the bill. This one is built the other way
round: audit first, verdict second, code last.
## What it actually does
read the repo → close the gaps → score → gate → pick one → implement → verify
1. Reads — framework, files, colour tokens, type stack, radii, spacing, keyframes,
transitions, control count, media count, and any cursor code already there. Component tags
count too: , and are not invisible.
2. Closes the gap — reports what it could not read (inline styles, utility classes,
CSS-in-JS, component internals) and names the five files worth opening. Those get read by
hand before anything is scored.
3. Scores five axes, each one requiring evidence from the code:
restrained ↔ expressive · precise ↔ organic · dense ↔ airy · calm ↔ energetic ·
product ↔ editorial — each with a confidence level.
4. Measures the motion signature — keyframe count, median transition, overshoot curves,
scroll-driven animations, reduced-motion support, touch guards.
5. Gates — hard constraints that outrank the score. Glass panels kill blend modes. An
unused GPU package kills the shader. Zero images kills the reveal.
6. Asks at most three questions, only where the code genuinely can't answer, each with a
default so "I don't know" still produces a decision.
7. Builds the winner as cursor.css + cursor.js, or a React component, wired to the
site's existing tokens. Then it checks its own work: greps, the build, and a real browser.
Nothing is invented at build time. The colour is a token that already exists. The speed comes
from the site's measured transitions. The size comes from its spacing.
## A real run
Run against a dark, animation-heavy AI product landing page — 82 files, 38 controls, 24
keyframes, median transition 200ms, and 177 inline styles the stylesheet scan could not read.
profile expressive 91 · organic 57 · airy 35 · energetic 94 · editorial 70
motion 24 keyframes · median transition 200ms · 0 overshoot · scroll-driven
reduced-motion: present · touch guard: absent
coverage 2 stylesheets · 38 markup files · 177 inline styles · 369 utility-class lists
Your site has a typeface, a palette, a spacing rhythm and a speed. The cursor is still the
system arrow. So you go looking for a cursor, find forty of them, and have no way to choose
except taste — which is exactly the thing that made the rest of the site good in the first
place.
cursorfit reads your repo, scores its design character, and picks one cursor for it. Then
it writes the code into the project, in your own colour token, at your own tempo.
It will also tell you when the right answer is no cursor at all.
## The part everyone skips
A custom cursor is a usability decision with a design budget attached. It replaces a control
the visitor has used since they were six. That costs something, and the cost is specific:
It has to survive over text, images, glass, video, and a disabled button.
It has to disappear on touch, and calm down under reduced-motion.
It has to keep working when JavaScript loads late or not at all.
And it has to look like it belongs to this site — not to the skill that generated it.
Most cursor skills sell the effect and leave you with the bill. This one is built the other way
round: audit first, verdict second, code last.
## What it actually does
read the repo → close the gaps → score → gate → pick one → implement → verify
1. Reads — framework, files, colour tokens, type stack, radii, spacing, keyframes,
transitions, control count, media count, and any cursor code already there. Component tags
count too: , and are not invisible.
2. Closes the gap — reports what it could not read (inline styles, utility classes,
CSS-in-JS, component internals) and names the five files worth opening. Those get read by
hand before anything is scored.
3. Scores five axes, each one requiring evidence from the code:
restrained ↔ expressive · precise ↔ organic · dense ↔ airy · calm ↔ energetic ·
product ↔ editorial — each with a confidence level.
4. Measures the motion signature — keyframe count, median transition, overshoot curves,
scroll-driven animations, reduced-motion support, touch guards.
5. Gates — hard constraints that outrank the score. Glass panels kill blend modes. An
unused GPU package kills the shader. Zero images kills the reveal.
6. Asks at most three questions, only where the code genuinely can't answer, each with a
default so "I don't know" still produces a decision.
7. Builds the winner as cursor.css + cursor.js, or a React component, wired to the
site's existing tokens. Then it checks its own work: greps, the build, and a real browser.
Nothing is invented at build time. The colour is a token that already exists. The speed comes
from the site's measured transitions. The size comes from its spacing.
## A real run
Run against a dark, animation-heavy AI product landing page — 82 files, 38 controls, 24
keyframes, median transition 200ms, and 177 inline styles the stylesheet scan could not read.
profile expressive 91 · organic 57 · airy 35 · energetic 94 · editorial 70
motion 24 keyframes · median transition 200ms · 0 overshoot · scroll-driven
reduced-motion: present · touch guard: absent
coverage 2 stylesheets · 38 markup files · 177 inline styles · 369 utility-class lists
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/husainmain-cursorfit/)
- Source
- github · https://github.com/HusainMain/cursorfit
- Browse by field
- Open source
- added
- today
More entries
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.