audio-standards

Enforce dual native and web audio recording standards for TranscribeJS.

1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/JoelShepard/TranscribeAPP --skill audio-standards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audio-standards
Source: https://github.com/JoelShepard/TranscribeAPP/tree/main/.agents/skills/audio-standards
Command: npx skills add https://github.com/JoelShepard/TranscribeAPP --skill audio-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides authoritative guidance for developing and maintaining the audio recording and processing pipelines of TranscribeJS, ensuring consistent behavior across native and web contexts.

Core Features & Use Cases

  • Dual Recording Path Integrity: Enforces separate native (tauri/Linux via Rust cpal) and web (navigator.mediaDevices + MediaRecorder) paths to prevent cross-path regressions.
  • Environment & Security: Specifies required headers (Cross-Origin-Opener-Policy and Cross-Origin-Embedder-Policy) to enable SharedArrayBuffer and OfflineAudioContext, with robust error handling for all async calls.
  • Service Architecture: Documents the location and responsibilities of audio processing services (e.g., duration, conversion, splitting) to guide implementation and reviews.

Quick Start

Review the documented standards to ensure dual recording paths, proper security headers, and robust audio services for TranscribeJS.

Frequently Asked Questions about audio-standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize audio recording across web and native Taurin environments?

Standardize audio recording across environments by maintaining dual paths: navigator.mediaDevices with MediaRecorder for web and cpal via Rust for native Taurin. This prevents cross-path regressions and enforces consistent async error handling across the app.

What security headers are required to enable SharedArrayBuffer for web audio processing?

To enable SharedArrayBuffer and OfflineAudioContext for web audio processing, you must configure Cross-Origin-Opener-Policy and Cross-Origin-Embedder-Policy headers. These secure headers are required for the web recording path to function correctly.

When should I use MediaRecorder versus cpal for audio capture?

Use MediaRecorder for the web recording path via navigator.mediaDevices, and use cpal via Rust for the native Linux path. Maintaining these as separate dual recording paths prevents cross-path regressions and ensures robust audio capture in each environment.

What audio services are needed for processing recorded audio files?

Audio processing services should handle duration calculation, audio format conversion, and audio file splitting. These services must be documented with clear locations and responsibilities to guide implementation and ensure robust operations around async audio tasks.

How do I handle errors in async audio recording operations?

Implement robust error handling around all async audio operations by wrapping MediaRecorder and cpal capture calls with proper error boundaries. This prevents silent failures during audio recording and ensures the service workflow degrades gracefully across both paths.