[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AMDACQ3YB7RSYGMWAX136S":3,"skill-same:01M7AMDACQ3YB7RSYGMWAX136S":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},"01M7AMDACQ3YB7RSYGMWAX136S","hw-specifying-assembly-firmware-tuning-and-benchmarking",null,"Use when building or fixing a machine: specifying a build from the workload backwards, assembly practice, firmware and boot including UEFI and the settings that actually matter, tuning and overclocking assessed honestly against the risk, troubleshooting method for intermittent and hard faults, and benchmarking that measures the thing you care about rather than a number.","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-specifying-assembly-firmware-tuning-and-benchmarking\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: hw-specifying-assembly-firmware-tuning-and-benchmarking\ndescription: \"Use when building or fixing a machine: specifying a build from the workload backwards, assembly practice, firmware and boot including UEFI and the settings that actually matter, tuning and overclocking assessed honestly against the risk, troubleshooting method for intermittent and hard faults, and benchmarking that measures the thing you care about rather than a number.\"\n---\n\n# Computer Hardware and Data Centres: Specifying a Build, Assembly, Firmware and Boot, Tuning and Overclocking, Troubleshooting, and Benchmarking\n\n> **Part 3 of 6** of the *Computer Hardware Engineering, Custom Rigs and Data Centres* reference (plugin `computer-hardware-and-data-centers`), covering §10–§15. Sibling skills: `hw-bottlenecks-cpu-memory-gpu-and-storage` (§0–§5), `hw-interconnect-power-thermals-and-networking` (§6–§9), `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 → `hw-interconnect-power-thermals-and-networking`, §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## §10. Specifying a Build\n\n> **⚠️ Start from the WORKLOAD, not from a parts list. Almost every wasted pound in a\n> custom build comes from balancing the machine wrong.**\n```\n⚠️ MATCH THE COMPONENT TO THE BOTTLENECK (§1)\n   ⚠️ Gaming  ⚠️ GPU-dominant; CPU matters at high frame rates and\n      low resolution; ⚠️ VRAM capacity increasingly binding\n   ⚠️ Content creation  cores, RAM CAPACITY, fast storage\n   ⚠️ Software development  ⚠️ single-thread speed for many tools,\n      cores for compilation, RAM for containers and VMs\n   ⚠️ ML  ⚠️ VRAM CAPACITY FIRST — a model that doesn't fit doesn't\n      run — then bandwidth, then compute\n   ⚠️ Workstation\u002FCAD  certified drivers, ECC where correctness matters\n   ⚠️ Home server\u002FNAS  ⚠️ reliability, ECC, drive bays, low idle power\n⚠️ THE BALANCE PRINCIPLE  ⚠️ a top GPU with an inadequate CPU or\n   insufficient RAM wastes most of what you paid for\n⚠️ WHERE MONEY IS USUALLY WASTED  ⚠️ oversized PSU (§7) · RGB ·\n   marginal RAM speed · exotic cooling for a part that isn't\n   thermally limited · high-end board features you'll never use\n⚠️ WHERE IT IS USUALLY WELL SPENT  ⚠️ a good PSU · adequate RAM\n   capacity · a decent monitor (⚠️ which outlasts the whole build)\n   · quiet cooling · a case you can work in\n```\n\n---\n\n## §11. Assembly\n\n**⚠️ ESD precautions** (see a cryptography-adjacent electronics reference on static —\n⚠️ **high voltage, tiny energy, harmless to you and destructive to semiconductors**): work\non a hard surface, ground yourself, handle boards by the edges.\n**⚠️ The order that saves rework**: ⚠️ **CPU, cooler backplate, RAM and M.2 into the board\nBEFORE it goes in the case; then PSU; then board; then GPU last.**\n**⚠️ The specific care points**: ⚠️ **CPU socket orientation and never touching LGA pins;\n⚠️ RAM in the correct slots for dual channel — usually A2\u002FB2, and getting this wrong\nhalves memory bandwidth silently; ⚠️ standoffs correct and no extras shorting the board;\n⚠️ every power connector FULLY seated (§7 → `hw-interconnect-power-thermals-and-networking`); and cable management for airflow.**\n**⚠️ Test outside the case first** if anything is uncertain — ⚠️ **it takes minutes and\nsaves a full disassembly.**\n\n---\n\n## §12. Firmware and Boot\n\n**⚠️ UEFI replaced BIOS** — ⚠️ **GPT partitioning, larger disks, faster boot, and Secure\nBoot.**\n**⚠️ POST and the boot chain**: ⚠️ **firmware → bootloader → kernel → init, and knowing this\nsequence is what lets you diagnose where a boot failure occurs.**\n**⚠️ Settings that actually matter**: ⚠️ **XMP\u002FEXPO to run memory at its rated speed\n(⚠️ memory ships at JEDEC defaults and does NOT run at advertised speed until you enable\nit — an extremely common oversight), resizable BAR, virtualization extensions, fan curves,\nand boot order.**\n**⚠️ Firmware updates** fix real bugs including microcode and stability issues — ⚠️ **and a\nfailed flash can brick a board, so use the vendor's recovery mechanism where available and\ndon't update without reason.**\n**⚠️ Secure Boot and TPM** underpin measured boot and disk encryption (see a cryptography\nreference §15).\n\n---\n\n## §13. Tuning and Overclocking, Honestly\n\n**⚠️ The modern reality**: ⚠️ **parts already boost to their limits automatically, so\nheadroom is far smaller than a decade ago and manual overclocking often loses to the\nstock algorithm.**\n**⚠️ What actually pays**: ⚠️ **UNDERVOLTING (⚠️ frequently gives equal performance at lower\ntemperature and noise — the best-value tuning available), memory timing tuning on some\nplatforms, fan curve tuning, and improving cooling** (§8 → `hw-interconnect-power-thermals-and-networking`).\n**⚠️ Stability testing must be workload-diverse** — ⚠️ **a system stable under one stress\ntest can fail under another, and instability manifests as silent data corruption, not\njust crashes.**\n**⚠️ The honest costs** (see a semiconductor reference §23): ⚠️ **higher voltage and\ntemperature consume rated device lifetime through electromigration and TDDB, warranties\nmay be affected, and the performance gain is usually single-digit percent.**\n\n---\n\n## §14. ⚠️ Troubleshooting\n\n```\n⚠️ THE METHOD  ⚠️ change ONE thing at a time · bisect · reduce to\n   minimum configuration · swap known-good parts · ⚠️ and READ\n   THE ACTUAL ERROR before theorizing\n⚠️ NO POST  ⚠️ power connectors (especially the CPU 8-pin, the\n   most commonly forgotten) · RAM reseat and try ONE stick ·\n   standoff short · ⚠️ CMOS clear · debug LEDs or POST codes\n   (⚠️ these tell you the stage — use them)\n⚠️ RANDOM CRASHES  ⚠️ this is the hardest class. ⚠️ Suspect, in\n   rough order: PSU transients (§7) · RAM (⚠️ run MemTest86\n   OVERNIGHT — a short pass proves little) · thermals · unstable\n   XMP · drivers · storage errors\n⚠️ THERMAL THROTTLING  monitor under sustained load, not at idle\n⚠️ POOR PERFORMANCE  ⚠️ check XMP enabled · dual channel populated ·\n   GPU in the CPU-attached x16 slot · power plan · background load ·\n   ⚠️ and confirm which resource is actually saturated (§15)\n⚠️ INTERMITTENT  ⚠️ the worst. Log everything; check event logs;\n   suspect connections, thermal cycling and marginal power\n⚠️ ⚠️ THE PRINCIPLE: SUSPECT WHAT YOU CHANGED, and prefer\n   measurement over replacement\n```\n\n---\n\n## §15. ⚠️ Benchmarking\n\n> **⚠️ Most published comparisons are misleading, and the errors are systematic rather than\n> random.**\n**⚠️ Synthetic vs real workload**: ⚠️ **synthetics are repeatable and frequently don't\npredict your application; run YOUR workload if you can.**\n**⚠️ The methodology errors that matter**: ⚠️ **testing only average FPS while ignoring\n1% and 0.1% LOWS (⚠️ which is what actually feels bad); short runs that miss thermal\nsteady state; run-to-run variance reported without repeats; comparing across different\ndriver, firmware and OS versions; and ⚠️ CPU tests run at resolutions where the GPU is the\nlimit, which flattens all CPUs into a meaningless tie.**\n**⚠️ Vendor benchmarks** are selected, not falsified — ⚠️ **and the selection is the whole\neffect.**\n**⚠️ For servers**: ⚠️ **measure TAIL latency (p99, p99.9) rather than mean, because mean\nlatency hides exactly the behaviour users notice.**\n**⚠️ The discipline**: ⚠️ **state the configuration completely, repeat, report variance,\nand change one variable at a time** (§14).\n\n---\n\n# PART III — DATA CENTRES\n","# Computer Hardware and Data Centres: Specifying a Build, Assembly, Firmware and Boot, Tuning and Overclocking, Troubleshooting, and Benchmarking\n\n> **Part 3 of 6** of the *Computer Hardware Engineering, Custom Rigs and Data Centres* reference (plugin `computer-hardware-and-data-centers`), covering §10–§15. Sibling skills: `hw-bottlenecks-cpu-memory-gpu-and-storage` (§0–§5), `hw-interconnect-power-thermals-and-networking` (§6–§9), `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 → `hw-interconnect-power-thermals-and-networking`, §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## §10. Specifying a Build\n\n> **⚠️ Start from the WORKLOAD, not from a parts list. Almost every wasted pound in a\n> custom build comes from balancing the machine wrong.**\n```\n⚠️ MATCH THE COMPONENT TO THE BOTTLENECK (§1)\n   ⚠️ Gaming  ⚠️ GPU-dominant; CPU matters at high frame rates and\n      low resolution; ⚠️ VRAM capacity increasingly binding\n   ⚠️ Content creation  cores, RAM CAPACITY, fast storage\n   ⚠️ Software development  ⚠️ single-thread speed for many tools,\n      cores for compilation, RAM for containers and VMs\n   ⚠️ ML  ⚠️ VRAM CAPACITY FIRST — a model that doesn't fit doesn't\n      run — then bandwidth, then compute\n   ⚠️ Workstation\u002FCAD  certified drivers, ECC where correctness matters\n   ⚠️ Home server\u002FNAS  ⚠️ reliability, ECC, drive bays, low idle power\n⚠️ THE BALANCE PRINCIPLE  ⚠️ a top GPU with an inadequate CPU or\n   insufficient RAM wastes most of what you paid for\n⚠️ WHERE MONEY IS USUALLY WASTED  ⚠️ oversized PSU (§7) · RGB ·\n   marginal RAM speed · exotic cooling for a part that isn't\n   thermally limited · high-end board features you'll never use\n⚠️ WHERE IT IS USUALLY WELL SPENT  ⚠️ a good PSU · adequate RAM\n   capacity · a decent monitor (⚠️ which outlasts the whole build)\n   · quiet cooling · a case you can work in\n```\n\n---\n\n## §11. Assembly\n\n**⚠️ ESD precautions** (see a cryptography-adjacent electronics reference on static —\n⚠️ **high voltage, tiny energy, harmless to you and destructive to semiconductors**): work\non a hard surface, ground yourself, handle boards by the edges.\n**⚠️ The order that saves rework**: ⚠️ **CPU, cooler backplate, RAM and M.2 into the board\nBEFORE it goes in the case; then PSU; then board; then GPU last.**\n**⚠️ The specific care points**: ⚠️ **CPU socket orientation and never touching LGA pins;\n⚠️ RAM in the correct slots for dual channel — usually A2\u002FB2, and getting this wrong\nhalves memory bandwidth silently; ⚠️ standoffs correct and no extras shorting the board;\n⚠️ every power connector FULLY seated (§7 → `hw-interconnect-power-thermals-and-networking`); and cable management for airflow.**\n**⚠️ Test outside the case first** if anything is uncertain — ⚠️ **it takes minutes and\nsaves a full disassembly.**\n\n---\n\n## §12. Firmware and Boot\n\n**⚠️ UEFI replaced BIOS** — ⚠️ **GPT partitioning, larger disks, faster boot, and Secure\nBoot.**\n**⚠️ POST and the boot chain**: ⚠️ **firmware → bootloader → kernel → init, and knowing this\nsequence is what lets you diagnose where a boot failure occurs.**\n**⚠️ Settings that actually matter**: ⚠️ **XMP\u002FEXPO to run memory at its rated speed\n(⚠️ memory ships at JEDEC defaults and does NOT run at advertised speed until you enable\nit — an extremely common oversight), resizable BAR, virtualization extensions, fan curves,\nand boot order.**\n**⚠️ Firmware updates** fix real bugs including microcode and stability issues — ⚠️ **and a\nfailed flash can brick a board, so use the vendor's recovery mechanism where available and\ndon't update without reason.**\n**⚠️ Secure Boot and TPM** underpin measured boot and disk encryption (see a cryptography\nreference §15).\n\n---\n\n## §13. Tuning and Overclocking, Honestly\n\n**⚠️ The modern reality**: ⚠️ **parts already boost to their limits automatically, so\nheadroom is far smaller than a decade ago and manual overclocking often loses to the\nstock algorithm.**\n**⚠️ What actually pays**: ⚠️ **UNDERVOLTING (⚠️ frequently gives equal performance at lower\ntemperature and noise — the best-value tuning available), memory timing tuning on some\nplatforms, fan curve tuning, and improving cooling** (§8 → `hw-interconnect-power-thermals-and-networking`).\n**⚠️ Stability testing must be workload-diverse** — ⚠️ **a system stable under one stress\ntest can fail under another, and instability manifests as silent data corruption, not\njust crashes.**\n**⚠️ The honest costs** (see a semiconductor reference §23): ⚠️ **higher voltage and\ntemperature consume rated device lifetime through electromigration and TDDB, warranties\nmay be affected, and the performance gain is usually single-digit percent.**\n\n---\n\n## §14. ⚠️ Troubleshooting\n\n```\n⚠️ THE METHOD  ⚠️ change ONE thing at a time · bisect · reduce to\n   minimum configuration · swap known-good parts · ⚠️ and READ\n   THE ACTUAL ERROR before theorizing\n⚠️ NO POST  ⚠️ power connectors (especially the CPU 8-pin, the\n   most commonly forgotten) · RAM reseat and try ONE stick ·\n   standoff short · ⚠️ CMOS clear · debug LEDs or POST codes\n   (⚠️ these tell you the stage — use them)\n⚠️ RANDOM CRASHES  ⚠️ this is the hardest class. ⚠️ Suspect, in\n   rough order: PSU transients (§7) · RAM (⚠️ run MemTest86\n   OVERNIGHT — a short pass proves little) · thermals · unstable\n   XMP · drivers · storage errors\n⚠️ THERMAL THROTTLING  monitor under sustained load, not at idle\n⚠️ POOR PERFORMANCE  ⚠️ check XMP enabled · dual channel populated ·\n   GPU in the CPU-attached x16 slot · power plan · background load ·\n   ⚠️ and confirm which resource is actually saturated (§15)\n⚠️ INTERMITTENT  ⚠️ the worst. Log everything; check event logs;\n   suspect connections, thermal cycling and marginal power\n⚠️ ⚠️ THE PRINCIPLE: SUSPECT WHAT YOU CHANGED, and prefer\n   measurement over replacement\n```\n\n---\n\n## §15. ⚠️ Benchmarking\n\n> **⚠️ Most published comparisons are misleading, and the errors are systematic rather than\n> random.**\n**⚠️ Synthetic vs real workload**: ⚠️ **synthetics are repeatable and frequently don't\npredict your application; run YOUR workload if you can.**\n**⚠️ The methodology errors that matter**: ⚠️ **testing only average FPS while ignoring\n1% and 0.1% LOWS (⚠️ which is what actually feels bad); short runs that miss thermal\nsteady state; run-to-run variance reported without repeats; comparing across different\ndriver, firmware and OS versions; and ⚠️ CPU tests run at resolutions where the GPU is the\nlimit, which flattens all CPUs into a meaningless tie.**\n**⚠️ Vendor benchmarks** are selected, not falsified — ⚠️ **and the selection is the whole\neffect.**\n**⚠️ For servers**: ⚠️ **measure TAIL latency (p99, p99.9) rather than mean, because mean\nlatency hides exactly the behaviour users notice.**\n**⚠️ The discipline**: ⚠️ **state the configuration completely, repeat, report variance,\nand change one variable at a time** (§14).\n\n---\n\n# PART III — DATA CENTRES\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fcomputer-hardware-and-data-centers\u002Fskills\u002Fhw-specifying-assembly-firmware-tuning-and-benchmarking",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-specifying-assembly-firmware-tuning-and-benchmarking",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill hw-specifying-assembly-firmware-tuning-and-benchmarking",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill hw-specifying-assembly-firmware-tuning-and-benchmarking","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fcomputer-hardware-and-data-centers\u002Fskills\u002Fhw-specifying-assembly-firmware-tuning-and-benchmarking\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",[],[]]