> For the complete documentation index, see [llms.txt](https://wiki.redmodding.org/cyberpunk-2077-modding/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/npcs/guides-all-about-hair.md).

# For V - All about Hair

Hair guides

## Summary

Last documented edit: Sep 08 2025 by [mana vortex](mailto:undefined)

This page collects all **hair guides**.

{% hint style="info" %}
To see the guides, please check the page tree in the left sidebar, or click the "next" panel at the bottom of the page.
{% endhint %}

### Wait, this is not what I want!

* Check out [Hair modeling beginner tutorial](/cyberpunk-2077-modding/for-mod-creators-theory/3d-modelling/hair-modeling-beginner-tutorial.md) for how to create hair from scratch in Blender
* For information on [NPV: How to add a CCXL hair color to an NPV](/cyberpunk-2077-modding/modding-guides/npcs/npv-v-as-custom-npc/npv-v-as-custom-npc/how-to-add-a-ccxl-hair-color-to-an-npv.md), check the corresponding guide
* The [Cheat Sheet: Hair](/cyberpunk-2077-modding/for-mod-creators-theory/references-lists-and-overviews/cheat-sheet-head/hair.md) has lists of all existing hairs and their files


---

# 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://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/npcs/guides-all-about-hair.md?ask=<question>&goal=<user_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.