> For the complete documentation index, see [llms.txt](https://docs.archisketch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.archisketch.com/guide/dev-kr/contents/custom-furniture/asset-upload.md).

# 5.1. 에셋 업로드

커스텀 가구를 구성하는 부품 / 반제품의 모델링을 서버에 올려서 "부품"으로 만들기 위한 단계입니다.

{% stepper %}
{% step %}

## 파라메트릭 라이브러리 > 부품 라이브러리 진입

![](https://3169559498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FgwWAdGTNDn40D9mxww%2Fuploads%2Fgit-blob-cbbce8684f736f37c3717856e10050eff17f9924%2Fcustom-furniture_asset-upload-1.png?alt=media)
{% endstep %}

{% step %}

## 부품 생성하기 진입

![](https://3169559498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FgwWAdGTNDn40D9mxww%2Fuploads%2Fgit-blob-18a30c61eaf37919581eeed1894319e90c41ec50%2Fcustom-furniture_asset-upload-2.png?alt=media)
{% endstep %}

{% step %}

## 부품 정보 기입 및 모델링 파일 업로드

![](https://3169559498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FgwWAdGTNDn40D9mxww%2Fuploads%2Fgit-blob-1323ff8a60350b5f2f64429ee0a4215a1468fe1d%2Fcustom-furniture_asset-upload-3.png?alt=media)

* 모델링 파일 주의 사항
  * 지원 포맷은 `GLTF` / `OBJ` / `SKP` 만 지원합니다.
  * GLTF 같은 경우 빈번히 필수 파일이 누락되어 오류가 나는 케이스가 발생합니다. (필수 파일은 Bin / gltf / png)
    {% endstep %}
    {% endstepper %}


---

# 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://docs.archisketch.com/guide/dev-kr/contents/custom-furniture/asset-upload.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.