add-sfx▌
remotion-dev/remotion · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Sound effects must first be added to the remotion.media repository. The source of truth is generate.ts in that repo. A sound effect must exist there before it can be added to @remotion/sfx.
Prerequisites
Sound effects must first be added to the remotion.media repository. The source of truth is generate.ts in that repo. A sound effect must exist there before it can be added to @remotion/sfx.
Sound effects must be:
- WAV format
- CC0 (Creative Commons 0) licensed
- Normalized to peak at -3dB
Steps
1. Add to remotion.media repo (must be done first)
In the remotion-dev/remotion.media repo:
- Add the WAV file to the root of the repo
- Add an entry to the
soundEffectsarray ingenerate.ts:{ fileName: "my-sound.wav", attribution: "Description by Author -- https://source-url -- License: Creative Commons 0", }, - Run
bun generate.tsto copy it tofiles/and regeneratevariants.json - Deploy
2. Add the export to packages/sfx/src/index.ts
Use camelCase for the variable name. Avoid JavaScript reserved words (e.g. use uiSwitch not switch).
export const mySound = 'https://remotion.media/my-sound.wav';
3. Create a doc page at packages/docs/docs/sfx/<name>.mdx
Follow the pattern of existing pages (e.g. whip.mdx). Include:
- Frontmatter with
image,title(camelCase export name),crumb: '@remotion/sfx' <AvailableFrom>tag with the next release version<PlayButton>import and usage- Description
- Example code using
@remotion/media's<Audio>component - Value section with the URL in a fenced code block
- Duration section (fetch the file and use
afinfoon macOS to get duration/format) - Attribution section with source link and license
- See also section linking to related sound effects
4. Register in sidebar and table of contents
packages/docs/sidebars.ts— add'sfx/<name>'to the@remotion/sfxcategory itemspackages/docs/docs/sfx/table-of-contents.tsx— add a<TOCItem>with a<PlayButton size={32}>
5. Update the skills rule file
Add the new URL to the list in packages/skills/skills/remotion/rules/sfx.md.
6. Build
cd packages/sfx && bun run make
Naming conventions
| File name | Export name |
|---|---|
my-sound.wav |
mySound |
switch.wav |
uiSwitch (reserved word) |
page-turn.wav |
pageTurn |
Version
Use the current version from packages/core/src/version.ts.
For docs <AvailableFrom>, increment the patch version by 1.
How to use add-sfx 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 add-sfx
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches add-sfx from GitHub repository remotion-dev/remotion 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 add-sfx. Access the skill through slash commands (e.g., /add-sfx) 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▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★26 reviews- ★★★★★Min Malhotra· Dec 8, 2024
add-sfx has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Chaitanya Patil· Dec 4, 2024
Solid pick for teams standardizing on skills: add-sfx is focused, and the summary matches what you get after install.
- ★★★★★Xiao Kapoor· Nov 27, 2024
add-sfx fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Piyush G· Nov 23, 2024
We added add-sfx from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Diego Chen· Nov 3, 2024
add-sfx is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Sakura Khan· Oct 22, 2024
Keeps context tight: add-sfx is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Xiao Sharma· Oct 18, 2024
We added add-sfx from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Shikha Mishra· Oct 14, 2024
add-sfx fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Ren Khan· Sep 13, 2024
add-sfx has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Omar Malhotra· Sep 9, 2024
Useful defaults in add-sfx — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 26