writing-docs
Guides for writing and editing Remotion documentation. Use when adding docs pages, editing MDX files in packages/docs, or writing documentation content.
Install
git clone https://github.com/remotion-dev/remotion /tmp/remotion && ln -s /tmp/remotion/.agents/skills/writing-docs ~/.claude/skills/writing-docs
From README
Writing Remotion Documentation Documentation lives in packages/docs/docs as .mdx files. Adding a new page Create a new .mdx file in packages/docs/docs Add the document to packages/docs/sidebars.ts Write the content following guidelines below Run bun render-cards.ts in packages/docs to generate social preview cards Breadcrumb (crumb): If a documentation page belongs to a package, add crumb: '@remotion/package-name' to the frontmatter. This displays the package name as a breadcrumb above the title. One API per page: Each function or API should have its own dedicated documentation page. Do not combine multiple APIs (e.g., getEncodableVideoCodecs() and getEncodableAudioCodecs()) on a single page. Public API only: Documentation is for public APIs only. Do not mention, reference, or compare against internal/private APIs or implementation details. API names in prose: Put API names in backticks, and link them if a docs page exists.
More from this repo
pr-name
Used to review or correct a Remotion pull request title
add-cli-option
Used to add a new Remotion CLI or config option by creating an AnyRemotionOption, registering CLI parsing, wiring...
add-effect
Used to add a new effect to @remotion/effects, including implementation, package exports, docs, demos, preview images,...
