[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AS6NNEW7HE318VRWM8R7WN":3,"skill-same:01M7AS6NNEW7HE318VRWM8R7WN":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},"01M7AS6NNEW7HE318VRWM8R7WN","smart-tv-reference",null,"Use when reviewing a TV app for known anti-patterns, weighing contested questions (native vs web vs React Native, how far back to support, SSAI vs CSAI, whether CTV measurement is trustworthy, platform billing, turnkey OTT platform vs custom build, whether to build for the long tail at all), checking whether a platform or market claim is still current (snapshot verified August 2026), finding the primary and practitioner sources, or needing the numbers, pre-launch checklist, and 'it's broken on TV' triage. Companion to the other smart-tv-app-development skills.","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\u002Fsmart-tv-app-development\u002Fskills\u002Fsmart-tv-reference\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: smart-tv-reference\ndescription: \"Use when reviewing a TV app for known anti-patterns, weighing contested questions (native vs web vs React Native, how far back to support, SSAI vs CSAI, whether CTV measurement is trustworthy, platform billing, turnkey OTT platform vs custom build, whether to build for the long tail at all), checking whether a platform or market claim is still current (snapshot verified August 2026), finding the primary and practitioner sources, or needing the numbers, pre-launch checklist, and 'it's broken on TV' triage. Companion to the other smart-tv-app-development skills.\"\n---\n\n# Smart TV Apps: Anti-Patterns, Contested Questions, Currency, and Canon\n\n> **Part 4 of 4** of the *Smart TV App Development* reference (plugin `smart-tv-app-development`), covering §15–§20. Sibling skills: `smart-tv-platforms-and-10-foot-ui` (§0–§3), `smart-tv-playback-drm-and-performance` (§4–§7), `smart-tv-monetization-certification-and-operations` (§8–§14). 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 below for the currency snapshot and what goes stale first.\n\n> **How to read this.** Reference, not tutorial. Sections are independent. Three markers:\n> - **[DURABLE]** — human factors, hardware physics, or a lesson every TV platform has\n>   independently arrived at. Does not expire.\n> - **[PLATFORM]** — specific to Roku, Tizen, webOS, Android TV, Fire OS\u002FVega, or tvOS.\n>   Verify against that vendor's current docs, which change annually with the model year.\n> - **[CONTESTED]** — real disagreement about approach, usually because the trade-off\n>   depends on your budget and platform mix.\n>\n> **⚠️ GOTCHA** boxes mark the mistakes that fail certification, get discovered only on a\n> five-year-old TV in someone's living room, or quietly halve your completion rate.\n>\n> **The three framings that organize everything below:**\n> 1. **You are writing for a 2015 phone bolted to a 2025 display.** TV silicon is\n>    cost-optimized to the bone. Assume ~1–2 GB RAM, a weak CPU, and a GPU that exists\n>    mostly to composite video. Your desktop intuitions about performance are wrong by an\n>    order of magnitude.\n> 2. **The remote has a D-pad, and that is the entire input model.** No pointer, no touch,\n>    no hover, no keyboard. Every interaction is up\u002Fdown\u002Fleft\u002Fright\u002FOK\u002Fback. Focus\n>    management is not a detail — it *is* the UI architecture.\n> 3. **The platform owner is your distributor, your competitor, and your ad network.**\n>    Certification is a gate they control, discovery placement is inventory they sell, and\n>    on most platforms they take a cut of your revenue. This is a commercial relationship\n>    wearing an SDK.\n\n---\n\n## §15. Anti-Patterns\n\n| Anti-pattern | Why | Instead |\n|---|---|---|\n| Porting a mobile or web UI directly | Wrong density, wrong input model, unreadable at 10 ft | Design for TV from scratch (§2 → `smart-tv-platforms-and-10-foot-ui`) |\n| Any UI element that requires hover | No pointer exists | Everything visible in default state |\n| Losing focus (zero focused elements) | Presents as a **completely dead remote** | Always move focus explicitly on DOM\u002Fnode changes (§3.1 → `smart-tv-platforms-and-10-foot-ui`) |\n| Subtle focus indicators | Invisible at 10 feet | Scale + border + brightness, at least two channels |\n| Not restoring focus on back-navigation | User loses their place every time | Save and restore focus per screen |\n| Content outside the ~90% safe area | Physically cut off by overscan | 5% margin all sides (§2.2 → `smart-tv-platforms-and-10-foot-ui`) |\n| Body text under ~18–24 px at 1080p | Unreadable | ≥24 px body |\n| Pure white on large areas | Painful on a bright panel in a dark room | ~#F0F0F0 or lower |\n| Rendering an entire long list | Memory death on TV silicon | Virtualize and recycle (§6.2 → `smart-tv-playback-drm-and-performance`) |\n| Full-size images scaled down in the client | Wastes bandwidth, decode memory, and CPU | Server-side exact-size thumbnails |\n| Assuming an evergreen browser on Tizen\u002FwebOS | A 2024 TV is on Chromium 108; a 2018 TV on 56 | Feature-detect, transpile, test the oldest target (§1.3 → `smart-tv-platforms-and-10-foot-ui`) |\n| Version-sniffing the Chromium build | Brittle and wrong | Feature detection |\n| Requiring on-screen keyboard sign-in | Miserable; users abandon | Device-code pairing (§3.4 → `smart-tv-platforms-and-10-foot-ui`) |\n| Saving playback position only on exit | You won't get the callback | Save continuously |\n| No deep-link support | **Invisible to platform search, voice, and recommendation rows** | Support play and detail deep links (§7.2 → `smart-tv-playback-drm-and-performance`) |\n| Sequential cold-start network cascade | Blows the time-to-first-frame budget | Parallelize auth\u002Fmanifest\u002Flicense |\n| Single CENC encryption scheme | `cbcs` vs `cenc` — silently black-screens older devices | Package both, select by capability (§5.1 → `smart-tv-playback-drm-and-performance`) |\n| Treating DRM config as set-and-forget | Vendor endpoints and revocation change | Calendar-driven re-checks |\n| Client-side entitlement decisions | Trivially bypassed | Enforce server-side (§8.2 → `smart-tv-monetization-certification-and-operations`) |\n| Reading the certification checklist before submission | Half of it is architectural | Read it before you design (§10.1 → `smart-tv-monetization-certification-and-operations`) |\n| Testing only on flagship hardware | Most users are on the cheap stick | Test on the worst device you support |\n| Aggregate-only analytics | Model-specific regressions are invisible | Segment by device model and OS version (§12 → `smart-tv-monetization-certification-and-operations`) |\n| Ignoring the platform's caption style settings | Accessibility failure and a cert risk | Honour system settings (§14.1 → `smart-tv-monetization-certification-and-operations`) |\n| Mismatched loudness between content and ads | Top-tier user complaint | −23 LUFS \u002F −24 LKFS (§4.2 → `smart-tv-playback-drm-and-performance`) |\n| Assuming one Amazon platform | Fire OS and Vega are both live, and APKs don't run on Vega | Plan for both (§1.2 → `smart-tv-platforms-and-10-foot-ui`) |\n\n---\n\n## §16. Contested Questions\n\n**16.1 Native vs. web vs. React Native.** §13.1 → `smart-tv-monetization-certification-and-operations`. The calculus genuinely changed in 2026:\nReact Native became strategically relevant because Amazon made it a **first-class citizen\non Vega**, with core RN and common dependencies precompiled into the OS. If your mix is\nVega + Android TV + tvOS, RN is now a defensible primary choice in a way it wasn't before.\nIf your mix is Tizen + webOS + the long tail, a web app still wins.\n\n**16.2 How far back to support.** Every additional model year you support drags your web\nbaseline backwards (§1.3 → `smart-tv-platforms-and-10-foot-ui`) and adds DRM and codec permutations. *For long support*: those\nTVs are in living rooms for a decade and their owners are real users. *Against*: the\nengineering tax is superlinear. **Decide with usage data from your own analytics, not with\nmarket-share reports.**\n\n**16.3 SSAI vs. CSAI.** §9.2 → `smart-tv-monetization-certification-and-operations`. SSAI wins on user experience and blocker resistance; CSAI\ngives the client richer signal and simpler debugging. SSAI is the default and the argument\nis mostly settled, but the measurement complexity it introduces is real.\n\n**16.4 Is CTV measurement trustworthy?** §9.3 → `smart-tv-monetization-certification-and-operations`.\n\n**16.5 Platform billing.** *For*: frictionless signup, the platform's stored payment\nmethod, and higher conversion. *Against*: revenue share, and the platform owns your\ncustomer relationship and churn flow. There's no universal answer; there is a very\ndifferent answer for a $5\u002Fmonth niche service than for a major studio.\n\n**16.6 Turnkey OTT platform vs. custom build.** *For turnkey*: fast, covers many\nplatforms, handles certification and updates. *Against*: you don't control the UX, you're\none of thousands of similar apps, and differentiation is limited to branding. Reasonable\nif content is your product and the app is a delivery mechanism.\n\n**16.7 Whether to build for the long tail at all.** VIDAA, whaleOS, webOS Hub, Xumo,\nTitan OS, SmartCast — each is a certification cycle and a QA burden for a small slice.\nRegionally, though, some of them are *not* small: ignoring VIDAA in markets where Hisense\nis dominant is a real revenue decision.\n\n---\n\n## §17. Currency Snapshot — verified August 2026\n\n| Thing | Status as of Aug 2026 | Decay risk |\n|---|---|---|\n| **US platform share** | Parks Associates (Apr 2026, most-used device for online video, US broadband households): **Roku OS 28%, Samsung Tizen 23%**; Fire TV, webOS, SmartCast mid-tier; tvOS, consoles, Android TV smaller. Other measures put Roku at ~38% of activated screens. **Global shipments rank differently** — Tizen and Android TV lead worldwide | Medium |\n| **Scale anchors** | Android TV\u002FGoogle TV **~300M monthly active devices**; Roku **~100M streaming households**; webOS ~12% overall but **~52% of premium OLED**; smart TV ownership heading past **1.1B households** | Medium |\n| **Amazon Vega OS** | ⚠️ **Linux-based, not Android — APKs do not run.** React Native 0.72 or Vega WebView; **VPKG** packaging. Shipped on Fire TV Stick 4K Select (2025) and Fire TV Stick HD (Apr 2026); Amazon states **all future Fire TV Sticks run Vega**. Existing Fire OS devices **not upgraded**, supported through at least 2030. **No sideloading.** Selected apps cloud-streamed with ~9 months free hosting during transition | **High** |\n| **Fox–Roku** | ⚠️ **April 2026: Fox announced an agreement to acquire Roku for ~$22B** (cash and stock). Expected to affect OS licensing and ad-supply terms | **High** |\n| **Samsung Tizen web engine** | **2026: Tizen 10.0 \u002F Chromium M130** · 2025: 9.0\u002FM120 · 2024: 8.0\u002F**M108** · 2023: 7.0\u002FM94 · 2022: 6.5\u002FM85 · 2021: 6.0\u002FM76 · 2020: 5.5\u002FM69 · 2019: 5.0\u002FM63 · 2018: 4.0\u002F**M56** · 2017: 3.0\u002FM47 · 2016 and earlier: WebKit. **Never updated after ship** | Low (annual) |\n| **Samsung native toolchain** | ⚠️ **GCC 9.2.0 through the 2025 model year; GCC 14.2.0 from 2026.** Native binaries must be rebuilt for 2026 sets | Low |\n| **LG webOS** | **webOS 26** introduced Jan 2026 with AI assistant integrations (**Microsoft Copilot** and **Google Gemini**). Enact (React-based) remains the LG-blessed framework | Medium |\n| **Roku certification** | ⚠️ **Spring 2026 update: Instant Resume required by 1 October 2026** for qualifying US Streaming Store apps. **`roAppMemoryMonitor`** usage required to pass certification testing. Static Analysis must pass to publish; App Behavior Analysis for free\u002Fad-based apps. **Direct Publisher has been wound down** — no-code publishing now goes through third-party OTT platforms | Medium |\n| **Roku OS** | 15.0 (Oct 2025). Linux-based; BrightScript + SceneGraph; ARM Cortex-A53\u002FA55\u002FA35 and some MIPS | Medium |\n| **CTV ad specs** | **VAST 4.x required** for full CTV format and measurement support. **SSAI is the default.** Loudness **−23 LUFS (EBU R128)** streaming\u002FSSAI, **−24 LKFS (ATSC A\u002F85)** US broadcast. Creative typically ≤200 MB (≤150 MB preferred). **Universal Ad ID** and **OM SDK** are the IAB Tech Lab interop answers | Medium |\n| **CTV market** | US digital video ad spend projected **>$80B in 2026**, passing **60% of total TV\u002Fvideo spend** for the first time. Streaming hit **~48.6% of US TV watch-time (Nielsen, May 2026)** | Annual |\n| **Privacy\u002FACR regulation** | **US Cyber Trust Mark** programme and **Kentucky HB 692** (ACR data handling) named as shaping 2026 privacy-by-design roadmaps. **Caption discovery** is a 2026 US accessibility compliance milestone | **High** |\n\n**Goes stale fastest:** the Vega transition; the Fox–Roku deal; Roku certification\nrequirements; ACR\u002Fprivacy legislation; ad-market figures. **Essentially never stale:**\n§2 → `smart-tv-platforms-and-10-foot-ui` (10-foot UI), §3 → `smart-tv-platforms-and-10-foot-ui` (focus and input), §4.3 → `smart-tv-playback-drm-and-performance` (playback metrics), §5.1 → `smart-tv-playback-drm-and-performance`'s `cenc`\u002F`cbcs` trap,\n§6.2 → `smart-tv-playback-drm-and-performance` (performance techniques), §15 (anti-patterns).\n\n---\n\n## §18. The Canon\n\n### 18.1 Primary sources — and here, they're nearly all you have\n\n**[DURABLE] Unlike web or mobile, TV development has almost no independent literature.\nThe vendor docs are the field.** Read them directly and read them annually.\n\n- **Roku**: `developer.roku.com` — the SceneGraph course, **certification docs**, the\n  BrightScript reference, and the **`rokudev` GitHub org**, especially\n  **`scenegraph-master-sample`** (a certification-compliant reference channel you can use\n  as a template) and `samples`. The **Roku developer blog's Certification category** is\n  where requirement changes are announced — subscribe to it.\n- **Samsung**: `developer.samsung.com\u002Fsmarttv` — and specifically the **Web Engine\n  Specifications** page, which carries the model-year\u002FChromium\u002Ffeature-support matrix in\n  §1.3 → `smart-tv-platforms-and-10-foot-ui` and §17. This single page will save you more time than anything else in this list.\n  Also **General Specifications** for HLS\u002FDASH tag support and the toolchain notes.\n- **LG**: `webostv.developer.lge.com` — webOS TV docs, the **Enact** framework, and the\n  Simulator\u002FCLI tooling.\n- **Google**: `developer.android.com\u002Ftv` — Leanback, **Compose for TV**, **Media3\u002F\n  ExoPlayer**, Watch Next and channel APIs, and the Android TV quality guidelines.\n- **Amazon**: `developer.amazon.com` — Fire TV docs and, critically, the **Vega Developer\n  Tools** getting-started guides, VS Code extension, and CLI.\n- **Apple**: the **tvOS Human Interface Guidelines** (the best-written TV design doc from\n  any vendor, and worth reading even if you never ship tvOS) plus TVMLKit and SwiftUI docs.\n- **IAB Tech Lab**: the **CTV Programmatic Guide**, VAST 4.x, **Universal Ad ID**, and\n  **OM SDK** specs — the standards layer under §9 → `smart-tv-monetization-certification-and-operations`.\n- **Standards bodies**: HbbTV (Europe), ATSC 3.0 (US broadcast), DASH-IF, and CTA\n  specifications, depending on your market.\n\n### 18.2 Practitioner sources\n\nVendor-neutral analysis lives with the OTT integrators and the measurement firms rather\nthan in books: **Conviva** (State of Streaming — the QoE benchmark data),\n**Parks Associates** and **Nielsen** (share and viewing), **Bitmovin's annual Video\nDeveloper Report**, **Accedo**, **Float Left**, **Fora Soft**, and **Lightcast** (platform\nnotes and build-cost writeups — commercially motivated, but the technical detail is real\nand hard to find elsewhere). **AFTVnews** is the best source on Fire TV\u002FVega specifics.\n**Dolby OptiView**, **Bitmovin**, **JW Player**, **THEO**, and **Shaka Player** docs are\nthe practical references for the player and DRM layers.\n\n**⚠️ Almost every source in this domain is a vendor or an integrator selling something.**\nCross-read, and treat platform-share numbers especially carefully (§1.1 → `smart-tv-platforms-and-10-foot-ui`).\n\n---\n\n## §19. Quick Reference\n\n### 19.1 Numbers\n- Design canvas **1920×1080**; **safe area 90%** (5% margin each side).\n- Body text **≥24 px**; nothing below ~18 px.\n- Focusable targets **≥60–80 px**.\n- Frame budget **16.6 ms**; time-to-first-video-frame **\u003C2 s**; cold start **\u003C3 s**.\n- Rebuffer ratio **\u003C0.5%**; playback failure **\u003C1%**.\n- Loudness **−23 LUFS** (streaming\u002FSSAI), **−24 LKFS** (US broadcast).\n- Ad creative **≤200 MB** (≤150 MB preferred); **VAST 4.x**.\n- Samsung 2024 TVs run **Chromium 108**; 2018 TVs run **Chromium 56**.\n- Roku **Instant Resume required by 1 Oct 2026** (qualifying US apps).\n\n### 19.2 Pre-launch checklist\n- [ ] Focus never lost; Back always predictable; initial focus set on every screen\n- [ ] Everything inside the 90% safe area; readable at 10 feet\n- [ ] Tested on the **cheapest** device and the **oldest model year** you support\n- [ ] Long lists virtualized; images server-sized; memory monitored\n- [ ] Cold start and time-to-first-frame measured on the slowest device\n- [ ] Deep links work: cold start, warm start, unentitled user, missing content\n- [ ] Playback position saved continuously; resume verified after a long suspend\n- [ ] Both `cenc` and `cbcs` packaging verified on old and new devices\n- [ ] Captions render and honour system style settings\n- [ ] Sign-in via device-code pairing, not an on-screen keyboard\n- [ ] Platform billing implemented per policy; entitlement enforced server-side\n- [ ] Analytics segmented by device model and OS version\n- [ ] Certification checklist walked end-to-end **before** submission\n- [ ] Catalogue feed submitted for platform search\u002Fvoice\u002Frecommendation rows\n\n### 19.3 \"It's broken on TV\" triage\n| Symptom | First look |\n|---|---|\n| Remote appears dead | Focus lost, or focus trapped in a container (§3.1 → `smart-tv-platforms-and-10-foot-ui`) |\n| Blank\u002Fwhite screen on some models only | Frozen-Chromium feature gap — check the engine version (§1.3 → `smart-tv-platforms-and-10-foot-ui`) |\n| Black screen on playback, older devices | `cenc`\u002F`cbcs` mismatch, or codec unsupported on that tier (§5.1 → `smart-tv-playback-drm-and-performance`) |\n| App killed during use | Memory budget exceeded — profile image cache and list virtualization |\n| Slow to start playing | Sequential cold-start network cascade (§4.3 → `smart-tv-playback-drm-and-performance`) |\n| Fails certification on launch time | Same, plus JS bundle parse cost |\n| Works via deep link, broken from search | Catalogue feed mapping or unentitled-user path (§7.2 → `smart-tv-playback-drm-and-performance`–7.3) |\n| Ads too loud | Loudness normalization (§4.2 → `smart-tv-playback-drm-and-performance`) |\n| Fine on the OLED, broken on the stick | You tested on the wrong device (§11 → `smart-tv-monetization-certification-and-operations`) |\n\n---\n\n## §20. Sources and Method\n\n**Method.** Narrative (not systematic) review. The durable material — §2 → `smart-tv-platforms-and-10-foot-ui` (10-foot UI),\n§3 → `smart-tv-platforms-and-10-foot-ui` (focus and input), §4.3 → `smart-tv-playback-drm-and-performance` (playback metrics), §5.1 → `smart-tv-playback-drm-and-performance` (DRM structure), §6 → `smart-tv-playback-drm-and-performance` (performance),\n§8.2 → `smart-tv-monetization-certification-and-operations`, §12 → `smart-tv-monetization-certification-and-operations`, §15 — is synthesized from vendor design guidelines, long-standing platform\ndocumentation, and consistent practitioner reporting. Every **time-sensitive** claim\n(platform shares, OS versions, engine matrices, certification requirements, ad specs,\nregulation) was verified against a primary or near-primary source in **August 2026** and\nis flagged in §17 with a decay-risk rating. Where the trade-off genuinely depends on\nplatform mix or budget, §16 presents both cases.\n\n**Search log** (August 2026): smart TV OS market share and platform landscape · Amazon\nVega OS and the Fire OS transition · Roku SceneGraph\u002FBrightScript and certification\nrequirements · Samsung Tizen and LG webOS SDK and Chromium version constraints · CTV\nadvertising specs, SSAI, ACR, and measurement.\n\n**Primary and near-primary sources consulted (selected):**\n- **Samsung Developer** — **Web Engine Specifications** (the model-year\u002FChromium table),\n  General Specifications (HLS\u002FDASH support, GCC toolchain change), TV Extension archive\n- **Roku Developer** — certification testing docs, SceneGraph course, the Roku developer\n  blog's Certification category (Spring 2026 update), the `rokudev` GitHub org\n- **Amazon Developer** — \"Announcing Vega OS\" \u002F Get started with Vega Developer Tools;\n  **Software Mansion**'s account of building React Native for Vega; **AFTVnews**,\n  **Ars Technica**-sourced reporting, **PCWorld**, and **Dolby OptiView** on the transition\n- **Parks Associates** (April 2026 Streaming Video Tracker press release, via PRNewswire\n  and TV Tech) — US platform shares; **Mordor Intelligence** on activated screens, the\n  Fox–Roku agreement, webOS 26, and the Cyber Trust Mark \u002F Kentucky HB 692 regulatory notes\n- **IAB Tech Lab** — CTV Programmatic Guide (Universal Ad ID, OM SDK); **Equativ** —\n  2026 CTV ad formats and specs, including loudness targets\n- **Nielsen** figures via **M+C Saatchi Performance**; **ScreenCloud** and **Play Signage**\n  on real-world Chromium version limits; **Float Left**, **Fora Soft**, **Lightcast**,\n  and **Accedo** on platform development practice\n\n**Confidence statement.** **High confidence** in §2–§8 → `smart-tv-platforms-and-10-foot-ui`, `smart-tv-monetization-certification-and-operations`, §10–§12 → `smart-tv-monetization-certification-and-operations`, §15, and §19 — these rest\non vendor documentation and consistently-reported practitioner experience. **High\nconfidence** in the Samsung engine matrix (§1.3 → `smart-tv-platforms-and-10-foot-ui`, §17), which comes directly from Samsung's\nown specification page, and in the Roku certification requirements, which come from Roku's\nown blog. **Moderate confidence** in §1.1 → `smart-tv-platforms-and-10-foot-ui`'s market-share figures: the sources genuinely\ndisagree because they measure different things (usage vs. activated screens vs. global\nshipments), the numbers come from commercial research firms with differing methodologies,\nand I have deliberately presented three framings rather than one number. **Moderate\nconfidence** in §9 → `smart-tv-monetization-certification-and-operations`'s advertising specifications — these come from ad-tech vendors and the\nIAB, are directionally consistent across sources, but vary by publisher in practice, and\nthe guidance throughout is to confirm specs with the specific publisher or platform rather\nthan treating any single figure as universal. The Fox–Roku acquisition (§1.2 → `smart-tv-platforms-and-10-foot-ui`, §17) was\n**announced**, and announced deals do not always close.\n","# Smart TV Apps: Anti-Patterns, Contested Questions, Currency, and Canon\n\n> **Part 4 of 4** of the *Smart TV App Development* reference (plugin `smart-tv-app-development`), covering §15–§20. Sibling skills: `smart-tv-platforms-and-10-foot-ui` (§0–§3), `smart-tv-playback-drm-and-performance` (§4–§7), `smart-tv-monetization-certification-and-operations` (§8–§14). 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 below for the currency snapshot and what goes stale first.\n\n> **How to read this.** Reference, not tutorial. Sections are independent. Three markers:\n> - **[DURABLE]** — human factors, hardware physics, or a lesson every TV platform has\n>   independently arrived at. Does not expire.\n> - **[PLATFORM]** — specific to Roku, Tizen, webOS, Android TV, Fire OS\u002FVega, or tvOS.\n>   Verify against that vendor's current docs, which change annually with the model year.\n> - **[CONTESTED]** — real disagreement about approach, usually because the trade-off\n>   depends on your budget and platform mix.\n>\n> **⚠️ GOTCHA** boxes mark the mistakes that fail certification, get discovered only on a\n> five-year-old TV in someone's living room, or quietly halve your completion rate.\n>\n> **The three framings that organize everything below:**\n> 1. **You are writing for a 2015 phone bolted to a 2025 display.** TV silicon is\n>    cost-optimized to the bone. Assume ~1–2 GB RAM, a weak CPU, and a GPU that exists\n>    mostly to composite video. Your desktop intuitions about performance are wrong by an\n>    order of magnitude.\n> 2. **The remote has a D-pad, and that is the entire input model.** No pointer, no touch,\n>    no hover, no keyboard. Every interaction is up\u002Fdown\u002Fleft\u002Fright\u002FOK\u002Fback. Focus\n>    management is not a detail — it *is* the UI architecture.\n> 3. **The platform owner is your distributor, your competitor, and your ad network.**\n>    Certification is a gate they control, discovery placement is inventory they sell, and\n>    on most platforms they take a cut of your revenue. This is a commercial relationship\n>    wearing an SDK.\n\n---\n\n## §15. Anti-Patterns\n\n| Anti-pattern | Why | Instead |\n|---|---|---|\n| Porting a mobile or web UI directly | Wrong density, wrong input model, unreadable at 10 ft | Design for TV from scratch (§2 → `smart-tv-platforms-and-10-foot-ui`) |\n| Any UI element that requires hover | No pointer exists | Everything visible in default state |\n| Losing focus (zero focused elements) | Presents as a **completely dead remote** | Always move focus explicitly on DOM\u002Fnode changes (§3.1 → `smart-tv-platforms-and-10-foot-ui`) |\n| Subtle focus indicators | Invisible at 10 feet | Scale + border + brightness, at least two channels |\n| Not restoring focus on back-navigation | User loses their place every time | Save and restore focus per screen |\n| Content outside the ~90% safe area | Physically cut off by overscan | 5% margin all sides (§2.2 → `smart-tv-platforms-and-10-foot-ui`) |\n| Body text under ~18–24 px at 1080p | Unreadable | ≥24 px body |\n| Pure white on large areas | Painful on a bright panel in a dark room | ~#F0F0F0 or lower |\n| Rendering an entire long list | Memory death on TV silicon | Virtualize and recycle (§6.2 → `smart-tv-playback-drm-and-performance`) |\n| Full-size images scaled down in the client | Wastes bandwidth, decode memory, and CPU | Server-side exact-size thumbnails |\n| Assuming an evergreen browser on Tizen\u002FwebOS | A 2024 TV is on Chromium 108; a 2018 TV on 56 | Feature-detect, transpile, test the oldest target (§1.3 → `smart-tv-platforms-and-10-foot-ui`) |\n| Version-sniffing the Chromium build | Brittle and wrong | Feature detection |\n| Requiring on-screen keyboard sign-in | Miserable; users abandon | Device-code pairing (§3.4 → `smart-tv-platforms-and-10-foot-ui`) |\n| Saving playback position only on exit | You won't get the callback | Save continuously |\n| No deep-link support | **Invisible to platform search, voice, and recommendation rows** | Support play and detail deep links (§7.2 → `smart-tv-playback-drm-and-performance`) |\n| Sequential cold-start network cascade | Blows the time-to-first-frame budget | Parallelize auth\u002Fmanifest\u002Flicense |\n| Single CENC encryption scheme | `cbcs` vs `cenc` — silently black-screens older devices | Package both, select by capability (§5.1 → `smart-tv-playback-drm-and-performance`) |\n| Treating DRM config as set-and-forget | Vendor endpoints and revocation change | Calendar-driven re-checks |\n| Client-side entitlement decisions | Trivially bypassed | Enforce server-side (§8.2 → `smart-tv-monetization-certification-and-operations`) |\n| Reading the certification checklist before submission | Half of it is architectural | Read it before you design (§10.1 → `smart-tv-monetization-certification-and-operations`) |\n| Testing only on flagship hardware | Most users are on the cheap stick | Test on the worst device you support |\n| Aggregate-only analytics | Model-specific regressions are invisible | Segment by device model and OS version (§12 → `smart-tv-monetization-certification-and-operations`) |\n| Ignoring the platform's caption style settings | Accessibility failure and a cert risk | Honour system settings (§14.1 → `smart-tv-monetization-certification-and-operations`) |\n| Mismatched loudness between content and ads | Top-tier user complaint | −23 LUFS \u002F −24 LKFS (§4.2 → `smart-tv-playback-drm-and-performance`) |\n| Assuming one Amazon platform | Fire OS and Vega are both live, and APKs don't run on Vega | Plan for both (§1.2 → `smart-tv-platforms-and-10-foot-ui`) |\n\n---\n\n## §16. Contested Questions\n\n**16.1 Native vs. web vs. React Native.** §13.1 → `smart-tv-monetization-certification-and-operations`. The calculus genuinely changed in 2026:\nReact Native became strategically relevant because Amazon made it a **first-class citizen\non Vega**, with core RN and common dependencies precompiled into the OS. If your mix is\nVega + Android TV + tvOS, RN is now a defensible primary choice in a way it wasn't before.\nIf your mix is Tizen + webOS + the long tail, a web app still wins.\n\n**16.2 How far back to support.** Every additional model year you support drags your web\nbaseline backwards (§1.3 → `smart-tv-platforms-and-10-foot-ui`) and adds DRM and codec permutations. *For long support*: those\nTVs are in living rooms for a decade and their owners are real users. *Against*: the\nengineering tax is superlinear. **Decide with usage data from your own analytics, not with\nmarket-share reports.**\n\n**16.3 SSAI vs. CSAI.** §9.2 → `smart-tv-monetization-certification-and-operations`. SSAI wins on user experience and blocker resistance; CSAI\ngives the client richer signal and simpler debugging. SSAI is the default and the argument\nis mostly settled, but the measurement complexity it introduces is real.\n\n**16.4 Is CTV measurement trustworthy?** §9.3 → `smart-tv-monetization-certification-and-operations`.\n\n**16.5 Platform billing.** *For*: frictionless signup, the platform's stored payment\nmethod, and higher conversion. *Against*: revenue share, and the platform owns your\ncustomer relationship and churn flow. There's no universal answer; there is a very\ndifferent answer for a $5\u002Fmonth niche service than for a major studio.\n\n**16.6 Turnkey OTT platform vs. custom build.** *For turnkey*: fast, covers many\nplatforms, handles certification and updates. *Against*: you don't control the UX, you're\none of thousands of similar apps, and differentiation is limited to branding. Reasonable\nif content is your product and the app is a delivery mechanism.\n\n**16.7 Whether to build for the long tail at all.** VIDAA, whaleOS, webOS Hub, Xumo,\nTitan OS, SmartCast — each is a certification cycle and a QA burden for a small slice.\nRegionally, though, some of them are *not* small: ignoring VIDAA in markets where Hisense\nis dominant is a real revenue decision.\n\n---\n\n## §17. Currency Snapshot — verified August 2026\n\n| Thing | Status as of Aug 2026 | Decay risk |\n|---|---|---|\n| **US platform share** | Parks Associates (Apr 2026, most-used device for online video, US broadband households): **Roku OS 28%, Samsung Tizen 23%**; Fire TV, webOS, SmartCast mid-tier; tvOS, consoles, Android TV smaller. Other measures put Roku at ~38% of activated screens. **Global shipments rank differently** — Tizen and Android TV lead worldwide | Medium |\n| **Scale anchors** | Android TV\u002FGoogle TV **~300M monthly active devices**; Roku **~100M streaming households**; webOS ~12% overall but **~52% of premium OLED**; smart TV ownership heading past **1.1B households** | Medium |\n| **Amazon Vega OS** | ⚠️ **Linux-based, not Android — APKs do not run.** React Native 0.72 or Vega WebView; **VPKG** packaging. Shipped on Fire TV Stick 4K Select (2025) and Fire TV Stick HD (Apr 2026); Amazon states **all future Fire TV Sticks run Vega**. Existing Fire OS devices **not upgraded**, supported through at least 2030. **No sideloading.** Selected apps cloud-streamed with ~9 months free hosting during transition | **High** |\n| **Fox–Roku** | ⚠️ **April 2026: Fox announced an agreement to acquire Roku for ~$22B** (cash and stock). Expected to affect OS licensing and ad-supply terms | **High** |\n| **Samsung Tizen web engine** | **2026: Tizen 10.0 \u002F Chromium M130** · 2025: 9.0\u002FM120 · 2024: 8.0\u002F**M108** · 2023: 7.0\u002FM94 · 2022: 6.5\u002FM85 · 2021: 6.0\u002FM76 · 2020: 5.5\u002FM69 · 2019: 5.0\u002FM63 · 2018: 4.0\u002F**M56** · 2017: 3.0\u002FM47 · 2016 and earlier: WebKit. **Never updated after ship** | Low (annual) |\n| **Samsung native toolchain** | ⚠️ **GCC 9.2.0 through the 2025 model year; GCC 14.2.0 from 2026.** Native binaries must be rebuilt for 2026 sets | Low |\n| **LG webOS** | **webOS 26** introduced Jan 2026 with AI assistant integrations (**Microsoft Copilot** and **Google Gemini**). Enact (React-based) remains the LG-blessed framework | Medium |\n| **Roku certification** | ⚠️ **Spring 2026 update: Instant Resume required by 1 October 2026** for qualifying US Streaming Store apps. **`roAppMemoryMonitor`** usage required to pass certification testing. Static Analysis must pass to publish; App Behavior Analysis for free\u002Fad-based apps. **Direct Publisher has been wound down** — no-code publishing now goes through third-party OTT platforms | Medium |\n| **Roku OS** | 15.0 (Oct 2025). Linux-based; BrightScript + SceneGraph; ARM Cortex-A53\u002FA55\u002FA35 and some MIPS | Medium |\n| **CTV ad specs** | **VAST 4.x required** for full CTV format and measurement support. **SSAI is the default.** Loudness **−23 LUFS (EBU R128)** streaming\u002FSSAI, **−24 LKFS (ATSC A\u002F85)** US broadcast. Creative typically ≤200 MB (≤150 MB preferred). **Universal Ad ID** and **OM SDK** are the IAB Tech Lab interop answers | Medium |\n| **CTV market** | US digital video ad spend projected **>$80B in 2026**, passing **60% of total TV\u002Fvideo spend** for the first time. Streaming hit **~48.6% of US TV watch-time (Nielsen, May 2026)** | Annual |\n| **Privacy\u002FACR regulation** | **US Cyber Trust Mark** programme and **Kentucky HB 692** (ACR data handling) named as shaping 2026 privacy-by-design roadmaps. **Caption discovery** is a 2026 US accessibility compliance milestone | **High** |\n\n**Goes stale fastest:** the Vega transition; the Fox–Roku deal; Roku certification\nrequirements; ACR\u002Fprivacy legislation; ad-market figures. **Essentially never stale:**\n§2 → `smart-tv-platforms-and-10-foot-ui` (10-foot UI), §3 → `smart-tv-platforms-and-10-foot-ui` (focus and input), §4.3 → `smart-tv-playback-drm-and-performance` (playback metrics), §5.1 → `smart-tv-playback-drm-and-performance`'s `cenc`\u002F`cbcs` trap,\n§6.2 → `smart-tv-playback-drm-and-performance` (performance techniques), §15 (anti-patterns).\n\n---\n\n## §18. The Canon\n\n### 18.1 Primary sources — and here, they're nearly all you have\n\n**[DURABLE] Unlike web or mobile, TV development has almost no independent literature.\nThe vendor docs are the field.** Read them directly and read them annually.\n\n- **Roku**: `developer.roku.com` — the SceneGraph course, **certification docs**, the\n  BrightScript reference, and the **`rokudev` GitHub org**, especially\n  **`scenegraph-master-sample`** (a certification-compliant reference channel you can use\n  as a template) and `samples`. The **Roku developer blog's Certification category** is\n  where requirement changes are announced — subscribe to it.\n- **Samsung**: `developer.samsung.com\u002Fsmarttv` — and specifically the **Web Engine\n  Specifications** page, which carries the model-year\u002FChromium\u002Ffeature-support matrix in\n  §1.3 → `smart-tv-platforms-and-10-foot-ui` and §17. This single page will save you more time than anything else in this list.\n  Also **General Specifications** for HLS\u002FDASH tag support and the toolchain notes.\n- **LG**: `webostv.developer.lge.com` — webOS TV docs, the **Enact** framework, and the\n  Simulator\u002FCLI tooling.\n- **Google**: `developer.android.com\u002Ftv` — Leanback, **Compose for TV**, **Media3\u002F\n  ExoPlayer**, Watch Next and channel APIs, and the Android TV quality guidelines.\n- **Amazon**: `developer.amazon.com` — Fire TV docs and, critically, the **Vega Developer\n  Tools** getting-started guides, VS Code extension, and CLI.\n- **Apple**: the **tvOS Human Interface Guidelines** (the best-written TV design doc from\n  any vendor, and worth reading even if you never ship tvOS) plus TVMLKit and SwiftUI docs.\n- **IAB Tech Lab**: the **CTV Programmatic Guide**, VAST 4.x, **Universal Ad ID**, and\n  **OM SDK** specs — the standards layer under §9 → `smart-tv-monetization-certification-and-operations`.\n- **Standards bodies**: HbbTV (Europe), ATSC 3.0 (US broadcast), DASH-IF, and CTA\n  specifications, depending on your market.\n\n### 18.2 Practitioner sources\n\nVendor-neutral analysis lives with the OTT integrators and the measurement firms rather\nthan in books: **Conviva** (State of Streaming — the QoE benchmark data),\n**Parks Associates** and **Nielsen** (share and viewing), **Bitmovin's annual Video\nDeveloper Report**, **Accedo**, **Float Left**, **Fora Soft**, and **Lightcast** (platform\nnotes and build-cost writeups — commercially motivated, but the technical detail is real\nand hard to find elsewhere). **AFTVnews** is the best source on Fire TV\u002FVega specifics.\n**Dolby OptiView**, **Bitmovin**, **JW Player**, **THEO**, and **Shaka Player** docs are\nthe practical references for the player and DRM layers.\n\n**⚠️ Almost every source in this domain is a vendor or an integrator selling something.**\nCross-read, and treat platform-share numbers especially carefully (§1.1 → `smart-tv-platforms-and-10-foot-ui`).\n\n---\n\n## §19. Quick Reference\n\n### 19.1 Numbers\n- Design canvas **1920×1080**; **safe area 90%** (5% margin each side).\n- Body text **≥24 px**; nothing below ~18 px.\n- Focusable targets **≥60–80 px**.\n- Frame budget **16.6 ms**; time-to-first-video-frame **\u003C2 s**; cold start **\u003C3 s**.\n- Rebuffer ratio **\u003C0.5%**; playback failure **\u003C1%**.\n- Loudness **−23 LUFS** (streaming\u002FSSAI), **−24 LKFS** (US broadcast).\n- Ad creative **≤200 MB** (≤150 MB preferred); **VAST 4.x**.\n- Samsung 2024 TVs run **Chromium 108**; 2018 TVs run **Chromium 56**.\n- Roku **Instant Resume required by 1 Oct 2026** (qualifying US apps).\n\n### 19.2 Pre-launch checklist\n- [ ] Focus never lost; Back always predictable; initial focus set on every screen\n- [ ] Everything inside the 90% safe area; readable at 10 feet\n- [ ] Tested on the **cheapest** device and the **oldest model year** you support\n- [ ] Long lists virtualized; images server-sized; memory monitored\n- [ ] Cold start and time-to-first-frame measured on the slowest device\n- [ ] Deep links work: cold start, warm start, unentitled user, missing content\n- [ ] Playback position saved continuously; resume verified after a long suspend\n- [ ] Both `cenc` and `cbcs` packaging verified on old and new devices\n- [ ] Captions render and honour system style settings\n- [ ] Sign-in via device-code pairing, not an on-screen keyboard\n- [ ] Platform billing implemented per policy; entitlement enforced server-side\n- [ ] Analytics segmented by device model and OS version\n- [ ] Certification checklist walked end-to-end **before** submission\n- [ ] Catalogue feed submitted for platform search\u002Fvoice\u002Frecommendation rows\n\n### 19.3 \"It's broken on TV\" triage\n| Symptom | First look |\n|---|---|\n| Remote appears dead | Focus lost, or focus trapped in a container (§3.1 → `smart-tv-platforms-and-10-foot-ui`) |\n| Blank\u002Fwhite screen on some models only | Frozen-Chromium feature gap — check the engine version (§1.3 → `smart-tv-platforms-and-10-foot-ui`) |\n| Black screen on playback, older devices | `cenc`\u002F`cbcs` mismatch, or codec unsupported on that tier (§5.1 → `smart-tv-playback-drm-and-performance`) |\n| App killed during use | Memory budget exceeded — profile image cache and list virtualization |\n| Slow to start playing | Sequential cold-start network cascade (§4.3 → `smart-tv-playback-drm-and-performance`) |\n| Fails certification on launch time | Same, plus JS bundle parse cost |\n| Works via deep link, broken from search | Catalogue feed mapping or unentitled-user path (§7.2 → `smart-tv-playback-drm-and-performance`–7.3) |\n| Ads too loud | Loudness normalization (§4.2 → `smart-tv-playback-drm-and-performance`) |\n| Fine on the OLED, broken on the stick | You tested on the wrong device (§11 → `smart-tv-monetization-certification-and-operations`) |\n\n---\n\n## §20. Sources and Method\n\n**Method.** Narrative (not systematic) review. The durable material — §2 → `smart-tv-platforms-and-10-foot-ui` (10-foot UI),\n§3 → `smart-tv-platforms-and-10-foot-ui` (focus and input), §4.3 → `smart-tv-playback-drm-and-performance` (playback metrics), §5.1 → `smart-tv-playback-drm-and-performance` (DRM structure), §6 → `smart-tv-playback-drm-and-performance` (performance),\n§8.2 → `smart-tv-monetization-certification-and-operations`, §12 → `smart-tv-monetization-certification-and-operations`, §15 — is synthesized from vendor design guidelines, long-standing platform\ndocumentation, and consistent practitioner reporting. Every **time-sensitive** claim\n(platform shares, OS versions, engine matrices, certification requirements, ad specs,\nregulation) was verified against a primary or near-primary source in **August 2026** and\nis flagged in §17 with a decay-risk rating. Where the trade-off genuinely depends on\nplatform mix or budget, §16 presents both cases.\n\n**Search log** (August 2026): smart TV OS market share and platform landscape · Amazon\nVega OS and the Fire OS transition · Roku SceneGraph\u002FBrightScript and certification\nrequirements · Samsung Tizen and LG webOS SDK and Chromium version constraints · CTV\nadvertising specs, SSAI, ACR, and measurement.\n\n**Primary and near-primary sources consulted (selected):**\n- **Samsung Developer** — **Web Engine Specifications** (the model-year\u002FChromium table),\n  General Specifications (HLS\u002FDASH support, GCC toolchain change), TV Extension archive\n- **Roku Developer** — certification testing docs, SceneGraph course, the Roku developer\n  blog's Certification category (Spring 2026 update), the `rokudev` GitHub org\n- **Amazon Developer** — \"Announcing Vega OS\" \u002F Get started with Vega Developer Tools;\n  **Software Mansion**'s account of building React Native for Vega; **AFTVnews**,\n  **Ars Technica**-sourced reporting, **PCWorld**, and **Dolby OptiView** on the transition\n- **Parks Associates** (April 2026 Streaming Video Tracker press release, via PRNewswire\n  and TV Tech) — US platform shares; **Mordor Intelligence** on activated screens, the\n  Fox–Roku agreement, webOS 26, and the Cyber Trust Mark \u002F Kentucky HB 692 regulatory notes\n- **IAB Tech Lab** — CTV Programmatic Guide (Universal Ad ID, OM SDK); **Equativ** —\n  2026 CTV ad formats and specs, including loudness targets\n- **Nielsen** figures via **M+C Saatchi Performance**; **ScreenCloud** and **Play Signage**\n  on real-world Chromium version limits; **Float Left**, **Fora Soft**, **Lightcast**,\n  and **Accedo** on platform development practice\n\n**Confidence statement.** **High confidence** in §2–§8 → `smart-tv-platforms-and-10-foot-ui`, `smart-tv-monetization-certification-and-operations`, §10–§12 → `smart-tv-monetization-certification-and-operations`, §15, and §19 — these rest\non vendor documentation and consistently-reported practitioner experience. **High\nconfidence** in the Samsung engine matrix (§1.3 → `smart-tv-platforms-and-10-foot-ui`, §17), which comes directly from Samsung's\nown specification page, and in the Roku certification requirements, which come from Roku's\nown blog. **Moderate confidence** in §1.1 → `smart-tv-platforms-and-10-foot-ui`'s market-share figures: the sources genuinely\ndisagree because they measure different things (usage vs. activated screens vs. global\nshipments), the numbers come from commercial research firms with differing methodologies,\nand I have deliberately presented three framings rather than one number. **Moderate\nconfidence** in §9 → `smart-tv-monetization-certification-and-operations`'s advertising specifications — these come from ad-tech vendors and the\nIAB, are directionally consistent across sources, but vary by publisher in practice, and\nthe guidance throughout is to confirm specs with the specific publisher or platform rather\nthan treating any single figure as universal. The Fox–Roku acquisition (§1.2 → `smart-tv-platforms-and-10-foot-ui`, §17) was\n**announced**, and announced deals do not always close.\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fsmart-tv-app-development\u002Fskills\u002Fsmart-tv-reference",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 smart-tv-reference",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill smart-tv-reference",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill smart-tv-reference","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fsmart-tv-app-development\u002Fskills\u002Fsmart-tv-reference\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",[],[]]