[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASD3A45XWYC52C9RYAW7SZ":3,"skill-same:01M7ASD3A45XWYC52C9RYAW7SZ":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},"01M7ASD3A45XWYC52C9RYAW7SZ","toc-beyond-np-space-and-distributed-limits",null,"Use when the hardness question goes past NP or into distributed systems: the polynomial hierarchy, PSPACE and counting classes, fine-grained complexity and conditional lower bounds (SETH, 3SUM, APSP), space complexity, streaming and sublinear algorithms, and the distributed computing impossibility results — FLP, CAP and consensus — with their honest practical readings.","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\u002Ftheory-of-computation\u002Fskills\u002Ftoc-beyond-np-space-and-distributed-limits\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: toc-beyond-np-space-and-distributed-limits\ndescription: \"Use when the hardness question goes past NP or into distributed systems: the polynomial hierarchy, PSPACE and counting classes, fine-grained complexity and conditional lower bounds (SETH, 3SUM, APSP), space complexity, streaming and sublinear algorithms, and the distributed computing impossibility results — FLP, CAP and consensus — with their honest practical readings.\"\n---\n\n# Theory of Computation: Beyond NP, Space and Streaming, and Distributed Impossibility Results\n\n> **Part 3 of 5** of the *Theory of Computation* reference (plugin `theory-of-computation`), covering §8–§11. Sibling skills: `toc-automata-regex-and-parsing` (§0–§3), `toc-computability-and-complexity` (§4–§7), `toc-type-systems-and-randomization` (§12–§13), `toc-reference` (§14–§19). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** Verified August 2026. See §16 → `toc-reference` for the currency snapshot and what goes stale first.\n\n> **How to read this.** Reference, not a course. Three markers:\n> - **[DURABLE]** — proven theorems and stable practice. **This is most of the document,\n>   and it does not expire.**\n> - **[VERSIONED]** — the small moving parts: recent results, solver capability, open\n>   problems.\n> - **[CONTESTED]** — genuine disagreement, mostly about pedagogy and practical relevance.\n>\n> **⚠️ GOTCHA** boxes mark places where ignorance of the theory produces a specific,\n> expensive production failure — which is the whole argument for learning it.\n>\n> **The three framings that organize everything below:**\n> 1. **This is the only branch of CS that tells you what you cannot do.** Everything else\n>    teaches techniques. Theory tells you when to stop looking — and **knowing a problem is\n>    undecidable or NP-hard is more valuable than any algorithm**, because it redirects\n>    you from an impossible goal to a tractable approximation of it.\n> 2. **You already use it; you may not know the names.** Regex is finite automata.\n>    Your parser is a pushdown automaton. Your state machine is a DFA. Your build system's\n>    cycle detection is graph theory. **The theory isn't an addition to your practice — it's\n>    a description of it**, and knowing the description tells you where the edges are.\n> 3. **\"Hard\" is not \"impossible,\" and this is the most consequential practical point.**\n>    NP-complete problems with thousands of variables are solved routinely (§9). The\n>    theory tells you *no algorithm is fast on all inputs* — it says nothing about\n>    **your** inputs, which are usually structured. **Treating NP-hardness as a verdict\n>    rather than a warning is the single most common misapplication of this material.**\n\n---\n\n## §8. Beyond NP\n\n**[DURABLE] Worth knowing the landscape so you recognize when you're in worse trouble than\nNP.**\n\n**PSPACE** — solvable in polynomial *space*, any amount of time. **PSPACE-complete\nproblems include quantified Boolean formulas (QBF), most two-player games, and many\nplanning problems.** ⚠️ **The tell: alternating quantifiers.** \"Is there a move such that\nfor all responses there is a move such that…\" That's QBF, that's PSPACE, and **it is a\nqualitatively harder thing than a single existential search.** If your problem has an\nadversary, you are probably here.\n\n**EXPTIME** and above — **provably harder than P** (by the time hierarchy theorem, this\none is not conjectural). Generalized games on n×n boards, some type-system and logic\ndecision problems.\n\n**Undecidable** — §4 → `toc-computability-and-complexity`.\n\n**[DURABLE] The hierarchy theorems are among the few unconditional separations we have**:\nmore time and more space strictly buy you more. Almost everything else in §5 → `toc-computability-and-complexity`'s map is open.\n\n---\n\n## §9. Fine-Grained Complexity\n\n**[DURABLE, and under-taught relative to its practical value.]** Classical complexity asks\n\"polynomial or not.\" **Fine-grained complexity asks: is my O(n²) algorithm actually\noptimal?** — and it answers via **conditional lower bounds**.\n\n**The method**: assume a hardness conjecture, then use **fine-grained reductions** — so\ntight that any improvement to the target implies an improvement to the source — to transfer\nhardness. **The core conjectures**: **SETH** (the Strong Exponential Time Hypothesis: for\nany ε > 0 there's a k such that k-SAT can't be solved in 2^((1-ε)n)), **the Orthogonal\nVectors hypothesis**, **3SUM**, and **APSP**.\n\n**[DURABLE] Why an engineer should care**: it tells you when to stop optimizing.\nWell-known results in this line establish, under SETH, that **Edit Distance and Longest\nCommon Subsequence have no strongly subquadratic algorithm**, that **Orthogonal Vectors\nneeds n²**, and that **Bellman's classic O(nT) Subset Sum algorithm can't be substantially\nimproved.** Similar conditional bounds cover graph diameter approximation, dominating set,\nand a range of computational-geometry problems.\n\n**⚠️ The engineering translation: if your string-diff is quadratic, that is very likely not\nyour fault, and no amount of profiling will fix it.** The right move is to change the\nproblem — restrict the input, exploit structure, approximate, or use a different similarity\nmeasure — not to keep optimizing the constant.\n\n**⚠️ These are conditional results.** If SETH is false the bounds evaporate — but SETH has\nsurvived decades of attack and is treated as a working assumption.\n\n**[VERSIONED] Quantum analogues exist and are active** (§16 → `toc-reference`): SETH itself fails quantumly\nbecause Grover solves CNF-SAT in about 2^(n\u002F2), so researchers built **QSETH** frameworks\nto get meaningful quantum conditional lower bounds instead.\n\n---\n\n## §10. Space and Memory\n\n**[DURABLE] Space is the resource engineers under-model.** The classes: **L** (logarithmic\nspace — you can hold a constant number of pointers, not a copy of the input), **NL**,\n**PSPACE**.\n\n**Two results worth carrying:**\n- **Savitch's theorem**: NSPACE(f) ⊆ SPACE(f²) — **nondeterminism buys you much less in\n  space than in time.**\n- **Reingold's theorem** (2005): **undirected s-t connectivity is in log space** — a\n  genuinely surprising result, and the directed case remains the standing open challenge.\n\n**[DURABLE] Streaming and sublinear algorithms are the applied face of space complexity**,\nand they're everywhere in production infrastructure: **HyperLogLog** (cardinality in\nkilobytes), **Count-Min Sketch** (frequency estimation), **Bloom filters** (membership with\none-sided error), **reservoir sampling**. **If you have a \"count distinct over a firehose\"\nproblem, the theory already solved it** — and the solution trades exactness for a bounded\nerror you choose.\n\n**[VERSIONED — the one genuinely major recent theorem in this document.]** In **February\n2025, Ryan Williams proved TIME[t] ⊆ SPACE[√(t log t)]** — every multitape Turing machine\nrunning in time t can be simulated in **O(√(t log t))** space. This replaced the\n**Hopcroft–Paul–Valiant bound of t\u002Flog t that had stood since 1975**, a near-quadratic\nimprovement described in the field as \"an earthquake of a result\" and \"a true classic\ncomplexity theorem.\" The proof reduces time-t computation to **Tree Evaluation** and\napplies the **Cook–Mertz** space-efficient algorithm from the catalytic-computing line.\n\n**⚠️ Read this correctly.** It is a **space** simulation — **it does not preserve the time\nbound**, so it is not an algorithm you deploy tomorrow. **Its significance is theoretical**:\nit is a real step toward separating **P from PSPACE**, and it demolished a decades-old\nbelief about what was possible. **The engineering-adjacent lesson is epistemic**: a\n50-year-old \"obvious barrier\" fell, which is worth remembering whenever someone says\nsomething is known to be impossible when what they mean is that nobody has done it.\n\n---\n\n## §11. Distributed Computing Impossibility Results\n\n**[DURABLE] Theory's most immediately actionable contribution to systems engineering.**\nThese are theorems, not architectural opinions, and violating them is not a design\ntrade-off — it's a claim to have solved something proven impossible.\n\n**FLP impossibility (1985)**: **in an asynchronous system with even one faulty process,\nthere is no deterministic algorithm guaranteeing consensus.** ⚠️ **This is why every real\nconsensus protocol uses timeouts, randomization, or a partial-synchrony assumption** —\nPaxos and Raft don't refute FLP, they add an assumption FLP excludes. **Anyone claiming\ndeterministic asynchronous consensus is wrong.**\n\n**CAP**: under network **partition**, choose consistency or availability. **⚠️ CAP is\nroutinely over-applied.** It is about behaviour *during a partition*, not a general licence\nto be inconsistent, and the more useful modern framing is **PACELC**: under Partition,\nchoose A or C; **Else**, choose Latency or Consistency — which is the trade-off you're\nactually making 99.9% of the time.\n\n**The Two Generals Problem**: no protocol achieves guaranteed agreement over a lossy\nchannel. **⚠️ This is why exactly-once delivery does not exist**, and why the achievable\ntarget is at-least-once plus idempotency (which is why §3 → `toc-automata-regex-and-parsing` of a payments reference and this\nparagraph are the same fact).\n\n**Byzantine fault tolerance**: tolerating arbitrary (malicious) faults requires **n > 3f**\nnodes for f faults.\n\n**Linearizability, serializability, and the consistency zoo** — these are formal\ndefinitions with precise meanings, and **\"eventual consistency\" without specifying which\nmodel is not a specification.**\n\n**[DURABLE] The practical instruction**: when a design assumes reliable delivery, ordered\ndelivery, synchronized clocks, or partition-free operation, **name the assumption\nexplicitly** — because you have just chosen a side of one of these theorems, and it should\nbe a decision rather than an accident.\n","# Theory of Computation: Beyond NP, Space and Streaming, and Distributed Impossibility Results\n\n> **Part 3 of 5** of the *Theory of Computation* reference (plugin `theory-of-computation`), covering §8–§11. Sibling skills: `toc-automata-regex-and-parsing` (§0–§3), `toc-computability-and-complexity` (§4–§7), `toc-type-systems-and-randomization` (§12–§13), `toc-reference` (§14–§19). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** Verified August 2026. See §16 → `toc-reference` for the currency snapshot and what goes stale first.\n\n> **How to read this.** Reference, not a course. Three markers:\n> - **[DURABLE]** — proven theorems and stable practice. **This is most of the document,\n>   and it does not expire.**\n> - **[VERSIONED]** — the small moving parts: recent results, solver capability, open\n>   problems.\n> - **[CONTESTED]** — genuine disagreement, mostly about pedagogy and practical relevance.\n>\n> **⚠️ GOTCHA** boxes mark places where ignorance of the theory produces a specific,\n> expensive production failure — which is the whole argument for learning it.\n>\n> **The three framings that organize everything below:**\n> 1. **This is the only branch of CS that tells you what you cannot do.** Everything else\n>    teaches techniques. Theory tells you when to stop looking — and **knowing a problem is\n>    undecidable or NP-hard is more valuable than any algorithm**, because it redirects\n>    you from an impossible goal to a tractable approximation of it.\n> 2. **You already use it; you may not know the names.** Regex is finite automata.\n>    Your parser is a pushdown automaton. Your state machine is a DFA. Your build system's\n>    cycle detection is graph theory. **The theory isn't an addition to your practice — it's\n>    a description of it**, and knowing the description tells you where the edges are.\n> 3. **\"Hard\" is not \"impossible,\" and this is the most consequential practical point.**\n>    NP-complete problems with thousands of variables are solved routinely (§9). The\n>    theory tells you *no algorithm is fast on all inputs* — it says nothing about\n>    **your** inputs, which are usually structured. **Treating NP-hardness as a verdict\n>    rather than a warning is the single most common misapplication of this material.**\n\n---\n\n## §8. Beyond NP\n\n**[DURABLE] Worth knowing the landscape so you recognize when you're in worse trouble than\nNP.**\n\n**PSPACE** — solvable in polynomial *space*, any amount of time. **PSPACE-complete\nproblems include quantified Boolean formulas (QBF), most two-player games, and many\nplanning problems.** ⚠️ **The tell: alternating quantifiers.** \"Is there a move such that\nfor all responses there is a move such that…\" That's QBF, that's PSPACE, and **it is a\nqualitatively harder thing than a single existential search.** If your problem has an\nadversary, you are probably here.\n\n**EXPTIME** and above — **provably harder than P** (by the time hierarchy theorem, this\none is not conjectural). Generalized games on n×n boards, some type-system and logic\ndecision problems.\n\n**Undecidable** — §4 → `toc-computability-and-complexity`.\n\n**[DURABLE] The hierarchy theorems are among the few unconditional separations we have**:\nmore time and more space strictly buy you more. Almost everything else in §5 → `toc-computability-and-complexity`'s map is open.\n\n---\n\n## §9. Fine-Grained Complexity\n\n**[DURABLE, and under-taught relative to its practical value.]** Classical complexity asks\n\"polynomial or not.\" **Fine-grained complexity asks: is my O(n²) algorithm actually\noptimal?** — and it answers via **conditional lower bounds**.\n\n**The method**: assume a hardness conjecture, then use **fine-grained reductions** — so\ntight that any improvement to the target implies an improvement to the source — to transfer\nhardness. **The core conjectures**: **SETH** (the Strong Exponential Time Hypothesis: for\nany ε > 0 there's a k such that k-SAT can't be solved in 2^((1-ε)n)), **the Orthogonal\nVectors hypothesis**, **3SUM**, and **APSP**.\n\n**[DURABLE] Why an engineer should care**: it tells you when to stop optimizing.\nWell-known results in this line establish, under SETH, that **Edit Distance and Longest\nCommon Subsequence have no strongly subquadratic algorithm**, that **Orthogonal Vectors\nneeds n²**, and that **Bellman's classic O(nT) Subset Sum algorithm can't be substantially\nimproved.** Similar conditional bounds cover graph diameter approximation, dominating set,\nand a range of computational-geometry problems.\n\n**⚠️ The engineering translation: if your string-diff is quadratic, that is very likely not\nyour fault, and no amount of profiling will fix it.** The right move is to change the\nproblem — restrict the input, exploit structure, approximate, or use a different similarity\nmeasure — not to keep optimizing the constant.\n\n**⚠️ These are conditional results.** If SETH is false the bounds evaporate — but SETH has\nsurvived decades of attack and is treated as a working assumption.\n\n**[VERSIONED] Quantum analogues exist and are active** (§16 → `toc-reference`): SETH itself fails quantumly\nbecause Grover solves CNF-SAT in about 2^(n\u002F2), so researchers built **QSETH** frameworks\nto get meaningful quantum conditional lower bounds instead.\n\n---\n\n## §10. Space and Memory\n\n**[DURABLE] Space is the resource engineers under-model.** The classes: **L** (logarithmic\nspace — you can hold a constant number of pointers, not a copy of the input), **NL**,\n**PSPACE**.\n\n**Two results worth carrying:**\n- **Savitch's theorem**: NSPACE(f) ⊆ SPACE(f²) — **nondeterminism buys you much less in\n  space than in time.**\n- **Reingold's theorem** (2005): **undirected s-t connectivity is in log space** — a\n  genuinely surprising result, and the directed case remains the standing open challenge.\n\n**[DURABLE] Streaming and sublinear algorithms are the applied face of space complexity**,\nand they're everywhere in production infrastructure: **HyperLogLog** (cardinality in\nkilobytes), **Count-Min Sketch** (frequency estimation), **Bloom filters** (membership with\none-sided error), **reservoir sampling**. **If you have a \"count distinct over a firehose\"\nproblem, the theory already solved it** — and the solution trades exactness for a bounded\nerror you choose.\n\n**[VERSIONED — the one genuinely major recent theorem in this document.]** In **February\n2025, Ryan Williams proved TIME[t] ⊆ SPACE[√(t log t)]** — every multitape Turing machine\nrunning in time t can be simulated in **O(√(t log t))** space. This replaced the\n**Hopcroft–Paul–Valiant bound of t\u002Flog t that had stood since 1975**, a near-quadratic\nimprovement described in the field as \"an earthquake of a result\" and \"a true classic\ncomplexity theorem.\" The proof reduces time-t computation to **Tree Evaluation** and\napplies the **Cook–Mertz** space-efficient algorithm from the catalytic-computing line.\n\n**⚠️ Read this correctly.** It is a **space** simulation — **it does not preserve the time\nbound**, so it is not an algorithm you deploy tomorrow. **Its significance is theoretical**:\nit is a real step toward separating **P from PSPACE**, and it demolished a decades-old\nbelief about what was possible. **The engineering-adjacent lesson is epistemic**: a\n50-year-old \"obvious barrier\" fell, which is worth remembering whenever someone says\nsomething is known to be impossible when what they mean is that nobody has done it.\n\n---\n\n## §11. Distributed Computing Impossibility Results\n\n**[DURABLE] Theory's most immediately actionable contribution to systems engineering.**\nThese are theorems, not architectural opinions, and violating them is not a design\ntrade-off — it's a claim to have solved something proven impossible.\n\n**FLP impossibility (1985)**: **in an asynchronous system with even one faulty process,\nthere is no deterministic algorithm guaranteeing consensus.** ⚠️ **This is why every real\nconsensus protocol uses timeouts, randomization, or a partial-synchrony assumption** —\nPaxos and Raft don't refute FLP, they add an assumption FLP excludes. **Anyone claiming\ndeterministic asynchronous consensus is wrong.**\n\n**CAP**: under network **partition**, choose consistency or availability. **⚠️ CAP is\nroutinely over-applied.** It is about behaviour *during a partition*, not a general licence\nto be inconsistent, and the more useful modern framing is **PACELC**: under Partition,\nchoose A or C; **Else**, choose Latency or Consistency — which is the trade-off you're\nactually making 99.9% of the time.\n\n**The Two Generals Problem**: no protocol achieves guaranteed agreement over a lossy\nchannel. **⚠️ This is why exactly-once delivery does not exist**, and why the achievable\ntarget is at-least-once plus idempotency (which is why §3 → `toc-automata-regex-and-parsing` of a payments reference and this\nparagraph are the same fact).\n\n**Byzantine fault tolerance**: tolerating arbitrary (malicious) faults requires **n > 3f**\nnodes for f faults.\n\n**Linearizability, serializability, and the consistency zoo** — these are formal\ndefinitions with precise meanings, and **\"eventual consistency\" without specifying which\nmodel is not a specification.**\n\n**[DURABLE] The practical instruction**: when a design assumes reliable delivery, ordered\ndelivery, synchronized clocks, or partition-free operation, **name the assumption\nexplicitly** — because you have just chosen a side of one of these theorems, and it should\nbe a decision rather than an accident.\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Ftheory-of-computation\u002Fskills\u002Ftoc-beyond-np-space-and-distributed-limits",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 toc-beyond-np-space-and-distributed-limits",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill toc-beyond-np-space-and-distributed-limits",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill toc-beyond-np-space-and-distributed-limits","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Ftheory-of-computation\u002Fskills\u002Ftoc-beyond-np-space-and-distributed-limits\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",[],[]]