modern-short-video▌
imaimai17468/modern-short-video-skills · updated Apr 17, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Create professional, modern product launch videos using Remotion and React.
Modern Short Video Skill
Create professional, modern product launch videos using Remotion and React.
Prerequisites (MANDATORY)
WARNING: Do NOT skip this step. Skipping will result in missing rich expression opportunities.
This skill extends Remotion best practices. You MUST do both:
-
Load the skill first:
/remotion-best-practices -
Read the SKILL.md of remotion-best-practices and identify which rules are relevant to the product (maps, charts, text animations, 3D, lottie, etc.)
Workflow
Step 1: Analyze Product & Select Rich Expressions (CRITICAL)
Before asking for screenshots, analyze the product and find relevant rich expressions from remotion-best-practices.
Replace static screenshots with dynamic content wherever possible:
- Map app → animated map with route drawing
- Dashboard → animated charts
- Text app → typewriter effects
- etc.
Read the relevant rule files from remotion-best-practices and use them.
Step 2: Device, Theme & BGM Questions
Use AskUserQuestion to ask:
-
Device Type: Is the product primarily for smartphone (SP) or PC/Desktop?
- SP (Smartphone) → Use phone mockup frame
- PC/Desktop → Use browser/desktop mockup frame
-
Screenshot Theme: Should screenshots be in Light mode or Dark mode?
- Dark mode (Recommended) → Blends with video background (#0a0a0a)
- Light mode → Higher contrast, screenshots stand out more
-
BGM (Background Music): Add background music?
- Yes (Recommended) → Download free music from Pixabay
- No → Create video without BGM
Step 3: Collect Screenshots
Note: Screenshots for scenes using rich expressions (Step 1) are not needed.
Required images (place in public/ folder):
| File | Purpose | Required |
|---|---|---|
mockup.png |
Main product screenshot (Mockups scene) | Yes |
feature-1.png |
Feature 1 screenshot | Yes |
feature-2.png |
Feature 2 screenshot | Optional |
feature-3.png |
Feature 3 screenshot | Optional |
Step 4: Collect Content
Required information:
- Product name
- One-line tagline/concept
- Feature 1: Title + short description
- Feature 2: Title + short description (optional)
- Feature 3: Title + short description (optional)
- CTA text (e.g., "Try it free")
- URL
Step 5: Verify Assets
ls public/*.png
Step 6: Create Composition
Create src/remotion/[ProductName]/[ProductName]Intro.tsx with all scenes.
Step 7: Register & Calculate Duration
Add to Root.tsx. IMPORTANT: Calculate durationInFrames correctly:
durationInFrames = Sum of scene durations - (transition duration × number of transitions)
See rules/duration-calculation.md for details.
Step 8: Test
Run pnpm run dev (or bun run remotion) and preview the video.
Scene Structure (8 Scenes)
┌─────────────────────────────────────────────────────────────┐
│ 1. REVEAL 2. CONCEPT 3. MOCKUPS │
│ (2-3s) (3-4s) (3-4s) │
│ Logo/Name Value prop Product preview │
├─────────────────────────────────────────────────────────────┤
│ 4. FEATURE 1 5. FEATURE 2 6. FEATURE 3 │
│ (3-4s each) (optional) (optional) │
│ Screenshot + Screenshot + Screenshot + │
│ Title/Desc Title/Desc Title/Desc │
├─────────────────────────────────────────────────────────────┤
│ 7. OUTRO 8. CTA │
│ (2-3s) (3-4s) │
│ Summary URL + Action │
└─────────────────────────────────────────────────────────────┘
Scene Details
| Scene | Duration | Content | Asset |
|---|---|---|---|
| 1. Reveal | 2-3s | Product name, minimal animation | - |
| 2. Concept | 3-4s | Tagline, value proposition | - |
| 3. Mockups | 3-4s | Device mockup with main screenshot | mockup.png or rich expression |
| 4. Feature 1 | 3-4s | Feature title + screenshot | feature-1.png or rich expression |
| 5. Feature 2 | 3-4s | Feature title + screenshot | feature-2.png or rich expression |
| 6. Feature 3 | 3-4s | Feature title + screenshot | feature-3.png or rich expression |
| 7. Outro | 2-3s | Product name + summary | - |
| 8. CTA | 3-4s | URL, call to action | - |
Total Duration: 15-25 seconds (depending on feature count)
Design Rules
| Element | Do | Don't |
|---|---|---|
| Background | Solid dark #0a0a0a |
Gradients |
| Typography | Single font (Inter/Noto Sans JP) | Multiple fonts |
| Animation | Subtle fade/slide | Bouncy/flashy |
| Mockups | Real screenshots or rich expressions | Placeholder graphics |
| Text | Minimal, clear | Long paragraphs |
Detailed Guidelines
For comprehensive guidance, read these rule files:
- rules/design-principles.md - Visual design system
- rules/scene-structure.md - Scene composition patterns
- rules/visual-elements.md - Mockups, typography, colors
- rules/animation-patterns.md - Motion design patterns
- rules/code-templates.md - Ready-to-use Remotion components
- rules/duration-calculation.md - How to calculate total video duration
- rules/bgm.md - Background music source and implementation
Quick Reference: Scene Components
// Scene order
<TransitionSeries>
<RevealScene /> {/* 1. Logo/Name */}
<ConceptScene /> {/* 2. Value proposition */}
<MockupsScene /> {/* 3. Main product mockup */}
<FeatureScene n={1} /> {/* 4. Feature 1 */}
<FeatureScene n={2} /> {/* 5. Feature 2 (if provided) */}
<FeatureScene n={3} /> {/* 6. Feature 3 (if provided) */}
<OutroScene /> {/* 7. Summary */}
<CTAScene /> {/* 8. Call to action */}
</TransitionSeries>
Checklist Before Delivery
- Prerequisites loaded (
/remotion-best-practicesexecuted and relevant rules read) - Rich expressions used where applicable (maps, charts, text animations, etc.)
- Screenshots collected for scenes not using rich expressions
- Screenshots are high quality (2x resolution preferred)
- Text is readable at 720p
- Total duration 15-25 seconds
- durationInFrames correctly calculated (subtract transition overlaps!)
- No black frames at the end of video
- Transitions are smooth (fade, 15 frames)
- CTA and URL clearly visible
- BGM added (optional, volume ~0.25)
How to use modern-short-video on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add modern-short-video
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches modern-short-video from GitHub repository imaimai17468/modern-short-video-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate modern-short-video. Access the skill through slash commands (e.g., /modern-short-video) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.8★★★★★55 reviews- ★★★★★Min Gupta· Dec 28, 2024
modern-short-video is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Shikha Mishra· Dec 16, 2024
modern-short-video has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Valentina Sharma· Dec 16, 2024
modern-short-video reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Dev Nasser· Dec 12, 2024
Useful defaults in modern-short-video — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Nia Yang· Nov 23, 2024
modern-short-video has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Valentina Farah· Nov 23, 2024
Keeps context tight: modern-short-video is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Kwame Flores· Nov 19, 2024
modern-short-video reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Dev Liu· Nov 7, 2024
modern-short-video is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Valentina Shah· Nov 3, 2024
I recommend modern-short-video for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Dev Farah· Oct 26, 2024
Useful defaults in modern-short-video — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 55