> For the complete documentation index, see [llms.txt](https://kami-1.gitbook.io/kami/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kami-1.gitbook.io/kami/art/collection-generation.md).

# Collection Generation

## Goals:

1. No mid-tier rares & no ugly Kami
2. Create a Kami everyone can **resonate** with and **want** to display as a PFP

## Traits:

Kami is a smaller collection but don't let that make you think we won't have great variation.

1. **150+** traits
2. **9** skins
3. **50+** clothing 
4. Only **4,269** Kami

{% hint style="warning" %}
The combination of a large head, big eyes, short neck, and small bodies presented a challenging canvas for creating numerous traits.
{% endhint %}

Initially, our collection had 200+ traits. However, after numerous test generations, we realized that having too many traits was counterproductive. We evaluated each NFT, asking ourselves whether this particular trait enhanced or detracted from the overall aesthetics of the Kami.

{% hint style="info" %}
To genuinely determine which traits don't complement each other, we conducted all generations without assigning rarity.
{% endhint %}

## Refining the collection:

Despite eliminating more than 50+ traits from the collection, we still weren't happy. Some traits just didn't blend well with each other, creating that mid-tier feel we were looking to eliminate.

We moved to Figma, where we got together to determine the rarity of each trait, analyzing them together in a visual layout.

<figure><img src="/files/VhFBc0lqALnl5htMyL9v" alt=""><figcaption></figcaption></figure>

Once rarities were determined, we knew we had to implement a custom logic ruling.

{% hint style="info" %}
**Examples:** \
"Clear glasses" can never go with "Kabuki"

"Snooze bubble" can only be applied when "Resting Eyes" are present

Only generate "\[redacted] Skin" with "\[redacted] traits"
{% endhint %}

We faced challenges on how the NFTs would look together after applying rarity and logic rules.

To resolve this, we created a custom gallery to gain a better understanding of the amount and appearance of traits generated from each rarity level in the collection.

<figure><img src="/files/vukLKfvEEI0MGq9SkKhJ" alt=""><figcaption></figcaption></figure>

## Final Result:

<figure><img src="/files/Dulv1Q4tbwTCMNTthQyS" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
No **mid-tier** rares and no **ugly** Kami
{% endhint %}

{% hint style="success" %}
Create a Kami everyone can **resonate** with and **want** to display as a PFP
{% 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://kami-1.gitbook.io/kami/art/collection-generation.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.