Web Artifacts Builder
anthropics/skills
Builds multi-component claude.ai HTML artifacts as a small React, TypeScript and Tailwind project, then bundles it into one shareable HTML file.
Wire mouse, wheel and touch input for react-horizontal-scrolling-menu: onWheel/onScroll are plain (api, event) = void callbacks, while ALL mouse/touch props (onMouseDown, onMouseUp, onMouseMove…
$ npx skills add asmyshlyaev177/react-horizontal-scrolling-menu --skill menu-interactions -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install asmyshlyaev177/react-horizontal-scrolling-menu menu-interactions --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/asmyshlyaev177/react-horizontal-scrolling-menu.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/menu-interactions .claude/skills/menu-interactions && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "menu-interactions" agent skill from https://github.com/asmyshlyaev177/react-horizontal-scrolling-menu/tree/master/skills/menu-interactions into .claude/skills/menu-interactions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "menu-interactions", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/asmyshlyaev177/react-horizontal-scrolling-menu/tree/master/skills/menu-interactionsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add asmyshlyaev177/react-horizontal-scrolling-menu --skill menu-interactions -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install asmyshlyaev177/react-horizontal-scrolling-menu menu-interactions --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/asmyshlyaev177/react-horizontal-scrolling-menu.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/menu-interactions .agents/skills/menu-interactions && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "menu-interactions" agent skill from https://github.com/asmyshlyaev177/react-horizontal-scrolling-menu/tree/master/skills/menu-interactions into .agents/skills/menu-interactions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "menu-interactions", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add asmyshlyaev177/react-horizontal-scrolling-menu --skill menu-interactions -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install asmyshlyaev177/react-horizontal-scrolling-menu menu-interactions --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/asmyshlyaev177/react-horizontal-scrolling-menu.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/menu-interactions .cursor/skills/menu-interactions && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "menu-interactions" agent skill from https://github.com/asmyshlyaev177/react-horizontal-scrolling-menu/tree/master/skills/menu-interactions into .cursor/skills/menu-interactions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "menu-interactions", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/asmyshlyaev177/react-horizontal-scrolling-menu.git --path skills/menu-interactions--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add asmyshlyaev177/react-horizontal-scrolling-menu --skill menu-interactions -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install asmyshlyaev177/react-horizontal-scrolling-menu menu-interactions --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/asmyshlyaev177/react-horizontal-scrolling-menu.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/menu-interactions .gemini/skills/menu-interactions && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "menu-interactions" agent skill from https://github.com/asmyshlyaev177/react-horizontal-scrolling-menu/tree/master/skills/menu-interactions into .gemini/skills/menu-interactions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "menu-interactions", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install asmyshlyaev177/react-horizontal-scrolling-menu menu-interactionsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add asmyshlyaev177/react-horizontal-scrolling-menu --skill menu-interactions -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/asmyshlyaev177/react-horizontal-scrolling-menu.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/menu-interactions .github/skills/menu-interactions && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "menu-interactions" agent skill from https://github.com/asmyshlyaev177/react-horizontal-scrolling-menu/tree/master/skills/menu-interactions into .github/skills/menu-interactions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "menu-interactions", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add asmyshlyaev177/react-horizontal-scrolling-menu --skill menu-interactions -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install asmyshlyaev177/react-horizontal-scrolling-menu menu-interactions --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/asmyshlyaev177/react-horizontal-scrolling-menu.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/menu-interactions .opencode/skills/menu-interactions && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "menu-interactions" agent skill from https://github.com/asmyshlyaev177/react-horizontal-scrolling-menu/tree/master/skills/menu-interactions into .opencode/skills/menu-interactions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "menu-interactions", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
menu-interactionsWire mouse, wheel and touch input for react-horizontal-scrolling-menu: onWheel/onScroll are plain (api, event) = void callbacks, while ALL mouse/touch props (onMouseDown, onMouseUp, onMouseMove…
Menu Interactions is an agent skill from asmyshlyaev177/react-horizontal-scrolling-menu. Wire mouse, wheel and touch input for react-horizontal-scrolling-menu: onWheel/onScroll are plain (api, event) = void callbacks, while ALL mouse/touch props (onMouseDown, onMouseUp, onMouseMove, onMouseLeave, onTouchStart, onTouchMove, onTouchEnd) are handler factories (api) = (event) = void. Covers mouse drag-to-scroll with the DragDealer pattern and dragging guard, onMouseLeave to stop drags, body-scroll locking, touchpad-vs-wheel detection, desktop swipe. Load when adding drag-to-scroll or custom wheel…
Its SKILL.md is about 3.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design. It works with React. The repository describes itself as: Horizontal scrolling menu component for React with per-item visibility tracking. Supports mouse and touch devices, SSR-safe. The licence is MIT.
Read from SKILL.md and the folder at commit 42c99aa. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Menu Interactions loads about 3.3k tokens when it runs. Until then it costs about 161 tokens; SKILL.md has 591 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from asmyshlyaev177/react-horizontal-scrolling-menu at commit 42c99aa, republished under its MIT licence (© asmyshlyaev177). 591 words, ~3,279 tokens.
.claude/skills/menu-interactions/SKILL.md (or your agent's skills folder).ScrollMenu has two callback shapes. Getting this wrong is the #1 input bug:
onWheel / onScroll are plain callbacks: (api, event) => voidonMouseDown, onMouseUp, onMouseMove,
onMouseLeave, onTouchStart, onTouchMove, onTouchEnd) are
handler factories: (api) => (event) => void. ScrollMenu invokes the
factory with the api during render and attaches the returned function as
the DOM handler.All wheel/mouse/touch handlers attach to the outermost wrapper div (so they
also fire over arrows, Header and Footer); onScroll attaches to the scroll
container itself (src/index.tsx:319-347). api is the same publicApiType
object that VisibilityContext provides.
Touch devices scroll the menu natively — no touch props are needed for basic mobile swipe. Drag-to-scroll below is the desktop "swipe" equivalent.
Both shapes wired on a minimal menu:
import React from 'react';
import {
ScrollMenu,
VisibilityContext,
type publicApiType,
} from 'react-horizontal-scrolling-menu';
import 'react-horizontal-scrolling-menu/dist/styles.css';
function Card({ itemId }: { itemId: string }) {
const api = React.useContext<publicApiType>(VisibilityContext);
const visible = api.useIsVisible(itemId, true);
return <div style={{ width: 160, opacity: visible ? 1 : 0.5 }}>{itemId}</div>;
}
// Plain shape — (api, event) => void
const onWheel = (api: publicApiType, ev: React.WheelEvent): void => {
if (ev.deltaY < 0) api.scrollNext();
else api.scrollPrev();
};
// Factory shape — (api) => (event) => void
const onMouseDown =
(_api: publicApiType) =>
(ev: React.MouseEvent): void => {
ev.preventDefault(); // block native image/link drag inside items
};
const ids = ['a', 'b', 'c', 'd', 'e', 'f'];
export function Menu() {
return (
<ScrollMenu onWheel={onWheel} onMouseDown={onMouseDown}>
{ids.map((id) => (
<Card itemId={id} key={id} />
))}
</ScrollMenu>
);
}The complete pattern from the MouseDrag story: track pointer position, flip a
dragging flag once movement exceeds 5px, scroll the container by the delta,
clear the flag in requestAnimationFrame after mouseup so item onClick
(which fires after the drag ends) can still see it and bail, and stop the
drag via onMouseLeave so the menu does not keep following a cursor that
left it.
import React from 'react';
import {
ScrollMenu,
VisibilityContext,
type publicApiType,
} from 'react-horizontal-scrolling-menu';
import 'react-horizontal-scrolling-menu/dist/styles.css';
class DragDealer {
clicked = false;
dragging = false;
position = 0;
dragStart = (ev: React.MouseEvent) => {
this.position = ev.clientX;
this.clicked = true;
};
// Clear flags one frame later: item onClick fires after mouseup and must
// still be able to read `dragging` to skip selection.
dragStop = () => {
window.requestAnimationFrame(() => {
this.dragging = false;
this.clicked = false;
});
};
dragMove = (ev: React.MouseEvent, cb: (posDiff: number) => void) => {
const newDiff = this.position - ev.clientX;
const movedEnough = Math.abs(newDiff) > 5;
if (this.clicked && movedEnough) {
this.dragging = true;
}
if (this.dragging && movedEnough) {
this.position = ev.clientX;
cb(newDiff);
}
};
}
function Card({
itemId,
onClick,
selected,
}: {
itemId: string;
onClick: () => void;
selected: boolean;
}) {
const api = React.useContext<publicApiType>(VisibilityContext);
const visible = api.useIsVisible(itemId, true);
return (
<div
onClick={onClick}
role="button"
tabIndex={0}
style={{
width: 160,
height: 120,
userSelect: 'none', // no text selection while dragging
opacity: visible ? 1 : 0.5,
background: selected ? 'lightgreen' : 'bisque',
}}
>
{itemId}
</div>
);
}
const ids = ['a', 'b', 'c', 'd', 'e', 'f', 'g', 'h'];
export function MouseDragMenu() {
const [selected, setSelected] = React.useState<string[]>([]);
const dragState = React.useRef(new DragDealer());
const handleDrag =
({ scrollContainer }: publicApiType) =>
(ev: React.MouseEvent) =>
dragState.current.dragMove(ev, (posDiff) => {
if (scrollContainer.current) {
scrollContainer.current.scrollLeft += posDiff;
}
});
const handleItemClick = (itemId: string) => {
if (dragState.current.dragging) {
return; // a drag just ended — not a real click
}
setSelected((cur) =>
cur.includes(itemId)
? cur.filter((el) => el !== itemId)
: [...cur, itemId],
);
};
return (
<ScrollMenu
onMouseDown={() => dragState.current.dragStart}
onMouseUp={() => dragState.current.dragStop}
onMouseMove={handleDrag}
onMouseLeave={() => dragState.current.dragStop}
>
{ids.map((id) => (
<Card
itemId={id}
key={id}
selected={selected.includes(id)}
onClick={() => handleItemClick(id)}
/>
))}
</ScrollMenu>
);
}On a scroll-snap-type: mandatory rail this drag stutters: the browser snaps
every scrollLeft write. Set scrollSnapType = 'none' on the container for
the gesture, glide to the closest item with scrollToItem on release, and
restore it once scrolling settles — skills/menu-recipes/references/scroll-snap.md.
One menu page per wheel tick, while touchpad gestures fall through to native
horizontal scrolling. There is no standard way to distinguish the two; the
heuristic is that touchpads emit deltaX (or small deltaY), a mouse wheel
emits large deltaY only.
import React from 'react';
import {
ScrollMenu,
type publicApiType,
} from 'react-horizontal-scrolling-menu';
import 'react-horizontal-scrolling-menu/dist/styles.css';
function onWheel(api: publicApiType, ev: React.WheelEvent): void {
const isTouchpad = Math.abs(ev.deltaX) !== 0 || Math.abs(ev.deltaY) < 15;
if (isTouchpad) {
ev.stopPropagation(); // let native scroll handle the gesture
return;
}
if (ev.deltaY < 0) {
api.scrollNext();
} else {
api.scrollPrev();
}
}
function Item({ itemId }: { itemId: string }) {
return <div style={{ width: 160, height: 80 }}>{itemId}</div>;
}
const ids = ['a', 'b', 'c', 'd', 'e', 'f'];
export function WheelMenu() {
return (
<ScrollMenu onWheel={onWheel}>
{ids.map((id) => (
<Item itemId={id} key={id} />
))}
</ScrollMenu>
);
}React attaches wheel listeners as passive, so ev.preventDefault() inside
the onWheel prop throws. Lock the page with a non-passive document-level
listener toggled on hover instead. ScrollMenu has no onMouseEnter prop, so
the toggle lives on a wrapper div.
import React from 'react';
import {
ScrollMenu,
type publicApiType,
} from 'react-horizontal-scrolling-menu';
import 'react-horizontal-scrolling-menu/dist/styles.css';
function usePreventBodyScroll() {
const preventDefault = React.useCallback((ev: Event) => {
ev.preventDefault();
}, []);
const enableScroll = React.useCallback(() => {
document.removeEventListener('wheel', preventDefault, false);
}, [preventDefault]);
const disableScroll = React.useCallback(() => {
document.addEventListener('wheel', preventDefault, { passive: false });
}, [preventDefault]);
// re-enable body scroll on unmount
React.useEffect(() => enableScroll, [enableScroll]);
return { disableScroll, enableScroll };
}
const onWheel = (api: publicApiType, ev: React.WheelEvent): void => {
const isTouchpad = Math.abs(ev.deltaX) !== 0 || Math.abs(ev.deltaY) < 15;
if (isTouchpad) {
ev.stopPropagation();
return;
}
if (ev.deltaY < 0) api.scrollNext();
else api.scrollPrev();
};
function Item({ itemId }: { itemId: string }) {
return <div style={{ width: 160, height: 80 }}>{itemId}</div>;
}
const ids = ['a', 'b', 'c', 'd', 'e', 'f'];
export function LockedMenu() {
const { disableScroll, enableScroll } = usePreventBodyScroll();
return (
<div onMouseEnter={disableScroll} onMouseLeave={enableScroll}>
<ScrollMenu onWheel={onWheel}>
{ids.map((id) => (
<Item itemId={id} key={id} />
))}
</ScrollMenu>
</div>
);
}Wrong:
<ScrollMenu onMouseMove={(ev) => drag(ev)}>Correct:
<ScrollMenu onMouseMove={(api) => (ev) => drag(ev)}>onWheel/onScroll are plain (api, event) => void, but ALL mouse/touch
props are factories (api) => (event) => void — ScrollMenu calls the prop
with the api during render, so a plain handler receives the api object as
its "event", runs once per render, and its return value is attached as the
DOM handler, which silently does nothing useful.
Source: src/index.tsx:101-107,322-328; README.md props table note
Wrong:
<Card onClick={() => select(id)} /> /* fires after every drag */Correct:
<Card
onClick={() => {
if (!dragState.current.dragging) select(id);
}}
/>
// dragging is cleared inside requestAnimationFrame after mouseUp,
// so it is still true when the post-drag click fires (DragDealer.dragStop)After a drag ends the browser still dispatches a click on the item under the cursor; guard click handlers with a dragging flag that is cleared one animation frame after mouseup.
Source: stories/MouseDrag/MouseDrag.source.tsx (DragDealer class)
Wrong:
<ScrollMenu
onMouseDown={() => dragState.current.dragStart}
onMouseUp={() => dragState.current.dragStop}
onMouseMove={handleDrag}
>Correct:
<ScrollMenu
onMouseDown={() => dragState.current.dragStart}
onMouseUp={() => dragState.current.dragStop}
onMouseMove={handleDrag}
onMouseLeave={() => dragState.current.dragStop}
>Without wiring onMouseLeave to end the drag, the container keeps following
a mouse that is no longer over it (mouseup outside the menu is never seen).
Source: https://github.com/asmyshlyaev177/react-horizontal-scrolling-menu/issues/278 (v7.1.0)
Wrong:
onWheel={(api, ev) => { ev.preventDefault(); api.scrollNext(); }}Correct:
onWheel={(api, ev) => {
const isTouchpad = Math.abs(ev.deltaX) !== 0 || Math.abs(ev.deltaY) < 15;
if (isTouchpad) return; // let native scroll handle it
ev.deltaY < 0 ? api.scrollPrev() : api.scrollNext();
}}React 17+ attaches wheel/touchmove as passive listeners, so
ev.preventDefault() throws "Unable to preventDefault inside passive event
listener" — body-scroll locking needs the non-passive workaround (the
document-level listener pattern above, or CSS overscroll-behavior).
Source: stories/PreventBodyScroll/PreventBodyScroll.source.tsx; stories/Simple onWheel recipe
Wrong:
onScroll={(api) => savePosition(api.scrollContainer.current.scrollLeft)}Correct:
onUpdate={(api) => savePosition(api.scrollContainer.current?.scrollLeft ?? 0)}onScroll fires before the scroll settles (documented in the props table),
so position reads there are intermediate mid-animation values — save state
from onUpdate or poll after the transition finishes.
Source: README.md props table (onScroll fires before scroll settles); stories/SaveRestorePosition
../menu-recipes/SKILL.md — drag, wheel and body-scroll recipes compose
these pointer callback shapes into features (autoplay, one item per
scroll, save/restore position).© asmyshlyaev177, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/menu-interactions of asmyshlyaev177/react-horizontal-scrolling-menu.
Open the folder on GitHubat commit 42c99aa
Menu Interactions next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Menu Interactions this skillasmyshlyaev177/react-horizontal-scrolling-menu | 790 | — | ~3.3k | Automated safety check: Pass | MIT | |
| Web Artifacts Builderanthropics/skills | 180k | 41 repos | ~769 | Automated safety check: Pass | Apache-2.0 | |
| React Doctormakeplane/plane | 61k | 12 repos | ~657 | Automated safety check: Pass | AGPL-3.0 | |
| React Router Developmentremix-run/react-router | 57k | 1 repos | ~1.5k | Automated safety check: Pass | MIT | |
| React UI State PatternsChrisWiles/claude-code-showcase | 6.1k | 8 repos | ~1.6k | Automated safety check: Pass | None | |
| GSAP Core Animationgreensock/gsap-skills | 16k | 4 repos | ~3.7k | Automated safety check: Pass | MIT |
anthropics/skills
Builds multi-component claude.ai HTML artifacts as a small React, TypeScript and Tailwind project, then bundles it into one shareable HTML file.
makeplane/plane
Scans React code for lint, accessibility, bundle size and architecture issues, reports a health score and checks that changes do not lower it.
remix-run/react-router
Guides work on React Router apps by first identifying whether the app uses Framework, Data or Declarative mode, then loading the matching reference and the installed package docs.
ChrisWiles/claude-code-showcase
Sets patterns for React interfaces: when to show loading spinners or skeletons, how to surface errors, how to disable buttons during async work and how to handle empty lists.
greensock/gsap-skills
Covers the GSAP core API for tweens, easing, staggers, defaults and matchMedia, and when to choose GSAP over CSS animations or other JavaScript animation libraries.
lobehub/lobehub
Builds single-file interactive HTML prototypes rendered with the real LobeHub UI components and written as production-style React, so they can later be split into files.
asmyshlyaev177/react-horizontal-scrolling-menu
Recipes composed on the react-horizontal-scrolling-menu public API — NOT props: autoplay (setInterval + scrollNext gated on menuVisible), infinite loop/carousel (clone head/tail + scrollLeft…
asmyshlyaev177/react-horizontal-scrolling-menu
Imperative scrolling for react-horizontal-scrolling-menu: scrollToItem(getItemById(id), behavior, inline, block), scrollNext/scrollPrev, apiRef for controlling the menu from outside (fire methods…
asmyshlyaev177/react-horizontal-scrolling-menu
Detect and upgrade pre-v8 react-horizontal-scrolling-menu patterns that agents trained on older data still generate: destructured visibleElements/isFirstItemVisible/isLastItemVisible/initComplete…
asmyshlyaev177/react-horizontal-scrolling-menu
Build a working react-horizontal-scrolling-menu: install, the mandatory 'react-horizontal-scrolling-menu/dist/styles.css' import, ScrollMenu with a unique itemId per child, arrow components via…
asmyshlyaev177/react-horizontal-scrolling-menu
Server rendering and testing for react-horizontal-scrolling-menu: the library is client-only ('use client' required in React Server Components, else "createContext is not a function"), SSR first…
asmyshlyaev177/react-horizontal-scrolling-menu
Animate react-horizontal-scrolling-menu scrolling and build right-to-left menus: noPolyfill defaults to true since v8, so transitionDuration (default 500), a custom-easing-function…
Works with
Categories
Wire mouse, wheel and touch input for react-horizontal-scrolling-menu: onWheel/onScroll are plain (api, event) = void callbacks, while ALL mouse/touch props (onMouseDown, onMouseUp, onMouseMove…. Menu Interactions is an agent skill from asmyshlyaev177/react-horizontal-scrolling-menu. Wire mouse, wheel and touch input for react-horizontal-scrolling-menu: onWheel/onScroll are plain (api, event) = void callbacks, while ALL mouse/touch props (onMouseDown, onMouseUp, onMouseMove, onMouseLeave, onTouchStart, onTouchMove, onTouchEnd) are handler factories (api) = (event) = void.
Menu Interactions fits situations like: frontend & Design work in your project.
Run `npx skills add asmyshlyaev177/react-horizontal-scrolling-menu --skill menu-interactions -a claude-code`. Or copy the skill folder (skills/menu-interactions in asmyshlyaev177/react-horizontal-scrolling-menu) into .claude/skills/menu-interactions in your project. Claude Code loads it when a task matches its description.
Run `npx skills add asmyshlyaev177/react-horizontal-scrolling-menu --skill menu-interactions -a codex`. Or copy the skill folder (skills/menu-interactions in asmyshlyaev177/react-horizontal-scrolling-menu) into .agents/skills/menu-interactions in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add asmyshlyaev177/react-horizontal-scrolling-menu --skill menu-interactions -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/menu-interactions, .gemini/skills/menu-interactions, .github/skills/menu-interactions and .opencode/skills/menu-interactions in your project.
SKILL.md names no scripts, command-line tools or credentials: Menu Interactions is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Menu Interactions is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.3k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Menu Interactions: Web Artifacts Builder (anthropics/skills, 180k stars), React Doctor (makeplane/plane, 61k stars), React Router Development (remix-run/react-router, 57k stars) and React UI State Patterns (ChrisWiles/claude-code-showcase, 6.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
asmyshlyaev177 (a GitHub user) maintains it in asmyshlyaev177/react-horizontal-scrolling-menu, which has 790 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 1, 2026.
Source: asmyshlyaev177/react-horizontal-scrolling-menu on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.