Home/Tech Writing/writing-docs
W

writing-docs

by @remotion-devv
4.4(40)

Writes Remotion documentation, guiding on how to create new .mdx files and add them to the documentation structure, ensuring document standardization.

technical-documentationapi-documentationmarkdowndeveloper-experienceremotionGitHub
Installation
npx skills add https://github.com/remotion-dev/remotion --skill writing-docs
compare_arrows

Before / After Comparison

1 组
Before

In the absence of clear guidance, document writing often lacks uniform standards, leading to inconsistent content formats and chaotic structures. This makes documents difficult to read and maintain, reduces information transfer efficiency, and affects team collaboration.

After

A standardized document writing process guides how to create and organize documents, ensuring consistent content formats and structures. This significantly improves document readability and maintainability, ensures accurate information transmission, and facilitates efficient team collaboration.

SKILL.md

writing-docs

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. --- image: /generated/articles-docs-my-package-my-api.png title: '' crumb: '@remotion/my-package' --- 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. Use headings for all fields: When documenting API options or return values, each property should be its own heading. Use ### for top-level properties and #### for nested properties within an options object. Do not use bullet points for individual fields. Language guidelines Keep it brief: Developers don't like to read. Extra words cause information loss. Link to terminology: Use terminology page for Remotion-specific terms. Avoid emotions: Remove filler like "Great! Let's move on..." - it adds no information. Separate into paragraphs: Break up long sections. Address as "you": Not "we". Don't blame the user: Say "The input is invalid" not "You provided wrong input". Don't assume it's easy: Avoid "simply" and "just" - beginners may struggle. Code snippets Basic syntax highlighting: ts const x = 1; Type-safe snippets (preferred) Use twoslash to check snippets against TypeScript: ts twoslash import {useCurrentFrame} from 'remotion'; const frame = useCurrentFrame(); Hiding imports Use // ---cut--- to hide setup code - only content below is displayed: ts twoslash import {useCurrentFrame} from 'remotion'; // ---cut--- const frame = useCurrentFrame(); Adding titles Always add a title to code fences that show example usage: ts twoslash title="MyComponent.tsx" console.log('Hello'); Special components Steps - 1 First step - 2 Second step Experimental badge This feature is experimental. Interactive demos Demos must be implemented in packages/docs/components/demos/index.tsx. See the docs-demo skill for details on adding new demos. AvailableFrom Use to indicate when a feature or parameter was added. No import needed - it's globally available. For page-level version indicators, use an # h1 heading with inline so it appears next to the title (not below it). Use < and > to escape angle brackets in component names: # <MyComponent> # @remotion/my-package For section headings: ## Saving to another cloud CompatibilityTable Use to indicate which runtimes and environments a component or API supports. No import needed. Place it in a ## Compatibility section before ## See also. Available boolean props: chrome, firefox, safari, player, studio, clientSideRendering, serverSideRendering. Set to true (supported) or {false} (not supported). Set to empty string "" for not applicable if this is a frontend API: nodejs="", bun="", serverlessFunctions="". Use hideServers to hide the Node.js/Bun/serverless row if this is a frontend API. ## Compatibility Optional parameters For optional parameters in API documentation: Add ? to the heading - this indicates the parameter is optional --> Don't do it if it is a CLI flag (beginning with --) - CLI flags are always optional Do NOT add optional text - the ? suffix is sufficient Include default value in description - mention it naturally in the text ### onError? Called when an error occurs. Default: errors are thrown. Do NOT do this: ### onError? optional Called when an error occurs. Combining optional and AvailableFrom When a parameter is both optional and was added in a specific version: ### onError? Called when an error occurs. "Optional since" pattern If a parameter became optional in a specific version (was previously required): ### codec? Optional since . Previously required. Generating preview cards After adding or editing a page, generate social media preview cards: cd packages/docs && bun render-cards.ts Verifying docs compile To check that documentation builds without errors: # from the monorepo root bun run build-docs This validates MDX syntax, twoslash snippets, and broken links.Weekly Installs373Repositoryremotion-dev/remotionGitHub Stars39.6KFirst SeenJan 20, 2026Security AuditsGen Agent Trust HubPassSocketPassSnykPassInstalled onclaude-code321opencode263gemini-cli263cursor258codex249github-copilot201

User Reviews (0)

Write a Review

Effect
Usability
Docs
Compatibility

No reviews yet

Statistics

Installs2.7K
Rating4.4 / 5.0
Version
Updated2026年10月14日
Comparisons1

User Rating

4.4(40)
5
28%
4
50%
3
20%
2
3%
1
0%

Rate this Skill

0.0

Compatible Platforms

🔧Claude Code
🔧OpenClaw
🔧OpenCode
🔧Codex
🔧Gemini CLI
🔧GitHub Copilot
🔧Amp
🔧Kimi CLI

Timeline

Created2026年3月17日
Last Updated2026年10月14日
🎁 Agent Knowledge Cards
Survey