Electron Heap Snapshot Analysis
keybase/client
Analyzes V8, Chrome and Electron .heapsnapshot files with Node scripts to find memory leaks, detached DOM nodes and the retainer paths that keep objects alive.
Guide for implementing, configuring, and debugging React Joyride v3 guided tours.
$ npx skills add cadence-workflow/cadence-web --skill react-joyride -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cadence-workflow/cadence-web react-joyride --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/cadence-workflow/cadence-web.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/react-joyride .claude/skills/react-joyride && 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 "react-joyride" agent skill from https://github.com/cadence-workflow/cadence-web/tree/master/.agents/skills/react-joyride into .claude/skills/react-joyride/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "react-joyride", 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/cadence-workflow/cadence-web/tree/master/.agents/skills/react-joyrideType 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 cadence-workflow/cadence-web --skill react-joyride -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cadence-workflow/cadence-web react-joyride --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cadence-workflow/cadence-web.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/react-joyride .agents/skills/react-joyride && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "react-joyride" agent skill from https://github.com/cadence-workflow/cadence-web/tree/master/.agents/skills/react-joyride into .agents/skills/react-joyride/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "react-joyride", 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 cadence-workflow/cadence-web --skill react-joyride -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cadence-workflow/cadence-web react-joyride --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cadence-workflow/cadence-web.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/react-joyride .cursor/skills/react-joyride && 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 "react-joyride" agent skill from https://github.com/cadence-workflow/cadence-web/tree/master/.agents/skills/react-joyride into .cursor/skills/react-joyride/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "react-joyride", 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/cadence-workflow/cadence-web.git --path .agents/skills/react-joyride--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 cadence-workflow/cadence-web --skill react-joyride -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cadence-workflow/cadence-web react-joyride --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cadence-workflow/cadence-web.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/react-joyride .gemini/skills/react-joyride && 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 "react-joyride" agent skill from https://github.com/cadence-workflow/cadence-web/tree/master/.agents/skills/react-joyride into .gemini/skills/react-joyride/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "react-joyride", 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 cadence-workflow/cadence-web react-joyrideInstalls 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 cadence-workflow/cadence-web --skill react-joyride -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cadence-workflow/cadence-web.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/react-joyride .github/skills/react-joyride && 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 "react-joyride" agent skill from https://github.com/cadence-workflow/cadence-web/tree/master/.agents/skills/react-joyride into .github/skills/react-joyride/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "react-joyride", 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 cadence-workflow/cadence-web --skill react-joyride -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cadence-workflow/cadence-web react-joyride --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cadence-workflow/cadence-web.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/react-joyride .opencode/skills/react-joyride && 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 "react-joyride" agent skill from https://github.com/cadence-workflow/cadence-web/tree/master/.agents/skills/react-joyride into .opencode/skills/react-joyride/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "react-joyride", 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.
react-joyrideGuide for implementing, configuring, and debugging React Joyride v3 guided tours.
React Joyride is an agent skill from cadence-workflow/cadence-web. Guide for implementing, configuring, and debugging React Joyride v3 guided tours. Use this skill whenever the user mentions joyride, guided tour, onboarding tour, walkthrough, tooltip tour, step-by-step guide, product tour, or wants to highlight UI elements sequentially. Also use when debugging tour issues like tooltips not appearing, targets not found, or controlled mode problems. This skill covers the useJoyride hook, Joyride component, step configuration, events, controls, custom components, and styling.
Its SKILL.md is about 3.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/api-events-components.md`, `references/api-props-options.md` and `references/api-step-state-controls.md`).
It sits in Development, covering Debugging. It works with React and webpack. The repository describes itself as: Web UI for visualizing workflows on Cadence. The licence is MIT.
3 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 5e06d86. 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.
Links to these hosts (documentation or services it may open):
v3.react-joyride.comFrom 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.
React Joyride loads about 3.9k tokens when it runs, and up to ~9.6k if it reads all its reference files. Until then it costs about 132 tokens; SKILL.md has 1,224 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 cadence-workflow/cadence-web at commit 5e06d86, republished under its MIT licence (© cadence-workflow). 1,224 words, ~3,937 tokens.
.claude/skills/react-joyride/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.Create guided tours in React apps. Two public APIs: the useJoyride() hook (recommended) and the <Joyride> component.
Online docs: https://v3.react-joyride.com
import { useJoyride, STATUS, Status } from 'react-joyride';
function App() {
const { Tour } = useJoyride({
continuous: true,
run: true,
steps: [
{ target: '.my-element', content: 'This is the first step', title: 'Welcome' },
{ target: '#sidebar', content: 'Navigate here', placement: 'right' },
],
onEvent: (data) => {
if (([STATUS.FINISHED, STATUS.SKIPPED] as Status).includes(data.status)) {
// Tour ended
}
},
});
return <div>{Tour}{/* rest of app */}</div>;
}import { Joyride, STATUS, Status } from 'react-joyride';
function App() {
return (
<Joyride
continuous
run={true}
steps={[
{ target: '.my-element', content: 'First step' },
{ target: '#sidebar', content: 'Second step' },
]}
onEvent={(data) => {
if (([STATUS.FINISHED, STATUS.SKIPPED] as Status).includes(data.status)) {
// Tour ended
}
}}
/>
);
}The hook returns { controls, failures, on, state, step, Tour }. Render Tour in your JSX.
Docs: https://v3.react-joyride.com/docs/getting-started
The tour has two state dimensions:
Tour Status: idle -> ready -> waiting -> running <-> paused -> finished | skipped
idle: No steps loadedready: Steps loaded, waiting for run: truewaiting: run=true but steps loading async (transitions to running when steps arrive)running: Tour activepaused: Tour paused (controlled mode at COMPLETE, or stop() called)finished / skipped: Tour endedStep Lifecycle (per step): init -> ready -> beacon_before -> beacon -> tooltip_before -> tooltip -> complete
*_before phases: scrolling and positioning happen herebeacon: Pulsing indicator shown (skipped when continuous + navigating, skipBeacon, or placement: 'center')tooltip: The tooltip is visible and interactiveDocs: https://v3.react-joyride.com/docs/how-it-works
Each step requires target and content. All other fields are optional.
{
target: '.my-element', // CSS selector, HTMLElement, React ref, or () => HTMLElement
content: 'Step body text', // ReactNode
title: 'Optional title', // ReactNode
placement: 'bottom', // Default. Also: top, left, right, *-start, *-end, auto, center
id: 'unique-id', // Optional identifier
data: { custom: 'data' }, // Attached to event callbacks
}// CSS selector
{ target: '.sidebar-nav' }
// HTMLElement
{ target: document.getElementById('my-el') }
// React ref
const ref = useRef(null);
{ target: ref }
// Function (evaluated each lifecycle)
{ target: () => document.querySelector('.dynamic-element') }| Option | Default | Description |
|---|---|---|
placement | 'bottom' | Tooltip position. Use 'center' for modal-style (requires target: 'body') |
skipBeacon | false | Skip beacon, show tooltip directly |
buttons | ['back','close','primary'] | Buttons in tooltip. Add 'skip' for skip button |
hideOverlay | false | Don't show dark overlay |
blockTargetInteraction | false | Block clicks on highlighted element |
before | - | (data) => Promise<void> — async hook before step shows |
after | - | (data) => void — fire-and-forget hook after step completes |
skipScroll | false | Don't scroll to target |
scrollTarget | - | Scroll to this element instead of target |
spotlightTarget | - | Highlight this element instead of target |
spotlightPadding | 10 | Padding around spotlight. Number or { top, right, bottom, left } |
targetWaitTimeout | 1000 | ms to wait for target to appear. 0 = no waiting |
beforeTimeout | 5000 | ms to wait for before hook. 0 = no timeout |
All Options fields can be set globally via options prop or per-step. Per-step values override global.
Docs: https://v3.react-joyride.com/docs/step | https://v3.react-joyride.com/docs/props/options
The tour manages step navigation internally. This is the right choice for most use cases.
The library handles async transitions for you. If a step needs to wait for a UI change (dropdown opening, data loading, animation), use before hooks — the tour waits for the promise to resolve before showing the step. If a target element isn't in the DOM yet, targetWaitTimeout (default: 1000ms) handles polling for it. You do NOT need controlled mode for these cases.
const { Tour } = useJoyride({
continuous: true,
run: isRunning,
steps: [
{ target: '.nav', content: 'Navigation' },
{
target: '.dropdown-item',
content: 'Inside the dropdown',
before: () => {
// Open dropdown and wait for animation — tour waits automatically
openDropdown();
return new Promise(resolve => setTimeout(resolve, 300));
},
after: () => closeDropdown(), // Clean up after step (fire-and-forget)
},
{ target: '.main-content', content: 'Main content' },
],
onEvent: (data) => {
if (([STATUS.FINISHED, STATUS.SKIPPED] as Status).includes(data.status)) {
setIsRunning(false);
}
},
});stepIndex) — use sparinglyOnly use controlled mode when the parent genuinely needs to manage the step index externally (e.g., syncing with URL params, external state machines, or complex multi-component coordination that before/after hooks can't handle).
const [stepIndex, setStepIndex] = useState(0);
const [run, setRun] = useState(true);
const { Tour } = useJoyride({
continuous: true,
run,
stepIndex, // This makes it controlled
steps,
onEvent: (data) => {
const { action, index, status, type } = data;
if (([STATUS.FINISHED, STATUS.SKIPPED] as Status).includes(status)) {
setRun(false);
return;
}
if (type === 'step:after' || type === 'error:target_not_found') {
setStepIndex(index + (action === 'prev' ? -1 : 1));
}
},
});Controlled mode rules:
go() and reset() are disabled (logged warning)stepIndex in response to eventsbefore/after hooks unless you have a strong reason for external index managementonEvent callbackonEvent: (data: EventData, controls: Controls) => voidThe data object contains the full tour state plus event-specific fields. The controls object lets you programmatically control the tour.
| Event | When |
|---|---|
tour:start | Tour begins |
step:before_hook | before hook is called |
step:before | Target found, step about to render |
scroll:start | Scrolling to target |
scroll:end | Scroll complete |
beacon | Beacon shown |
tooltip | Tooltip shown |
step:after | User navigated (next/prev/close/skip) |
step:after_hook | after hook called |
tour:end | Tour finished or skipped |
tour:status | Status changed (on stop/reset) |
error:target_not_found | Target element not found |
error | Generic error |
on()const { on, Tour } = useJoyride({ ... });
useEffect(() => {
const unsubscribe = on('tooltip', (data, controls) => {
analytics.track('tour_step_viewed', { step: data.index });
});
return unsubscribe;
}, [on]);Docs: https://v3.react-joyride.com/docs/events
Available via useJoyride() return value or onEvent second argument:
| Method | Description |
|---|---|
next() | Advance to next step |
prev() | Go to previous step |
close(origin?) | Close current step, advance |
skip(origin?) | Skip the tour entirely |
start(index?) | Start the tour |
stop(advance?) | Stop (pause) the tour |
go(index) | Jump to step (uncontrolled only) |
reset(restart?) | Reset tour (uncontrolled only) |
open() | Open tooltip for current step |
info() | Get current state |
Docs: https://v3.react-joyride.com/docs/hook
Three layers of customization (from simple to full control):
options: {
primaryColor: '#1976d2', // Buttons and beacon
backgroundColor: '#1a1a2e', // Tooltip background
textColor: '#ffffff', // Tooltip text
overlayColor: 'rgba(0,0,0,0.7)', // Overlay backdrop
arrowColor: '#1a1a2e', // Arrow (match background)
}styles: {
tooltip: { borderRadius: 12 },
buttonPrimary: { backgroundColor: '#1976d2' },
buttonBack: { color: '#666' },
spotlight: { borderRadius: 8 },
}Style keys: arrow, beacon, beaconInner, beaconOuter, beaconWrapper, buttonBack, buttonClose, buttonPrimary, buttonSkip, floater, loader, overlay, tooltip, tooltipContainer, tooltipContent, tooltipFooter, tooltipFooterSpacer, tooltipTitle
See next section.
Docs: https://v3.react-joyride.com/docs/props/styles
Replace any UI component via props. Each receives render props with step data and button handlers.
import type { TooltipRenderProps } from 'react-joyride';
function MyTooltip({ backProps, index, primaryProps, size, skipProps, step, tooltipProps }: TooltipRenderProps) {
return (
<div {...tooltipProps} style={{ background: '#fff', padding: 16, borderRadius: 8, width: step.width }}>
{step.title && <h3>{step.title}</h3>}
<div>{step.content}</div>
<div>
{index > 0 && <button {...backProps}>Back</button>}
<button {...primaryProps}>Next</button>
</div>
</div>
);
}
// Usage
<Joyride tooltipComponent={MyTooltip} ... />Important: Spread tooltipProps on the container (sets role="dialog" and aria-modal). Spread button props (backProps, primaryProps, closeProps, skipProps) on buttons for correct action handling.
Must render a <span> (placed inside a <button> wrapper). Receives BeaconRenderProps: { continuous, index, isLastStep, size, step }.
Receives ArrowRenderProps: { base, placement, size }.
Receives LoaderRenderProps: { step }. Set to null to disable the loader.
Docs: https://v3.react-joyride.com/docs/custom-components
| I need to... | Use |
|---|---|
| Wait for async UI changes between steps (dropdown, animation, data load) | before hook returning a Promise — not controlled mode |
| Control step navigation externally (URL sync, external state machine) | Controlled mode with stepIndex — but try before/after hooks first |
| Track which steps failed (target missing, hook error) | failures array from useJoyride() return |
Listen to specific events without onEvent switch | on('event:type', handler) from useJoyride() return |
| Show a centered modal-style step | target: 'body' + placement: 'center' |
debug: true firstThe debug prop is the most powerful troubleshooting tool. It logs detailed lifecycle transitions, state changes, and event emissions to the console. Always start here when something isn't working.
<Joyride debug={true} ... />
// or
useJoyride({ debug: true, ... })The console output shows exactly which lifecycle phase the tour reaches, what actions are firing, and where it gets stuck.
run={true} is setsteps array is not empty and steps have valid target + content<Joyride> component (auto-guards DOM access) or check typeof window !== 'undefined'document.querySelector('.your-selector')display: none, visibility: hidden, or zero dimensions)targetWaitTimeout (default: 1000ms)targetWaitTimeout: 0 to skip waiting entirelyerror:target_not_found eventdebug: true and check the console to see which lifecycle phase is reachedoverflow: hidden on ancestors clipping the targetbefore/after hooks in uncontrolled modestepIndex in your onEvent handler when type === 'step:after'action !== 'prev') and backward (action === 'prev') navigationerror:target_not_found to skip broken stepsgo() and reset() don't work in controlled modebeforeTimeout is 5000ms — increase if your async operation takes longerbeforeTimeout: 0 for no timeoutloaderDelay (300ms) while waitingscrollTarget to scroll to a different element than the tooltip targetscrollOffset (default: 20px) for headers or fixed elementsskipScroll: true to disable auto-scrolling for a stepscrollToFirstStep: false by default — set to true if first step is off-screenplacement: 'center' with target: 'body' for modal-style centered tooltips// Named exports only (no default export in v3)
import { Joyride, useJoyride } from 'react-joyride';
// Constants for type-safe comparisons
import { ACTIONS, EVENTS, LIFECYCLE, ORIGIN, STATUS } from 'react-joyride';
// Types
import type { Step, Props, EventData, Controls, TooltipRenderProps } from 'react-joyride';Docs: https://v3.react-joyride.com/docs/exports
Read these for complete API details:
references/api-props-options.md — Full Props, Options (all 30+ fields with defaults), Locale, FloatingOptions, Styles typesreferences/api-step-state-controls.md — Step, StepMerged, StepTarget, State, Controls (all 10 methods), UseJoyrideReturn, StepFailurereferences/api-events-components.md — All 13 event types, ACTIONS/LIFECYCLE/STATUS/ORIGIN constants, EventData, custom component render propsreferences/patterns.md — Complete working examples: controlled mode, before/after hooks, custom tooltip, event subscription, dynamic steps© cadence-workflow, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 4 other files (references) in .agents/skills/react-joyride of cadence-workflow/cadence-web.
Open the folder on GitHubat commit 5e06d86
React Joyride 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 |
|---|---|---|---|---|---|---|
| React Joyride this skillcadence-workflow/cadence-web | 435 | — | ~3.9k | Automated safety check: Pass | MIT | |
| Electron Heap Snapshot Analysiskeybase/client | 9.3k | — | ~875 | Automated safety check: Pass | BSD-3-Clause | |
| Electron DevTools Trace Analysiskeybase/client | 9.3k | — | ~809 | Automated safety check: Pass | BSD-3-Clause | |
| React DevTools Profile Analyzerkeybase/client | 9.3k | — | ~978 | Automated safety check: Pass | BSD-3-Clause | |
| Jazz UI Developmentgarden-co/classic-jazz | 2.5k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Implement GitHub FeatureAgnosticUI/agnosticui | 826 | — | ~1.6k | Automated safety check: Pass | Apache-2.0 |
keybase/client
Analyzes V8, Chrome and Electron .heapsnapshot files with Node scripts to find memory leaks, detached DOM nodes and the retainer paths that keep objects alive.
keybase/client
Analyzes Chrome or Electron DevTools Performance trace exports with Python scripts to find where render time actually goes, without opening DevTools.
keybase/client
Parses a React DevTools Profiler JSON export with Python scripts to find re-render storms, commit fan-out and why a component rendered, without opening the DevTools UI.
garden-co/classic-jazz
A skill your agent uses when building, debugging, or optimizing Jazz applications.
AgnosticUI/agnosticui
Design and implement a new feature or component from a GitHub issue.
rudybear/renderdoc-skill
GPU frame debugging with RenderDoc via rdc-cli. An agent skill from rudybear/renderdoc-skill.
cadence-workflow/cadence-web
Add a new boolean feature flag (dynamic config key) to cadence-web.
Categories
Guide for implementing, configuring, and debugging React Joyride v3 guided tours. React Joyride is an agent skill from cadence-workflow/cadence-web. Guide for implementing, configuring, and debugging React Joyride v3 guided tours.
React Joyride fits situations like: the user mentions joyride; onboarding tour; step-by-step guide; wants to highlight UI elements sequentially.
Run `npx skills add cadence-workflow/cadence-web --skill react-joyride -a claude-code`. Or copy the skill folder (.agents/skills/react-joyride in cadence-workflow/cadence-web) into .claude/skills/react-joyride in your project. Claude Code loads it when a task matches its description.
Run `npx skills add cadence-workflow/cadence-web --skill react-joyride -a codex`. Or copy the skill folder (.agents/skills/react-joyride in cadence-workflow/cadence-web) into .agents/skills/react-joyride 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 cadence-workflow/cadence-web --skill react-joyride -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/react-joyride, .gemini/skills/react-joyride, .github/skills/react-joyride and .opencode/skills/react-joyride in your project.
SKILL.md names no scripts, command-line tools or credentials: React Joyride is instructions for the agent only.
SKILL.md names 1 domain. As links in the text: v3.react-joyride.com. 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.
React Joyride is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.9k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.7k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with React Joyride: Electron Heap Snapshot Analysis (keybase/client, 9.3k stars), Electron DevTools Trace Analysis (keybase/client, 9.3k stars), React DevTools Profile Analyzer (keybase/client, 9.3k stars) and Jazz UI Development (garden-co/classic-jazz, 2.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
cadence-workflow (a GitHub organization) maintains it in cadence-workflow/cadence-web, which has 435 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 6, 2026.
Source: cadence-workflow/cadence-web on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.