Skip to content

guanyang/open-agent-hub / skills/remotion-best-practices

remotion-best-practices

Verified

Router for all Remotion skills

FileKindSize
SKILL.mdskill md4.1 KB
agents/openai.yamlconfig311 B
assets/remotion-icon.pngbinary1.3 KB
assets/remotion-icon.svgother1.3 KB
remotion-license/REFERENCE.mdmarkdown498 B
remotion-license/agents/openai.yamlconfig300 B
remotion-license/assets/remotion-icon.svgother1.3 KB
remotion-maps/REFERENCE.mdmarkdown1.0 KB
remotion-maps/agents/openai.yamlconfig293 B
remotion-maps/assets/remotion-icon.pngbinary1.3 KB
remotion-maps/assets/remotion-icon.svgother1.3 KB
remotion-maps/techniques/cesium/TECHNIQUE.mdmarkdown3.9 KB
remotion-maps/techniques/cesium/assets/CesiumFlythrough.tsxother8.2 KB
remotion-maps/techniques/cesium/assets/cesium-path.jsonconfig12.0 KB
remotion-maps/techniques/cesium/assets/city-path.jsonconfig223 B
remotion-maps/techniques/cesium/assets/example-Root.tsxother923 B
remotion-maps/techniques/cesium/assets/flight-path.tsscript1.2 KB
remotion-maps/techniques/cesium/assets/sample-river.geojsonother6.3 KB
remotion-maps/techniques/cesium/references/3d-data-sources.mdmarkdown1.6 KB
remotion-maps/techniques/cesium/references/3d-flyover-architecture.mdmarkdown7.8 KB
remotion-maps/techniques/cesium/references/3d-troubleshooting.mdmarkdown6.6 KB
remotion-maps/techniques/cesium/scripts/prep-cesium-path.mjsscript5.4 KB
remotion-maps/techniques/mapbox/TECHNIQUE.mdmarkdown12.7 KB
remotion-maps/techniques/mapbox/references/render-stability.mdmarkdown3.6 KB
remotion-maps/techniques/maplibre/TECHNIQUE.mdmarkdown13.5 KB
remotion-maps/techniques/maplibre/references/render-stability.mdmarkdown3.6 KB
remotion-maps/techniques/maptiler/TECHNIQUE.mdmarkdown3.5 KB
remotion-maps/techniques/maptiler/assets/CountryLabel.tsxother1.8 KB
remotion-maps/techniques/maptiler/assets/MapTilerVectorElement.tsscript1.5 KB
remotion-maps/techniques/maptiler/assets/RiverReveal.tsxother10.6 KB
remotion-maps/techniques/maptiler/assets/example-Root.tsxother1.0 KB
remotion-maps/techniques/maptiler/assets/sample-data/country-meta.jsonconfig325.3 KB
remotion-maps/techniques/maptiler/assets/sample-data/yarlung-flow.jsonconfig12.8 KB
remotion-maps/techniques/maptiler/assets/tokens.tsscript1.2 KB
remotion-maps/techniques/maptiler/references/map-data-sources.mdmarkdown4.6 KB
remotion-maps/techniques/maptiler/references/map-explainer-architecture.mdmarkdown6.7 KB
remotion-maps/techniques/maptiler/references/map-geo-prep.mdmarkdown4.0 KB
remotion-maps/techniques/maptiler/references/render-stability.mdmarkdown3.6 KB
remotion-maps/techniques/maptiler/scripts/prep-geo.mjsscript7.4 KB
remotion-maps/techniques/static-map/TECHNIQUE.mdmarkdown1.1 KB
remotion-multimedia/REFERENCE.mdmarkdown705 B
remotion-multimedia/agents/openai.yamlconfig317 B
remotion-multimedia/assets/remotion-icon.pngbinary1.3 KB
remotion-multimedia/assets/remotion-icon.svgother1.3 KB
remotion-multimedia/get-audio-duration.mdmarkdown1.5 KB
remotion-multimedia/get-video-dimensions.mdmarkdown1.8 KB
remotion-multimedia/get-video-duration.mdmarkdown1.4 KB
remotion-studio/REFERENCE.mdmarkdown1.5 KB
remotion-studio/agents/openai.yamlconfig237 B
remotion-studio/assets/remotion-icon.pngbinary1.3 KB
remotion-studio/assets/remotion-icon.svgother1.3 KB
remotion-upgrade/REFERENCE.mdmarkdown1.9 KB
remotion-upgrade/agents/openai.yamlconfig282 B
remotion-upgrade/assets/remotion-icon.pngbinary1.3 KB
remotion-upgrade/assets/remotion-icon.svgother1.3 KB

remotion-maps/techniques/maptiler/references/map-data-sources.md

View on GitHub
# Map element data sources

Choose the source independently for every story element. A single map can—and often should—mix
provider vectors with custom geodata.

## Decision rule

Use a MapTiler Planet vector layer when the feature already exists there, its attributes support an
editorially precise filter, and provider geometry is acceptable for the claim. Use custom GeoJSON when
the feature is absent, proposed, historical, disputed, corrected, privately sourced, or needs ordered
geometry for a deterministic draw.

| Requirement                                                                 | MapTiler vector layer | Custom GeoJSON                              |
| --------------------------------------------------------------------------- | --------------------- | ------------------------------------------- |
| Roads, waterways, water, boundaries, land cover, or other standard context  | Prefer                | Use only when provider data is insufficient |
| Basemap-consistent geometry without a duplicate local dataset               | Prefer                | No                                          |
| Proposed, historical, classified, corrected, or production-specific element | No                    | Prefer                                      |
| Fade, colour, width, radius, blur, or fill-opacity animation                | Yes                   | Yes                                         |
| Feature-state highlight when a stable feature ID exists                     | Yes                   | Yes                                         |
| Deterministic source-to-end line draw or perimeter draw                     | Bake first            | Prefer                                      |
| Geometry editing, morphing, clipping, or exact sequencing                   | No                    | Prefer                                      |

Provider alignment is not proof of correctness. Inspect the attributes and geometry against the
editorial source before presenting a provider feature as evidence.

## MapTiler vector mode

MapTiler Planet is a vector tile source. Add it once, then build story layers with a
`source-layer` and an exact attribute filter. Read the current MapTiler Planet schema before choosing
layer names or fields.

Common layer categories include `waterway`, `water`, `transportation`, `boundary`, `landcover`, and
`poi`; availability, fields, and zoom ranges vary by schema version.

Replace `YOUR_API_KEY` in `../assets/MapTilerVectorElement.ts` with a MapTiler key.

```ts
import {addMapTilerVectorElement, setVectorElementPaint} from "./MapTilerVectorElement";

addMapTilerVectorElement(map, {
  id: "story-roads",
  sourceLayer: "transportation",
  type: "line",
  filter: ["==", ["get", "class"], "motorway"],
  layout: {"line-cap": "round", "line-join": "round"},
  paint: {
    "line-color": "#E8F7FF",
    "line-width": 3,
    "line-opacity": 0,
  },
});

setVectorElementPaint(map, "story-roads", {
  "line-opacity": reveal,
  "line-width": 2 + reveal * 2,
});
```

Animate provider features by changing paint properties from the Remotion frame: opacity, colour,
width, blur, fill opacity, circle radius, or symbol opacity. Use feature state only when the source
provides stable IDs and the selection remains deterministic across tiles.

Do not treat a tiled line as one ordered path. Vector tiles split features at tile boundaries, so a
source-to-mouth or start-to-end draw has no reliable global order. If that motion carries meaning,
extract and verify the complete feature, order it once, save it as GeoJSON, and use the custom mode.

## Custom geodata mode

Load verified GeoJSON into a map source and update it from the Remotion frame. Preprocess geometry
into an ordered path when the animation needs distance-based slicing or deterministic sequencing.

Custom mode is mandatory when:

- the feature is not in the provider dataset;
- the story uses a proposed route, planned tunnel, historical boundary, disputed interpretation, or
  non-public dataset;
- provider geometry was editorially corrected;
- motion must travel through the geometry in a verified order;
- a complete off-screen boundary matters and a viewport query would silently crop it.

## Hybrid mode

Use provider vectors for ordinary contextual features and custom GeoJSON for the specific claim. For
example: MapTiler waterways and roads as aligned context; a custom proposed tunnel, dam site, disputed
boundary, or verified evacuation area as the highlighted evidence.

Keep provider and custom layers visually distinct when they carry different evidentiary weight. Record
the source and effective date of every custom layer in the production notes.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall