> For the complete documentation index, see [llms.txt](https://docs.danielvoelk.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.danielvoelk.de/filtering-types/picky-filtering-premium.md).

# Picky Filtering (Premium)

When you normally filter e.g. two classes, the result will be all elements that contain one or both of these classes.

### Example

We have a button with the classes: df-button dfc-cats dfc-blue

#### Without Picky Filtering

Without Picky Filtering, it would show all elements, that have either the cats OR the blue class.

That means, also blue dogs would show.

#### With Picky Filtering

With Picky Filtering it shows only blue cats. Only elements that have the cats AND the blue class.

After adding the **`df-picky`** class to your `df-area` section, only elements that have both classes will show after filtering.

{% hint style="info" %}
You can get Divi Filter Premium by clicking [here](https://shop.danielvoelk.de/#divi-filter).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.danielvoelk.de/filtering-types/picky-filtering-premium.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.