writing-docs-majo

Standardize documentation writing with British spelling and structured templates.

Updated Feb 2, 2026
One-click install
npx skills add https://github.com/markjoshwel/skills --skill writing-docs-majo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-docs-majo
Source: https://github.com/markjoshwel/skills/tree/main/writing-docs-majo
Command: npx skills add https://github.com/markjoshwel/skills --skill writing-docs-majo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Documentation consistency across projects reduces onboarding time, prevents miscommunication, and lowers maintenance costs.

Core Features & Use Cases

  • Clear, repeatable writing standards for READMEs, changelogs, API docs, and user guides.
  • Tone and style guidance to ensure a coherent voice across teams.
  • Templates and checklists to speed up documentation tasks and improve readability.

Quick Start

Train the team on the standards and start applying them to the next docs task.

Frequently Asked Questions about writing-docs-majo

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize project documentation across multiple repositories?

Standardize project documentation by applying repeatable writing standards, structured templates, and tone guidance to READMEs, changelogs, and API docs. This ensures a coherent voice across teams, reducing onboarding time and maintenance costs.

What writing style does this documentation standard use for headings and voice?

The documentation standard uses sentence-case headings and a first-person lowercase voice. It enforces British English spelling to maintain consistent readability and tone across all project docs.

Can I use these documentation templates for API docs and user guides?

Yes, these documentation templates are applicable to API docs, user guides, READMEs, changelogs, and installation notes. They provide structured checklists to speed up writing tasks and improve readability.

What is the best way to enforce a style guide for markdown documentation?

Enforce a markdown documentation style guide by implementing specific writing standards that dictate tone, readability, and formatting. Applying these standards consistently prevents miscommunication and lowers long-term maintenance costs.

Does this documentation standard support American English spelling?

No, this documentation standard implements British English spelling specifically. Teams requiring American English will need to adjust the writing standards manually to match their preferred style guide.