[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AMCYCE025NEZ9HR34KQGFJ":3,"skill-same:01M7AMCYCE025NEZ9HR34KQGFJ":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},"01M7AMCYCE025NEZ9HR34KQGFJ","hw-interconnect-power-thermals-and-networking",null,"Use for the parts that quietly limit everything else: interconnect including PCIe lanes, generations and bifurcation, power supplies with efficiency, rails, transients and sizing, thermals and why cooling capacity rather than peak clock sets sustained performance, and networking at the host level.","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\u002Fcomputer-hardware-and-data-centers\u002Fskills\u002Fhw-interconnect-power-thermals-and-networking\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: hw-interconnect-power-thermals-and-networking\ndescription: \"Use for the parts that quietly limit everything else: interconnect including PCIe lanes, generations and bifurcation, power supplies with efficiency, rails, transients and sizing, thermals and why cooling capacity rather than peak clock sets sustained performance, and networking at the host level.\"\n---\n\n# Computer Hardware and Data Centres: Interconnect, Power Supplies, Thermals, and Networking\n\n> **Part 2 of 6** of the *Computer Hardware Engineering, Custom Rigs and Data Centres* reference (plugin `computer-hardware-and-data-centers`), covering §6–§9. Sibling skills: `hw-bottlenecks-cpu-memory-gpu-and-storage` (§0–§5), `hw-specifying-assembly-firmware-tuning-and-benchmarking` (§10–§15), `hw-datacentre-facility-power-cooling-and-efficiency` (§16–§20), `hw-datacentre-network-storage-failure-and-operations` (§21–§25), `hw-reference` (§26–§31). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** The architecture is stable. Two areas moved decisively. See §26 → `hw-reference` for grid power as the binding constraint, and the shift to high-voltage DC rack distribution.\n\n> **⚠️ The systems level above a semiconductor reference.** ⚠️ **That file covers how chips\n> are made; this covers what happens when you have to power them, cool them, connect them\n> and keep them running — at one desk or at a hundred megawatts.**\n>\n> **Complements an electromagnetism reference (power delivery, signal integrity, I²R\n> losses), a refrigeration reference (cooling physics), a thermodynamics reference (heat\n> rejection and exergy), and a resource-extraction reference (where the grid power comes\n> from).**\n>\n> **⚠️ GOTCHA** boxes mark where spec sheets mislead and where builders waste money.\n>\n> **The three ideas that organize this document:**\n> 1. **⚠️ THE BOTTLENECK IS ALMOST NEVER WHERE YOU THINK** (§1 → `hw-bottlenecks-cpu-memory-gpu-and-storage`, §3 → `hw-bottlenecks-cpu-memory-gpu-and-storage`, §26.1 → `hw-reference`). **It moves.\n>    It has gone from clock speed to memory to packaging to — currently — the electrical\n>    substation. Optimizing the wrong layer is the standard mistake at every scale.**\n> 2. **⚠️ MEMORY, NOT COMPUTE, GOVERNS REAL PERFORMANCE** (§3 → `hw-bottlenecks-cpu-memory-gpu-and-storage`). **The gap between\n>    processor speed and memory latency is the single most important fact in computer\n>    architecture, and most \"slow\" systems are memory-bound.**\n> 3. **⚠️ POWER AND HEAT ARE THE SAME NUMBER** (§8, §18 → `hw-datacentre-facility-power-cooling-and-efficiency`). **Essentially all electrical\n>    power into a computer leaves as heat. Every watt you draw is a watt you must remove,\n>    and at scale that equivalence dominates the entire building.**\n\n---\n\n## §6. Interconnect\n\n**⚠️ PCIe** — ⚠️ **lanes and generations, with bandwidth roughly doubling per generation;\n⚠️ lane ALLOCATION is the practical constraint on a consumer board, where the CPU provides\na fixed number and the chipset multiplexes the rest.**\n**⚠️ Check whether a slot is CPU-attached or chipset-attached** — ⚠️ **it matters for\nlatency and for contention.**\n**⚠️ CXL** builds on PCIe to provide cache-coherent access to attached memory —\n⚠️ **enabling memory expansion, pooling and disaggregation, which is genuinely significant\nfor servers.**\n**⚠️ Chipset, DMI\u002FInfinity Fabric, and the SoC trend** — ⚠️ **integrating memory controller,\nI\u002FO and increasingly memory itself onto the package, which improves latency and reduces\nupgradeability.**\n**⚠️ Signal integrity** (see an electromagnetism reference) — ⚠️ **at PCIe 5 and 6 speeds,\ntrace length, via stubs and connector quality genuinely matter, and RETIMERS exist because\nof it.**\n\n---\n\n## §7. ⚠️ Power Supplies\n\n```\n⚠️ WHAT IT DOES  AC mains → regulated DC rails (12V dominant;\n   3.3V and 5V now minor)\n⚠️ EFFICIENCY  ⚠️ 80 PLUS tiers. ⚠️ Efficiency PEAKS around\n   40-60% load, so a wildly oversized PSU runs LESS efficiently\n   at idle — the \"buy double what you need\" instinct is wrong\n⚠️ ⚠️ TRANSIENT RESPONSE IS THE SPEC THAT ACTUALLY MATTERS AND\n   ISN'T ON THE BOX. ⚠️ Modern GPUs draw microsecond power spikes\n   FAR above their rated average. ⚠️ A PSU with adequate continuous\n   rating but poor transient handling will trip OCP and shut the\n   system down under load — and it looks like an unstable GPU\n⚠️ ⚠️ SINGLE vs MULTI-RAIL · ⚠️ HOLD-UP TIME (ride-through on brief\n   mains dips) · ripple · protections (OCP\u002FOVP\u002FOTP\u002FSCP)\n⚠️ CONNECTORS  ⚠️ 12VHPWR\u002F12V-2x6 has a documented history of\n   melting when not FULLY SEATED — ⚠️ the failure mode is contact\n   resistance at partial insertion, and it is an installation\n   discipline issue as much as a design one\n⚠️ ⚠️ DO NOT MIX CABLES BETWEEN PSUs. Modular connectors are\n   NOT standardized pinouts, and mismatched cables destroy hardware\n⚠️ UPS  ⚠️ line-interactive vs double-conversion; ⚠️ simulated vs\n   pure sine wave matters for active PFC supplies\n```\n\n---\n\n## §8. ⚠️ Thermals\n\n> **⚠️ Essentially 100% of electrical power into a computer leaves as heat. Power draw and\n> cooling requirement are THE SAME NUMBER, and this equivalence scales all the way to §18 → `hw-datacentre-facility-power-cooling-and-efficiency`.**\n```\n⚠️ THE THERMAL PATH  die → ⚠️ TIM\u002Fsolder → IHS → TIM → cold plate\n   or heatsink → ⚠️ AIR OR LIQUID → room → outside\n   ⚠️ The chain is only as good as its worst link, and the\n   die-to-IHS interface is often it\n⚠️ THERMAL RESISTANCE in °C\u002FW, summed along the path\n⚠️ AIR COOLING  heat pipes (⚠️ phase change, very effective),\n   vapour chambers, fin density vs static pressure, ⚠️ and fan\n   curves — noise rises steeply with RPM\n⚠️ LIQUID  ⚠️ AIO closed loop (⚠️ pump is a wear item and a single\n   point of failure) vs custom loop. ⚠️ Water's heat capacity\n   moves heat AWAY effectively; ⚠️ it does not create cooling —\n   the radiator still rejects to air\n⚠️ CASE AIRFLOW  ⚠️ front-to-back, bottom-to-top; positive pressure\n   with filtration reduces dust. ⚠️ GPUs dump heat INTO the case,\n   which then feeds the CPU cooler\n⚠️ ⚠️ THROTTLING IS NORMAL AND BY DESIGN. ⚠️ Modern parts boost\n   until they hit a power, thermal or current limit. ⚠️ Therefore\n   BETTER COOLING IS A PERFORMANCE UPGRADE, not just a quiet one\n⚠️ TIM  ⚠️ application method matters far less than people argue\n   about; ⚠️ pump-out and dry-out over years is real\n```\n\n---\n\n## §9. Networking\n\n**⚠️ Ethernet dominates** — ⚠️ **1\u002F2.5\u002F10\u002F25\u002F40\u002F100 GbE and beyond; ⚠️ note that copper\ndistance falls sharply with speed, which is why fibre and DAC cables appear.**\n**⚠️ Latency vs bandwidth** — ⚠️ **and for distributed workloads latency and TAIL latency\nusually matter more than headline bandwidth.**\n**⚠️ Wi-Fi** — ⚠️ **shared medium, half duplex, and real throughput is a fraction of the\nadvertised PHY rate; ⚠️ for anything latency-sensitive, use a cable.**\n**⚠️ Offload** — ⚠️ **TSO\u002FLRO, RDMA (RoCE, InfiniBand) which bypasses the kernel and is\nstandard in HPC and AI clusters, and SmartNIC\u002FDPU offload of networking and storage from\nthe host CPU.**\n\n---\n\n# PART II — BUILDING AND RUNNING A MACHINE\n","# Computer Hardware and Data Centres: Interconnect, Power Supplies, Thermals, and Networking\n\n> **Part 2 of 6** of the *Computer Hardware Engineering, Custom Rigs and Data Centres* reference (plugin `computer-hardware-and-data-centers`), covering §6–§9. Sibling skills: `hw-bottlenecks-cpu-memory-gpu-and-storage` (§0–§5), `hw-specifying-assembly-firmware-tuning-and-benchmarking` (§10–§15), `hw-datacentre-facility-power-cooling-and-efficiency` (§16–§20), `hw-datacentre-network-storage-failure-and-operations` (§21–§25), `hw-reference` (§26–§31). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** The architecture is stable. Two areas moved decisively. See §26 → `hw-reference` for grid power as the binding constraint, and the shift to high-voltage DC rack distribution.\n\n> **⚠️ The systems level above a semiconductor reference.** ⚠️ **That file covers how chips\n> are made; this covers what happens when you have to power them, cool them, connect them\n> and keep them running — at one desk or at a hundred megawatts.**\n>\n> **Complements an electromagnetism reference (power delivery, signal integrity, I²R\n> losses), a refrigeration reference (cooling physics), a thermodynamics reference (heat\n> rejection and exergy), and a resource-extraction reference (where the grid power comes\n> from).**\n>\n> **⚠️ GOTCHA** boxes mark where spec sheets mislead and where builders waste money.\n>\n> **The three ideas that organize this document:**\n> 1. **⚠️ THE BOTTLENECK IS ALMOST NEVER WHERE YOU THINK** (§1 → `hw-bottlenecks-cpu-memory-gpu-and-storage`, §3 → `hw-bottlenecks-cpu-memory-gpu-and-storage`, §26.1 → `hw-reference`). **It moves.\n>    It has gone from clock speed to memory to packaging to — currently — the electrical\n>    substation. Optimizing the wrong layer is the standard mistake at every scale.**\n> 2. **⚠️ MEMORY, NOT COMPUTE, GOVERNS REAL PERFORMANCE** (§3 → `hw-bottlenecks-cpu-memory-gpu-and-storage`). **The gap between\n>    processor speed and memory latency is the single most important fact in computer\n>    architecture, and most \"slow\" systems are memory-bound.**\n> 3. **⚠️ POWER AND HEAT ARE THE SAME NUMBER** (§8, §18 → `hw-datacentre-facility-power-cooling-and-efficiency`). **Essentially all electrical\n>    power into a computer leaves as heat. Every watt you draw is a watt you must remove,\n>    and at scale that equivalence dominates the entire building.**\n\n---\n\n## §6. Interconnect\n\n**⚠️ PCIe** — ⚠️ **lanes and generations, with bandwidth roughly doubling per generation;\n⚠️ lane ALLOCATION is the practical constraint on a consumer board, where the CPU provides\na fixed number and the chipset multiplexes the rest.**\n**⚠️ Check whether a slot is CPU-attached or chipset-attached** — ⚠️ **it matters for\nlatency and for contention.**\n**⚠️ CXL** builds on PCIe to provide cache-coherent access to attached memory —\n⚠️ **enabling memory expansion, pooling and disaggregation, which is genuinely significant\nfor servers.**\n**⚠️ Chipset, DMI\u002FInfinity Fabric, and the SoC trend** — ⚠️ **integrating memory controller,\nI\u002FO and increasingly memory itself onto the package, which improves latency and reduces\nupgradeability.**\n**⚠️ Signal integrity** (see an electromagnetism reference) — ⚠️ **at PCIe 5 and 6 speeds,\ntrace length, via stubs and connector quality genuinely matter, and RETIMERS exist because\nof it.**\n\n---\n\n## §7. ⚠️ Power Supplies\n\n```\n⚠️ WHAT IT DOES  AC mains → regulated DC rails (12V dominant;\n   3.3V and 5V now minor)\n⚠️ EFFICIENCY  ⚠️ 80 PLUS tiers. ⚠️ Efficiency PEAKS around\n   40-60% load, so a wildly oversized PSU runs LESS efficiently\n   at idle — the \"buy double what you need\" instinct is wrong\n⚠️ ⚠️ TRANSIENT RESPONSE IS THE SPEC THAT ACTUALLY MATTERS AND\n   ISN'T ON THE BOX. ⚠️ Modern GPUs draw microsecond power spikes\n   FAR above their rated average. ⚠️ A PSU with adequate continuous\n   rating but poor transient handling will trip OCP and shut the\n   system down under load — and it looks like an unstable GPU\n⚠️ ⚠️ SINGLE vs MULTI-RAIL · ⚠️ HOLD-UP TIME (ride-through on brief\n   mains dips) · ripple · protections (OCP\u002FOVP\u002FOTP\u002FSCP)\n⚠️ CONNECTORS  ⚠️ 12VHPWR\u002F12V-2x6 has a documented history of\n   melting when not FULLY SEATED — ⚠️ the failure mode is contact\n   resistance at partial insertion, and it is an installation\n   discipline issue as much as a design one\n⚠️ ⚠️ DO NOT MIX CABLES BETWEEN PSUs. Modular connectors are\n   NOT standardized pinouts, and mismatched cables destroy hardware\n⚠️ UPS  ⚠️ line-interactive vs double-conversion; ⚠️ simulated vs\n   pure sine wave matters for active PFC supplies\n```\n\n---\n\n## §8. ⚠️ Thermals\n\n> **⚠️ Essentially 100% of electrical power into a computer leaves as heat. Power draw and\n> cooling requirement are THE SAME NUMBER, and this equivalence scales all the way to §18 → `hw-datacentre-facility-power-cooling-and-efficiency`.**\n```\n⚠️ THE THERMAL PATH  die → ⚠️ TIM\u002Fsolder → IHS → TIM → cold plate\n   or heatsink → ⚠️ AIR OR LIQUID → room → outside\n   ⚠️ The chain is only as good as its worst link, and the\n   die-to-IHS interface is often it\n⚠️ THERMAL RESISTANCE in °C\u002FW, summed along the path\n⚠️ AIR COOLING  heat pipes (⚠️ phase change, very effective),\n   vapour chambers, fin density vs static pressure, ⚠️ and fan\n   curves — noise rises steeply with RPM\n⚠️ LIQUID  ⚠️ AIO closed loop (⚠️ pump is a wear item and a single\n   point of failure) vs custom loop. ⚠️ Water's heat capacity\n   moves heat AWAY effectively; ⚠️ it does not create cooling —\n   the radiator still rejects to air\n⚠️ CASE AIRFLOW  ⚠️ front-to-back, bottom-to-top; positive pressure\n   with filtration reduces dust. ⚠️ GPUs dump heat INTO the case,\n   which then feeds the CPU cooler\n⚠️ ⚠️ THROTTLING IS NORMAL AND BY DESIGN. ⚠️ Modern parts boost\n   until they hit a power, thermal or current limit. ⚠️ Therefore\n   BETTER COOLING IS A PERFORMANCE UPGRADE, not just a quiet one\n⚠️ TIM  ⚠️ application method matters far less than people argue\n   about; ⚠️ pump-out and dry-out over years is real\n```\n\n---\n\n## §9. Networking\n\n**⚠️ Ethernet dominates** — ⚠️ **1\u002F2.5\u002F10\u002F25\u002F40\u002F100 GbE and beyond; ⚠️ note that copper\ndistance falls sharply with speed, which is why fibre and DAC cables appear.**\n**⚠️ Latency vs bandwidth** — ⚠️ **and for distributed workloads latency and TAIL latency\nusually matter more than headline bandwidth.**\n**⚠️ Wi-Fi** — ⚠️ **shared medium, half duplex, and real throughput is a fraction of the\nadvertised PHY rate; ⚠️ for anything latency-sensitive, use a cable.**\n**⚠️ Offload** — ⚠️ **TSO\u002FLRO, RDMA (RoCE, InfiniBand) which bypasses the kernel and is\nstandard in HPC and AI clusters, and SmartNIC\u002FDPU offload of networking and storage from\nthe host CPU.**\n\n---\n\n# PART II — BUILDING AND RUNNING A MACHINE\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fcomputer-hardware-and-data-centers\u002Fskills\u002Fhw-interconnect-power-thermals-and-networking",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 hw-interconnect-power-thermals-and-networking",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill hw-interconnect-power-thermals-and-networking",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill hw-interconnect-power-thermals-and-networking","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fcomputer-hardware-and-data-centers\u002Fskills\u002Fhw-interconnect-power-thermals-and-networking\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",[],[]]