avoid Latin shorthand

Replace Latin abbreviations with plain English equivalents in technical content.

3|2|Updated May 12, 2026
One-click install
npx skills add https://github.com/kriscendobot/garden --skill avoid-latin-shorthand
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: avoid Latin shorthand
Source: https://github.com/kriscendobot/garden/tree/main/skills/no-latin-shorthand
Command: npx skills add https://github.com/kriscendobot/garden --skill avoid-latin-shorthand

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes dense, register-shifting Latin abbreviations from bot-authored content, ensuring that technical documentation and PR communications remain legible to a global, diverse audience.

Core Features & Use Cases

  • Standardized Replacements: Automatically maps common Latin shorthand like i.e., e.g., and cf. to their plain English equivalents.
  • Context-Aware Rewriting: Provides guidance on restructuring sentences for better flow rather than performing mechanical, awkward substitutions.
  • Use Case: When the bot drafts a PR review or a design document, this Skill ensures the language is direct and inclusive, avoiding jargon that assumes a specific academic background.

Quick Start

Apply the avoid Latin shorthand skill to the current file to replace all instances of Latin abbreviations with clear English alternatives.

Frequently Asked Questions about avoid Latin shorthand

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

FAQPage Schema
How do I replace Latin abbreviations like i.e. and e.g. with plain English in technical documentation?

To replace Latin abbreviations with plain English in technical documentation, apply this Skill to standardize prose by mapping shorthand like i.e. and e.g. to their accessible English equivalents during routine file edits.

Why does bot-authored content use Latin shorthand that needs to be standardized for accessible communication?

Bot-authored content often defaults to dense Latin shorthand, which needs standardization because such abbreviations assume an academic background and reduce legibility for a global, diverse audience reading technical documentation.

Can I enforce plain language guidelines automatically in PR descriptions and code comments?

You can enforce plain language guidelines automatically in PR descriptions and code comments by applying this Skill, which operates during routine file edits to replace Latin abbreviations with clear English alternatives.

Does replacing Latin abbreviations with plain English alternatives affect sentence flow in design documents?

Replacing Latin abbreviations with plain English alternatives maintains sentence flow in design documents by providing context-aware rewriting guidance, ensuring restructuring reads naturally rather than resulting in mechanical, awkward substitutions.

What is the best way to ensure inclusive communication standards in generated technical content?

The best way to ensure inclusive communication standards in generated technical content is to enforce plain language guidelines that remove jargon, replacing Latin abbreviations with direct English equivalents across all generated text.

When should I not use mechanical substitutions for Latin shorthand in prose writing?

You should not use mechanical substitutions for Latin shorthand when they create awkward phrasing; instead, context-aware restructuring is needed to ensure standardized replacements integrate smoothly into the sentence flow.