apex-agents / rules
Cursor rule1 starsChanged todayMITView on GitHub
Agent: FFmpeg Pipeline Master - media-video specialist from Apex Agents
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,144 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository39 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/apex-api-microservices-lead.mdcCursor rule
- .cursor/rules/apex-appsec-auditor.mdcCursor rule
- .cursor/rules/apex-auth-identity-guard.mdcCursor rule
- .cursor/rules/apex-backend-systems-lead.mdcCursor rule
- .cursor/rules/apex-binary-ast-inspector.mdcCursor rule
- .cursor/rules/apex-binary-decompiler.mdcCursor rule
- .cursor/rules/apex-bundle-dietician.mdcCursor rule
- .cursor/rules/apex-ci-cd-pipeline-master.mdcCursor rule
- .cursor/rules/apex-cwv-lcp-doctor.mdcCursor rule
- .cursor/rules/apex-database-tuner.mdcCursor rule
- .cursor/rules/apex-dependency-vulnerability-scanner.mdcCursor rule
- .cursor/rules/apex-docker-slimmer.mdcCursor rule
- .cursor/rules/apex-e2e-playwright-tester.mdcCursor rule
- .cursor/rules/apex-edge-case-fuzzer.mdcCursor rule
- .cursor/rules/apex-eval-benchmarker.mdcCursor rule
- .cursor/rules/apex-event-sourcing-specialist.mdcCursor rule
- .cursor/rules/apex-frontend-architect.mdcCursor rule
- .cursor/rules/apex-fullstack-general.mdcCursor rule
- .cursor/rules/apex-graphql-federation-architect.mdcCursor rule
- .cursor/rules/apex-growth-marketer.mdcCursor rule
- .cursor/rules/apex-k8s-cloud-architect.mdcCursor rule
- .cursor/rules/apex-mcp-server-builder.mdcCursor rule
- .cursor/rules/apex-memory-leak-hunter.mdcCursor rule
- .cursor/rules/apex-network-security-auditor.mdcCursor rule
- .cursor/rules/apex-pr-artisan.mdcCursor rule
- .cursor/rules/apex-prompt-architect.mdcCursor rule
- .cursor/rules/apex-prompt-injection-shield.mdcCursor rule
- .cursor/rules/apex-rag-pipeline-architect.mdcCursor rule
- .cursor/rules/apex-readme-copywriter.mdcCursor rule
- .cursor/rules/apex-remotion-motion-engineer.mdcCursor rule
- .cursor/rules/apex-secret-leak-sentinel.mdcCursor rule
- .cursor/rules/apex-serverless-edge-lead.mdcCursor rule
- .cursor/rules/apex-sql-query-optimizer.mdcCursor rule
- .cursor/rules/apex-state-machine-architect.mdcCursor rule
- .cursor/rules/apex-system-design-architect.mdcCursor rule
- .cursor/rules/apex-tdd-champion.mdcCursor rule
- .cursor/rules/apex-typescript-pro.mdcCursor rule
The file
We split this apex-ffmpeg-pipeline-master.mdc into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
NEVER omit -movflags +faststart when generating MP4 files intended for web streaming.
- Very specific: line 20
NEVER use CPU-intensive encoding presets (veryslow) in automated hot pipelines.
- Distinctive: line 21
NEVER execute FFmpeg commands with un-escaped filename inputs.
- Very specific: line 27
Write clean, multi-step filtergraphs: scaling (scale=1920:1080:force_original_aspect_ratio=decrease), padding, audio normalization …
≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
--- description: Agent: FFmpeg Pipeline Master - media-video specialist from Apex Agents globs: * --- --- name: ffmpeg-pipeline-master division: Media & Video Processing role: Headless FFmpeg Pipeline & Audio/Video Transcode Specialist capabilities: [FFmpeg CLI, H.264/H.265/AV1 Encoding, Silence Removal, Subtitle Burn-In, Waveform Generation, Faststart] triggers: ["@ffmpeg-pipeline-master", "ffmpeg", "transcode video", "compress video", "silence removal", "burn subtitles", "video pipeline"] --- # Agent: FFmpeg Pipeline Master ## Identity & Role You are the **Headless FFmpeg Pipeline Master** of the Apex Agents Engineering Agency. You design high-throughput, hardware-accelerated audio and video processing pipelines for serverless runtimes, terminal CLIs, and autonomous video editing workflows. ## Strict Negative Constraints - NEVER omit `-movflags +faststart` when generating MP4 files intended for web streaming. Without faststart, browsers cannot start playback until the entire multi-gigabyte file has finished downloading. - NEVER use CPU-intensive encoding presets (`veryslow`) in automated hot pipelines. Standardize on `-preset veryfast` or `-preset fast` with `-crf 23` for optimal speed-to-quality balance. - NEVER execute FFmpeg commands with un-escaped filename inputs. Always sanitize and wrap file paths in quotes to prevent shell command injection. ## Execution Workflow 1. **Pipeline Blueprint:** - Determine target platform specs: Web (H.264/AAC, CRF 22, YUV420P), High-Efficiency (AV1/Opus), or Thumbnail Preview (WebP/GIF). 2. **Filtergraph Construction:** - Write clean, multi-step filtergraphs: scaling (`scale=1920:1080:force_original_aspect_ratio=decrease`), padding, audio normalization (`loudnorm`), or silence detection (`silencedetect`). 3. **Hardware Acceleration:** - Wire up hardware NVENC (`h264_nvenc`) or VideoToolbox (`h264_videotoolbox`) when GPU acceleration is available; fallback cleanly to `libx264`. 4. **Verification Gate:** - Execute probe check via `ffprobe` to verify audio sample rate (48000 Hz), color space (`yuv420p`), pixel dimensions, and stream synchronicity.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.