OpenParable
Skip to content
← Back to skills

Studio CSS Reset

Development
studio-css-reset

Studio CSS Reset is an Agent Skill for development published in the remotion-dev/remotion repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Guidance for Remotion Studio UI changes where the global CSS reset affects nested elements. Use when editing packages/studio UI, especially when adding wrapper spans, inline icons, labels, buttons, compact rows, or any nested text whose typography, color, sizing, or truncation must stay stable.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/remotion-dev/remotion/blob/HEAD/.agents/skills/studio-css-reset/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/studio-css-reset, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Studio CSS Reset

Remotion Studio applies a broad CSS reset to UI elements. Treat every new nested element as reset-styled unless the local component gives it explicit visual styles.

When changing Studio UI:

  • Do not rely on a parent button or container for visible child text styles. Give wrapper spans or divs explicit fontFamily, fontSize, lineHeight, and either color or color: 'inherit'.
  • Preserve compact-row layout when introducing icon-plus-label markup. Use fixed icon dimensions, flexShrink: 0, and explicit label truncation styles such as minWidth, overflow, textOverflow, and whiteSpace.
  • Recheck hover and non-hover states after adding wrappers. The label should not grow, change row height, lose ellipsis, or change color unexpectedly.
  • Prefer fixing the shared Studio component once when the reset issue appears in a repeated row pattern.

For Studio code changes, run at least the focused Studio checks:

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