> For the complete documentation index, see [llms.txt](https://pipeline.groupthought.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pipeline.groupthought.com/siblings/product-siblings/cutline.md).
# Cutline
Metafield editor
> Feature introduced in Pipeline 6.2
The first required custom metafield is **`theme.cutline`**
```
theme.cutline
```
*The content type is Single line text, One value.*
This metafield is used for both the swatch label and subtitle for the product which helps with identifying the color version of the current product:
Start by defining a **Products** metafield and name it **Cutline**. Then change the Namespace from `custom` to `theme`:
{% hint style="info" %}
Important step: Rename **`custom`** to **`theme`**
{% endhint %}
Next, add a description. You can use **Cutline** again.
Click on **Select content type** and choose **Single line text** as the type and **One value**:
**Save** the definition.
### Important - Check the saved metafield
Your final metafield should look like this:
{% hint style="success" %}
Please ensure you change the Namespace and key to this custom version for Pipeline:\
\
**`theme.cutline`**\
\
By default, the namespace begins with**`custom`**. This will need to be changed to**`theme`**.
{% endhint %}
The content type is **Single line text** and the value is **One value**.
### Next step
We require a second metafield to be defined:
{% content-ref url="/pages/id2b2GJeU3UEQgjrtJ8E" %}
[Siblings collection](/siblings/product-siblings/siblings-collection.md)
{% endcontent-ref %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://pipeline.groupthought.com/siblings/product-siblings/cutline.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
