Skip to main content
Agent skill

No Pointer

Apply Remotion Studio's pointerless interaction styling to clickable controls. Use when adding or revising Studio buttons or links that should use the default cursor, brighten on hover, and show focus decoration only for keyboard navigation.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use No Pointer when an AI agent needs a reusable SKILL.md workflow for this job: Apply Remotion Studio's pointerless interaction styling to clickable controls. Use when adding or revising Studio buttons or links that should use the default cursor, brighten on hover, and show focus decoration only for keyboard navigation.

When not to use it

Skip No Pointer when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/no-pointer
# Save SKILL.md to ~/.claude/skills/no-pointer/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/no-pointer/SKILL.md. For a shared project, commit the folder at .claude/skills/no-pointer/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the No Pointer skill for this task: Use No Pointer when this documented workflow matches the task. Confirm any required inputs or files before making changes.

What supports this recommendation?

70/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
77/100
Practical detail
68/100
Source evidence
63/100
Source signals
70/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# No Pointer

Use the established Studio interaction convention for clickable controls:

- Set `cursor: 'default'`; do not use `cursor: 'pointer'`. - Drive purely visual hover styling through `HOVERABLE_CLASS_NAME` and `hoverableStyle()` from `packages/studio/src/helpers/hoverable.ts`. Do not add React hover state for color or background changes. - Keep the background unchanged unless the surrounding component already uses a shared background-hover convention. For a text-only action, use `TRANSPARENT` for both `idleBackground` and `hoverBackground`. - Use `LIGHT_TEXT` (`#A6A7A9`) as the idle color and `WHITE` (`white`) as the hover color. Icons and nested text must follow the same state; inspect the element that paints the pixels if the Studio CSS reset blocks inheritance.

## Focus styling

Remove the default outline and pointer-focus shadow, but preserve a visible keyboard focus indicator. Add `FOCUS_VISIBLE_ONLY_CLASS_NAME` from `packages/studio/src/helpers/hoverable.ts` to the control alongside `HOVERABLE_CLASS_NAME`. The shared class implements this pattern:

```css .__remotion-focus-visible-only:focus { outline: none; box-shadow: none; }

.__remotion-focus-visible-only:focus-visible { box-shadow: ${FOCUS_BOX_SHADOW}; } ```

Never remove the `:focus-visible` indicator. Keep hidden actions out of the tab order until they are discoverable.

## Verify

In a running Studio, check the control's computed styles in all relevant states:

- idle and hovered cursor: `default`; - idle color: `rgb(166, 167, 169)`; - hovered color: `rgb(255, 255, 255)`; - pointer focus: no outline or box shadow; - keyboard `Tab` focus: the standard `FOCUS_BOX_SHADOW` is visible.

For Studio code changes, run:

```bash bunx turbo run make --filter='@remotion/studio' bunx turbo run lint test --filter='@remotion/studio' ```

Intended uses

  • Use No Pointer when this documented workflow matches the task.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.