القائمة
Clean AI-typical prose patterns from documentation files. Fixes em dash overuse, filler phrases, redundant openings, and bolded-label-with-em-dash lists. Use after writing or editing documentation.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | de-slop |
| description | Clean AI-typical prose patterns from documentation files. Fixes em dash overuse, filler phrases, redundant openings, and bolded-label-with-em-dash lists. Use after writing or editing documentation. |
| argument-hint | <file-or-glob> |
| disable-model-invocation | true |
| allowed-tools | Read Edit Glob Grep |
Remove AI-typical writing patterns from prose files. $ARGUMENTS is a file path or glob pattern (e.g., docs/**/*.mdx).
Replace — (and –) with simpler punctuation:
An occasional em dash is fine when nothing else reads as well. But it should not be the default connector between clauses.
Skip em dashes inside code blocks, inline code, and code comments.
Remove or rewrite these. They add no information:
If a filler phrase introduces a list or code block, either drop it and let the list speak for itself, or replace it with a sentence that adds real context.
If a heading says "Root Directive" and the first sentence says "The root directive initializes the state machine", the sentence restates the heading. Either cut it or replace it with something the reader does not already know.
Same for sections that open with "This section covers..." or "In this section we will...".
- **Thing** — description is a strong AI signal. Replace with:
- **Thing**: description- **Thing** descriptionIf the code block above already shows how something works, don't restate it in prose. Trim sentences that add no new information beyond what the code or heading communicates.
--- markers)Do not add emojis. Do not change the document's factual content.
$ARGUMENTS to a file list. If it contains * or **, treat it as a glob. Otherwise treat it as a single file path.Rebase the current branch into clean conventional commits with proper author attribution. Use when the user wants to clean up a branch's commit history into well-organized conventional commits.
Use when writing, reviewing, or refactoring Angular component or directive tests, especially tests for inputs, outputs, host behavior, template probes, forms, accessibility, or signal-backed behavior.
Use when writing, reviewing, or refactoring Angular tests for application behavior, services, routes, state, forms, pipes, or integration flows, especially when tests may assert implementation details instead of public outcomes.
Use when writing, reviewing, or refactoring React component tests, especially tests for props, callbacks, controlled state, children, accessibility, form behavior, or multiple public component API variants.
Use when writing, reviewing, or refactoring React tests for application behavior, hooks, routes, state, or integration flows, especially when tests may assert implementation details instead of public outcomes.
Use when writing, reviewing, or refactoring tests that run in Vitest Browser Mode, especially tests using page, userEvent, expect.element, browser locators, polling assertions, or real DOM interactions.