myco:write-myco-user-documentation

To enforce a consistent documentation voice across README files and onboarding guides, run this skill on your drafts to apply the Myco doc-voice contract before committing. It checks for capability-first language and user-centric terminology to reduce ambiguity and review cycles.

Capability-first language describes what users can achieve rather than internal mechanics. To apply it to CLI references, run this skill to review drafts and edit wording, ensuring all user-facing content prevents internal jargon leakage and uses only user-facing terminology.

Yes, you can use this skill to review feature docs before a commit. It gates your documentation by checking for alignment with the Myco voice contract, ensuring all user-facing content is clear, consistent, and free of internal mechanics leakage.

To prevent internal mechanics and jargon from leaking into user documentation, run this skill on your drafts. It enforces the doc-voice contract by identifying internal terminology and guiding edits to replace it with user-facing language before commits.

Yes, this documentation review skill works for onboarding guides, feature docs, README files, and CLI references. It applies the Myco doc-voice contract to any user-facing content, guiding edits for consistency and capability-first wording across teams and projects.

The best way to maintain doc-voice consistency across contributors is to run this skill on all drafts before commits. It enforces the Myco doc-voice contract, guiding edits for capability-first language and consistent user-facing terminology across teams and projects.