> For the complete documentation index, see [llms.txt](https://atiysus-organization.gitbook.io/aty-scripts/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atiysus-organization.gitbook.io/aty-scripts/weapon-editor/guide/ai-designs.md).

# AI designs

## AI designs

A design is plain JSON, so any capable AI chat can write one. The studio does the hard part for you: it builds a prompt containing the entire format specification plus your theme, and you paste back what the AI answers with.

No image files, no tools, no account anywhere.

### The workflow

**1. Open the AI design panel**

It is on the right-hand side of the Skin Studio.

**2. Choose Still or Animated**

This matters more than it looks. Left to itself a model almost always returns a static design, because the static layer types are described first and there are more of them. Picking **Animated** adds an explicit instruction to build the design around exactly one moving pattern.

**3. Type a theme**

Anything descriptive — *"a rusted post-apocalyptic shotgun"*, *"deep space, purple nebula"*, *"police issue, navy and white"*. There are presets to tap if you would rather not think of one.

**4. Press Build prompt, then Copy**

That copies the whole specification plus your theme.

{% hint style="info" %}
If the copy button reports the clipboard is blocked, select the text in the box and copy it manually. Some clients block programmatic clipboard access inside NUI.
{% endhint %}

**5. Paste it into any AI chat**

Any model that can return JSON will do.

**6. Paste the answer into the Share box**

The Share box is just below the AI panel. It accepts **raw JSON exactly as the AI returned it** — no cleaning up, no re-encoding — and also accepts `ATY1:` share codes.

The design loads as an editable draft. Move things, recolour, then **Save**.

### Doing it by hand

You do not have to use the panel. Hand any AI the specification file and ask for one design:

> Give me ONE weapon skin design as raw JSON, nothing else. Theme: a rusted post-apocalyptic shotgun.

The specification lives in `AI_SKINS.md` in the resource root, and it is the same text the studio's Build prompt copies. It is also reproduced as Design format.

### What to expect back

```json
{
  "base": "#4a3a2c",
  "layers": [
    { "type": "pattern", "pattern": 0, "color": "#7a4a22", "opacity": 0.55, "blend": "multiply" },
    { "type": "pattern", "pattern": 4, "color": "#2a2018", "opacity": 0.4, "blend": "normal" },
    { "type": "stroke", "points": [[0.05,0.3],[0.28,0.36],[0.52,0.28],[0.78,0.38],[0.96,0.31]],
      "color": "#1d150f", "width": 0.02, "opacity": 0.8, "blend": "normal" },
    { "type": "decal", "decal": 7, "color": "#8a5a2b", "x": 0.5, "y": 0.5,
      "scale": 1.4, "rot": 0, "opacity": 0.5, "blend": "overlay" }
  ]
}
```

Rusty base, mottled dots multiplied for corrosion, a dark camo break-up, one scratch, and a faint frame for a worn edge. Four layers, three colours.

### When it does not work

**The paste box rejects it.** Almost always a wrapper the model added — a markdown code fence, a `"design":` wrapper object, or a sentence before the JSON. The design must be the bare object shown above. Delete everything around it.

**It came back invalid or from a newer version.** The same thing: something in the JSON is not a field the schema knows. Ask the model to return only the fields in the specification.

**The design saved but the weapon looks black in places.** No `base`. The whole texture is replaced, so anything a layer does not cover is transparent, which reads as black. Add a base colour.

**It used an image that will not load.** Models like to invent image URLs. Ask for built-in `pattern` and `decal` layers only — those always exist, while `image` layers depend on what your server has installed and allowed.

**Nothing moves, even though you asked for animation.** The pattern index has to be 14–21, and `speed` must not be `0`. Pick **Animated** in the panel rather than asking for motion in the theme text.

### See also

* Design format — every layer type and field
* Skin Studio — the editor itself