This is a comprehensive style guide for writing Remotion's API documentation, covering everything from file structure to voice and tone. You'll want this when documenting React components, CLI tools, or any public API in the Remotion ecosystem. The guidelines are opinionated in useful ways: one API per page, headings for every parameter instead of bullet lists, type-checked code snippets using twoslash, and strict rules about optional parameters. It includes MDX components for version badges, compatibility tables, and interactive demos. The language section is particularly solid, pushing for brevity and discouraging assumptions about difficulty. If you're maintaining technical docs for a TypeScript library, you could adapt most of this directly.
npx -y skills add remotion-dev/remotion --skill writing-docs --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
supercent-io/skills-template
supercent-io/skills-template
huangjia2019/claude-code-engineering
reactjs/react.dev
reactjs/react.dev