[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7APQTGBM75JSFS0XXXAC2AQ":3,"skill-same:01M7APQTGBM75JSFS0XXXAC2AQ":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7APQTGBM75JSFS0XXXAC2AQ","media-production-and-loudness",null,"Use when working on the production side: audio production (DAWs, plugin formats such as VST3, AU and AAX, latency and buffer sizes, sample-accurate automation), video production (NLEs, intermediate codecs, colour management, timecode and sync, frame-rate pulldown), and loudness — LUFS, true peak, the broadcast standards, and why a mix that sounds right in the studio is quiet on streaming platforms.","the-vibey-project\u002Fvibey","the-vibey-project","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F329298758?v=4","01M7AJHGZ9722CTJ4JNQZVRH0Q","the vibey project","01M7AJHGZVMG2K7TGXQ6XFHVG3",5,"MIT","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fmedia-engineering\u002Fskills\u002Fmedia-production-and-loudness\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: media-production-and-loudness\ndescription: \"Use when working on the production side: audio production (DAWs, plugin formats such as VST3, AU and AAX, latency and buffer sizes, sample-accurate automation), video production (NLEs, intermediate codecs, colour management, timecode and sync, frame-rate pulldown), and loudness — LUFS, true peak, the broadcast standards, and why a mix that sounds right in the studio is quiet on streaming platforms.\"\n---\n\n# Media Engineering: Audio Production, Video Production, and Loudness\n\n> **Part 2 of 5** of the *Media Engineering* reference (plugin `media-engineering`), covering §4–§6. Sibling skills: `media-fundamentals-containers-and-codecs` (§0–§3), `media-transcoding-streaming-and-drm` (§7–§9), `media-captions-podcasts-rights-and-qc` (§10–§14), `media-reference` (§15–§20). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** Verified August 2026. See §17 → `media-reference` for the currency snapshot and what goes stale first.\n\n> **How to read this.** Reference for engineers building media systems — deliberately\n> distinct from a DSP reference (which covers the algorithms) and a smart-TV reference\n> (which covers app platforms). **This is the production, packaging and delivery stack.**\n>\n> Three markers:\n> - **[DURABLE]** — formats, workflow structure, and the physical and perceptual\n>   constraints. Most of this document.\n> - **[VERSIONED]** — codecs, protocols, platforms, rights. ⚠️ **Verify.**\n> - **[CONTESTED]** — genuine disagreement.\n>\n> **⚠️ GOTCHA** boxes mark where media pipelines silently corrupt, desync, or get rejected.\n>\n> **The three framings that organize everything below:**\n> 1. **⚠️ Media is a compatibility problem wearing a compression costume.** The hard part\n>    is almost never the codec — it's that **every device, browser, and platform accepts a\n>    different subset of a different container with different DRM**, and you must serve all\n>    of them (§3 → `media-fundamentals-containers-and-codecs`, §8 → `media-transcoding-streaming-and-drm`).\n> 2. **Every media decision is a triangle: quality, bitrate, and compute.** ⚠️ **You pick\n>    two.** A better codec moves the triangle; it doesn't abolish it — **and encoding\n>    complexity is the price AV1 and VVC charge for their bitrate savings** (§3.2 → `media-fundamentals-containers-and-codecs`).\n> 3. **⚠️ The rights layer is now as load-bearing as the technical one**, and it's moving\n>    faster. Loudness normalization, content ID, licensing metadata, and the AI training\n>    fight all determine what you may ship, not just what you can encode (§12 → `media-captions-podcasts-rights-and-qc`, §13 → `media-captions-podcasts-rights-and-qc`).\n\n---\n\n## §4. Audio Production\n\n**[DURABLE] The stack an audio engineer actually uses, and what a software engineer needs\nto know to integrate with it.**\n\n**DAWs**: Pro Tools (⚠️ **still the post-production and studio standard**), Logic, Ableton\nLive, Reaper (⚠️ **cheap, scriptable, and beloved by engineers**), Cubase, FL Studio,\nStudio One, Bitwig.\n\n**Plugin formats** — ⚠️ **the interop layer, and a real engineering concern**:\n**VST3** (cross-platform, Steinberg), **AU \u002F AUv3** (Apple), **AAX** (Pro Tools only),\n**LV2** (Linux\u002Fopen), and **CLAP** — ⚠️ **the newer open format (Bitwig\u002Fu-he) with better\nthreading, modulation and note expression, gaining real traction.** **JUCE** is the\ndominant framework for writing plugins across all of them.\n\n**⚠️ The real-time constraint governs everything**: the audio callback is a hard real-time\nthread. **No allocation, no locks, no file I\u002FO, no logging.** Buffer size sets latency\n(⚠️ **64 samples at 48 kHz ≈ 1.3 ms; 512 ≈ 10.7 ms**) and trades against CPU. **Lock-free\nring buffers** to talk to the UI thread.\n\n**MIDI**: 7-bit values, note on\u002Foff, CC, and the ⚠️ **note-off-vs-velocity-zero\nambiguity**. **MIDI 2.0** adds 32-bit resolution, per-note controllers, and\nbidirectional negotiation — ⚠️ **adoption is real but slow, and MIDI 1.0 remains the\nlingua franca.** **MPE** gives per-note pitch and pressure over MIDI 1.0 and is widely\nsupported.\n\n**Audio interfaces and drivers**: **ASIO** (Windows, low-latency, ⚠️ **and the reason\nWDM\u002FDirectSound is unusable for production**), **Core Audio** (macOS, excellent),\n**ALSA\u002FJACK\u002FPipeWire** (Linux — ⚠️ **PipeWire has largely resolved the historic\nJACK\u002FPulseAudio split**). **Network audio**: **Dante** (⚠️ **the professional standard**),\nAES67, AVB, NDI for video-plus-audio over IP.\n\n---\n\n## §5. Video Production\n\n**5.1 Acquisition and intermediates.** **Camera formats**: ProRes (⚠️ **the post-production\nstandard — cheap to decode, expensive in storage**), DNxHD\u002FHR, **RAW** (BRAW, R3D, ARRIRAW\n— ⚠️ **maximum flexibility, enormous files, and debayering cost**), and long-GOP camera\ncodecs (⚠️ **H.264\u002FHEVC from a camera is painful to edit — transcode to an intermediate\nfirst**). **Proxies** are standard practice: edit at low resolution, conform to full\nresolution at the end.\n\n**5.2 Colour.** **Log formats** (S-Log, C-Log, V-Log, Log C) preserve dynamic range for\ngrading. **LUTs** for transforms — ⚠️ **and a 1D LUT cannot do what a 3D LUT does; using\nthe wrong kind silently misgrades**. **ACES** is the standardized colour-managed pipeline.\n⚠️ **The recurring bug: mismatched colour space or transfer function between stages,\nproducing washed-out or oversaturated output that looks like a grading choice rather\nthan an error.**\n\n**5.3 ⚠️ Timecode — the most common source of \"off by a few frames\"**\n**SMPTE timecode**, and the killer detail: **drop-frame vs non-drop-frame.**\nAt 29.97 fps, ⚠️ **drop-frame timecode skips frame *numbers* (never actual frames) to keep\nclock time accurate — 2 numbers per minute, except every tenth minute.** Non-drop counts\nsequentially and drifts ~3.6 seconds per hour against wall clock.\n**⚠️ Mixing them, or assuming 30 fps arithmetic on 29.97 material, is the classic sync\nerror.** **Genlock and word clock** keep devices frame- and sample-aligned in a facility.\n\n**5.4 Editing and delivery.** NLEs: Premiere, Final Cut, DaVinci Resolve (⚠️ **which\nabsorbed colour grading and audio into one application and changed the market**), Avid\nMedia Composer (broadcast\u002Ffilm standard). **Interchange**: EDL, AAF, XML, **OTIO**\n(⚠️ **OpenTimelineIO — the open, scriptable interchange format, and the one worth knowing\nif you're building tooling**). **Deliverables**: IMF for studio distribution, DCP for\ncinema, and **broadcast spec sheets that will reject your file for reasons you did not\nanticipate** (§14 → `media-captions-podcasts-rights-and-qc`).\n\n---\n\n## §6. Loudness\n\n**[DURABLE] The single most practically useful section for anyone shipping audio, and the\none most often discovered too late.**\n\n**⚠️ Peak level and perceived loudness are different things.** A track can peak at 0 dBFS\nand sound quiet, or peak at −6 and sound crushed. **The loudness war** — decades of\never-heavier compression to sound louder than the competition — **was ended not by taste\nbut by normalization.**\n\n**The standards**: **ITU-R BS.1770** defines the measurement (K-weighted, gated).\n**EBU R128** (Europe) targets **−23 LUFS integrated** with a max true peak of −1 dBTP;\n**ATSC A\u002F85** (US broadcast) targets **−24 LKFS**. ⚠️ **LUFS and LKFS are the same unit\nwith different names.**\n\n**⚠️ The units to keep straight**: **Integrated LUFS** (whole-programme average),\n**short-term** (3 s), **momentary** (400 ms), **LRA** (loudness range),\nand **True Peak (dBTP)** — ⚠️ **which measures the inter-sample peaks that appear after\nD\u002FA conversion or lossy encoding, and is why a file that peaks at exactly 0 dBFS can clip\non playback.** Leave −1 dBTP of headroom minimum.\n\n> **⚠️ GOTCHA — this is why your master sounds quiet on streaming.** **Every major platform\n> normalizes playback loudness**, typically in the region of **−14 LUFS**, though **targets\n> differ by platform and change without announcement.** If you master to −8 LUFS, the\n> platform **turns it down** — and you've spent your dynamic range for nothing, arriving\n> quieter *and* more crushed than a competitor who mastered sensibly.\n>\n> ⚠️ **Do not master to a platform target as a hard number.** Master for the music, keep\n> true peak headroom, and check the integrated value. **Verify current targets per platform\n> at release time rather than trusting any figure — including the one in this document.**\n","# Media Engineering: Audio Production, Video Production, and Loudness\n\n> **Part 2 of 5** of the *Media Engineering* reference (plugin `media-engineering`), covering §4–§6. Sibling skills: `media-fundamentals-containers-and-codecs` (§0–§3), `media-transcoding-streaming-and-drm` (§7–§9), `media-captions-podcasts-rights-and-qc` (§10–§14), `media-reference` (§15–§20). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** Verified August 2026. See §17 → `media-reference` for the currency snapshot and what goes stale first.\n\n> **How to read this.** Reference for engineers building media systems — deliberately\n> distinct from a DSP reference (which covers the algorithms) and a smart-TV reference\n> (which covers app platforms). **This is the production, packaging and delivery stack.**\n>\n> Three markers:\n> - **[DURABLE]** — formats, workflow structure, and the physical and perceptual\n>   constraints. Most of this document.\n> - **[VERSIONED]** — codecs, protocols, platforms, rights. ⚠️ **Verify.**\n> - **[CONTESTED]** — genuine disagreement.\n>\n> **⚠️ GOTCHA** boxes mark where media pipelines silently corrupt, desync, or get rejected.\n>\n> **The three framings that organize everything below:**\n> 1. **⚠️ Media is a compatibility problem wearing a compression costume.** The hard part\n>    is almost never the codec — it's that **every device, browser, and platform accepts a\n>    different subset of a different container with different DRM**, and you must serve all\n>    of them (§3 → `media-fundamentals-containers-and-codecs`, §8 → `media-transcoding-streaming-and-drm`).\n> 2. **Every media decision is a triangle: quality, bitrate, and compute.** ⚠️ **You pick\n>    two.** A better codec moves the triangle; it doesn't abolish it — **and encoding\n>    complexity is the price AV1 and VVC charge for their bitrate savings** (§3.2 → `media-fundamentals-containers-and-codecs`).\n> 3. **⚠️ The rights layer is now as load-bearing as the technical one**, and it's moving\n>    faster. Loudness normalization, content ID, licensing metadata, and the AI training\n>    fight all determine what you may ship, not just what you can encode (§12 → `media-captions-podcasts-rights-and-qc`, §13 → `media-captions-podcasts-rights-and-qc`).\n\n---\n\n## §4. Audio Production\n\n**[DURABLE] The stack an audio engineer actually uses, and what a software engineer needs\nto know to integrate with it.**\n\n**DAWs**: Pro Tools (⚠️ **still the post-production and studio standard**), Logic, Ableton\nLive, Reaper (⚠️ **cheap, scriptable, and beloved by engineers**), Cubase, FL Studio,\nStudio One, Bitwig.\n\n**Plugin formats** — ⚠️ **the interop layer, and a real engineering concern**:\n**VST3** (cross-platform, Steinberg), **AU \u002F AUv3** (Apple), **AAX** (Pro Tools only),\n**LV2** (Linux\u002Fopen), and **CLAP** — ⚠️ **the newer open format (Bitwig\u002Fu-he) with better\nthreading, modulation and note expression, gaining real traction.** **JUCE** is the\ndominant framework for writing plugins across all of them.\n\n**⚠️ The real-time constraint governs everything**: the audio callback is a hard real-time\nthread. **No allocation, no locks, no file I\u002FO, no logging.** Buffer size sets latency\n(⚠️ **64 samples at 48 kHz ≈ 1.3 ms; 512 ≈ 10.7 ms**) and trades against CPU. **Lock-free\nring buffers** to talk to the UI thread.\n\n**MIDI**: 7-bit values, note on\u002Foff, CC, and the ⚠️ **note-off-vs-velocity-zero\nambiguity**. **MIDI 2.0** adds 32-bit resolution, per-note controllers, and\nbidirectional negotiation — ⚠️ **adoption is real but slow, and MIDI 1.0 remains the\nlingua franca.** **MPE** gives per-note pitch and pressure over MIDI 1.0 and is widely\nsupported.\n\n**Audio interfaces and drivers**: **ASIO** (Windows, low-latency, ⚠️ **and the reason\nWDM\u002FDirectSound is unusable for production**), **Core Audio** (macOS, excellent),\n**ALSA\u002FJACK\u002FPipeWire** (Linux — ⚠️ **PipeWire has largely resolved the historic\nJACK\u002FPulseAudio split**). **Network audio**: **Dante** (⚠️ **the professional standard**),\nAES67, AVB, NDI for video-plus-audio over IP.\n\n---\n\n## §5. Video Production\n\n**5.1 Acquisition and intermediates.** **Camera formats**: ProRes (⚠️ **the post-production\nstandard — cheap to decode, expensive in storage**), DNxHD\u002FHR, **RAW** (BRAW, R3D, ARRIRAW\n— ⚠️ **maximum flexibility, enormous files, and debayering cost**), and long-GOP camera\ncodecs (⚠️ **H.264\u002FHEVC from a camera is painful to edit — transcode to an intermediate\nfirst**). **Proxies** are standard practice: edit at low resolution, conform to full\nresolution at the end.\n\n**5.2 Colour.** **Log formats** (S-Log, C-Log, V-Log, Log C) preserve dynamic range for\ngrading. **LUTs** for transforms — ⚠️ **and a 1D LUT cannot do what a 3D LUT does; using\nthe wrong kind silently misgrades**. **ACES** is the standardized colour-managed pipeline.\n⚠️ **The recurring bug: mismatched colour space or transfer function between stages,\nproducing washed-out or oversaturated output that looks like a grading choice rather\nthan an error.**\n\n**5.3 ⚠️ Timecode — the most common source of \"off by a few frames\"**\n**SMPTE timecode**, and the killer detail: **drop-frame vs non-drop-frame.**\nAt 29.97 fps, ⚠️ **drop-frame timecode skips frame *numbers* (never actual frames) to keep\nclock time accurate — 2 numbers per minute, except every tenth minute.** Non-drop counts\nsequentially and drifts ~3.6 seconds per hour against wall clock.\n**⚠️ Mixing them, or assuming 30 fps arithmetic on 29.97 material, is the classic sync\nerror.** **Genlock and word clock** keep devices frame- and sample-aligned in a facility.\n\n**5.4 Editing and delivery.** NLEs: Premiere, Final Cut, DaVinci Resolve (⚠️ **which\nabsorbed colour grading and audio into one application and changed the market**), Avid\nMedia Composer (broadcast\u002Ffilm standard). **Interchange**: EDL, AAF, XML, **OTIO**\n(⚠️ **OpenTimelineIO — the open, scriptable interchange format, and the one worth knowing\nif you're building tooling**). **Deliverables**: IMF for studio distribution, DCP for\ncinema, and **broadcast spec sheets that will reject your file for reasons you did not\nanticipate** (§14 → `media-captions-podcasts-rights-and-qc`).\n\n---\n\n## §6. Loudness\n\n**[DURABLE] The single most practically useful section for anyone shipping audio, and the\none most often discovered too late.**\n\n**⚠️ Peak level and perceived loudness are different things.** A track can peak at 0 dBFS\nand sound quiet, or peak at −6 and sound crushed. **The loudness war** — decades of\never-heavier compression to sound louder than the competition — **was ended not by taste\nbut by normalization.**\n\n**The standards**: **ITU-R BS.1770** defines the measurement (K-weighted, gated).\n**EBU R128** (Europe) targets **−23 LUFS integrated** with a max true peak of −1 dBTP;\n**ATSC A\u002F85** (US broadcast) targets **−24 LKFS**. ⚠️ **LUFS and LKFS are the same unit\nwith different names.**\n\n**⚠️ The units to keep straight**: **Integrated LUFS** (whole-programme average),\n**short-term** (3 s), **momentary** (400 ms), **LRA** (loudness range),\nand **True Peak (dBTP)** — ⚠️ **which measures the inter-sample peaks that appear after\nD\u002FA conversion or lossy encoding, and is why a file that peaks at exactly 0 dBFS can clip\non playback.** Leave −1 dBTP of headroom minimum.\n\n> **⚠️ GOTCHA — this is why your master sounds quiet on streaming.** **Every major platform\n> normalizes playback loudness**, typically in the region of **−14 LUFS**, though **targets\n> differ by platform and change without announcement.** If you master to −8 LUFS, the\n> platform **turns it down** — and you've spent your dynamic range for nothing, arriving\n> quieter *and* more crushed than a competitor who mastered sensibly.\n>\n> ⚠️ **Do not master to a platform target as a hard number.** Master for the music, keep\n> true peak headroom, and check the integrated value. **Verify current targets per platform\n> at release time rather than trusting any figure — including the one in this document.**\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fmedia-engineering\u002Fskills\u002Fmedia-production-and-loudness",3,"https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey","https:\u002F\u002Fthe-vibey-project.github.io\u002Fvibey\u002F","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project","https:\u002F\u002Fvibewithadam.matthewsteinberger.com","freedom for software engineers","2026-11-15 05:47:42",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add the-vibey-project\u002Fvibey --skill media-production-and-loudness",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill media-production-and-loudness",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill media-production-and-loudness","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fmedia-engineering\u002Fskills\u002Fmedia-production-and-loudness\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7AT1FQJAE1FQYAMDTF490Y4","white-paper-writing","Use when writing white papers, technical reports, policy documents, thought leadership pieces, or any long-form authoritative document. Triggers on requests to write, structure, outline, or review white papers, technical reports, position papers, policy briefs, or evidence-driven arguments. Also use for B2B content marketing strategy, technical documentation requiring authority, academic-style reports, or any document that must educate while persuading. Use when someone asks \"how should I structure this\" for a long-form document.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fwhite-paper-writing\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7AT16BJRJJKK2MASXRZS76G","prose-technical-mechanics","Use when editing or writing prose at a technical\u002Fmechanical level: choosing between Anglo-Saxon and Latinate diction, placing information in topic vs stress positions, writing periodic vs cumulative sentences, handling sentence rhythm, punctuation as logic, transitions, paragraph structure, or phonesthetics. Use when someone wants to understand WHY prose works or doesn't, not just surface-level style advice. Triggers on word choice, sentence structure, emphasis, rhythm, diction, or any deep writing mechanics question.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-technical-mechanics\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7AT0W9HT0ZZ9Y287NW99MR3","prose-mechanics","Use when writing, editing, or analyzing prose style; when trying to avoid generic AI-sounding writing; when applying specific prose styles such as journalistic, academic, narrative, KJV biblical, Hemingway plain, Latinate\u002FJamesian, Orwellian, Augustan, Victorian, Early Modern (Bacon, Browne, Milton), or free indirect discourse; or when coaching someone on writing voice and mechanics. Triggers on any request to improve, analyze, or write in a specific prose style, to fix \"AI-sounding\" writing, to make prose more vivid or concrete, to vary sentence rhythm, or to understand how a particular writer achieves their effects.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-mechanics\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AT0KR635JX66X2X6F3E2CP","narrative-structure","Use when structuring stories, pitches, presentations, white papers, or any persuasive narrative; analyzing the hero's journey in fiction or non-fiction; applying StoryBrand for business communication; designing narrative arcs for thought leadership; or understanding Vogler, Snyder, Propp, or Campbell frameworks. Triggers on any narrative structure, storytelling, pitch structure, StoryBrand, hero's journey, three-act structure, Freytag, Save the Cat, narrative arc, or \"how should I structure this story\u002Fpitch\u002Fpresentation\" request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fnarrative-structure\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AT0AKGW09NKKZDYBT8VRDE","legal-brief-writing","Use when writing legal briefs, motions, or any court filing; when analyzing judicial cognition and persuasion; when applying elite brief-writing techniques from Roberts, Clement, Kagan, Garner; or when structuring legal arguments for maximum persuasion. Also use for autistic\u002Fneurodivergent advocates who need to understand how their natural communication style maps to elite legal advocacy. Triggers on any legal writing, brief drafting, motion preparation, or legal argument structuring request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Flegal-brief-writing\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7AT00VWPS4Q8B5VEMXX9NQT","journal-publishability-criteria","Use whenever a research paper, article or preprint is being written, revised, reviewed or published, and specifically before every publication of docs\u002Fpaper.md. Covers what legitimate journals actually gate on, in order of gating — the editor's desk screen (scope, novelty, package problems), what reviewers judge (methodological soundness, claims the evidence can carry, statistical and qualitative reporting), EQUATOR reporting guidelines, the ICMJE authorship criteria, COPE's view of text recycling, the near-universal generative-AI policy (no AI author, disclosure, author responsibility), TOP 2025 transparency standards, how to verify a journal is legitimate, submitting without an institution, and a pre-submission checklist. Triggers on requests to evaluate, review, prepare or submit a paper, to judge publishability, to write a declarations or data-availability section, to disclose AI use, or to check a journal.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fjournal-publishability-criteria\u002FSKILL.md",[],[]]