[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7APA8GSKERAD656SD3V8Q8E":3,"skill-same:01M7APA8GSKERAD656SD3V8Q8E":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},"01M7APA8GSKERAD656SD3V8Q8E","itgov-infrastructure-layers-compute-storage-and-networking",null,"Use when orienting in an enterprise estate or making a platform decision: the infrastructure layers and where responsibility sits at each, compute and virtualization including hypervisors, consolidation and the on-premises versus cloud decision, storage tiers and protocols, and enterprise networking including segmentation, the edge and remote access. Includes the router for the whole it-infrastructure-governance reference.","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\u002Fit-infrastructure-governance\u002Fskills\u002Fitgov-infrastructure-layers-compute-storage-and-networking\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: itgov-infrastructure-layers-compute-storage-and-networking\ndescription: \"Use when orienting in an enterprise estate or making a platform decision: the infrastructure layers and where responsibility sits at each, compute and virtualization including hypervisors, consolidation and the on-premises versus cloud decision, storage tiers and protocols, and enterprise networking including segmentation, the edge and remote access. Includes the router for the whole it-infrastructure-governance reference.\"\n---\n\n# IT Infrastructure and Governance: The Layers, Compute and Virtualization, Storage, and Networking\n\n> **Part 1 of 5** of the *IT Infrastructure and Governance* reference (plugin `it-infrastructure-governance`), covering §0–§4. Sibling skills: `itgov-directory-authentication-authorization-and-privileged-access` (§5–§8), `itgov-identity-lifecycle-access-review-and-segregation-of-duties` (§9–§11), `itgov-endpoints-continuity-itsm-and-vendor-risk` (§12–§19), `itgov-reference` (§20–§26). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** RBAC theory, directory concepts, backup strategy and ITIL process are stable. Two areas moved. See §21 → `itgov-reference` for the phishing-resistant authentication mandate timeline and non-human identity governance.\n\n> **⚠️ Scope.** The enterprise on-prem and hybrid layer. **Complements a Linux server\n> administration reference (host-level operations), a cloud reference (cloud-native\n> patterns), and a security reference (threat modelling and defensive controls).**\n> ⚠️ **The through-line here is access: who and what can do what, how you know, and how\n> you prove it.**\n>\n> **⚠️ GOTCHA** boxes mark the things that cause audit findings and breaches.\n>\n> **The three ideas that organize this:**\n> 1. **⚠️ Identity is the perimeter.** The network boundary stopped being the control\n>    point years ago. **Every meaningful access decision now happens at authentication and\n>    authorization time** (§5 → `itgov-directory-authentication-authorization-and-privileged-access`, §6 → `itgov-directory-authentication-authorization-and-privileged-access`).\n> 2. **⚠️ Access accumulates and never sheds by itself.** People change roles and keep old\n>    permissions; service accounts outlive their systems. **Privilege creep is the default\n>    state of any system without deliberate revocation** (§9 → `itgov-identity-lifecycle-access-review-and-segregation-of-duties`, §10 → `itgov-identity-lifecycle-access-review-and-segregation-of-duties`).\n> 3. **⚠️ Governance is the ability to answer \"who has access to what, why, and who\n>    approved it\" — with evidence.** If you cannot answer it, you do not have governance,\n>    you have configuration (§10 → `itgov-identity-lifecycle-access-review-and-segregation-of-duties`, §17 → `itgov-endpoints-continuity-itsm-and-vendor-risk`).\n\n---\n\n## §0. Routing\n\n| You want... | Go to |\n|---|---|\n| Infrastructure layers | §1 |\n| Compute and virtualization | §2 |\n| Storage | §3 |\n| Networking | §4 |\n| **Directory services and hybrid identity** | **§5 → `itgov-directory-authentication-authorization-and-privileged-access`** |\n| **Authentication** | **§6 → `itgov-directory-authentication-authorization-and-privileged-access`** |\n| **Authorization: RBAC, ABAC and role explosion** | **§7 → `itgov-directory-authentication-authorization-and-privileged-access`** |\n| **Privileged access** | **§8 → `itgov-directory-authentication-authorization-and-privileged-access`** |\n| **Identity lifecycle (JML)** | **§9 → `itgov-identity-lifecycle-access-review-and-segregation-of-duties`** |\n| **Access review and certification** | **§10 → `itgov-identity-lifecycle-access-review-and-segregation-of-duties`** |\n| Segregation of duties | §11 → `itgov-identity-lifecycle-access-review-and-segregation-of-duties` |\n| Endpoint management and patching | §12 → `itgov-endpoints-continuity-itsm-and-vendor-risk` |\n| **Backup, DR and continuity** | **§13 → `itgov-endpoints-continuity-itsm-and-vendor-risk`** |\n| Monitoring and logging | §14 → `itgov-endpoints-continuity-itsm-and-vendor-risk` |\n| ITSM and change management | §15 → `itgov-endpoints-continuity-itsm-and-vendor-risk` |\n| Asset and configuration management | §16 → `itgov-endpoints-continuity-itsm-and-vendor-risk` |\n| **Governance frameworks** | **§17 → `itgov-endpoints-continuity-itsm-and-vendor-risk`** |\n| Capacity and lifecycle planning | §18 → `itgov-endpoints-continuity-itsm-and-vendor-risk` |\n| Vendor and third-party risk | §19 → `itgov-endpoints-continuity-itsm-and-vendor-risk` |\n| Anti-patterns | §20 → `itgov-reference` |\n| **What moved** | **§21 → `itgov-reference`** |\n| Misconceptions | §22 → `itgov-reference` |\n| Numbers | §23 → `itgov-reference` |\n| Books | §24 → `itgov-reference` |\n| Quick reference | §25 → `itgov-reference` |\n\n---\n\n## §1. The Layers\n\n```\nFACILITY      power, cooling, physical security  (see a power engineering reference §12)\nCOMPUTE       servers, hypervisors, containers\nSTORAGE       block, file, object; SAN\u002FNAS\nNETWORK       switching, routing, firewalls, load balancing, WAN\nPLATFORM      OS, middleware, databases\nIDENTITY      ⚠️ directory, authentication, authorization — the control plane\nAPPLICATION   the things people actually use\n⚠️ GOVERNANCE  policy, process, evidence — wraps all of it\n```\n**⚠️ The hybrid reality is the normal case and worth stating plainly**: **very few\norganizations are all-cloud or all-on-prem.** ⚠️ **Most run on-prem Active Directory\nsynchronized to a cloud identity provider, some workloads in a datacentre and some in\ncloud, and the seams between them are where both the operational pain and the security\ngaps live.**\n\n---\n\n## §2. Compute and Virtualization\n\n**Bare metal** — ⚠️ **still correct for latency-sensitive, licence-bound, or\nhardware-dependent workloads.**\n**Hypervisors**: **Type 1 (bare metal — ESXi, Hyper-V, KVM, Xen)** vs **Type 2 (hosted)**.\n**⚠️ Consolidation ratios, overcommit (memory and CPU), and the failure mode of\novercommitting: noisy neighbours and unpredictable latency.**\n**Clustering and HA**: **live migration, failover, anti-affinity rules** (⚠️ **so your two\nredundant VMs don't land on the same physical host — a classic and embarrassing outage\ncause**).\n**Containers** vs VMs — ⚠️ **different isolation boundaries; a container escape is a\ndifferent risk class from a VM escape.**\n**⚠️ Licensing is a genuine architectural constraint in enterprise virtualization** —\n**per-core, per-socket and per-VM models change the economics of consolidation\nsubstantially, and licence audits are a real financial exposure.**\n\n---\n\n## §3. Storage\n\n```\nBLOCK    SAN, iSCSI, FC — ⚠️ raw volumes; databases and VMs\nFILE     NAS, SMB\u002FCIFS, NFS — shared filesystems, permissions\nOBJECT   S3-compatible — ⚠️ flat namespace, HTTP, massive scale, no POSIX semantics\n```\n**RAID levels and their real trade-offs** — ⚠️ **RAID is not backup; it protects against\ndrive failure, not deletion, corruption or ransomware.**\n**Tiering, thin provisioning** (⚠️ **and the failure mode: over-provisioning until the\npool fills and everything stops at once**), **snapshots** (⚠️ **which are not backups\neither — they usually share the same storage and the same fate**), **replication\n(sync vs async)**, **deduplication and compression.**\n**⚠️ Storage permissions are where file-level access governance actually lives**, and\n**NTFS\u002Fshare permission interaction, inheritance, and the accumulated mess of nested\ngroups is a perennial audit finding** (§7 → `itgov-directory-authentication-authorization-and-privileged-access`).\n\n---\n\n## §4. Networking\n\n**Layers and segmentation**: **VLANs**, **subnets**, **routing**, ⚠️ **microsegmentation\n— and the point of segmentation is blast radius: it limits lateral movement after an\ninitial compromise, which is the assumption you should be designing to.**\n**Firewalls** (stateful, NGFW), **load balancers**, **proxies**, **NAT**, **VPN**\n(⚠️ **site-to-site and remote access, and remote-access VPN is progressively being\ndisplaced by zero-trust network access, which authenticates per-application rather than\ngranting network presence**).\n**⚠️ DNS and DHCP are load-bearing and under-appreciated** — ⚠️ **a large share of \"the\nnetwork is down\" incidents are DNS**, and **in a Windows environment AD depends on DNS\nabsolutely** (§5 → `itgov-directory-authentication-authorization-and-privileged-access`).\n**WAN**: MPLS, SD-WAN, internet breakout. **NTP** — ⚠️ **time skew breaks Kerberos, logging\ncorrelation, and certificate validation, and it is the cause of a surprising number of\nauthentication failures** (§6 → `itgov-directory-authentication-authorization-and-privileged-access`).\n","# IT Infrastructure and Governance: The Layers, Compute and Virtualization, Storage, and Networking\n\n> **Part 1 of 5** of the *IT Infrastructure and Governance* reference (plugin `it-infrastructure-governance`), covering §0–§4. Sibling skills: `itgov-directory-authentication-authorization-and-privileged-access` (§5–§8), `itgov-identity-lifecycle-access-review-and-segregation-of-duties` (§9–§11), `itgov-endpoints-continuity-itsm-and-vendor-risk` (§12–§19), `itgov-reference` (§20–§26). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** RBAC theory, directory concepts, backup strategy and ITIL process are stable. Two areas moved. See §21 → `itgov-reference` for the phishing-resistant authentication mandate timeline and non-human identity governance.\n\n> **⚠️ Scope.** The enterprise on-prem and hybrid layer. **Complements a Linux server\n> administration reference (host-level operations), a cloud reference (cloud-native\n> patterns), and a security reference (threat modelling and defensive controls).**\n> ⚠️ **The through-line here is access: who and what can do what, how you know, and how\n> you prove it.**\n>\n> **⚠️ GOTCHA** boxes mark the things that cause audit findings and breaches.\n>\n> **The three ideas that organize this:**\n> 1. **⚠️ Identity is the perimeter.** The network boundary stopped being the control\n>    point years ago. **Every meaningful access decision now happens at authentication and\n>    authorization time** (§5 → `itgov-directory-authentication-authorization-and-privileged-access`, §6 → `itgov-directory-authentication-authorization-and-privileged-access`).\n> 2. **⚠️ Access accumulates and never sheds by itself.** People change roles and keep old\n>    permissions; service accounts outlive their systems. **Privilege creep is the default\n>    state of any system without deliberate revocation** (§9 → `itgov-identity-lifecycle-access-review-and-segregation-of-duties`, §10 → `itgov-identity-lifecycle-access-review-and-segregation-of-duties`).\n> 3. **⚠️ Governance is the ability to answer \"who has access to what, why, and who\n>    approved it\" — with evidence.** If you cannot answer it, you do not have governance,\n>    you have configuration (§10 → `itgov-identity-lifecycle-access-review-and-segregation-of-duties`, §17 → `itgov-endpoints-continuity-itsm-and-vendor-risk`).\n\n---\n\n## §0. Routing\n\n| You want... | Go to |\n|---|---|\n| Infrastructure layers | §1 |\n| Compute and virtualization | §2 |\n| Storage | §3 |\n| Networking | §4 |\n| **Directory services and hybrid identity** | **§5 → `itgov-directory-authentication-authorization-and-privileged-access`** |\n| **Authentication** | **§6 → `itgov-directory-authentication-authorization-and-privileged-access`** |\n| **Authorization: RBAC, ABAC and role explosion** | **§7 → `itgov-directory-authentication-authorization-and-privileged-access`** |\n| **Privileged access** | **§8 → `itgov-directory-authentication-authorization-and-privileged-access`** |\n| **Identity lifecycle (JML)** | **§9 → `itgov-identity-lifecycle-access-review-and-segregation-of-duties`** |\n| **Access review and certification** | **§10 → `itgov-identity-lifecycle-access-review-and-segregation-of-duties`** |\n| Segregation of duties | §11 → `itgov-identity-lifecycle-access-review-and-segregation-of-duties` |\n| Endpoint management and patching | §12 → `itgov-endpoints-continuity-itsm-and-vendor-risk` |\n| **Backup, DR and continuity** | **§13 → `itgov-endpoints-continuity-itsm-and-vendor-risk`** |\n| Monitoring and logging | §14 → `itgov-endpoints-continuity-itsm-and-vendor-risk` |\n| ITSM and change management | §15 → `itgov-endpoints-continuity-itsm-and-vendor-risk` |\n| Asset and configuration management | §16 → `itgov-endpoints-continuity-itsm-and-vendor-risk` |\n| **Governance frameworks** | **§17 → `itgov-endpoints-continuity-itsm-and-vendor-risk`** |\n| Capacity and lifecycle planning | §18 → `itgov-endpoints-continuity-itsm-and-vendor-risk` |\n| Vendor and third-party risk | §19 → `itgov-endpoints-continuity-itsm-and-vendor-risk` |\n| Anti-patterns | §20 → `itgov-reference` |\n| **What moved** | **§21 → `itgov-reference`** |\n| Misconceptions | §22 → `itgov-reference` |\n| Numbers | §23 → `itgov-reference` |\n| Books | §24 → `itgov-reference` |\n| Quick reference | §25 → `itgov-reference` |\n\n---\n\n## §1. The Layers\n\n```\nFACILITY      power, cooling, physical security  (see a power engineering reference §12)\nCOMPUTE       servers, hypervisors, containers\nSTORAGE       block, file, object; SAN\u002FNAS\nNETWORK       switching, routing, firewalls, load balancing, WAN\nPLATFORM      OS, middleware, databases\nIDENTITY      ⚠️ directory, authentication, authorization — the control plane\nAPPLICATION   the things people actually use\n⚠️ GOVERNANCE  policy, process, evidence — wraps all of it\n```\n**⚠️ The hybrid reality is the normal case and worth stating plainly**: **very few\norganizations are all-cloud or all-on-prem.** ⚠️ **Most run on-prem Active Directory\nsynchronized to a cloud identity provider, some workloads in a datacentre and some in\ncloud, and the seams between them are where both the operational pain and the security\ngaps live.**\n\n---\n\n## §2. Compute and Virtualization\n\n**Bare metal** — ⚠️ **still correct for latency-sensitive, licence-bound, or\nhardware-dependent workloads.**\n**Hypervisors**: **Type 1 (bare metal — ESXi, Hyper-V, KVM, Xen)** vs **Type 2 (hosted)**.\n**⚠️ Consolidation ratios, overcommit (memory and CPU), and the failure mode of\novercommitting: noisy neighbours and unpredictable latency.**\n**Clustering and HA**: **live migration, failover, anti-affinity rules** (⚠️ **so your two\nredundant VMs don't land on the same physical host — a classic and embarrassing outage\ncause**).\n**Containers** vs VMs — ⚠️ **different isolation boundaries; a container escape is a\ndifferent risk class from a VM escape.**\n**⚠️ Licensing is a genuine architectural constraint in enterprise virtualization** —\n**per-core, per-socket and per-VM models change the economics of consolidation\nsubstantially, and licence audits are a real financial exposure.**\n\n---\n\n## §3. Storage\n\n```\nBLOCK    SAN, iSCSI, FC — ⚠️ raw volumes; databases and VMs\nFILE     NAS, SMB\u002FCIFS, NFS — shared filesystems, permissions\nOBJECT   S3-compatible — ⚠️ flat namespace, HTTP, massive scale, no POSIX semantics\n```\n**RAID levels and their real trade-offs** — ⚠️ **RAID is not backup; it protects against\ndrive failure, not deletion, corruption or ransomware.**\n**Tiering, thin provisioning** (⚠️ **and the failure mode: over-provisioning until the\npool fills and everything stops at once**), **snapshots** (⚠️ **which are not backups\neither — they usually share the same storage and the same fate**), **replication\n(sync vs async)**, **deduplication and compression.**\n**⚠️ Storage permissions are where file-level access governance actually lives**, and\n**NTFS\u002Fshare permission interaction, inheritance, and the accumulated mess of nested\ngroups is a perennial audit finding** (§7 → `itgov-directory-authentication-authorization-and-privileged-access`).\n\n---\n\n## §4. Networking\n\n**Layers and segmentation**: **VLANs**, **subnets**, **routing**, ⚠️ **microsegmentation\n— and the point of segmentation is blast radius: it limits lateral movement after an\ninitial compromise, which is the assumption you should be designing to.**\n**Firewalls** (stateful, NGFW), **load balancers**, **proxies**, **NAT**, **VPN**\n(⚠️ **site-to-site and remote access, and remote-access VPN is progressively being\ndisplaced by zero-trust network access, which authenticates per-application rather than\ngranting network presence**).\n**⚠️ DNS and DHCP are load-bearing and under-appreciated** — ⚠️ **a large share of \"the\nnetwork is down\" incidents are DNS**, and **in a Windows environment AD depends on DNS\nabsolutely** (§5 → `itgov-directory-authentication-authorization-and-privileged-access`).\n**WAN**: MPLS, SD-WAN, internet breakout. **NTP** — ⚠️ **time skew breaks Kerberos, logging\ncorrelation, and certificate validation, and it is the cause of a surprising number of\nauthentication failures** (§6 → `itgov-directory-authentication-authorization-and-privileged-access`).\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fit-infrastructure-governance\u002Fskills\u002Fitgov-infrastructure-layers-compute-storage-and-networking",3,"https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey","https:\u002F\u002Fthe-vibey-project.github.io\u002Fvibey\u002F","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project","https:\u002F\u002Fvibewithadam.matthewsteinberger.com","freedom for software engineers","2026-11-15 05:47:42",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add the-vibey-project\u002Fvibey --skill itgov-infrastructure-layers-compute-storage-and-networking",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill itgov-infrastructure-layers-compute-storage-and-networking",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill itgov-infrastructure-layers-compute-storage-and-networking","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fit-infrastructure-governance\u002Fskills\u002Fitgov-infrastructure-layers-compute-storage-and-networking\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7AT1FQJAE1FQYAMDTF490Y4","white-paper-writing","Use when writing white papers, technical reports, policy documents, thought leadership pieces, or any long-form authoritative document. Triggers on requests to write, structure, outline, or review white papers, technical reports, position papers, policy briefs, or evidence-driven arguments. Also use for B2B content marketing strategy, technical documentation requiring authority, academic-style reports, or any document that must educate while persuading. Use when someone asks \"how should I structure this\" for a long-form document.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fwhite-paper-writing\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7AT16BJRJJKK2MASXRZS76G","prose-technical-mechanics","Use when editing or writing prose at a technical\u002Fmechanical level: choosing between Anglo-Saxon and Latinate diction, placing information in topic vs stress positions, writing periodic vs cumulative sentences, handling sentence rhythm, punctuation as logic, transitions, paragraph structure, or phonesthetics. Use when someone wants to understand WHY prose works or doesn't, not just surface-level style advice. Triggers on word choice, sentence structure, emphasis, rhythm, diction, or any deep writing mechanics question.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-technical-mechanics\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7AT0W9HT0ZZ9Y287NW99MR3","prose-mechanics","Use when writing, editing, or analyzing prose style; when trying to avoid generic AI-sounding writing; when applying specific prose styles such as journalistic, academic, narrative, KJV biblical, Hemingway plain, Latinate\u002FJamesian, Orwellian, Augustan, Victorian, Early Modern (Bacon, Browne, Milton), or free indirect discourse; or when coaching someone on writing voice and mechanics. Triggers on any request to improve, analyze, or write in a specific prose style, to fix \"AI-sounding\" writing, to make prose more vivid or concrete, to vary sentence rhythm, or to understand how a particular writer achieves their effects.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-mechanics\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AT0KR635JX66X2X6F3E2CP","narrative-structure","Use when structuring stories, pitches, presentations, white papers, or any persuasive narrative; analyzing the hero's journey in fiction or non-fiction; applying StoryBrand for business communication; designing narrative arcs for thought leadership; or understanding Vogler, Snyder, Propp, or Campbell frameworks. Triggers on any narrative structure, storytelling, pitch structure, StoryBrand, hero's journey, three-act structure, Freytag, Save the Cat, narrative arc, or \"how should I structure this story\u002Fpitch\u002Fpresentation\" request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fnarrative-structure\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AT0AKGW09NKKZDYBT8VRDE","legal-brief-writing","Use when writing legal briefs, motions, or any court filing; when analyzing judicial cognition and persuasion; when applying elite brief-writing techniques from Roberts, Clement, Kagan, Garner; or when structuring legal arguments for maximum persuasion. Also use for autistic\u002Fneurodivergent advocates who need to understand how their natural communication style maps to elite legal advocacy. Triggers on any legal writing, brief drafting, motion preparation, or legal argument structuring request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Flegal-brief-writing\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7AT00VWPS4Q8B5VEMXX9NQT","journal-publishability-criteria","Use whenever a research paper, article or preprint is being written, revised, reviewed or published, and specifically before every publication of docs\u002Fpaper.md. Covers what legitimate journals actually gate on, in order of gating — the editor's desk screen (scope, novelty, package problems), what reviewers judge (methodological soundness, claims the evidence can carry, statistical and qualitative reporting), EQUATOR reporting guidelines, the ICMJE authorship criteria, COPE's view of text recycling, the near-universal generative-AI policy (no AI author, disclosure, author responsibility), TOP 2025 transparency standards, how to verify a journal is legitimate, submitting without an institution, and a pre-submission checklist. Triggers on requests to evaluate, review, prepare or submit a paper, to judge publishability, to write a declarations or data-availability section, to disclose AI use, or to check a journal.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fjournal-publishability-criteria\u002FSKILL.md",[],[]]