BuildHub Skill
It names the effect you can only describe.
Put it in your agent. As the agent works, it tells you the term: this is a Tooltip, that is a skeleton screen, and each one opens a page you can play with. You never have to ask what it is called.
- 334 term entries
- 143 with a live demo
- 1 line to install
When I hover this button, show a small hint explaining what it does.
Done: hovering or keyboard focus now shows Download. That short hint is usually a TooltipTooltipExplain a compact control with a short text labelOpen entry.
Hover the term, or Tab to it with the keyboard
About a minute
Paste this to your agent
The agent opens the repository, finds skills/buildhub and installs it. No commands required.
https://github.com/one-person-lab/build-hub
Install the skills/buildhub Skill from this repository.
Prefer a command? Copy this:
npx skills add https://github.com/one-person-lab/build-hub --skill buildhub
Function 1 · Say it precisely
Vague words in, a request you can send straight out
It only adds the terms that matter. It keeps your intent and never picks a framework, a component library or parameters for you.
Make this button change colour on hover, and give it some feedback when I press it.
Add Hover and Active states to the button, and use a Transition so the change feels smooth.
Function 2 · It brings it up
You do not have to ask what it is called
When your wording is ambiguous or missing a precise noun, it picks the 1 to 3 terms that matter from this turn and explains each in one line, inside the task you are on.
I want this setting to apply as soon as I change it, without a second click on Save.
This wants a Switch: two states, on and off, applied immediately. If the user has to adjust several fields and confirm once, this is the wrong pattern.
- The first mention of a term links to its BuildHub entry
- Explanations stay with the task, no dictionary definitions
- At most 3 terms in one reply
Why it can name things
Guess first, then verify
It does not throw your sentence at a search box. It infers candidate terms, then checks them against the site in one pass.
Unverified stays out
It only links to entry pages that really exist on BuildHub. A candidate that misses is left out rather than invented.
Plain files all the way
The skill and its script live in the repository. Read them, change them. No runtime, no black box, no lock-in.
When what you need is a reference rather than a noun:SkillsPromptsUI samples