natural-writing
Natural Writing
LLMs produce statistically average text. This creates identifiable patterns: overused words, formulaic structures, and hollow emphasis. This skill helps you write text indistinguishable from a skilled human writer.
Core Principle
Specific beats generic. Facts beat significance claims. Direct beats hedged.
AI text regresses to the mean: specific facts fade into generic praise, concrete details blur into vague importance. Fight this by being concrete and direct.
Vocabulary Red Flags
These words appear far more frequently in AI text than human text. One or two is fine; clustering several is a tell.
High-Alert Words
Avoid or use sparingly: delve, tapestry, vibrant, landscape (metaphorical), nuanced, multifaceted, pivotal, crucial, foster, underscore, highlight, showcase, leverage, navigate, realm, intricate, comprehensive, robust, seamless, cutting-edge, game-changing, groundbreaking
Filler Transitions
More from third774/dotfiles
opensrc
Fetch source code for npm, PyPI, or crates.io packages and GitHub/GitLab repos to provide AI agents with implementation context beyond types and docs. Use when needing to understand how a library works internally, debug dependency issues, or explore package implementations.
90agent-skills
Author and improve Agent Skills following the agentskills.io specification. Use when creating new SKILL.md files, modifying existing skills, reviewing skill quality, or organizing skill directories with proper naming, descriptions, and progressive disclosure.
31documenting-code-comments
Standards for writing self-documenting code and best practices for when to write (and avoid) code comments. Use when auditing, cleaning up, or improving inline code documentation.
28customizing-opencode
Configure OpenCode via opencode.json, agents, commands, MCP servers, custom tools, plugins, themes, keybinds, and permissions. Use when setting up or modifying OpenCode configuration.
23adversarial-code-review
Review code through hostile perspectives to find bugs, security issues, and unintended consequences the author missed. Use when reviewing PRs, auditing codebases, or before critical deployments.
21verification-before-completion
Run verification commands before claiming work is complete or fixed. Use before asserting any task is done, bug is fixed, tests pass, or feature works.
18