القائمة
Remove AI writing patterns to make documentation sound natural, specific, and human. Covers content patterns, language patterns, style patterns, and communication patterns.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
How to author a kubb.config.ts and pick the right @kubb/plugin-* packages when generating TypeScript from an OpenAPI/Swagger spec. Use whenever setting up Kubb, adding a generator, or debugging codegen output.
Remove AI-generated code slop from a branch or diff. Use after writing or generating code to strip unnecessary comments, defensive checks, `any` casts, and style that does not match the surrounding file. For prose and markdown, use the humanizer skill instead.
Import and use Kubb's generated code (types, clients, hooks, schemas, mocks). Use when writing app or test code that consumes a Kubb build.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when writing blog posts or documentation markdown files - provides writing style guide (active voice, present tense), content structure patterns, and SEO optimization. Overrides brevity rules for proper grammar.
Full JSDoc format guide for TypeScript, covering @example formats (short, multi-line, multi-variant), tag usage (@default, @deprecated, what to avoid), documentation patterns for properties/enums/functions, and tag order.
| name | humanizer |
| description | Remove AI writing patterns to make documentation sound natural, specific, and human. Covers content patterns, language patterns, style patterns, and communication patterns. |
Identifies and removes AI-generated text patterns so writing sounds natural and specific instead of generic and hollow.
Ensure the result sounds natural read aloud, varies sentence structure, uses specific details, and keeps the right tone.
Removing patterns is only half the job. Sterile, voiceless writing is just as obvious. Have opinions and react to facts instead of only reporting them. Vary sentence rhythm: short punchy sentences, then longer ones that take their time. Acknowledge complexity ("it works, but it also feels like a workaround"), use specific details, and let natural asides appear.
Load the category you need:
| Reference | Covers |
|---|---|
| content-patterns.md | Undue significance, empty credibility signals, -ing-participle filler, marketing language, vague attributions, generic filler sections |
| language-patterns.md | AI vocabulary, copula avoidance, negative parallelisms, rule-of-three, elegant variation, false ranges, filler and hedging, words to cut |
| style-patterns.md | Dashes and semicolons as punctuation, unnecessary bold, inline-header lists, title-case headings, emojis |
| communication-patterns.md | Chatbot artifacts, sycophantic openers |
