Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

de-slopify

Étoiles16

Forks9

Mis à jour21 avril 2026 à 20:38

Remove telltale AI-writing patterns from README, docs, and user-facing text. Must be done line-by-line, manually. No regex. Use after agents write any user-visible prose.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

hoangsonww

hoangsonww/Forge-Agentic-Coding-CLI

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	de-slopify
description	Remove telltale AI-writing patterns from README, docs, and user-facing text. Must be done line-by-line, manually. No regex. Use after agents write any user-visible prose.

/de-slopify

AI writing has tells. Emdashes. "It's not just X, it's Y." "Here's why." Forced enthusiasm. Pseudo-profound openers. These patterns signal "LLM wrote this" to readers and erode trust in the project.

Prompt

Use the verbatim prompt at .flywheel/prompts/de-slopify.md.

Hard rule

No regex. No script. Read each line. Revise each line deliberately. Attempts to automate this pass fail, because the fixes are context-dependent.

When to run

After an agent writes or substantially revises README.md.
After any change to user-facing CLI help text, error messages, or the onboarding walkthrough.
After generating release notes or CHANGELOG.md entries.

What to preserve

Technical specifics, command names, exact flag names, actual counts (tests, providers, tools). Strip tone tics, not information.

Plus depuis ce dépôt

même dépôt

deep-review

hoangsonww/Forge-Agentic-Coding-CLI

Deep review — random exploration + cross-agent review, alternating. Finds integration bugs that self-review misses. Run every 30–60 min during active implementation.

2026-04-2116

flywheel

hoangsonww/Forge-Agentic-Coding-CLI

Overview of Forge's Agentic Coding Flywheel methodology. Use to route between plan, bead, and code space. See FLYWHEEL.md at the repo root.

2026-04-2116

landing

hoangsonww/Forge-Agentic-Coding-CLI

End-of-session ritual. Close finished beads, file new ones for remaining work, run verify, commit in logical groupings, push. Work is not complete until git push succeeds.

2026-04-2116

plan

hoangsonww/Forge-Agentic-Coding-CLI

Start a new Flywheel planning round. Produce initial markdown plan, route to competing frontier models, synthesize hybrid, refine 4–5×. Use before any coding begins on a new feature.

2026-04-2116

plan-to-beads

hoangsonww/Forge-Agentic-Coding-CLI

Translate a polished markdown plan into self-contained beads in .beads/beads.jsonl. Every bead must be executable without reopening the plan. Use after the plan has converged.

2026-04-2116

polish-beads

hoangsonww/Forge-Agentic-Coding-CLI

Polishing pass over all open beads. Run 4–6 times. "Check your beads N times, implement once." Use after plan-to-beads and between refinement rounds.

2026-04-2116

name	de-slopify
description	Remove telltale AI-writing patterns from README, docs, and user-facing text. Must be done line-by-line, manually. No regex. Use after agents write any user-visible prose.

/de-slopify

AI writing has tells. Emdashes. "It's not just X, it's Y." "Here's why." Forced enthusiasm. Pseudo-profound openers. These patterns signal "LLM wrote this" to readers and erode trust in the project.

Prompt

Use the verbatim prompt at .flywheel/prompts/de-slopify.md.

Hard rule

No regex. No script. Read each line. Revise each line deliberately. Attempts to automate this pass fail, because the fixes are context-dependent.

When to run

After an agent writes or substantially revises README.md.
After any change to user-facing CLI help text, error messages, or the onboarding walkthrough.
After generating release notes or CHANGELOG.md entries.

What to preserve

Technical specifics, command names, exact flag names, actual counts (tests, providers, tools). Strip tone tics, not information.