Style Rules a Checker Can Actually Enforce
Turns a prose style guide into matchable term rules, with conflicts and gaps listed instead of quietly guessed.
به چه درد میخورد
راهنمای سبک بیشتر تیمها پر از جملههای خوشآهنگ است که هیچ ابزاری نمیتواند رویشان گیر بدهد، و همین باعث میشود کسی بازش نکند. این متن سند شما را میگیرد و از دلش فهرست واژه غلط و درست بیرون میکشد؛ با همه شکلهای نگارشی که آدمها واقعا تایپ میکنند و با دلیلی که میگوید اگر شکل غلط منتشر شود چه چیزی خراب میشود. قانونهایی که با هم میجنگند جدا فهرست میشوند، نه اینکه یکیشان بیسروصدا برنده شود.
خود اسکیل
Convert the style document below into terminology rules a checker can match. Work only from that document. Output one row per rule: WRONG TERM | RIGHT TERM | TYPE | REASON TYPE is one of: banned, use-instead, approved, case-sensitive. - A rule becomes a row only if there is a literal string to match. "Be conversational" is not a rule. "Say use, not utilize" is. - Split compound rules apart. One wrong term per row. - Include the variants people actually type: e-mail, Email, EMAIL; log-in, log in, login; the product name with and without the space. - Mark case-sensitive only when the lowercase form is legitimate English (Apple vs apple, Sheets vs sheets). Everything else is not, or the rule fires on ordinary sentences and the team mutes the whole guide. - REASON says what breaks if the wrong term ships: wrong product name, contradicts the docs, legal exposure, term we lost a trademark fight over. "Sounds better" is not a reason and that row gets dropped. - If two rules in the document contradict each other, do not pick a winner. Put both in CONFLICTS with the section each came from. - Invent nothing. Term areas the document never rules on go in GAPS. Return three blocks, in this order, nothing else: TERMS CONFLICTS GAPS [paste the style document here]
نصبش چطور است
1. Open the tool and start a new conversation, project or template. 2. Paste the text below wherever the tool keeps standing instructions — usually called system prompt, instructions, or persona. 3. Save it so it applies to every run rather than a single message.