# Patterns

Patterns surfaces what's actually working in your content over time. Instead of staring at individual post metrics, you see the recurring formats, hooks, and topics that drive performance.

### What it shows

* **Top-performing formats** — which post structures consistently win (lists, single-line hooks, threads, carousels)
* **High-signal hooks** — opening lines and angles that drive above-average engagement
* **Topic strength** — which subjects your audience responds to
* **Underperformers** — formats and topics that consistently disappoint, so you stop wasting effort

### How it works

Patterns analyzes the analytics ingested through [Data Ingestion](/thecontentforge-docs/feature-guides/data-ingestion.md). It looks across your post history, normalizes for reach, and clusters by structural and topical features.

### Workflow

1. Open Patterns after a fresh weekly upload
2. Note the 2–3 strongest formats or hooks for the period
3. Bring those into your next planning session
4. Run an [Experiment](/thecontentforge-docs/feature-guides/experiments.md) on anything you're unsure about

### Tips

* Patterns gets smarter with more data — give it at least 4–6 weeks of ingested analytics before drawing strong conclusions
* Don't over-fit. A format that wins for two weeks isn't a guaranteed third-week winner
* Use Patterns to *start* the conversation about content direction, not end it


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://thecontentforge.gitbook.io/thecontentforge-docs/feature-guides/patterns.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
