Create an editable developer skills announcement video for [PROJECT] and [AUDIENCE]. Use the attached reference video to study composition and pacing, then build a new result with approved content and your own visual identity.

## Objective and Inputs

Type the release headline; explain the skill concept; play an actual workflow recording; close with the release identity.

Ask for the required assets, exact on-screen copy, intended destination, output size and licensed audio. Use [APPROVED_CONTENT] for names, quantities, claims and interface labels, and [BRAND_RULES] for the visual system. If an input is missing, list it before choosing a substitute. Treat any demonstration data as fictional and label it.

## Scene Plan

1. Type the release headline. Specify its entrance, reading hold, visible action and transition to the next scene.
2. Explain the skill concept. Specify its entrance, reading hold, visible action and transition to the next scene.
3. Play an actual workflow recording. Specify its entrance, reading hold, visible action and transition to the next scene.
4. Close with the release identity. Specify its entrance, reading hold, visible action and transition to the next scene.

Before implementation, return a timing table with scene start, end, copy and assets. The reference runs approximately 20.2 seconds at 1920 × 1080; use that as a comparison, not a requirement to cram longer copy into the same duration. Propose a shorter state list or longer reading holds when the supplied material needs them.

## Task-Specific Motion

Keep the two title lines in order and allow a reading hold after typing. Use a continuous zoom into the recording’s important region rather than repeated hard crops.

Keep transitions tied to the story. Preserve a recognizable anchor between adjacent scenes and avoid changing scale, color, type and camera direction all at the same time. Hold information still long enough to read. If a cursor, pointer or highlight is used, align it with the exact target and show the resulting response.

## Typography, Assets and Audio

- Make the main message readable at normal phone playback size.
- Preserve approved asset proportions; do not stretch a logo, device, chart or screenshot.
- Keep editable text separate from images where the project allows it.
- Mark music and sound cues on the timing table. Use only supplied or properly licensed audio.
- Use a silent timing preview when audio is unavailable, rather than claiming the film is synchronized to a track that was not provided.

## Implementation and Deliverables

Use the existing project stack. Build an explicit timeline whose state can be inspected at any timestamp. Keep copy, input data, colors and scene timing in editable configuration rather than scattering them through rendering logic. Reuse authorized assets locally and report missing fonts or integrations.

Return editable source, the timing table, a poster and an MP4 render. Preview one frame from every scene and inspect the transitions before the full export. Do not use the reference video itself as the finished deliverable or imply that a visual demonstration implements real product functionality.

## Review This Specific Result

Every UI recording must correspond to the announced feature and remain readable during the zoom.

Check the first and last frame, the longest line of copy, the smallest important label and every scene boundary. Verify that the exported frame count, aspect ratio and audio length agree with the approved timeline. Review a silent playback first to confirm the visual story is understandable. Record any differences from the reference and any behavior not implemented.

## Reference and Attribution

Reference creator: @edwinarbus.
Source: https://www.remotion.dev/prompts/cursor-agent-skills-announcement
This is an OpenDesign editorial adaptation of the public task idea. Use the reference to learn from its structure; obtain permission before redistributing creator media beyond your authorized use.