[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AMCJAN2JYNMT4PB39G3R5R":3,"skill-same:01M7AMCJAN2JYNMT4PB39G3R5R":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},"01M7AMCJAN2JYNMT4PB39G3R5R","hw-datacentre-facility-power-cooling-and-efficiency",null,"Use for data centre facilities: facility basics and tier models, power distribution from utility feed through UPS and PDU to the rack with redundancy topologies, cooling at scale including air containment, liquid and direct-to-chip, efficiency metrics such as PUE and what they hide, and racks and the physical infrastructure that constrains everything else.","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-datacentre-facility-power-cooling-and-efficiency\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: hw-datacentre-facility-power-cooling-and-efficiency\ndescription: \"Use for data centre facilities: facility basics and tier models, power distribution from utility feed through UPS and PDU to the rack with redundancy topologies, cooling at scale including air containment, liquid and direct-to-chip, efficiency metrics such as PUE and what they hide, and racks and the physical infrastructure that constrains everything else.\"\n---\n\n# Computer Hardware and Data Centres: Facility Basics, Power Distribution, Cooling at Scale, Efficiency Metrics, and Racks and Physical Infrastructure\n\n> **Part 4 of 6** of the *Computer Hardware Engineering, Custom Rigs and Data Centres* reference (plugin `computer-hardware-and-data-centers`), covering §16–§20. Sibling skills: `hw-bottlenecks-cpu-memory-gpu-and-storage` (§0–§5), `hw-interconnect-power-thermals-and-networking` (§6–§9), `hw-specifying-assembly-firmware-tuning-and-benchmarking` (§10–§15), `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 → `hw-interconnect-power-thermals-and-networking`, §18). **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## §16. Facility Basics\n\n```\n⚠️ WHAT A DATA CENTRE ACTUALLY IS  ⚠️ a building that converts\n   electricity into computation and heat, reliably. ⚠️ Everything\n   else is in service of that\n⚠️ THE MAJOR SYSTEMS  ⚠️ POWER (§17) · ⚠️ COOLING (§18) · space\n   and structure · network · fire suppression · security ·\n   monitoring\n⚠️ TIER CLASSIFICATION (Uptime Institute)  ⚠️ I basic · II\n   redundant components · ⚠️ III CONCURRENTLY MAINTAINABLE (you\n   can service anything without shutting down) · ⚠️ IV FAULT\n   TOLERANT (survives a single failure anywhere)\n   ⚠️ Note \"Tier III\" is frequently claimed and rarely certified —\n   ask whether the CERTIFICATION exists or just the aspiration\n⚠️ TYPES  hyperscale · colocation (retail and wholesale) ·\n   enterprise · ⚠️ EDGE (small, distributed, latency-driven)\n⚠️ SITE SELECTION  ⚠️ POWER AVAILABILITY FIRST (§26.1) · fibre\n   routes · water · climate (free cooling hours) · land ·\n   natural hazard exposure · latency to users · tax and politics\n```\n\n---\n\n## §17. ⚠️ Power Distribution\n\n> **⚠️ The dominant capital cost, the dominant design constraint, and increasingly the\n> reason a facility can or cannot be built at all** (§26 → `hw-reference`).\n```\n⚠️ THE CHAIN  utility medium voltage → transformer → switchgear →\n   ⚠️ UPS → PDU → rack busbar\u002FPDU → server PSU → VRM → chip\n   ⚠️ EVERY CONVERSION LOSES ENERGY, and the losses compound (§19)\n⚠️ REDUNDANCY NOTATION  ⚠️ N (no redundancy) · N+1 (one spare) ·\n   ⚠️ 2N (fully duplicated) · 2N+1\n   ⚠️ THE KEY DISTINCTION: redundancy protects against COMPONENT\n   failure; ⚠️ CONCURRENT MAINTAINABILITY means you can also\n   service it without downtime, and those are different properties\n⚠️ UPS TYPES  ⚠️ double-conversion (cleanest, least efficient) ·\n   line-interactive · ⚠️ ECO\u002Fmulti-mode which trades a little\n   protection for meaningful efficiency · flywheel · lithium\n   batteries increasingly displacing VRLA\n⚠️ GENERATORS  ⚠️ diesel standby, with the UPS covering only the\n   seconds until they start and stabilize. ⚠️ FUEL CONTRACTS and\n   ⚠️ REGULAR LOAD-BANK TESTING are what make them real — an\n   untested generator is a decoration\n⚠️ ⚠️ THE FAILURE PATTERN: most data centre outages trace to POWER,\n   and disproportionately to the TRANSFER between sources —\n   ATS failures, batteries that had degraded silently, and\n   generators that didn't start\n⚠️ AT RACK LEVEL  ⚠️ 208\u002F415V AC three-phase or 48 VDC, and now\n   ⚠️ 800 VDC (§26.2)\n```\n\n---\n\n## §18. ⚠️ Cooling at Scale\n\n**⚠️ Every watt in becomes a watt of heat out** (§8 → `hw-interconnect-power-thermals-and-networking`) — ⚠️ **so a 100 MW facility is a 100 MW\nheat source.** **See a refrigeration reference for the underlying physics.**\n```\n⚠️ AIR-BASED  ⚠️ hot aisle \u002F cold aisle containment (⚠️ the single\n   highest-value retrofit in legacy facilities) · CRAC\u002FCRAH ·\n   raised floor or overhead delivery\n   ⚠️ AIR RUNS OUT OF CAPACITY around 30-40 kW per rack even\n   with optimized design (§26.2)\n⚠️ ECONOMIZATION  ⚠️ air-side (⚠️ outside air directly, subject to\n   humidity and contamination) and water-side (cooling towers)\n   ⚠️ FREE COOLING HOURS drive site selection\n⚠️ LIQUID  ⚠️ rear-door heat exchangers (⚠️ easiest retrofit) →\n   ⚠️ DIRECT-TO-CHIP cold plates with a CDU → immersion\n   (single or two-phase)\n   ⚠️ Liquid is now MANDATORY, not optional, above roughly\n   50-100 kW per rack (§26.2)\n⚠️ WATER  ⚠️ evaporative cooling consumes water and trades it\n   against electricity. ⚠️ WUE is a real metric and a real siting\n   constraint in stressed regions\n⚠️ ⚠️ ASHRAE THERMAL GUIDELINES  ⚠️ and the important finding is\n   that the allowable ranges are WIDER than operators historically\n   assumed — running warmer saves substantial cooling energy at\n   little reliability cost, and over-cooling is a widespread and\n   expensive habit\n⚠️ HEAT REUSE  district heating from data centre waste heat is\n   real where the geography permits, and limited by the LOW\n   TEMPERATURE of the rejected heat (see a thermodynamics\n   reference on exergy)\n```\n\n---\n\n## §19. Efficiency Metrics\n\n**⚠️ PUE = total facility energy ÷ IT equipment energy.** ⚠️ **1.0 is the theoretical\nideal; hyperscale facilities operate close to it and legacy enterprise rooms are far\nworse.**\n> **⚠️ GOTCHA — PUE IS EASILY GAMED AND FREQUENTLY MISUSED.** ⚠️ **It measures\n> INFRASTRUCTURE overhead, not useful work.** **⚠️ Making the IT equipment less efficient\n> IMPROVES PUE, because it increases the denominator.** ⚠️ **A facility with excellent PUE\n> running idle servers is wasting more energy than a worse-PUE facility doing useful work.**\n> **⚠️ Also check the measurement boundary, the averaging period, and whether it's\n> annualized or a favourable-day figure.**\n\n**⚠️ Complementary metrics**: ⚠️ **WUE (water), CUE (carbon), and — the ones that actually\nmatter — WORK PER WATT: transactions, queries or tokens per joule.**\n**⚠️ The largest efficiency wins are usually not in the facility at all**: ⚠️ **server\nutilization (⚠️ idle servers draw a large fraction of peak power for zero output),\nvirtualization and consolidation, decommissioning zombie servers, and software\nefficiency.**\n\n---\n\n## §20. Racks and Physical Infrastructure\n\n**⚠️ The 19-inch rack, measured in U (1U = 1.75 inches \u002F 44.45 mm)**, ⚠️ **with 42U and 48U\ncommon and depth mattering more than people expect.**\n**⚠️ OCP (Open Compute Project)** — ⚠️ **21-inch racks, DC busbar distribution, PSUs moved\nout of the server, and a genuinely different mechanical standard now widely adopted by\nhyperscalers.**\n**⚠️ Weight and floor loading are real constraints** — ⚠️ **a fully populated high-density\nrack is very heavy, and liquid cooling adds more.**\n**⚠️ Cable management, structured cabling, and labelling** — ⚠️ **unglamorous and the\ndifference between a maintainable facility and an unmaintainable one.**\n**⚠️ Physical security**: **layered access, mantraps, CCTV, cage-level separation in colo.**\n","# Computer Hardware and Data Centres: Facility Basics, Power Distribution, Cooling at Scale, Efficiency Metrics, and Racks and Physical Infrastructure\n\n> **Part 4 of 6** of the *Computer Hardware Engineering, Custom Rigs and Data Centres* reference (plugin `computer-hardware-and-data-centers`), covering §16–§20. Sibling skills: `hw-bottlenecks-cpu-memory-gpu-and-storage` (§0–§5), `hw-interconnect-power-thermals-and-networking` (§6–§9), `hw-specifying-assembly-firmware-tuning-and-benchmarking` (§10–§15), `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 → `hw-interconnect-power-thermals-and-networking`, §18). **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## §16. Facility Basics\n\n```\n⚠️ WHAT A DATA CENTRE ACTUALLY IS  ⚠️ a building that converts\n   electricity into computation and heat, reliably. ⚠️ Everything\n   else is in service of that\n⚠️ THE MAJOR SYSTEMS  ⚠️ POWER (§17) · ⚠️ COOLING (§18) · space\n   and structure · network · fire suppression · security ·\n   monitoring\n⚠️ TIER CLASSIFICATION (Uptime Institute)  ⚠️ I basic · II\n   redundant components · ⚠️ III CONCURRENTLY MAINTAINABLE (you\n   can service anything without shutting down) · ⚠️ IV FAULT\n   TOLERANT (survives a single failure anywhere)\n   ⚠️ Note \"Tier III\" is frequently claimed and rarely certified —\n   ask whether the CERTIFICATION exists or just the aspiration\n⚠️ TYPES  hyperscale · colocation (retail and wholesale) ·\n   enterprise · ⚠️ EDGE (small, distributed, latency-driven)\n⚠️ SITE SELECTION  ⚠️ POWER AVAILABILITY FIRST (§26.1) · fibre\n   routes · water · climate (free cooling hours) · land ·\n   natural hazard exposure · latency to users · tax and politics\n```\n\n---\n\n## §17. ⚠️ Power Distribution\n\n> **⚠️ The dominant capital cost, the dominant design constraint, and increasingly the\n> reason a facility can or cannot be built at all** (§26 → `hw-reference`).\n```\n⚠️ THE CHAIN  utility medium voltage → transformer → switchgear →\n   ⚠️ UPS → PDU → rack busbar\u002FPDU → server PSU → VRM → chip\n   ⚠️ EVERY CONVERSION LOSES ENERGY, and the losses compound (§19)\n⚠️ REDUNDANCY NOTATION  ⚠️ N (no redundancy) · N+1 (one spare) ·\n   ⚠️ 2N (fully duplicated) · 2N+1\n   ⚠️ THE KEY DISTINCTION: redundancy protects against COMPONENT\n   failure; ⚠️ CONCURRENT MAINTAINABILITY means you can also\n   service it without downtime, and those are different properties\n⚠️ UPS TYPES  ⚠️ double-conversion (cleanest, least efficient) ·\n   line-interactive · ⚠️ ECO\u002Fmulti-mode which trades a little\n   protection for meaningful efficiency · flywheel · lithium\n   batteries increasingly displacing VRLA\n⚠️ GENERATORS  ⚠️ diesel standby, with the UPS covering only the\n   seconds until they start and stabilize. ⚠️ FUEL CONTRACTS and\n   ⚠️ REGULAR LOAD-BANK TESTING are what make them real — an\n   untested generator is a decoration\n⚠️ ⚠️ THE FAILURE PATTERN: most data centre outages trace to POWER,\n   and disproportionately to the TRANSFER between sources —\n   ATS failures, batteries that had degraded silently, and\n   generators that didn't start\n⚠️ AT RACK LEVEL  ⚠️ 208\u002F415V AC three-phase or 48 VDC, and now\n   ⚠️ 800 VDC (§26.2)\n```\n\n---\n\n## §18. ⚠️ Cooling at Scale\n\n**⚠️ Every watt in becomes a watt of heat out** (§8 → `hw-interconnect-power-thermals-and-networking`) — ⚠️ **so a 100 MW facility is a 100 MW\nheat source.** **See a refrigeration reference for the underlying physics.**\n```\n⚠️ AIR-BASED  ⚠️ hot aisle \u002F cold aisle containment (⚠️ the single\n   highest-value retrofit in legacy facilities) · CRAC\u002FCRAH ·\n   raised floor or overhead delivery\n   ⚠️ AIR RUNS OUT OF CAPACITY around 30-40 kW per rack even\n   with optimized design (§26.2)\n⚠️ ECONOMIZATION  ⚠️ air-side (⚠️ outside air directly, subject to\n   humidity and contamination) and water-side (cooling towers)\n   ⚠️ FREE COOLING HOURS drive site selection\n⚠️ LIQUID  ⚠️ rear-door heat exchangers (⚠️ easiest retrofit) →\n   ⚠️ DIRECT-TO-CHIP cold plates with a CDU → immersion\n   (single or two-phase)\n   ⚠️ Liquid is now MANDATORY, not optional, above roughly\n   50-100 kW per rack (§26.2)\n⚠️ WATER  ⚠️ evaporative cooling consumes water and trades it\n   against electricity. ⚠️ WUE is a real metric and a real siting\n   constraint in stressed regions\n⚠️ ⚠️ ASHRAE THERMAL GUIDELINES  ⚠️ and the important finding is\n   that the allowable ranges are WIDER than operators historically\n   assumed — running warmer saves substantial cooling energy at\n   little reliability cost, and over-cooling is a widespread and\n   expensive habit\n⚠️ HEAT REUSE  district heating from data centre waste heat is\n   real where the geography permits, and limited by the LOW\n   TEMPERATURE of the rejected heat (see a thermodynamics\n   reference on exergy)\n```\n\n---\n\n## §19. Efficiency Metrics\n\n**⚠️ PUE = total facility energy ÷ IT equipment energy.** ⚠️ **1.0 is the theoretical\nideal; hyperscale facilities operate close to it and legacy enterprise rooms are far\nworse.**\n> **⚠️ GOTCHA — PUE IS EASILY GAMED AND FREQUENTLY MISUSED.** ⚠️ **It measures\n> INFRASTRUCTURE overhead, not useful work.** **⚠️ Making the IT equipment less efficient\n> IMPROVES PUE, because it increases the denominator.** ⚠️ **A facility with excellent PUE\n> running idle servers is wasting more energy than a worse-PUE facility doing useful work.**\n> **⚠️ Also check the measurement boundary, the averaging period, and whether it's\n> annualized or a favourable-day figure.**\n\n**⚠️ Complementary metrics**: ⚠️ **WUE (water), CUE (carbon), and — the ones that actually\nmatter — WORK PER WATT: transactions, queries or tokens per joule.**\n**⚠️ The largest efficiency wins are usually not in the facility at all**: ⚠️ **server\nutilization (⚠️ idle servers draw a large fraction of peak power for zero output),\nvirtualization and consolidation, decommissioning zombie servers, and software\nefficiency.**\n\n---\n\n## §20. Racks and Physical Infrastructure\n\n**⚠️ The 19-inch rack, measured in U (1U = 1.75 inches \u002F 44.45 mm)**, ⚠️ **with 42U and 48U\ncommon and depth mattering more than people expect.**\n**⚠️ OCP (Open Compute Project)** — ⚠️ **21-inch racks, DC busbar distribution, PSUs moved\nout of the server, and a genuinely different mechanical standard now widely adopted by\nhyperscalers.**\n**⚠️ Weight and floor loading are real constraints** — ⚠️ **a fully populated high-density\nrack is very heavy, and liquid cooling adds more.**\n**⚠️ Cable management, structured cabling, and labelling** — ⚠️ **unglamorous and the\ndifference between a maintainable facility and an unmaintainable one.**\n**⚠️ Physical security**: **layered access, mantraps, CCTV, cage-level separation in colo.**\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fcomputer-hardware-and-data-centers\u002Fskills\u002Fhw-datacentre-facility-power-cooling-and-efficiency",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-datacentre-facility-power-cooling-and-efficiency",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill hw-datacentre-facility-power-cooling-and-efficiency",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill hw-datacentre-facility-power-cooling-and-efficiency","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fcomputer-hardware-and-data-centers\u002Fskills\u002Fhw-datacentre-facility-power-cooling-and-efficiency\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",[],[]]