Our review

Transforms AI-generated technical documents into a more natural human writing style by removing common AI patterns.

Strengths

Removes decorative symbols and rigid tables
Adds colloquial tone and first-person pronouns for subjectivity
Incorporates real-world examples and speculative analysis
Simplifies section structure to avoid rigid numbering

Limitations

May not suit formal documents requiring an objective tone
Subjective opinions might be inappropriate in some contexts
Relies on user judgment to apply each rule appropriately

When to use it

When you have AI-generated technical content that reads synthetically and you want it to feel like it was written by a human expert.

When not to use it

When you need to maintain strict formal language or objective factual reporting without personal opinions.

Examples

De-AI a file

/de-ai /path/to/rendering_guide.md

De-AI inline text

/de-ai 本段内容是由AI生成的，它包含很多符号和表格，需要被改写为更自然的风格。✓ 检查点 ✅ 完成项 ⚠️ 注意项。以下是一些技术要点：

Humanize a technical blog post

Please humanize this game development document: The rendering pipeline can be optimized using occlusion culling. Advantages include reduced draw calls and improved performance. Disadvantages include added complexity.

name: de-ai description: Remove AI-style patterns from technical documents, making them read more naturally like human-written content. Trigger when user asks to "de-AI", "humanize", or "polish" a document.

De-AI: Remove AI Writing Patterns

Transform AI-assisted technical documents (especially game development & rendering docs) into more natural, human-like writing.

Usage

/de-ai <file path or text content>

Instructions

You are helping the user remove AI-style patterns from technical documents. Apply the following transformations:

1. Remove Decorative Symbols

Delete all emoji-like symbols: ✓ ✗ ❌ ✅ ⚠️ 💡 🎯 📌 🔥 ⭐ etc.
Express "correct/incorrect" or "pros/cons" using plain text instead

2. Minimize Table Usage

Do not use tables for comparisons or summaries
Convert tables to concise prose paragraphs or simple bullet lists
Example: Instead of a comparison table, write: "方案A的优点是xxx，缺点是xxx；方案B则..."

3. Add Colloquial Tone and Subjectivity

Use first-person pronouns: "我们"、"我认为"、"我的理解是"
Allow uncertainty expressions: "也许"、"可能"、"大概"、"应该是"
Be honest about uncertain information rather than stating everything as fact
Add personal judgments: "我觉得这样做的原因可能是..."

4. Include Subjective Opinions and Real-World Examples

When introducing a technique, proactively mention how other games or projects use it
Examples:
- "《原神》的渲染管线也采用了类似的方案"
- "UE5的Nanite在处理这个问题时..."
- "我猜测他们这样设计是因为..."
Add speculative analysis: "这可能是出于性能考量"
These examples and opinions add depth and authenticity

5. Simplify Section Structure

Avoid deep nested numbering (like 1.1.1, 1.1.2)
Use flexible structure instead:
- Major sections: ## headings
- Subsections: ### or bold text as lead-ins
- No strict numbering required; use descriptive titles
Humans rarely maintain rigid hierarchical numbering due to high maintenance cost

6. Additional Guidelines

Vary sentence length; avoid uniform sentence patterns
Use colloquial connectors: "说白了"、"换句话说"、"简单来说"
Add transitional sentences between paragraphs instead of rigid enumeration
Don't end every section with a summary sentence

Output Requirements

If user provides a file path, read the file and rewrite it
If user provides text directly, rewrite that text
Output the rewritten result directly without explaining what was changed
Preserve technical accuracy; only adjust the writing style

De-AI: Humanize Technical Documents

Recommended for