Use when writing code, documentation, or comments - always use accessible and respectful terminology
/plugin marketplace add troykelly/claude-skills
The exact command may vary by repository. Check the README on GitHub.
For the skill author
Shows your skill is listed on Skillteca, generates a backlink and trackable traffic.
[](https://www.skillteca.com.br/skills/inclusive-language?utm_source=badge&utm_medium=readme&utm_campaign=badge)
Guides users through a structured workflow for co-authoring documentation, proposals, technical specs, and similar content. It helps efficiently transfer context, refine content through iteration, and verify its effectiveness for readers.
Creates original algorithmic art using p5.js, seeded randomness, and interactive parameter exploration. Use this for requests involving generative art, flow fields, or particle systems, ensuring no copyright infringement.
Writes long-form blog posts with TL;DR block, definition sentence, comparison table, and 5-question FAQ for SEO ranking and AEO citation. Activate when the user wants to write a blog post, article, or long-form content piece.
Create long-form, high-quality, SEO-optimized blog posts ready for WordPress with truth boxes and FAQ schema.
Category alert
One short email with only the new Escrita e Conteúdo skills. 4 minutes of reading, no spam, unsubscribe with one click.
You confirm your email on the first send. No spam. Unsubscribe with one click.
Use respectful, accessible language in all code and documentation.
Core principle: Words matter. Use inclusive terminology.
This applies to: Code, comments, documentation, commit messages, branch names, and all text.
| Instead of | Use |
|---|---|
| master | main |
| slave | replica, secondary, follower |
# Correct
git checkout main
git push origin main
# Repository default branch should be
[Description truncada. Veja o README completo no GitHub.]
Sign in to comment. Sign in