[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AR9PA5Z3C48W7MF10YN83J":3,"skill-same:01M7AR9PA5Z3C48W7MF10YN83J":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},"01M7AR9PA5Z3C48W7MF10YN83J","power-reference",null,"Use when checking a power-engineering anti-pattern, looking up a voltage, rating or system value, asking what actually moved (the inverter-dominated grid and datacenter load growth, verified August 2026), finding the books, or needing a picker and the orientation questions to ask before starting grid software work. Companion to the other power-engineering 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\u002Fpower-engineering\u002Fskills\u002Fpower-reference\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: power-reference\ndescription: \"Use when checking a power-engineering anti-pattern, looking up a voltage, rating or system value, asking what actually moved (the inverter-dominated grid and datacenter load growth, verified August 2026), finding the books, or needing a picker and the orientation questions to ask before starting grid software work. Companion to the other power-engineering skills.\"\n---\n\n# Power Engineering: Anti-Patterns, Numbers, What Moved, and Canon\n\n> **Part 5 of 5** of the *Power Engineering* reference (plugin `power-engineering`), covering §13–§18. Sibling skills: `power-ac-fundamentals-generation-and-grid` (§0–§3), `power-system-analysis-and-protection` (§4–§5), `power-scada-ems-and-protocols` (§6–§7), `power-inverters-storage-markets-and-datacenters` (§8–§12). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** Circuit theory and power system analysis are settled; the inverter-dominated grid and datacenter load growth moved fast. See §15 below for both, dated.\n\n> **Scope.** Complements an electrical-engineering reference, which is circuit-level —\n> components, op-amps, PCB layout, signal integrity. ⚠️ **This is grid scale: kilovolts\n> and megawatts, and the software that runs it.**\n>\n> **⚠️ GOTCHA** boxes mark what kills people, destroys equipment, or causes blackouts.\n>\n> **The three ideas that organize the whole field:**\n> 1. **⚠️ Generation must equal load, continuously, everywhere.** The grid stores almost\n>    nothing. **Frequency IS the balance signal** — it falls when load exceeds generation\n>    and rises when it doesn't, in real time, across a continent (§1.4 → `power-ac-fundamentals-generation-and-grid`).\n> 2. **⚠️ Reactive power is not \"wasted\" power — it's a separate commodity that must also\n>    balance, and it's local.** Real power flows across a system; reactive power doesn't\n>    travel well, so voltage is a local problem and frequency is a global one (§1.2 → `power-ac-fundamentals-generation-and-grid`).\n> 3. **⚠️ Protection is the fastest software in the system and it acts on trust.** A relay\n>    decides in milliseconds to disconnect equipment, and it must be right — a false trip\n>    causes an outage, a missed trip destroys equipment or kills someone (§5 → `power-system-analysis-and-protection`).\n\n---\n\n## §13. Anti-Patterns\n\n| Anti-pattern | Why |\n|---|---|\n| Treating reactive power as waste | ⚠️ **It holds voltage up. The question is where it's sourced** (§1.2 → `power-ac-fundamentals-generation-and-grid`) |\n| Assuming voltage is a system-wide quantity | ⚠️ **Voltage is local; frequency is global** (§1.2 → `power-ac-fundamentals-generation-and-grid`) |\n| Undersized neutral in a nonlinear-load facility | ⚠️ **Triplen harmonics add rather than cancel** (§1.3 → `power-ac-fundamentals-generation-and-grid`) |\n| Ignoring per-unit conventions | Every number will confuse you (§1.5 → `power-ac-fundamentals-generation-and-grid`) |\n| Relaxing tolerance when power flow won't converge | ⚠️ **Non-convergence may mean genuine infeasibility** (§4.1 → `power-system-analysis-and-protection`) |\n| Acting on raw telemetry rather than the state estimate | That's what state estimation is for (§4.2 → `power-system-analysis-and-protection`) |\n| Overcurrent protection settings assuming synchronous fault current | ⚠️ **Inverters supply ~1.1–2× rated. The relay may not see it** (§5 → `power-system-analysis-and-protection`, §8.1 → `power-inverters-storage-markets-and-datacenters`) |\n| Treating GFM inverters as a solved replacement for inertia | ⚠️ **~12% of UK contracted inertia by 2026; the rest is rotating mass** (§8.2 → `power-inverters-storage-markets-and-datacenters`) |\n| Assuming an air gap protects OT | ⚠️ **It's mostly mythical. Segment properly** (§11.2 → `power-inverters-storage-markets-and-datacenters`) |\n| Applying IT patch cadence to OT | ⚠️ **Availability outranks confidentiality here** (§11.2 → `power-inverters-storage-markets-and-datacenters`) |\n| Assuming a protocol authenticates the sender | ⚠️ **Most in §7 → `power-scada-ems-and-protocols` don't** (§7 → `power-scada-ems-and-protocols`) |\n| Phasor-domain simulation for inverter control studies | ⚠️ **Misses the fast dynamics. Use EMT** (§11.3 → `power-inverters-storage-markets-and-datacenters`) |\n| Sloppy time synchronization | ⚠️ **Sequence-of-events analysis becomes worthless** (§11.3 → `power-inverters-storage-markets-and-datacenters`) |\n| Alarm design that floods during real events | Documented blackout escalation factor (§6 → `power-scada-ems-and-protocols`) |\n| Greedy battery dispatch ignoring state of charge | ⚠️ **Empty when the obligation lands** (§9 → `power-inverters-storage-markets-and-datacenters`) |\n| Storage optimization without degradation cost | Destroys the asset profitably (§9 → `power-inverters-storage-markets-and-datacenters`) |\n| Optimizing PUE while ignoring workload efficiency | ⚠️ **PUE cannot see software at all** (§12.1 → `power-inverters-storage-markets-and-datacenters`) |\n| Air cooling at modern AI rack density | ⚠️ **It doesn't work above ~40 kW\u002Frack** (§12.2 → `power-inverters-storage-markets-and-datacenters`) |\n| Assuming grid capacity is available on your timeline | ⚠️ **4–10 year interconnection queues** (§15.2) |\n\n---\n\n## §14. Numbers\n\n```\nFREQUENCY   60 Hz (NA, parts of Asia\u002FLatAm) · 50 Hz (most of the world)\n⚠️ Normal band ±0.05 Hz typical; under-frequency load shedding begins ~59.3 Hz (60 Hz sys)\nGovernor droop 4–5%\n\nVOLTAGE LEVELS\nTransmission 115 \u002F 138 \u002F 230 \u002F 345 \u002F 500 \u002F 765 kV\nDistribution 4.16 \u002F 12.47 \u002F 13.8 \u002F 34.5 kV\nUtilization 120\u002F240 V (NA residential) · 208Y\u002F120 · 480Y\u002F277 V (NA commercial)\n230 V \u002F 400Y\u002F230 V (most of the world)\n\nTHREE-PHASE\nWye: V_line = √3 V_phase · Delta: I_line = √3 I_phase\nP_3φ = √3 · V_L · I_L · cos θ\n\nPOWER FACTOR\nPF 0.7 draws ~43% more current than PF 1.0 for the same real power\n\nPROTECTION (ANSI)\n50\u002F51 overcurrent · 87 differential · 21 distance · 27\u002F59 volt · 81 freq · 79 reclose\n⚠️ IEC 61850 GOOSE delivery requirement ~4 ms\n⚠️ Inverter fault current ~1.1–2× rated (vs many× for synchronous machines)\n\nDATACENTER\nPUE: 1.0 ideal · ~1.1 hyperscale · 1.5–2.0 older enterprise\n⚠️ AI rack density to ~140 kW (vs 5–15 kW traditional)\nAI site draw 100–750 MW  ·  ⚠️ a 500 MW site at 90% util ≈ 3.9 TWh\u002Fyr\n```\n\n---\n\n## §15. What Actually Moved — verified August 2026\n\n### 15.1 The inverter-dominated grid\n**⚠️ This has moved from academic concern to operational reality.** One trade source puts\nit directly: **in 2026 the conversation moved from IEEE papers to utility boardrooms\nbecause high-profile outages showed how fast frequency collapses when inverter-dominated\nregions lose a transmission tie.** ⚠️ **The Iberian Peninsula event of 28 April 2025 has an\nofficial expert panel report (October 2025) and is now a standard reference in the\nprotection literature — worth reading directly rather than through commentary.**\n\n**Instantaneous non-synchronous generation penetration has reached 60–80% in many small\npower systems**, which makes this a present-tense engineering problem in those systems,\nnot a future one.\n\n**⚠️ The honest state of GFM deployment is the §8.2 → `power-inverters-storage-markets-and-datacenters` gotcha and I'd weight it heavily**:\nthe UK's procurement outcome — **~12% of contracted inertia from GFM by 2026, the rest from\nsynchronous machines and mainly synchronous condensers** — is a market revealing that\n**adding back rotating mass has so far beaten synthetic inertia on cost and confidence.**\n**Germany's 2026 technology-differentiated procurement is the test to watch.**\n\n**Standards**: **IEEE 2800** and NERC guideline revisions now explicitly address IBR fault\nperformance, and ⚠️ **grid-forming capability is increasingly asked about in 2026\ninterconnection requests.**\n\n### 15.2 ⚠️ Datacenter load growth — the biggest grid story for this audience\n**The structural picture, which is consistent across sources:**\n- **Data centers used roughly 415 TWh in 2024, ~1.5% of global demand**, with **IEA\n  projections around 945 TWh by 2030 (~3%)** — ⚠️ **roughly 15% annual growth, far above\n  overall electricity demand growth.**\n- **⚠️ Concentration, not aggregate growth, is the actual problem.** A single training\n  facility can draw **several hundred MW to over 1 GW**, and **clustering in Northern\n  Virginia, Texas, Ireland and parts of East Asia** is what stresses specific systems.\n- **⚠️ The timescale mismatch is the core tension**, and it's well put in one source:\n  **datacenter demand moves at the speed of capital markets, while grid infrastructure\n  moves at the speed of permitting, procurement, and construction.**\n- **Interconnection queues**: ⚠️ **reported delays of 4–10 years**, with median time from\n  request to commercial operation **over five years.** ⚠️ **And a sobering base rate — of\n  capacity that submitted interconnection requests 2000–2019, only 13% had reached\n  commercial operation by end-2024; 77% was withdrawn.**\n- **⚠️ Physical bottlenecks are transformers, substations, switchgear and transmission\n  capacity** — long-lead-time hardware, not software.\n\n**⚠️ The responses, and the one that matters most to software people:**\n- **\"Bring your own power\"** — on-site generation, behind-the-meter, microgrids, fuel\n  cells; ⚠️ **mandated in some markets, and operators are moving from PPAs to directly\n  funding generation.**\n- **⚠️ Flexibility as an interconnection strategy.** **PJM's board announced a\n  connect-and-manage framework in January 2026** under which **incremental large load that\n  doesn't bring its own generation may be subject to curtailment** ahead of\n  pre-emergency demand response. ⚠️ **This is the important one: a datacenter that can\n  modulate its consumption can connect sooner than one that can't — which turns workload\n  flexibility from an efficiency nicety into a capital-deployment lever.** **If you write\n  schedulers, that is your problem now.**\n\n> **⚠️ GOTCHA — the numbers in this subsection are forecasts from interested parties and\n> should be read as such.** ⚠️ **Sources include consultancies, real estate firms,\n> equipment vendors, grid-analytics companies, and investment banks — all of whom benefit\n> from the growth narrative.** **Projections varied noticeably across the sources I saw**\n> (2030 datacenter consumption at ~945 TWh from IEA-derived figures, with other estimates\n> running higher; US demand forecasts differ by tens of GW). **The physical constraints —\n> queue lengths, transformer lead times, PJM's actual policy — are better attested than\n> the demand forecasts.** ⚠️ **Treat direction as solid and magnitude as contested.**\n\n---\n\n## §16. Books\n\n| Author | Work | Why |\n|---|---|---|\n| **Kundur** | ***Power System Stability and Control*** | ⚠️ **The canonical stability reference. §4.4 → `power-system-analysis-and-protection` is this book** |\n| **Glover, Sarma & Overbye** | ***Power System Analysis and Design*** | ⚠️ **The best all-round textbook; start here** |\n| **Wood, Wollenberg & Sheblé** | ***Power Generation, Operation, and Control*** | §10 → `power-inverters-storage-markets-and-datacenters` — unit commitment and dispatch |\n| **Blackburn & Domin** | ***Protective Relaying: Principles and Applications*** | ⚠️ **§5 → `power-system-analysis-and-protection`, definitively** |\n| **Grainger & Stevenson** | *Power System Analysis* | Classic fundamentals |\n| **Kersting** | *Distribution System Modeling and Analysis* | ⚠️ **Distribution is genuinely different; this is the reference** |\n| **Denholm et al. (NREL)** | ***\"Inertia and the Power Grid: A Guide Without the Spin\"*** | ⚠️ **Free, and exactly the §8 → `power-inverters-storage-markets-and-datacenters` explainer you want** |\n| **Expert Panel** | *Grid Incident in Spain and Portugal, 28 April 2025* (Oct 2025) | ⚠️ **Read the primary report** |\n| **Bergen & Vittal** | *Power Systems Analysis* | Rigorous |\n\n**Practical**: **NERC standards and reliability guidelines** (⚠️ **public and readable**),\n**IEEE 1547 \u002F 2800**, **IEC 61850** documentation, **EPRI reports**, **NREL publications**\n(⚠️ **consistently excellent and free**), **MATPOWER and pandapower** docs as working\nintroductions, and **FERC\u002FRTO filings** for how markets actually operate.\n\n---\n\n## §17. Quick Reference\n\n### 17.1 Picker\n| Need | Use |\n|---|---|\n| Bus voltages and line flows | **Power flow, Newton-Raphson** (§4.1 → `power-system-analysis-and-protection`) |\n| Fast approximate flows for markets | ⚠️ **DC power flow** (§4.1 → `power-system-analysis-and-protection`) |\n| Best estimate of current system state | **State estimation** (§4.2 → `power-system-analysis-and-protection`) |\n| Breaker sizing, relay settings | **Fault analysis, symmetrical components** (§4.3 → `power-system-analysis-and-protection`) |\n| Inverter control dynamics | ⚠️ **EMT simulation (PSCAD\u002FEMTP), not phasor domain** (§11.3 → `power-inverters-storage-markets-and-datacenters`) |\n| Distribution feeder study | **OpenDSS \u002F GridLAB-D** (§11.3 → `power-inverters-storage-markets-and-datacenters`) |\n| Open research \u002F scripting | **pandapower, MATPOWER, PowerModels.jl** (§11.3 → `power-inverters-storage-markets-and-datacenters`) |\n| Fast protection signalling | ⚠️ **IEC 61850 GOOSE (~4 ms)** (§7 → `power-scada-ems-and-protocols`) |\n| Network model exchange | **CIM** (§7 → `power-scada-ems-and-protocols`) |\n| Wide-area dynamics visibility | **PMUs \u002F synchrophasors** (§4.2 → `power-system-analysis-and-protection`) |\n| Inertia in a low-inertia system | ⚠️ **Synchronous condenser or GFM inverter — and see §8.2 → `power-inverters-storage-markets-and-datacenters`** |\n| Fast frequency response | **BESS** (§9 → `power-inverters-storage-markets-and-datacenters`) |\n| Connect a large load sooner | ⚠️ **Demonstrable demand flexibility** (§15.2) |\n\n### 17.2 Orientation questions for grid software work\n- [ ] Which timescale am I in — protection, control, dispatch, or planning? (§11.1 → `power-inverters-storage-markets-and-datacenters`)\n- [ ] Per-unit or physical units, and on what base? (§1.5 → `power-ac-fundamentals-generation-and-grid`)\n- [ ] Is this phasor-domain or does it need EMT? (§11.3 → `power-inverters-storage-markets-and-datacenters`)\n- [ ] Does the network model match reality, and when was it last validated? (§11.3 → `power-inverters-storage-markets-and-datacenters`)\n- [ ] Are timestamps traceable to a synchronized source? (§11.3 → `power-inverters-storage-markets-and-datacenters`)\n- [ ] What happens to this system during an alarm flood? (§6 → `power-scada-ems-and-protocols`)\n- [ ] Is this in NERC CIP scope? (§11.2 → `power-inverters-storage-markets-and-datacenters`)\n- [ ] What does it do when it can't converge \u002F can't reach a device \u002F is late? (§4.1 → `power-system-analysis-and-protection`, §10 → `power-inverters-storage-markets-and-datacenters`)\n\n---\n\n## §18. Method\n\n**§1–§14 → `power-ac-fundamentals-generation-and-grid`, `power-system-analysis-and-protection`, `power-scada-ems-and-protocols`, `power-inverters-storage-markets-and-datacenters` rest on settled material** — **Fortescue's symmetrical components (1918)**,\nper-unit, Newton-Raphson power flow, protection principles, and market optimization\nformulations — sourced from the references in §16, chiefly **Kundur**, **Glover\u002FSarma\u002F\nOverbye**, **Blackburn & Domin**, and **Wood\u002FWollenberg**. ⚠️ **None of that needed\nverification; it's been stable for decades and the textbooks are the authority.**\n\n**Scoped to complement**: component-level circuit design, op-amps, PCB layout and signal\nintegrity sit in an electrical-engineering reference. **This picks up at the kilovolt\nscale.** ⚠️ **§11.1 → `power-inverters-storage-markets-and-datacenters` and §11.2 → `power-inverters-storage-markets-and-datacenters` deliberately parallel the flight-software and automotive\nreferences — safety-critical embedded practice converges across industries, and the\nreasoning transfers.**\n\n**Two searches were run in August 2026**, on the two areas that genuinely moved: **the\ninverter-dominated grid** and **datacenter load growth.**\n\n**Confidence.** **High** in §1–§11 → `power-ac-fundamentals-generation-and-grid`, `power-system-analysis-and-protection`, `power-scada-ems-and-protocols`, `power-inverters-storage-markets-and-datacenters` and §14 — textbook material stated with its\nassumptions, and the assumptions are the useful part. **High** in §8 → `power-inverters-storage-markets-and-datacenters`'s technical content:\nthe GFL\u002FGFM distinction, the inertia and short-circuit-ratio mechanism, and the\nprotection consequences of limited inverter fault current are **consistent across\npeer-reviewed sources** (IET, ScienceDirect, MDPI, arXiv reviews) **and NREL\u002FNERC\nmaterial.**\n\n⚠️ **Two hedges, weighted differently.**\n\n**§8.2 → `power-inverters-storage-markets-and-datacenters`'s UK procurement figure I'd treat as solid and important** — it comes from a\nconsultancy analysis but is a **concrete, checkable procurement outcome** rather than a\nforecast, and ⚠️ **it cuts directly against the prevailing enthusiasm, which is part of\nwhy I've given it prominence.** **Verify the current figure if you're making a\ntechnology decision on it.**\n\n**⚠️ §15.2 is the weak section and is flagged in place.** The sourcing is **consultancies,\nreal estate firms, equipment vendors, grid-analytics companies and investment banks, all\nof whom benefit from the growth narrative**, and ⚠️ **the demand projections varied\nnoticeably between them.** **I have deliberately separated the better-attested physical\nfacts — interconnection queue lengths, the 13%\u002F77% historical completion base rate,\ntransformer and switchgear lead times, PJM's January 2026 connect-and-manage\nannouncement — from the forecasts, and I'd trust the former considerably more than the\nlatter.** ⚠️ **Direction is solid; magnitude is contested.**\n\n**One thing I'd flag as the actionable insight rather than trivia**: ⚠️ **PJM's\nconnect-and-manage framework makes workload flexibility an interconnection asset.** **If\nthat model spreads, scheduler design becomes a determinant of how fast compute capacity\ncan be built** — which is an unusually direct line from software architecture to physical\ninfrastructure.\n","# Power Engineering: Anti-Patterns, Numbers, What Moved, and Canon\n\n> **Part 5 of 5** of the *Power Engineering* reference (plugin `power-engineering`), covering §13–§18. Sibling skills: `power-ac-fundamentals-generation-and-grid` (§0–§3), `power-system-analysis-and-protection` (§4–§5), `power-scada-ems-and-protocols` (§6–§7), `power-inverters-storage-markets-and-datacenters` (§8–§12). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** Circuit theory and power system analysis are settled; the inverter-dominated grid and datacenter load growth moved fast. See §15 below for both, dated.\n\n> **Scope.** Complements an electrical-engineering reference, which is circuit-level —\n> components, op-amps, PCB layout, signal integrity. ⚠️ **This is grid scale: kilovolts\n> and megawatts, and the software that runs it.**\n>\n> **⚠️ GOTCHA** boxes mark what kills people, destroys equipment, or causes blackouts.\n>\n> **The three ideas that organize the whole field:**\n> 1. **⚠️ Generation must equal load, continuously, everywhere.** The grid stores almost\n>    nothing. **Frequency IS the balance signal** — it falls when load exceeds generation\n>    and rises when it doesn't, in real time, across a continent (§1.4 → `power-ac-fundamentals-generation-and-grid`).\n> 2. **⚠️ Reactive power is not \"wasted\" power — it's a separate commodity that must also\n>    balance, and it's local.** Real power flows across a system; reactive power doesn't\n>    travel well, so voltage is a local problem and frequency is a global one (§1.2 → `power-ac-fundamentals-generation-and-grid`).\n> 3. **⚠️ Protection is the fastest software in the system and it acts on trust.** A relay\n>    decides in milliseconds to disconnect equipment, and it must be right — a false trip\n>    causes an outage, a missed trip destroys equipment or kills someone (§5 → `power-system-analysis-and-protection`).\n\n---\n\n## §13. Anti-Patterns\n\n| Anti-pattern | Why |\n|---|---|\n| Treating reactive power as waste | ⚠️ **It holds voltage up. The question is where it's sourced** (§1.2 → `power-ac-fundamentals-generation-and-grid`) |\n| Assuming voltage is a system-wide quantity | ⚠️ **Voltage is local; frequency is global** (§1.2 → `power-ac-fundamentals-generation-and-grid`) |\n| Undersized neutral in a nonlinear-load facility | ⚠️ **Triplen harmonics add rather than cancel** (§1.3 → `power-ac-fundamentals-generation-and-grid`) |\n| Ignoring per-unit conventions | Every number will confuse you (§1.5 → `power-ac-fundamentals-generation-and-grid`) |\n| Relaxing tolerance when power flow won't converge | ⚠️ **Non-convergence may mean genuine infeasibility** (§4.1 → `power-system-analysis-and-protection`) |\n| Acting on raw telemetry rather than the state estimate | That's what state estimation is for (§4.2 → `power-system-analysis-and-protection`) |\n| Overcurrent protection settings assuming synchronous fault current | ⚠️ **Inverters supply ~1.1–2× rated. The relay may not see it** (§5 → `power-system-analysis-and-protection`, §8.1 → `power-inverters-storage-markets-and-datacenters`) |\n| Treating GFM inverters as a solved replacement for inertia | ⚠️ **~12% of UK contracted inertia by 2026; the rest is rotating mass** (§8.2 → `power-inverters-storage-markets-and-datacenters`) |\n| Assuming an air gap protects OT | ⚠️ **It's mostly mythical. Segment properly** (§11.2 → `power-inverters-storage-markets-and-datacenters`) |\n| Applying IT patch cadence to OT | ⚠️ **Availability outranks confidentiality here** (§11.2 → `power-inverters-storage-markets-and-datacenters`) |\n| Assuming a protocol authenticates the sender | ⚠️ **Most in §7 → `power-scada-ems-and-protocols` don't** (§7 → `power-scada-ems-and-protocols`) |\n| Phasor-domain simulation for inverter control studies | ⚠️ **Misses the fast dynamics. Use EMT** (§11.3 → `power-inverters-storage-markets-and-datacenters`) |\n| Sloppy time synchronization | ⚠️ **Sequence-of-events analysis becomes worthless** (§11.3 → `power-inverters-storage-markets-and-datacenters`) |\n| Alarm design that floods during real events | Documented blackout escalation factor (§6 → `power-scada-ems-and-protocols`) |\n| Greedy battery dispatch ignoring state of charge | ⚠️ **Empty when the obligation lands** (§9 → `power-inverters-storage-markets-and-datacenters`) |\n| Storage optimization without degradation cost | Destroys the asset profitably (§9 → `power-inverters-storage-markets-and-datacenters`) |\n| Optimizing PUE while ignoring workload efficiency | ⚠️ **PUE cannot see software at all** (§12.1 → `power-inverters-storage-markets-and-datacenters`) |\n| Air cooling at modern AI rack density | ⚠️ **It doesn't work above ~40 kW\u002Frack** (§12.2 → `power-inverters-storage-markets-and-datacenters`) |\n| Assuming grid capacity is available on your timeline | ⚠️ **4–10 year interconnection queues** (§15.2) |\n\n---\n\n## §14. Numbers\n\n```\nFREQUENCY   60 Hz (NA, parts of Asia\u002FLatAm) · 50 Hz (most of the world)\n⚠️ Normal band ±0.05 Hz typical; under-frequency load shedding begins ~59.3 Hz (60 Hz sys)\nGovernor droop 4–5%\n\nVOLTAGE LEVELS\nTransmission 115 \u002F 138 \u002F 230 \u002F 345 \u002F 500 \u002F 765 kV\nDistribution 4.16 \u002F 12.47 \u002F 13.8 \u002F 34.5 kV\nUtilization 120\u002F240 V (NA residential) · 208Y\u002F120 · 480Y\u002F277 V (NA commercial)\n230 V \u002F 400Y\u002F230 V (most of the world)\n\nTHREE-PHASE\nWye: V_line = √3 V_phase · Delta: I_line = √3 I_phase\nP_3φ = √3 · V_L · I_L · cos θ\n\nPOWER FACTOR\nPF 0.7 draws ~43% more current than PF 1.0 for the same real power\n\nPROTECTION (ANSI)\n50\u002F51 overcurrent · 87 differential · 21 distance · 27\u002F59 volt · 81 freq · 79 reclose\n⚠️ IEC 61850 GOOSE delivery requirement ~4 ms\n⚠️ Inverter fault current ~1.1–2× rated (vs many× for synchronous machines)\n\nDATACENTER\nPUE: 1.0 ideal · ~1.1 hyperscale · 1.5–2.0 older enterprise\n⚠️ AI rack density to ~140 kW (vs 5–15 kW traditional)\nAI site draw 100–750 MW  ·  ⚠️ a 500 MW site at 90% util ≈ 3.9 TWh\u002Fyr\n```\n\n---\n\n## §15. What Actually Moved — verified August 2026\n\n### 15.1 The inverter-dominated grid\n**⚠️ This has moved from academic concern to operational reality.** One trade source puts\nit directly: **in 2026 the conversation moved from IEEE papers to utility boardrooms\nbecause high-profile outages showed how fast frequency collapses when inverter-dominated\nregions lose a transmission tie.** ⚠️ **The Iberian Peninsula event of 28 April 2025 has an\nofficial expert panel report (October 2025) and is now a standard reference in the\nprotection literature — worth reading directly rather than through commentary.**\n\n**Instantaneous non-synchronous generation penetration has reached 60–80% in many small\npower systems**, which makes this a present-tense engineering problem in those systems,\nnot a future one.\n\n**⚠️ The honest state of GFM deployment is the §8.2 → `power-inverters-storage-markets-and-datacenters` gotcha and I'd weight it heavily**:\nthe UK's procurement outcome — **~12% of contracted inertia from GFM by 2026, the rest from\nsynchronous machines and mainly synchronous condensers** — is a market revealing that\n**adding back rotating mass has so far beaten synthetic inertia on cost and confidence.**\n**Germany's 2026 technology-differentiated procurement is the test to watch.**\n\n**Standards**: **IEEE 2800** and NERC guideline revisions now explicitly address IBR fault\nperformance, and ⚠️ **grid-forming capability is increasingly asked about in 2026\ninterconnection requests.**\n\n### 15.2 ⚠️ Datacenter load growth — the biggest grid story for this audience\n**The structural picture, which is consistent across sources:**\n- **Data centers used roughly 415 TWh in 2024, ~1.5% of global demand**, with **IEA\n  projections around 945 TWh by 2030 (~3%)** — ⚠️ **roughly 15% annual growth, far above\n  overall electricity demand growth.**\n- **⚠️ Concentration, not aggregate growth, is the actual problem.** A single training\n  facility can draw **several hundred MW to over 1 GW**, and **clustering in Northern\n  Virginia, Texas, Ireland and parts of East Asia** is what stresses specific systems.\n- **⚠️ The timescale mismatch is the core tension**, and it's well put in one source:\n  **datacenter demand moves at the speed of capital markets, while grid infrastructure\n  moves at the speed of permitting, procurement, and construction.**\n- **Interconnection queues**: ⚠️ **reported delays of 4–10 years**, with median time from\n  request to commercial operation **over five years.** ⚠️ **And a sobering base rate — of\n  capacity that submitted interconnection requests 2000–2019, only 13% had reached\n  commercial operation by end-2024; 77% was withdrawn.**\n- **⚠️ Physical bottlenecks are transformers, substations, switchgear and transmission\n  capacity** — long-lead-time hardware, not software.\n\n**⚠️ The responses, and the one that matters most to software people:**\n- **\"Bring your own power\"** — on-site generation, behind-the-meter, microgrids, fuel\n  cells; ⚠️ **mandated in some markets, and operators are moving from PPAs to directly\n  funding generation.**\n- **⚠️ Flexibility as an interconnection strategy.** **PJM's board announced a\n  connect-and-manage framework in January 2026** under which **incremental large load that\n  doesn't bring its own generation may be subject to curtailment** ahead of\n  pre-emergency demand response. ⚠️ **This is the important one: a datacenter that can\n  modulate its consumption can connect sooner than one that can't — which turns workload\n  flexibility from an efficiency nicety into a capital-deployment lever.** **If you write\n  schedulers, that is your problem now.**\n\n> **⚠️ GOTCHA — the numbers in this subsection are forecasts from interested parties and\n> should be read as such.** ⚠️ **Sources include consultancies, real estate firms,\n> equipment vendors, grid-analytics companies, and investment banks — all of whom benefit\n> from the growth narrative.** **Projections varied noticeably across the sources I saw**\n> (2030 datacenter consumption at ~945 TWh from IEA-derived figures, with other estimates\n> running higher; US demand forecasts differ by tens of GW). **The physical constraints —\n> queue lengths, transformer lead times, PJM's actual policy — are better attested than\n> the demand forecasts.** ⚠️ **Treat direction as solid and magnitude as contested.**\n\n---\n\n## §16. Books\n\n| Author | Work | Why |\n|---|---|---|\n| **Kundur** | ***Power System Stability and Control*** | ⚠️ **The canonical stability reference. §4.4 → `power-system-analysis-and-protection` is this book** |\n| **Glover, Sarma & Overbye** | ***Power System Analysis and Design*** | ⚠️ **The best all-round textbook; start here** |\n| **Wood, Wollenberg & Sheblé** | ***Power Generation, Operation, and Control*** | §10 → `power-inverters-storage-markets-and-datacenters` — unit commitment and dispatch |\n| **Blackburn & Domin** | ***Protective Relaying: Principles and Applications*** | ⚠️ **§5 → `power-system-analysis-and-protection`, definitively** |\n| **Grainger & Stevenson** | *Power System Analysis* | Classic fundamentals |\n| **Kersting** | *Distribution System Modeling and Analysis* | ⚠️ **Distribution is genuinely different; this is the reference** |\n| **Denholm et al. (NREL)** | ***\"Inertia and the Power Grid: A Guide Without the Spin\"*** | ⚠️ **Free, and exactly the §8 → `power-inverters-storage-markets-and-datacenters` explainer you want** |\n| **Expert Panel** | *Grid Incident in Spain and Portugal, 28 April 2025* (Oct 2025) | ⚠️ **Read the primary report** |\n| **Bergen & Vittal** | *Power Systems Analysis* | Rigorous |\n\n**Practical**: **NERC standards and reliability guidelines** (⚠️ **public and readable**),\n**IEEE 1547 \u002F 2800**, **IEC 61850** documentation, **EPRI reports**, **NREL publications**\n(⚠️ **consistently excellent and free**), **MATPOWER and pandapower** docs as working\nintroductions, and **FERC\u002FRTO filings** for how markets actually operate.\n\n---\n\n## §17. Quick Reference\n\n### 17.1 Picker\n| Need | Use |\n|---|---|\n| Bus voltages and line flows | **Power flow, Newton-Raphson** (§4.1 → `power-system-analysis-and-protection`) |\n| Fast approximate flows for markets | ⚠️ **DC power flow** (§4.1 → `power-system-analysis-and-protection`) |\n| Best estimate of current system state | **State estimation** (§4.2 → `power-system-analysis-and-protection`) |\n| Breaker sizing, relay settings | **Fault analysis, symmetrical components** (§4.3 → `power-system-analysis-and-protection`) |\n| Inverter control dynamics | ⚠️ **EMT simulation (PSCAD\u002FEMTP), not phasor domain** (§11.3 → `power-inverters-storage-markets-and-datacenters`) |\n| Distribution feeder study | **OpenDSS \u002F GridLAB-D** (§11.3 → `power-inverters-storage-markets-and-datacenters`) |\n| Open research \u002F scripting | **pandapower, MATPOWER, PowerModels.jl** (§11.3 → `power-inverters-storage-markets-and-datacenters`) |\n| Fast protection signalling | ⚠️ **IEC 61850 GOOSE (~4 ms)** (§7 → `power-scada-ems-and-protocols`) |\n| Network model exchange | **CIM** (§7 → `power-scada-ems-and-protocols`) |\n| Wide-area dynamics visibility | **PMUs \u002F synchrophasors** (§4.2 → `power-system-analysis-and-protection`) |\n| Inertia in a low-inertia system | ⚠️ **Synchronous condenser or GFM inverter — and see §8.2 → `power-inverters-storage-markets-and-datacenters`** |\n| Fast frequency response | **BESS** (§9 → `power-inverters-storage-markets-and-datacenters`) |\n| Connect a large load sooner | ⚠️ **Demonstrable demand flexibility** (§15.2) |\n\n### 17.2 Orientation questions for grid software work\n- [ ] Which timescale am I in — protection, control, dispatch, or planning? (§11.1 → `power-inverters-storage-markets-and-datacenters`)\n- [ ] Per-unit or physical units, and on what base? (§1.5 → `power-ac-fundamentals-generation-and-grid`)\n- [ ] Is this phasor-domain or does it need EMT? (§11.3 → `power-inverters-storage-markets-and-datacenters`)\n- [ ] Does the network model match reality, and when was it last validated? (§11.3 → `power-inverters-storage-markets-and-datacenters`)\n- [ ] Are timestamps traceable to a synchronized source? (§11.3 → `power-inverters-storage-markets-and-datacenters`)\n- [ ] What happens to this system during an alarm flood? (§6 → `power-scada-ems-and-protocols`)\n- [ ] Is this in NERC CIP scope? (§11.2 → `power-inverters-storage-markets-and-datacenters`)\n- [ ] What does it do when it can't converge \u002F can't reach a device \u002F is late? (§4.1 → `power-system-analysis-and-protection`, §10 → `power-inverters-storage-markets-and-datacenters`)\n\n---\n\n## §18. Method\n\n**§1–§14 → `power-ac-fundamentals-generation-and-grid`, `power-system-analysis-and-protection`, `power-scada-ems-and-protocols`, `power-inverters-storage-markets-and-datacenters` rest on settled material** — **Fortescue's symmetrical components (1918)**,\nper-unit, Newton-Raphson power flow, protection principles, and market optimization\nformulations — sourced from the references in §16, chiefly **Kundur**, **Glover\u002FSarma\u002F\nOverbye**, **Blackburn & Domin**, and **Wood\u002FWollenberg**. ⚠️ **None of that needed\nverification; it's been stable for decades and the textbooks are the authority.**\n\n**Scoped to complement**: component-level circuit design, op-amps, PCB layout and signal\nintegrity sit in an electrical-engineering reference. **This picks up at the kilovolt\nscale.** ⚠️ **§11.1 → `power-inverters-storage-markets-and-datacenters` and §11.2 → `power-inverters-storage-markets-and-datacenters` deliberately parallel the flight-software and automotive\nreferences — safety-critical embedded practice converges across industries, and the\nreasoning transfers.**\n\n**Two searches were run in August 2026**, on the two areas that genuinely moved: **the\ninverter-dominated grid** and **datacenter load growth.**\n\n**Confidence.** **High** in §1–§11 → `power-ac-fundamentals-generation-and-grid`, `power-system-analysis-and-protection`, `power-scada-ems-and-protocols`, `power-inverters-storage-markets-and-datacenters` and §14 — textbook material stated with its\nassumptions, and the assumptions are the useful part. **High** in §8 → `power-inverters-storage-markets-and-datacenters`'s technical content:\nthe GFL\u002FGFM distinction, the inertia and short-circuit-ratio mechanism, and the\nprotection consequences of limited inverter fault current are **consistent across\npeer-reviewed sources** (IET, ScienceDirect, MDPI, arXiv reviews) **and NREL\u002FNERC\nmaterial.**\n\n⚠️ **Two hedges, weighted differently.**\n\n**§8.2 → `power-inverters-storage-markets-and-datacenters`'s UK procurement figure I'd treat as solid and important** — it comes from a\nconsultancy analysis but is a **concrete, checkable procurement outcome** rather than a\nforecast, and ⚠️ **it cuts directly against the prevailing enthusiasm, which is part of\nwhy I've given it prominence.** **Verify the current figure if you're making a\ntechnology decision on it.**\n\n**⚠️ §15.2 is the weak section and is flagged in place.** The sourcing is **consultancies,\nreal estate firms, equipment vendors, grid-analytics companies and investment banks, all\nof whom benefit from the growth narrative**, and ⚠️ **the demand projections varied\nnoticeably between them.** **I have deliberately separated the better-attested physical\nfacts — interconnection queue lengths, the 13%\u002F77% historical completion base rate,\ntransformer and switchgear lead times, PJM's January 2026 connect-and-manage\nannouncement — from the forecasts, and I'd trust the former considerably more than the\nlatter.** ⚠️ **Direction is solid; magnitude is contested.**\n\n**One thing I'd flag as the actionable insight rather than trivia**: ⚠️ **PJM's\nconnect-and-manage framework makes workload flexibility an interconnection asset.** **If\nthat model spreads, scheduler design becomes a determinant of how fast compute capacity\ncan be built** — which is an unusually direct line from software architecture to physical\ninfrastructure.\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fpower-engineering\u002Fskills\u002Fpower-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 power-reference",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill power-reference",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill power-reference","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fpower-engineering\u002Fskills\u002Fpower-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",[],[]]