From Office
Detects and eliminates AI writing tropes that make text sound artificial or formulaic. Use when generating text content, writing documentation, creating code comments, or reviewing writing style. Supports two-tier preference overrides (global ~/.claude/office.local.md + project .claude/office.local.md).
How this skill is triggered — by the user, by Claude, or both
Slash command
/office:tropesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Scan generated text for common AI writing patterns that make content sound artificial or formulaic. This skill provides a systematic workflow for identifying and eliminating tropes.
Scan generated text for common AI writing patterns that make content sound artificial or formulaic. This skill provides a systematic workflow for identifying and eliminating tropes.
Source: tropes.fyi by ossama.is
Write like a human expert: varied, precise, and professional.
The goal is to find the "middle ground" between overly colloquial or casual writing and the obscure, formulaic style typical of AI generation. A single pattern used once is usually fine; the problem occurs when multiple tropes cluster together or when the same trope repeats throughout the text.
Scan for tropes when:
Check for preference files in order (project overrides global):
.claude/office.local.md (project-level, in the current working directory)~/.claude/office.local.md (user-level, global)If either exists:
If neither exists, offer to create the global file with default values after the detection run completes.
See references/preferences-schema.md for the full field reference and precedence rules.
Read through the text and identify:
Look for multiple tropes appearing together:
For each identified trope:
After revision:
After the detection run, offer to save preferences to either ~/.claude/office.local.md (global) or .claude/office.local.md (project):
banned_wordspreferred_termssensitivityDefault target is the global file unless the user specifies project-level. Do not auto-write preferences. Present the proposed changes and let the user confirm.
The complete trope catalog is organized into seven categories. Load specific references as needed:
Word Choice - references/word-choice.md
Ornate vocabulary, magic adverbs, pompous constructions
Sentence Structure - references/sentence-structure.md
Negative parallelism, rhetorical questions, formulaic patterns
Paragraph Structure - references/paragraph-structure.md
Short fragments, listicle disguises
Tone - references/tone.md
False suspense, pedagogical voice, vague attributions
Formatting - references/formatting.md
Em-dash overuse, bold-first bullets, unicode decoration
Composition - references/composition.md
Fractal summaries, dead metaphors, content duplication
Professional Balance - references/professional-balance.md
Avoiding both overly colloquial "humanisms" and obscure AI-isms.
User Preferences - references/preferences-schema.md
Two-tier overrides: global ~/.claude/office.local.md + project .claude/office.local.md. Custom banned words, sensitivity, tone, skip categories.
npx claudepluginhub est7/dotclaude --plugin officeCreates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.