[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AMWXEBZHSJT5WW9ZRCZM84":3,"skill-same:01M7AMWXEBZHSJT5WW9ZRCZM84":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},"01M7AMWXEBZHSJT5WW9ZRCZM84","devex-reference",null,"Use when measuring developer experience (perception surveys paired with system data, one North Star per team), running the launch checklist before shipping a developer tool, checking which developer-experience claims are weak or contested (Diataxis, DX Core 4, the 23-minute interruption figure, flaky-test statistics, the METR AI trial, AGENTS.md adoption counts, the unverified iOS, Material 3 Expressive and RedAccess figures), or finding the primary sources. Triggers on DevEx survey, DORA, SPACE, DX Core 4, developer productivity metrics, METR study, launch checklist, evidence grade. Companion to the other developer-experience 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\u002Fdeveloper-experience\u002Fskills\u002Fdevex-reference\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: devex-reference\ndescription: \"Use when measuring developer experience (perception surveys paired with system data, one North Star per team), running the launch checklist before shipping a developer tool, checking which developer-experience claims are weak or contested (Diataxis, DX Core 4, the 23-minute interruption figure, flaky-test statistics, the METR AI trial, AGENTS.md adoption counts, the unverified iOS, Material 3 Expressive and RedAccess figures), or finding the primary sources. Triggers on DevEx survey, DORA, SPACE, DX Core 4, developer productivity metrics, METR study, launch checklist, evidence grade. Companion to the other developer-experience skills.\"\n---\n\n# Developer Experience: Measurement, Launch Checklist, Weak Evidence, and Sources\n\n> **Part 9 of 9** of the *Developer Experience Blueprint* (plugin `developer-experience`), covering: Measurement and launch checklist; Where the evidence is weak or conflicting; Sources. Sibling skills: `devex-principles-and-feedback-loops`, `devex-cli-and-errors`, `devex-api-sdk-and-docs`, `devex-interfaces-onboarding-and-agents`, `devex-surface-placement`, `devex-editor-and-desktop-surfaces`, `devex-mobile-and-web-surfaces`, `devex-non-developers-and-visual-design`. A reference into a sibling is written *Section name → `skill`*.\n>\n> **Currency:** the blueprint is dated Oct 23, 2026; its evidence base and the AI-tooling claims age fastest, so re-check those first.\n>\n> Evidence grades used throughout: **A** = peer-reviewed or large study, **B** = credible practitioner or single study, **C** = vendor or opinion. Thin evidence is flagged where it occurs, and collected under *Where the evidence is weak or conflicting* in `devex-reference`.\n\n## Measurement and launch checklist\n\nPair what developers say with what systems record, and choose one North Star per team.\n\n| Dimension | Perception (survey) | Workflow (system data) |\n| --- | --- | --- |\n| Feedback loops | Satisfaction with build, test and review speed | Build, test, CI and review-turnaround times (median and tail) |\n| Cognitive load | \"How hard is it to understand this code?\" | Time to first successful call; onboarding duration |\n| Flow state | Focus time and interruptions | Meeting load; context switches |\n| Reliability | Trust in tests and tooling | Flaky-test rate; failed-build rate |\n\n**Launch checklist**\n\n- [ ] Fresh-machine setup finishes with one command and is timed\n- [ ] Every command has examples in `--help`, `--json` where useful, and documented exit codes\n- [ ] Every error has a location, a cause, a fix and a stable code\n- [ ] README runs end to end and doc examples are tested in CI\n- [ ] Public API names reviewed for consistency; deprecation policy published\n- [ ] AGENTS.md and an llms.txt exist, and MCP tool count is justified\n- [ ] Telemetry is opt-in, disclosed and honors `DO_NOT_TRACK`\n- [ ] Accessibility checked with a screen reader and keyboard only\n- [ ] A quarterly DevEx survey and a named owner exist\n\nThe doc is general because no repository was supplied; an audit of your actual codebase, CLI and docs against this checklist is the natural next step.\n\n## Where the evidence is weak or conflicting\n\n- **Diátaxis:** read only through secondary sources; the official site was not retrieved.\n- **DX Core 4:** vendor-affiliated, so its figures are marketing-adjacent until independently replicated.\n- **Interruption recovery:** the widely repeated \\~23 minutes comes from Mark's work; another paper reports about 25 minutes 26 seconds, and the return interval includes other productive work, so treat it as order-of-magnitude.\n- **Flaky-test trust erosion:** the numbers are secondary-sourced.\n- **AGENTS.md adoption:** counts conflict (20,000+ versus 60,000+).\n- **METR trial:** small sample and a narrow setting; it does not show that AI slows all developers.\n- **LLM-enhanced error messages:** ineffective in one study only.\n- **CLI screen-reader finding:** checked from an abstract and a summary, not the full paper.\n- **Agent-friendly CLI patterns and llms.txt:** practitioner evidence only.\n- **Part 2, iOS:** Apple's Human Interface Guidelines could not be retrieved, so all iOS advice is from secondary references and unverified.\n- **Part 2, desktop and Windows:** desktop and mobile specifics come from loaded reference skills (secondary); Microsoft's Windows design page gave only an index.\n- **Part 2, VS Code:** the contribution-points page was blocked, so walkthrough contribution details are unverified; JetBrains, Visual Studio, Xcode and Android Studio were not researched.\n- **Part 2, Material 3 Expressive:** the research figures are Google's own, reported via press; not independently reproduced.\n- **Part 2, RedAccess figure:** a reference stated \"about 40% of 5,000\"; the article gives about 5,000 of roughly 380,000 apps, so the article's figures are used. Tool makers dispute that public exposure equals breach.\n- **Part 2, NN\u002Fg and WebAIM:** NN\u002Fg articles were not re-read for sample sizes; the WebAIM 83.9% figure was not opened.\n- **Part 2, the non-developer ladder and feature matrix:** design proposals, not tested findings.\n\n## Sources\n\n- [DevEx: What Actually Drives Productivity (ACM Queue)](https:\u002F\u002Fqueue.acm.org\u002Fdetail.cfm?id=3595878)\n- [METR early-2025 AI and experienced open-source developers study](https:\u002F\u002Fmetr.org\u002Fblog\u002F2025-07-10-early-2025-ai-experienced-os-dev-study\u002F)\n- [DX newsletter: build times and developer productivity](https:\u002F\u002Fnewsletter.getdx.com\u002Fp\u002Fbuild-times-and-developer-productivity)\n- [Steinmacher et al., barriers faced by OSS newcomers](https:\u002F\u002Fwww.ime.usp.br\u002F~gerosa\u002Fpapers\u002F08254320.pdf)\n- [Compiler error messages considered unhelpful (summary)](https:\u002F\u002Fneverworkintheory.org\u002F2021\u002F09\u002F02\u002Fcompiler-error-messages-considered-unhelpful.html)\n- [Rust compiler development guide: diagnostics](https:\u002F\u002Frustc-dev-guide.rust-lang.org\u002Fdiagnostics.html)\n- [Command Line Interface Guidelines](https:\u002F\u002Fgithub.com\u002Fcli-guidelines\u002Fcli-guidelines) and a [condensed copy](https:\u002F\u002Fcdn.jsdelivr.net\u002Fnpm\u002F@hacxy\u002Fskills@0.1.0\u002Fskills\u002Fcreate-cli\u002Freferences\u002Fcli-guidelines.md)\n- [NO\\_COLOR](https:\u002F\u002Fno-color.org)\n- [Stripe: API versioning](https:\u002F\u002Fstripe.com\u002Fblog\u002Fapi-versioning)\n- [Nordic APIs: time to first call](https:\u002F\u002Fnordicapis.com\u002Fwhy-time-to-first-call-is-a-vital-api-metric\u002F)\n- [Cloudinary llms.txt (example)](https:\u002F\u002Fcloudinary.com\u002Fdocumentation\u002Fllms.txt)\n- [VS Code UX guidelines: overview](https:\u002F\u002Fcode.visualstudio.com\u002Fapi\u002Fux-guidelines\u002Foverview.md), [webviews](https:\u002F\u002Fcode.visualstudio.com\u002Fapi\u002Fux-guidelines\u002Fwebviews.md), [notifications](https:\u002F\u002Fcode.visualstudio.com\u002Fapi\u002Fux-guidelines\u002Fnotifications.md)\n- [Android: widget quality](https:\u002F\u002Fdeveloper.android.com\u002Fdesign\u002Fui\u002Fmobile\u002Fguides\u002Fwidgets\u002Fwidget-quality), [widget design](https:\u002F\u002Fdeveloper.android.com\u002Fdesign\u002Fui\u002Fmobile\u002Fguides\u002Fwidgets), [core app quality](https:\u002F\u002Fdeveloper.android.com\u002Fdocs\u002Fquality-guidelines\u002Fcore-app-quality)\n- [Microsoft: Windows design guidelines overview](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fwindows\u002Fapps\u002Fdesign\u002Fguidelines-overview)\n- [MDN: making PWAs installable](https:\u002F\u002Fdeveloper.mozilla.org\u002Fen-US\u002Fdocs\u002FWeb\u002FProgressive_web_apps\u002FGuides\u002FMaking_PWAs_installable) and [web.dev PWA checklist](https:\u002F\u002Fweb.dev\u002Farticles\u002Fpwa-checklist)\n- NN\u002Fg: [mobile-app onboarding](https:\u002F\u002Fwww.nngroup.com\u002Farticles\u002Fmobile-app-onboarding\u002F), [empty states](https:\u002F\u002Fwww.nngroup.com\u002Farticles\u002Fempty-state-interface-design\u002F), [progressive disclosure](https:\u002F\u002Fwww.nngroup.com\u002Farticles\u002Fprogressive-disclosure\u002F), [confirmation dialogs](https:\u002F\u002Fwww.nngroup.com\u002Farticles\u002Fconfirmation-dialog\u002F)\n- [GitHub: engineering team moved to Codespaces](https:\u002F\u002Fgithub.blog\u002Fengineering\u002Finfrastructure\u002Fgithubs-engineering-team-moved-codespaces\u002F)\n- [Laws of UX: aesthetic-usability effect](https:\u002F\u002Flawsofux.com\u002Faesthetic-usability-effect\u002F)\n- Also used, cited by title without a link: Security Boulevard coverage of the RedAccess scan of AI-built apps; Dezeen coverage of Material 3 Expressive. Part 2's desktop, iOS and extension details also draw on reference skills loaded in this session (secondary sources).\n\nStudies cited by name without a link (Myers & Stylos, Robillard & DeLine, Fagerholm & Münch, Greiler\u002FStorey\u002FNoda, SPACE, Mark) were recalled from earlier reading in this session and not re-opened for the final doc.\n","# Developer Experience: Measurement, Launch Checklist, Weak Evidence, and Sources\n\n> **Part 9 of 9** of the *Developer Experience Blueprint* (plugin `developer-experience`), covering: Measurement and launch checklist; Where the evidence is weak or conflicting; Sources. Sibling skills: `devex-principles-and-feedback-loops`, `devex-cli-and-errors`, `devex-api-sdk-and-docs`, `devex-interfaces-onboarding-and-agents`, `devex-surface-placement`, `devex-editor-and-desktop-surfaces`, `devex-mobile-and-web-surfaces`, `devex-non-developers-and-visual-design`. A reference into a sibling is written *Section name → `skill`*.\n>\n> **Currency:** the blueprint is dated Oct 23, 2026; its evidence base and the AI-tooling claims age fastest, so re-check those first.\n>\n> Evidence grades used throughout: **A** = peer-reviewed or large study, **B** = credible practitioner or single study, **C** = vendor or opinion. Thin evidence is flagged where it occurs, and collected under *Where the evidence is weak or conflicting* in `devex-reference`.\n\n## Measurement and launch checklist\n\nPair what developers say with what systems record, and choose one North Star per team.\n\n| Dimension | Perception (survey) | Workflow (system data) |\n| --- | --- | --- |\n| Feedback loops | Satisfaction with build, test and review speed | Build, test, CI and review-turnaround times (median and tail) |\n| Cognitive load | \"How hard is it to understand this code?\" | Time to first successful call; onboarding duration |\n| Flow state | Focus time and interruptions | Meeting load; context switches |\n| Reliability | Trust in tests and tooling | Flaky-test rate; failed-build rate |\n\n**Launch checklist**\n\n- [ ] Fresh-machine setup finishes with one command and is timed\n- [ ] Every command has examples in `--help`, `--json` where useful, and documented exit codes\n- [ ] Every error has a location, a cause, a fix and a stable code\n- [ ] README runs end to end and doc examples are tested in CI\n- [ ] Public API names reviewed for consistency; deprecation policy published\n- [ ] AGENTS.md and an llms.txt exist, and MCP tool count is justified\n- [ ] Telemetry is opt-in, disclosed and honors `DO_NOT_TRACK`\n- [ ] Accessibility checked with a screen reader and keyboard only\n- [ ] A quarterly DevEx survey and a named owner exist\n\nThe doc is general because no repository was supplied; an audit of your actual codebase, CLI and docs against this checklist is the natural next step.\n\n## Where the evidence is weak or conflicting\n\n- **Diátaxis:** read only through secondary sources; the official site was not retrieved.\n- **DX Core 4:** vendor-affiliated, so its figures are marketing-adjacent until independently replicated.\n- **Interruption recovery:** the widely repeated \\~23 minutes comes from Mark's work; another paper reports about 25 minutes 26 seconds, and the return interval includes other productive work, so treat it as order-of-magnitude.\n- **Flaky-test trust erosion:** the numbers are secondary-sourced.\n- **AGENTS.md adoption:** counts conflict (20,000+ versus 60,000+).\n- **METR trial:** small sample and a narrow setting; it does not show that AI slows all developers.\n- **LLM-enhanced error messages:** ineffective in one study only.\n- **CLI screen-reader finding:** checked from an abstract and a summary, not the full paper.\n- **Agent-friendly CLI patterns and llms.txt:** practitioner evidence only.\n- **Part 2, iOS:** Apple's Human Interface Guidelines could not be retrieved, so all iOS advice is from secondary references and unverified.\n- **Part 2, desktop and Windows:** desktop and mobile specifics come from loaded reference skills (secondary); Microsoft's Windows design page gave only an index.\n- **Part 2, VS Code:** the contribution-points page was blocked, so walkthrough contribution details are unverified; JetBrains, Visual Studio, Xcode and Android Studio were not researched.\n- **Part 2, Material 3 Expressive:** the research figures are Google's own, reported via press; not independently reproduced.\n- **Part 2, RedAccess figure:** a reference stated \"about 40% of 5,000\"; the article gives about 5,000 of roughly 380,000 apps, so the article's figures are used. Tool makers dispute that public exposure equals breach.\n- **Part 2, NN\u002Fg and WebAIM:** NN\u002Fg articles were not re-read for sample sizes; the WebAIM 83.9% figure was not opened.\n- **Part 2, the non-developer ladder and feature matrix:** design proposals, not tested findings.\n\n## Sources\n\n- [DevEx: What Actually Drives Productivity (ACM Queue)](https:\u002F\u002Fqueue.acm.org\u002Fdetail.cfm?id=3595878)\n- [METR early-2025 AI and experienced open-source developers study](https:\u002F\u002Fmetr.org\u002Fblog\u002F2025-07-10-early-2025-ai-experienced-os-dev-study\u002F)\n- [DX newsletter: build times and developer productivity](https:\u002F\u002Fnewsletter.getdx.com\u002Fp\u002Fbuild-times-and-developer-productivity)\n- [Steinmacher et al., barriers faced by OSS newcomers](https:\u002F\u002Fwww.ime.usp.br\u002F~gerosa\u002Fpapers\u002F08254320.pdf)\n- [Compiler error messages considered unhelpful (summary)](https:\u002F\u002Fneverworkintheory.org\u002F2021\u002F09\u002F02\u002Fcompiler-error-messages-considered-unhelpful.html)\n- [Rust compiler development guide: diagnostics](https:\u002F\u002Frustc-dev-guide.rust-lang.org\u002Fdiagnostics.html)\n- [Command Line Interface Guidelines](https:\u002F\u002Fgithub.com\u002Fcli-guidelines\u002Fcli-guidelines) and a [condensed copy](https:\u002F\u002Fcdn.jsdelivr.net\u002Fnpm\u002F@hacxy\u002Fskills@0.1.0\u002Fskills\u002Fcreate-cli\u002Freferences\u002Fcli-guidelines.md)\n- [NO\\_COLOR](https:\u002F\u002Fno-color.org)\n- [Stripe: API versioning](https:\u002F\u002Fstripe.com\u002Fblog\u002Fapi-versioning)\n- [Nordic APIs: time to first call](https:\u002F\u002Fnordicapis.com\u002Fwhy-time-to-first-call-is-a-vital-api-metric\u002F)\n- [Cloudinary llms.txt (example)](https:\u002F\u002Fcloudinary.com\u002Fdocumentation\u002Fllms.txt)\n- [VS Code UX guidelines: overview](https:\u002F\u002Fcode.visualstudio.com\u002Fapi\u002Fux-guidelines\u002Foverview.md), [webviews](https:\u002F\u002Fcode.visualstudio.com\u002Fapi\u002Fux-guidelines\u002Fwebviews.md), [notifications](https:\u002F\u002Fcode.visualstudio.com\u002Fapi\u002Fux-guidelines\u002Fnotifications.md)\n- [Android: widget quality](https:\u002F\u002Fdeveloper.android.com\u002Fdesign\u002Fui\u002Fmobile\u002Fguides\u002Fwidgets\u002Fwidget-quality), [widget design](https:\u002F\u002Fdeveloper.android.com\u002Fdesign\u002Fui\u002Fmobile\u002Fguides\u002Fwidgets), [core app quality](https:\u002F\u002Fdeveloper.android.com\u002Fdocs\u002Fquality-guidelines\u002Fcore-app-quality)\n- [Microsoft: Windows design guidelines overview](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fwindows\u002Fapps\u002Fdesign\u002Fguidelines-overview)\n- [MDN: making PWAs installable](https:\u002F\u002Fdeveloper.mozilla.org\u002Fen-US\u002Fdocs\u002FWeb\u002FProgressive_web_apps\u002FGuides\u002FMaking_PWAs_installable) and [web.dev PWA checklist](https:\u002F\u002Fweb.dev\u002Farticles\u002Fpwa-checklist)\n- NN\u002Fg: [mobile-app onboarding](https:\u002F\u002Fwww.nngroup.com\u002Farticles\u002Fmobile-app-onboarding\u002F), [empty states](https:\u002F\u002Fwww.nngroup.com\u002Farticles\u002Fempty-state-interface-design\u002F), [progressive disclosure](https:\u002F\u002Fwww.nngroup.com\u002Farticles\u002Fprogressive-disclosure\u002F), [confirmation dialogs](https:\u002F\u002Fwww.nngroup.com\u002Farticles\u002Fconfirmation-dialog\u002F)\n- [GitHub: engineering team moved to Codespaces](https:\u002F\u002Fgithub.blog\u002Fengineering\u002Finfrastructure\u002Fgithubs-engineering-team-moved-codespaces\u002F)\n- [Laws of UX: aesthetic-usability effect](https:\u002F\u002Flawsofux.com\u002Faesthetic-usability-effect\u002F)\n- Also used, cited by title without a link: Security Boulevard coverage of the RedAccess scan of AI-built apps; Dezeen coverage of Material 3 Expressive. Part 2's desktop, iOS and extension details also draw on reference skills loaded in this session (secondary sources).\n\nStudies cited by name without a link (Myers & Stylos, Robillard & DeLine, Fagerholm & Münch, Greiler\u002FStorey\u002FNoda, SPACE, Mark) were recalled from earlier reading in this session and not re-opened for the final doc.\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fdeveloper-experience\u002Fskills\u002Fdevex-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 devex-reference",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill devex-reference",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill devex-reference","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fdeveloper-experience\u002Fskills\u002Fdevex-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",[],[]]