> For the complete documentation index, see [llms.txt](https://story.groupthought.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://story.groupthought.com/siblings/product-siblings/cutline.md).

# Cutline

> Feature introduced in Story 3.2.0

The first required metafield is **`theme.cutline`** 

```
theme.cutline
```

The content type is: Text, Single line text. 

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:

![](/files/gVktxX1mM8BlIBBMfQRH)

Start by defining a **Products** metafield and name it **Cutline**. Then change the Namespace from `my_fields` to `theme`:

{% hint style="info" %}
Important step: Rename **`my_fields`** to **`theme`**
{% endhint %}

![](/files/gfdIDrwzlM7gPcMqpozV)

Next, add a description. You can use Cutline again. Then click on **Select content type** and choose **Text**, **Single line** as the type:

![](/files/77UoYzCiUBKMQ3asfIkB)

**Save** the definition. 

### Check the saved metafield

Your final metafield should look like this:

![](/files/z4MDQwdJEpClSyzSlgNr)

{% hint style="success" %}
Please ensure you change the Namespace and key to this custom version for Story:\
\
\&#xNAN;**`theme.cutline`**\
\
By default, the namespace begins with **`my_fields`**. This will need to be changed to **`theme`**
{% endhint %}

The content type is **Text** and style is **Single line text**. 

### Next step

We require a second metafield to be defined:

{% content-ref url="/pages/ujg62BwEKsyoKNaLtA7Z" %}
[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 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://story.groupthought.com/siblings/product-siblings/cutline.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.