$npx -y skills add flutter/agent-plugins --skill natural-writingContains well-defined rules for creating natural, accurate, and readable writing. Use whenever authoring longer text, like analysis documents, PR or CL descriptions, or documentation.
| 1 | # Rules for Natural Writing |
| 2 | |
| 3 | This document outlines strict rules to avoid common "AI-isms"—stylistic and structural patterns that language models typically fall into. Follow these rules to produce content that is more understandable, and reads as natural, human-authored text. |
| 4 | |
| 5 | ## 1. Vocabulary & Phrasing Controls |
| 6 | |
| 7 | ### The "Banned" List |
| 8 | |
| 9 | Avoid these words, which are statistically overrepresented in AI text. Use simpler, more direct alternatives. |
| 10 | |
| 11 | * **Verbs:** delve, underscore, highlight (as verb), foster, cultivate, maximize, leverage, democratize, ensure, align with, resonate with, encompass, bridge. |
| 12 | * **Nouns:** tapestry, landscape (abstract), realm, testament, interplay, synergy, cornerstone, hub, ecosystem (abstract). |
| 13 | * **Adjectives:** pivotal, crucial, vibrant, intricate, nuanced, unwavering, indelible, uncharted, rapidly evolving, transformative, breathtaking, nestled, dynamic. |
| 14 | |
| 15 | ### Avoid "Copula" Substitutions |
| 16 | |
| 17 | Do not replace simple "is/are" verbs with flowery equivalents. |
| 18 | |
| 19 | * **Bad:** "The library *serves as* a center for learning." |
| 20 | * **Bad:** "The statue *stands as* a monument to..." |
| 21 | * **Good:** "The library *is* a center for learning." |
| 22 | * **Good:** "The statue *is* a monument to..." |
| 23 | |
| 24 | ### Eliminate "Elegant Variation" |
| 25 | |
| 26 | Do not use synonyms just to avoid repeating a subject's name (e.g., "the eponymous character," "the titular protagonist," "the celebrated author"). It is acceptable to repeat the name or use pronouns naturally. |
| 27 | |
| 28 | ### Banned Temporal Words in Code & Comments |
| 29 | |
| 30 | Do not use relative temporal terms in code, variable names, function names, or comments. These words lose their meaning as the codebase evolves over time. |
| 31 | * **Banned Words**: now, currently, existing behavior, previous behavior, old, new, modern. |
| 32 | * **Bad**: `// This function now uses the config parser instead of hardcoding.` |
| 33 | * **Good**: `// Resolves paths via [ConfigParser.loadConfig] to support custom config locations.` |
| 34 | |
| 35 | ## 2. Content & Tone |
| 36 | |
| 37 | ### No "Puffery" or Forced Significance |
| 38 | |
| 39 | Do not inflate the importance of a topic with vague praise. If a subject is important, the facts should demonstrate it without help. |
| 40 | |
| 41 | * **Rule:** Avoid phrases like *"serves as a testament to," "marking a pivotal moment," "underscoring the importance of," "leaving an indelible mark,"* or *"shaping the landscape."* |
| 42 | * **Bad:** "The founding of the institute marked a pivotal moment in the evolution of regional statistics, representing a significant shift toward independence." |
| 43 | * **Good:** "The institute was founded in 1989 to collect regional statistics." |
| 44 | |
| 45 | ### No Superficial Analysis |
| 46 | |
| 47 | Avoid attaching "dangling" present-participle phrases that offer vague commentary. |
| 48 | |
| 49 | * **Rule:** Delete clauses starting with *"highlighting," "emphasizing," "reflecting," "showcasing,"* or *"demonstrating"* if they just restate the obvious or add fluff. |
| 50 | * **Bad:** "The building uses blue glass, *reflecting the region's natural beauty and symbolizing unity.*" |
| 51 | * **Good:** "The building uses blue glass." |
| 52 | |
| 53 | ### Avoid Promotional Language |
| 54 | |
| 55 | Maintain a neutral tone. Avoid "advertisement" words. |
| 56 | |
| 57 | * **Words to Watch:** boasts, features (as a verb), offers, premier, leading, state-of-the-art, committed to, dedicated to. |
| 58 | * **Bad:** "Nestled in the heart of the city, the hotel boasts a vibrant atmosphere." |
| 59 | * **Good:** "The hotel is located in the city center." |
| 60 | |
| 61 | ### No "Challenges and Future Outlook" Formula |
| 62 | |
| 63 | LLMs often end articles with a generic "Despite challenges... remains important" conclusion. |
| 64 | |
| 65 | * **Rule:** Do not end with a summary paragraph starting with "Despite \[X\], \[Subject\] continues to..." or speculating on the future. End with the last fact. |
| 66 | * **Bad:** "Despite facing economic hurdles, the company continues to thrive and remains a beacon of innovation." |
| 67 | |
| 68 | ### No "Title as Proper Noun" Leads |
| 69 | |
| 70 | Do not treat a descriptive article title (like a list or broad topic) as a proper noun in the first sentence. |
| 71 | |
| 72 | * **Bad:** "*The List of songs about Mexico* is a curated compilation..." |
| 73 | * **Good:** "This list contains songs about Mexico..." |
| 74 | |
| 75 | ### No Generic "See Also" Links |
| 76 | |
| 77 | Do not populate "See Also" sections with broad, generic terms. |
| 78 | |
| 79 | * **Rule:** Links must be directly relevant and specific to the subject. |
| 80 | * **Bad:** Linking *Financial technology* in an article about a specific startup. |
| 81 | * **Good:** Linking a competitor or specific related technology. |
| 82 | |
| 83 | ### Attribution Precision |
| 84 | |
| 85 | Do not use vague "weasel words." |
| 86 | |
| 87 | * **Rule:** Avoid *"Experts argue," "Observers have noted,"* or *"Several sources indicate"* unless you cite specific people immediately. |
| 88 | * **Rule:** Do not claim a subject interacts with a "broader" history or trend unless a source explicitly says so. |
| 89 | |
| 90 | ## 3. Sentence Structure |
| 91 | |
| 92 | ### No Negative Parallelism |
| 93 | |
| 94 | Avoid sentences t |