> For the complete documentation index, see [llms.txt](https://docs.decentraland.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decentraland.org/creator/content-creator-ko/wearables-and-emotes.md).

# 웨어러블 및 이모트

- [웨어러블](https://docs.decentraland.org/creator/content-creator-ko/wearables-and-emotes/wearables.md): Decentraland용 웨어러블 NFT 개요
- [웨어러블 만들기](https://docs.decentraland.org/creator/content-creator-ko/wearables-and-emotes/wearables/creating-wearables.md): Decentraland 웨어러블 제작을 위한 팁과 가이드라인
- [스프링 본](https://docs.decentraland.org/creator/content-creator-ko/wearables-and-emotes/wearables/spring-bones.md): 스프링 본으로 웨어러블에 동적 물리 효과를 추가합니다
- [연결된 웨어러블](https://docs.decentraland.org/creator/content-creator-ko/wearables-and-emotes/wearables/linked-wearables.md): 3자 토큰의 웨어러블 표현
- [이모트](https://docs.decentraland.org/creator/content-creator-ko/wearables-and-emotes/emotes.md): Decentraland용 이모트 NFT 개요
- [이모트 만들기](https://docs.decentraland.org/creator/content-creator-ko/wearables-and-emotes/emotes/creating-emotes.md): Decentraland 이모트를 만드는 팁과 가이드라인.
- [아바타 리그](https://docs.decentraland.org/creator/content-creator-ko/wearables-and-emotes/emotes/avatar-rig.md): 아바타 리그의 기본 사항.
- [이모트의 파티클](https://docs.decentraland.org/creator/content-creator-ko/wearables-and-emotes/emotes/particles-in-emotes.md): Armature를 사용해 이모트에서 파티클을 내보내는 방법
- [소품 및 사운드](https://docs.decentraland.org/creator/content-creator-ko/wearables-and-emotes/emotes/props-and-sounds.md): 이모트에 소품과 사운드를 추가하는 가이드라인.
- [리그 기능](https://docs.decentraland.org/creator/content-creator-ko/wearables-and-emotes/emotes/rig-features.md): 아바타 리그와 다운로드 가능한 파일에 대한 기능.
- [컬렉션 관리](https://docs.decentraland.org/creator/content-creator-ko/wearables-and-emotes/manage-collections.md): 웨어러블 및 이모트 컬렉션을 관리하세요
- [컬렉션 만들기](https://docs.decentraland.org/creator/content-creator-ko/wearables-and-emotes/manage-collections/creating-a-collection.md): Decentraland 컬렉션을 만드는 가이드라인
- [웨어러블 업로드](https://docs.decentraland.org/creator/content-creator-ko/wearables-and-emotes/manage-collections/uploading-wearables.md): 에디터에 웨어러블을 업로드하는 가이드라인
- [이모트 업로드](https://docs.decentraland.org/creator/content-creator-ko/wearables-and-emotes/manage-collections/uploading-emotes.md): 에디터에 이모트를 업로드하는 가이드라인
- [스마트 웨어러블 업로드](https://docs.decentraland.org/creator/content-creator-ko/wearables-and-emotes/manage-collections/uploading-smart-wearables.md): 에디터에 스마트 웨어러블을 업로드하는 가이드라인
- [컬렉션 게시](https://docs.decentraland.org/creator/content-creator-ko/wearables-and-emotes/publishing-collections.md)
- [컬렉션 게시](https://docs.decentraland.org/creator/content-creator-ko/wearables-and-emotes/publishing-collections/publishing-collections.md): Decentraland 웨어러블의 게시 및 승인 프로세스에 대한 설명
- [큐레이션 위원회](https://docs.decentraland.org/creator/content-creator-ko/wearables-and-emotes/publishing-collections/curation-committee.md): 웨어러블 큐레이션 위원회에 대한 설명과 논의


---

# 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.decentraland.org/creator/content-creator-ko/wearables-and-emotes.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.