> For the complete documentation index, see [llms.txt](https://ccxl-tattoo-toolkit.gitbook.io/main/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ccxl-tattoo-toolkit.gitbook.io/main/tutorial/the-.app-file.md).

# The .app file

We are almost done creating a custom tattoo with the *CCXL Tattoo Toolkit!* There are just a few more things we need to take care of—a rather easy step is configuring our <kbd>*.app*</kbd> file.

Go ahead, open it!

<figure><img src="https://181024330-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDecuWTGPSBrawvB4cIcq%2Fuploads%2Fwifvn2Ee8cOXu4Tasoyy%2FScreenshot%202025-03-14%20223038.png?alt=media&amp;token=f88ff6ac-1ecb-40c3-ba32-abbbfe473a4c" alt=""><figcaption></figcaption></figure>

As you can see, we have an appearance definition for each variant of our tattoo (female and male) with [names that we saw](/main/tutorial/configuring-the-appearanceinfo.md#appearance-definitions) when configuring our <kbd>gameuiAppearanceInfo</kbd>.

Go ahead and expand one of these appearance definitions:

<figure><img src="https://181024330-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDecuWTGPSBrawvB4cIcq%2Fuploads%2FFfRYeb5Nf3NEPrjM3dWm%2FScreenshot%202025-03-14%20230138.png?alt=media&amp;token=5dbab3bf-49df-4fed-b2d9-f27af8a023de" alt=""><figcaption></figcaption></figure>

There isn't much to be changed here. Make sure that <kbd>name</kbd> is consistent with the appearance definition in your .inkcc from earlier. Ensure the path in <kbd>resolvedDependencies</kbd> points to your <kbd>*.mesh*</kbd> file, or <kbd>*.morphtarget*</kbd> for female chest tattoos, and has a "*soft"* flag (see why, [here](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-creators-theory/files-and-what-they-do/dependency-resolution#raref)).

<kbd>visualTags</kbd> should be consistent with the gender that the appearance definition is for.

Now, expand <kbd>components</kbd> and take a look at <kbd>entGarmentSkinnedMeshComponent</kbd>:

<figure><img src="https://181024330-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDecuWTGPSBrawvB4cIcq%2Fuploads%2FMWeCvoC48hR32p8tbius%2FScreenshot%202025-03-14%20232035.png?alt=media&amp;token=d9a62671-9fee-478a-95fb-97dcafaaa4f7" alt=""><figcaption></figcaption></figure>

Despite the amount of things to look at here, you only need to verify that <kbd>mesh</kbd> points to the correct <kbd>*.mesh*</kbd> file, and <kbd>meshAppearance</kbd> calls the correct appearance in the mesh.&#x20;

In this circumstance, <kbd>name</kbd> can be changed to anything ("Component" is the default name) but I like to keep it consistent with the <kbd>meshAppearance</kbd>.

Verify the same for opposite gender and [move on.](/main/tutorial/the-.xl-file.md)

> ***For chest tattoos,** the female appearance component is&#x20;*<kbd>*entMorphTargetSkinnedMeshComponent*</kbd>*&#x20;, but the process stays the same; instead of&#x20;*<kbd>*mesh*</kbd>*&#x20;you have&#x20;*<kbd>*morphResource*</kbd>*, which should point to your&#x20;*<kbd>*.morphtarget*</kbd>*&#x20;file.*
