원클릭으로
writing-check
Check a LaTeX file for common writing pet peeves based on Margo Seltzer's writing guidelines
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Check a LaTeX file for common writing pet peeves based on Margo Seltzer's writing guidelines
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | writing-check |
| description | Check a LaTeX file for common writing pet peeves based on Margo Seltzer's writing guidelines |
| argument-hint | [file-path] |
Read the file at $ARGUMENTS and check it against the writing pet peeves listed below. For each violation found, report:
Group violations by rule. At the end, provide a summary count of violations per rule.
Only report clear violations -- do not flag ambiguous cases. Focus on the prose text, not LaTeX commands, labels, or comments.
Never use citations as the subject of a sentence. Write "Smith et al. show that X [1]" not "In [1], X is shown." The reader should never have to look at the bibliography to parse a sentence.
Use "that" for restrictive (essential) clauses and "which" (preceded by a comma) for non-restrictive (parenthetical) clauses. If the clause can be removed without changing the meaning, use ", which". If it's essential to the meaning, use "that" with no comma.
Place "only" immediately before the word or clause it modifies. "We only run three experiments" (implies we don't do anything else with them) vs. "We run only three experiments" (implies the number is small).
Do not put a comma between two predicates that share the same subject. "We build a system, and evaluate it" is wrong -- remove the comma.
Do not dump multiple citations without context, e.g., "Many systems have addressed this problem [1,2,3,4,5]." Instead, briefly describe each reference's contribution.
Delete "very" or replace with a stronger word. "Very large" -> "enormous". "Very important" -> "critical".
Don't say "This paper attempts to..." or "We try to...". State what the work does. "We present..." not "We attempt to present..."
Prefer active voice. "We designed the system" not "The system was designed." Passive voice is acceptable when the actor is irrelevant or unknown.
State results and contributions upfront (especially in abstracts and introductions). Don't build suspense.
Use "fewer" for countable nouns (fewer threads, fewer errors). Use "less" for uncountable nouns (less memory, less time).
Use "such as" when giving actual examples. Use "like" only for inexact comparisons. "Mechanisms such as containers and VMs" not "Mechanisms like containers and VMs."
Use "affect" or "effect" instead. "This impacts performance" -> "This affects performance."
Be direct. "We build..." not "We seek to build..." or "We aim to build..."
"And so we conclude..." -> "So we conclude..." (or better, just "We conclude...")
Say "Figure 3 illustrates..." or "Figure 3 shows..." Never say "Figure 3 visualizes..."
Use "point out", "note", or "observe" instead. "We argue" sounds adversarial.
Flag obvious typos and misspellings in prose (not in commands/identifiers).
Present the main point first, then the reasoning. "X is better because Y" not "Because of Y, X is better."
Big things are composed of small things. Small things comprise big things. "The system comprises three modules" or "The system is composed of three modules." Never say "comprised of."
Rephrase to avoid this word. "This encourages..." or "This motivates..."
Combine sentences: "X happens because Y" instead of "X happens. This is because Y."
"May" = permission. "Can" = ability. "Might" = possibility. Be precise.
Overall, writing should be: Concise, Crisp, Clear, and Correct.
Do not use em-dashes (--- in LaTeX). Replace with a comma, colon, semicolon, or parentheses depending on the context. Em-dashes are informal and interrupt flow.