# Pattern 3: Sayings That Sound Deep: Examples from the Humanizer Skill

> Explore Pattern 3 sayings that sound deep, like at its core and the real question is. Learn how these phrases add aphoristic language without concrete meaning in the blader/humanizer repository.

- Repository: [Siqi Chen/humanizer](https://github.com/blader/humanizer)
- Tags: deep-dive
- Published: 2026-09-09

---

**Pattern 3: Sayings That Sound Deep targets vague philosophical phrases like "at its core" and "the real question is" that dress ordinary points in aphoristic language without adding concrete meaning.**

Pattern 3: Sayings That Sound Deep is a writing anti-pattern defined in the `blader/humanizer` repository that identifies vague, philosophical-sounding language masking specific claims. According to the skill definition in [`SKILL.md`](https://github.com/blader/humanizer/blob/main/SKILL.md), these phrases act as a **tell** that the text is dressing an ordinary point as a hidden truth rather than stating it directly.

## Recognizing Pattern 3: Sayings That Sound Deep

Pattern 3 flags phrases that create the illusion of insight while providing no new data. These sayings typically use **"X is the Y of Z"** constructions, aphoristic wrappers like **"at its core,"** or rhetorical pivots such as **"the real question is..."**

Common markers identified in [`SKILL.md`](https://github.com/blader/humanizer/blob/main/SKILL.md) (lines 96-108) include:

- **"The real question is..."** – implies hidden depth where none exists
- **"At its core"** – suggests fundamental truth without specifying mechanics
- **"X is the language of Y"** – metaphorical abstraction replacing concrete description
- **"Efficiency becomes a trap"** – generic warning without specific causal links

These phrases mimic maxims that sound profound but transfer zero factual information to the reader.

## Why Deep-Sounding Sayings Create Reader Friction

According to the Humanizer source code analysis, Pattern 3: Sayings That Sound Deep degrades text quality in four specific ways:

- **Vagueness**: The phrase provides the illusion of insight while delivering no new data.
- **Redundancy**: It often rephrases a point already evident in surrounding sentences.
- **Aphoristic tone**: The language mimics philosophical maxims that sound profound but remain empty of content.
- **Reader friction**: Readers must infer the actual meaning behind the metaphorical wrapper, slowing comprehension and increasing cognitive load.

## How Humanizer Rewrites Pattern 3

The `blader/humanizer` skill applies a three-step transformation to eliminate these patterns:

1. **Identify the saying** – Locate the aphoristic phrase (e.g., "the real question is...").
2. **Clarify the underlying claim** – Extract the concrete point being obscured.
3. **Remove the aphoristic wrapper** – Replace the vague language with specific, factual statements.

This process restores precision by replacing philosophical dressing with direct claims.

## Before and After Examples

The following examples from [`SKILL.md`](https://github.com/blader/humanizer/blob/main/SKILL.md) demonstrate how Pattern 3: Sayings That Sound Deep transforms into clear technical prose.

### Example 1: Removing "At Its Core"

Before:

```text
The real question is whether teams can adapt. At its core, what really matters is organizational readiness.

```

After:

```text
The question is whether teams can adapt. That mostly depends on whether the organization is ready to change its habits.

```

### Example 2: Eliminating "Language Of" Metaphors

Before:

```text
Symmetry is the language of trust. Efficiency becomes a trap when teams forget the human layer.

```

After:

```text
Symmetric layouts often feel more predictable to users. Teams can over-optimize workflows and miss how people actually use them.

```

### Example 3: Clarifying "Architecture Of" and "Currency Of"

Before:

```text
The deeper issue is the architecture of our data pipeline; the currency of decisions is data latency.

```

After:

```text
The main challenge is how our data pipeline is built; decisions are driven by data latency.

```

## Source Location in Humanizer

Pattern 3: Sayings That Sound Deep is formally defined in the `blader/humanizer` repository with the following key files:

- **[`SKILL.md`](https://github.com/blader/humanizer/blob/main/SKILL.md)** (lines 96-108): Contains the complete pattern definition, rewrite rules, and the examples cited above.
- **[`README.md`](https://github.com/blader/humanizer/blob/main/README.md)**: Provides installation instructions and high-level usage guidance for the Humanizer skill.
- **[`AGENTS.md`](https://github.com/blader/humanizer/blob/main/AGENTS.md)**: Documents how the skill integrates with various AI agents to detect and rewrite these patterns automatically.

## Summary

- Pattern 3: Sayings That Sound Deep identifies vague philosophical phrases that obscure concrete claims.
- Common tells include "at its core," "the real question is," and "X is the Y of Z" constructions.
- These phrases create reader friction by forcing inference without delivering new information.
- The Humanizer rewrite strategy extracts the specific claim and removes the aphoristic wrapper.
- Source definitions reside in [`SKILL.md`](https://github.com/blader/humanizer/blob/main/SKILL.md) lines 96-108 within the `blader/humanizer` repository.

## Frequently Asked Questions

### What specific phrases trigger Pattern 3: Sayings That Sound Deep?

The Humanizer skill flags constructions like **"the real question is..."**, **"at its core"**, **"X is the language of Y"**, and **"the architecture of"** when they dress ordinary observations in philosophical language. These appear in [`SKILL.md`](https://github.com/blader/humanizer/blob/main/SKILL.md) as explicit markers of Pattern 3.

### How does Pattern 3 differ from other Humanizer patterns?

While other patterns may target jargon or unnecessary complexity, Pattern 3 specifically addresses **aphoristic tone**—text that mimics deep wisdom without substance. It focuses on the **redundancy** of stating an obvious point through vague metaphor rather than technical specificity.

### Can aphorisms ever be useful in technical writing?

According to the Humanizer implementation in `blader/humanizer`, aphorisms are considered a **tell** of imprecise thinking in technical contexts. The skill treats them as removable noise because they force readers to decode meaning; concrete statements always outperform philosophical wrappers for conveying actionable information.

### Where is Pattern 3 defined in the Humanizer source code?

Pattern 3 is defined in **[`SKILL.md`](https://github.com/blader/humanizer/blob/main/SKILL.md)** at lines 96-108, which provides the classification rules, specific examples, and rewrite logic. Supporting documentation appears in [`README.md`](https://github.com/blader/humanizer/blob/main/README.md) (general overview) and [`AGENTS.md`](https://github.com/blader/humanizer/blob/main/AGENTS.md) (integration specifications).