npx skills add remotion-dev/remotion --skill docs-demo
dexhunter/remotion · Archived
docs-demo
Add an interactive demo to the Remotion documentation. Use when creating a new <Demo> component for docs pages.
Installation
npx skills add dexhunter/remotion --skill docs-demo
Stronger alternatives
This repository is archived — consider an actively maintained alternative.
Add a new Remotion bug entry to packages/bugs/api/[v].ts. Use when the user describes a bug and…
1 installsAdd a test case to the web renderer
1 installsAdd a new package to the Remotion monorepo, including package scaffolding, monorepo registratio…
1 installsBest practices for writing Remotion animations that stay intuitive for agents and editable in R…
1 installsSimilar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybr…
568.2K installsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or bot…
216.8K installsUse this skill whenever the user wants to do anything with PDF files. This includes reading or …
192.4K installsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.do…
184.5K installsUse this skill any time a spreadsheet file is the primary input or output. This means any task …
165K installsAlso in this package
Other skills from dexhunter/remotion · top by installs.
npx skills add dexhunter/remotion
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Also listed on
Alternate registries and mirrors of this skill.
Repository health
main
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md2,198 B -
docs
SUMMARY.md128 B
History
- First seen on skills.sh
- First recorded snapshot · 1 installs
SKILL.md
Adding an Interactive Demo to Docs
Interactive demos render a Remotion composition inline in documentation pages using @remotion/player. They live in packages/docs/components/demos/.
Effect demos are separate: use <EffectsDemo type="effects-..." /> and register them in packages/docs/components/effects-demos/registry.ts with the real effect schema, not the generic <Demo> options array.
Steps
- Create a component in
packages/docs/components/demos/(e.g.MyDemo.tsx). It should be a standard React component using Remotion hooks likeuseCurrentFrame()anduseVideoConfig().
- Register the demo in
packages/docs/components/demos/types.ts:
- Import the component - Export a DemoType object with these fields: - id: unique string used in <Demo type="..." /> - comp: the React component - compWidth / compHeight: canvas dimensions (e.g. 1280x720) - fps: frame rate (typically 30) - durationInFrames: animation length - autoPlay: whether it plays automatically - options: array of interactive controls (can be empty [])
- Add to the demos array in
packages/docs/components/demos/index.tsx:
- Import the demo constant from ./types - Add it to the demos array
- Use in MDX with
<Demo type="your-id" />
Options
Options add interactive controls below the player. Each option needs name and optional ('no', 'default-enabled', or 'default-disabled').
Supported types:
type: 'numeric'— slider withmin,max,step,defaulttype: 'boolean'— checkbox withdefaulttype: 'enum'— dropdown withvaluesarray anddefaulttype: 'string'— text input withdefault
Option values are passed to the component as inputProps. Access them as regular React props.
Example registration
export const myDemo: DemoType = {
comp: MyDemoComp,
compHeight: 720,
compWidth: 1280,
durationInFrames: 150,
fps: 30,
id: 'my-demo',
autoPlay: true,
options: [],
};