[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AMRFZY556XVQSAGDGJ2T06":3,"skill-same:01M7AMRFZY556XVQSAGDGJ2T06":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},"01M7AMRFZY556XVQSAGDGJ2T06","building-accessibility-energy-drawings-bim-and-codes",null,"Use for the regulated and documented layer: accessibility requirements and the design consequences, energy and comfort including thermal comfort criteria and performance modelling, drawings, specifications and BIM as the actual deliverable and coordination mechanism, and codes and permitting — how the code is structured, what is prescriptive versus performance-based, and how approvals work.","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\u002Fdesigning-and-building-buildings\u002Fskills\u002Fbuilding-accessibility-energy-drawings-bim-and-codes\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: building-accessibility-energy-drawings-bim-and-codes\ndescription: \"Use for the regulated and documented layer: accessibility requirements and the design consequences, energy and comfort including thermal comfort criteria and performance modelling, drawings, specifications and BIM as the actual deliverable and coordination mechanism, and codes and permitting — how the code is structured, what is prescriptive versus performance-based, and how approvals work.\"\n---\n\n# Buildings and Civil Structures: Accessibility, Energy and Comfort, Drawings, Specifications and BIM, and Codes and Permitting\n\n> **Part 3 of 6** of the *Designing and Building Buildings and Other Civil Structures* reference (plugin `designing-and-building-buildings`), covering §11–§14. Sibling skills: `building-disciplines-site-brief-planning-and-design` (§0–§5), `building-structure-foundations-envelope-services-and-fire` (§6–§10), `building-procurement-cost-sequencing-materials-and-quality` (§15–§19), `building-site-safety-commissioning-retrofit-and-why-projects-fail` (§20–§23), `building-reference` (§24–§29). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** The engineering is settled. Two areas moved. See §24 → `building-reference` for tall mass timber code adoption, and embodied carbon regulation.\n\n> **⚠️ The practice companion to a civil\u002Findustrial engineering reference.** ⚠️ **That one\n> translates concepts for outsiders — factor of safety, codes as accumulated failure logs,\n> the megaproject estimation record.** **This one is how the work is actually done.**\n>\n> **⚠️ The organizing reality: a building is a MULTI-DISCIPLINARY SYSTEM delivered by\n> parties with different contracts, different liabilities and different incentives.**\n> ⚠️ **Most building failures are not engineering failures — they are COORDINATION\n> failures at the boundaries between disciplines and between design and construction**\n> (§23 → `building-site-safety-commissioning-retrofit-and-why-projects-fail`).\n>\n> **⚠️ GOTCHA** boxes mark the assumptions that cause litigation.\n>\n> **⚠️ Scope note**: ⚠️ **structural, fire and geotechnical design are licensed activities\n> in most jurisdictions for good reason. This is a map of the territory, not a\n> substitute for a qualified engineer or a local code review.**\n>\n> **The three ideas that organize this document:**\n> 1. **⚠️ Design decisions bind cost early and irreversibly** (§1 → `building-disciplines-site-brief-planning-and-design`, §16 → `building-procurement-cost-sequencing-materials-and-quality`). **Most of a\n>    building's cost and carbon are committed during concept design, when almost nothing\n>    has been spent.**\n> 2. **⚠️ WATER destroys more buildings than structural failure** (§8 → `building-structure-foundations-envelope-services-and-fire`). **Envelope and\n>    moisture management cause the overwhelming majority of building defects, claims and\n>    premature failures — and they are the least glamorous part of the job.**\n> 3. **⚠️ Load paths and lateral systems are the two things a structure is** (§6 → `building-structure-foundations-envelope-services-and-fire`).\n>    **Gravity is the obvious problem; wind and seismic are the ones that govern.**\n\n---\n\n## §11. Accessibility\n\n**⚠️ A legal requirement and a design quality issue, and treating it as the former only\nproduces bad buildings.**\n**⚠️ Typical requirements**: **accessible routes and entrances, ⚠️ gradients and ramps,\ndoor widths and clear opening, manoeuvring space, sanitary accommodation, lift provision,\n⚠️ means of escape for disabled occupants (refuges and evacuation lifts — frequently\noverlooked), signage, acoustics and lighting for sensory impairment.**\n**⚠️ Standards**: **ADA and ANSI A117.1 (US), Approved Document M and BS 8300 (UK), and\nequivalents elsewhere.**\n**⚠️ Universal design is the better framing** — ⚠️ **designing for the widest range of\nusers produces buildings that work better for everyone, and retrofitting accessibility is\nfar more expensive than designing it in.**\n\n---\n\n## §12. Energy and Comfort\n\n**⚠️ The load-order principle**: ⚠️ **reduce demand → use passive measures → efficient\nsystems → renewables.** **⚠️ Doing this in the wrong order produces oversized plant on a\nleaky building.**\n**⚠️ Passive measures**: **orientation, form factor (⚠️ surface-to-volume ratio, which\ncompact buildings win on), insulation continuity, airtightness, shading (⚠️ external\nshading is far more effective than internal), glazing ratio, thermal mass, and natural\nventilation.**\n**⚠️ Comfort is not temperature alone** — ⚠️ **it's operative temperature, humidity, air\nmovement, radiant asymmetry and clothing\u002Factivity, and the ADAPTIVE comfort model shows\noccupants accept a wider range in naturally ventilated buildings than in sealed ones.**\n> **⚠️ GOTCHA — THE PERFORMANCE GAP is real and well documented.** ⚠️ **Buildings routinely\n> use substantially more energy than their design models predicted.** **⚠️ Causes:\n> modelling assumptions versus real occupancy, construction quality (thermal bridging and\n> air leakage as built), controls that were never commissioned properly (§21 → `building-site-safety-commissioning-retrofit-and-why-projects-fail`), and\n> occupants defeating systems that annoy them.**\n> **⚠️ The lesson is that predicted performance is a design intention, and measured\n> performance requires commissioning, metering and someone paying attention afterwards.**\n\n---\n\n# PART III — DOCUMENTATION AND DELIVERY\n\n## §13. Drawings, Specifications and BIM\n\n**⚠️ The drawings say WHERE and HOW BIG; the specification says WHAT and HOW GOOD.**\n⚠️ **Conflicts between them are resolved by a stated precedence clause in the contract —\nand if you don't know which governs, that's a problem waiting.**\n**⚠️ Specification types**: ⚠️ **PRESCRIPTIVE (name the product) versus PERFORMANCE (state\nthe requirement and let the contractor propose).** **⚠️ Performance specs transfer design\nrisk and require you to be able to judge what comes back.**\n**⚠️ BIM**: ⚠️ **a coordinated 3D model with data, used for clash detection, quantities,\nsequencing (4D) and cost (5D).** **⚠️ Levels of detail\u002Fdevelopment matter — a model element\nat concept LOD is not a fabrication instruction, and treating it as one causes real\nerrors.**\n**⚠️ What BIM genuinely delivers**: **geometric clash detection and coordinated\nquantities.** ⚠️ **What it does not: constructability judgement, tolerance reality, or\nmaintenance access** (§9 → `building-structure-foundations-envelope-services-and-fire`).\n**⚠️ RFIs and submittals** are the formal question-and-approval mechanism during\nconstruction — ⚠️ **and RFI volume is a decent proxy for documentation quality.**\n\n---\n\n## §14. ⚠️ Codes and Permitting\n\n**⚠️ Codes are law where adopted, and adoption is LOCAL** (§24.1 → `building-reference`).\n```\n⚠️ THE STRUCTURE  model codes (⚠️ IBC\u002FIRC\u002FIFC and the I-Codes;\n   Eurocodes; national building regulations) → adopted by\n   jurisdiction, ⚠️ frequently WITH AMENDMENTS → interpreted by\n   the local authority having jurisdiction (AHJ)\n⚠️ THEREFORE  ⚠️ the model code is not the law. The ADOPTED and\n   AMENDED version in that jurisdiction is, and editions lag —\n   a state may still be several cycles behind (§24.1)\n⚠️ REFERENCED STANDARDS  ⚠️ codes incorporate standards by reference\n   (ASCE 7 for loads, ACI 318 for concrete, AISC 360 for steel,\n   NFPA for fire), and the referenced EDITION matters\n⚠️ THE PROCESS  permit application → plan review → permits →\n   ⚠️ INSPECTIONS at defined hold points → certificate of occupancy\n⚠️ SPECIAL INSPECTIONS  independent verification of critical work\n   (§19)\n```\n**⚠️ Alternative means and methods** allow non-prescriptive solutions where equivalence is\ndemonstrated — ⚠️ **the route for innovation, and it costs time and review.**\n","# Buildings and Civil Structures: Accessibility, Energy and Comfort, Drawings, Specifications and BIM, and Codes and Permitting\n\n> **Part 3 of 6** of the *Designing and Building Buildings and Other Civil Structures* reference (plugin `designing-and-building-buildings`), covering §11–§14. Sibling skills: `building-disciplines-site-brief-planning-and-design` (§0–§5), `building-structure-foundations-envelope-services-and-fire` (§6–§10), `building-procurement-cost-sequencing-materials-and-quality` (§15–§19), `building-site-safety-commissioning-retrofit-and-why-projects-fail` (§20–§23), `building-reference` (§24–§29). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** The engineering is settled. Two areas moved. See §24 → `building-reference` for tall mass timber code adoption, and embodied carbon regulation.\n\n> **⚠️ The practice companion to a civil\u002Findustrial engineering reference.** ⚠️ **That one\n> translates concepts for outsiders — factor of safety, codes as accumulated failure logs,\n> the megaproject estimation record.** **This one is how the work is actually done.**\n>\n> **⚠️ The organizing reality: a building is a MULTI-DISCIPLINARY SYSTEM delivered by\n> parties with different contracts, different liabilities and different incentives.**\n> ⚠️ **Most building failures are not engineering failures — they are COORDINATION\n> failures at the boundaries between disciplines and between design and construction**\n> (§23 → `building-site-safety-commissioning-retrofit-and-why-projects-fail`).\n>\n> **⚠️ GOTCHA** boxes mark the assumptions that cause litigation.\n>\n> **⚠️ Scope note**: ⚠️ **structural, fire and geotechnical design are licensed activities\n> in most jurisdictions for good reason. This is a map of the territory, not a\n> substitute for a qualified engineer or a local code review.**\n>\n> **The three ideas that organize this document:**\n> 1. **⚠️ Design decisions bind cost early and irreversibly** (§1 → `building-disciplines-site-brief-planning-and-design`, §16 → `building-procurement-cost-sequencing-materials-and-quality`). **Most of a\n>    building's cost and carbon are committed during concept design, when almost nothing\n>    has been spent.**\n> 2. **⚠️ WATER destroys more buildings than structural failure** (§8 → `building-structure-foundations-envelope-services-and-fire`). **Envelope and\n>    moisture management cause the overwhelming majority of building defects, claims and\n>    premature failures — and they are the least glamorous part of the job.**\n> 3. **⚠️ Load paths and lateral systems are the two things a structure is** (§6 → `building-structure-foundations-envelope-services-and-fire`).\n>    **Gravity is the obvious problem; wind and seismic are the ones that govern.**\n\n---\n\n## §11. Accessibility\n\n**⚠️ A legal requirement and a design quality issue, and treating it as the former only\nproduces bad buildings.**\n**⚠️ Typical requirements**: **accessible routes and entrances, ⚠️ gradients and ramps,\ndoor widths and clear opening, manoeuvring space, sanitary accommodation, lift provision,\n⚠️ means of escape for disabled occupants (refuges and evacuation lifts — frequently\noverlooked), signage, acoustics and lighting for sensory impairment.**\n**⚠️ Standards**: **ADA and ANSI A117.1 (US), Approved Document M and BS 8300 (UK), and\nequivalents elsewhere.**\n**⚠️ Universal design is the better framing** — ⚠️ **designing for the widest range of\nusers produces buildings that work better for everyone, and retrofitting accessibility is\nfar more expensive than designing it in.**\n\n---\n\n## §12. Energy and Comfort\n\n**⚠️ The load-order principle**: ⚠️ **reduce demand → use passive measures → efficient\nsystems → renewables.** **⚠️ Doing this in the wrong order produces oversized plant on a\nleaky building.**\n**⚠️ Passive measures**: **orientation, form factor (⚠️ surface-to-volume ratio, which\ncompact buildings win on), insulation continuity, airtightness, shading (⚠️ external\nshading is far more effective than internal), glazing ratio, thermal mass, and natural\nventilation.**\n**⚠️ Comfort is not temperature alone** — ⚠️ **it's operative temperature, humidity, air\nmovement, radiant asymmetry and clothing\u002Factivity, and the ADAPTIVE comfort model shows\noccupants accept a wider range in naturally ventilated buildings than in sealed ones.**\n> **⚠️ GOTCHA — THE PERFORMANCE GAP is real and well documented.** ⚠️ **Buildings routinely\n> use substantially more energy than their design models predicted.** **⚠️ Causes:\n> modelling assumptions versus real occupancy, construction quality (thermal bridging and\n> air leakage as built), controls that were never commissioned properly (§21 → `building-site-safety-commissioning-retrofit-and-why-projects-fail`), and\n> occupants defeating systems that annoy them.**\n> **⚠️ The lesson is that predicted performance is a design intention, and measured\n> performance requires commissioning, metering and someone paying attention afterwards.**\n\n---\n\n# PART III — DOCUMENTATION AND DELIVERY\n\n## §13. Drawings, Specifications and BIM\n\n**⚠️ The drawings say WHERE and HOW BIG; the specification says WHAT and HOW GOOD.**\n⚠️ **Conflicts between them are resolved by a stated precedence clause in the contract —\nand if you don't know which governs, that's a problem waiting.**\n**⚠️ Specification types**: ⚠️ **PRESCRIPTIVE (name the product) versus PERFORMANCE (state\nthe requirement and let the contractor propose).** **⚠️ Performance specs transfer design\nrisk and require you to be able to judge what comes back.**\n**⚠️ BIM**: ⚠️ **a coordinated 3D model with data, used for clash detection, quantities,\nsequencing (4D) and cost (5D).** **⚠️ Levels of detail\u002Fdevelopment matter — a model element\nat concept LOD is not a fabrication instruction, and treating it as one causes real\nerrors.**\n**⚠️ What BIM genuinely delivers**: **geometric clash detection and coordinated\nquantities.** ⚠️ **What it does not: constructability judgement, tolerance reality, or\nmaintenance access** (§9 → `building-structure-foundations-envelope-services-and-fire`).\n**⚠️ RFIs and submittals** are the formal question-and-approval mechanism during\nconstruction — ⚠️ **and RFI volume is a decent proxy for documentation quality.**\n\n---\n\n## §14. ⚠️ Codes and Permitting\n\n**⚠️ Codes are law where adopted, and adoption is LOCAL** (§24.1 → `building-reference`).\n```\n⚠️ THE STRUCTURE  model codes (⚠️ IBC\u002FIRC\u002FIFC and the I-Codes;\n   Eurocodes; national building regulations) → adopted by\n   jurisdiction, ⚠️ frequently WITH AMENDMENTS → interpreted by\n   the local authority having jurisdiction (AHJ)\n⚠️ THEREFORE  ⚠️ the model code is not the law. The ADOPTED and\n   AMENDED version in that jurisdiction is, and editions lag —\n   a state may still be several cycles behind (§24.1)\n⚠️ REFERENCED STANDARDS  ⚠️ codes incorporate standards by reference\n   (ASCE 7 for loads, ACI 318 for concrete, AISC 360 for steel,\n   NFPA for fire), and the referenced EDITION matters\n⚠️ THE PROCESS  permit application → plan review → permits →\n   ⚠️ INSPECTIONS at defined hold points → certificate of occupancy\n⚠️ SPECIAL INSPECTIONS  independent verification of critical work\n   (§19)\n```\n**⚠️ Alternative means and methods** allow non-prescriptive solutions where equivalence is\ndemonstrated — ⚠️ **the route for innovation, and it costs time and review.**\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fdesigning-and-building-buildings\u002Fskills\u002Fbuilding-accessibility-energy-drawings-bim-and-codes",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 building-accessibility-energy-drawings-bim-and-codes",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill building-accessibility-energy-drawings-bim-and-codes",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill building-accessibility-energy-drawings-bim-and-codes","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fdesigning-and-building-buildings\u002Fskills\u002Fbuilding-accessibility-energy-drawings-bim-and-codes\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",[],[]]