> For the complete documentation index, see [llms.txt](https://docs.klipwallet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.klipwallet.com/klip-guide.md).

# Klip Guide

이 페이지는 Klip의 각종 가이드를 소개합니다.

본 문서는 Klip을 활용함에 있어 참고할 수 있는 각종 디자인/개발 가이드를 안내하고 있습니다.

| 항목                                                    | 설명                             | 비고      |
| ----------------------------------------------------- | ------------------------------ | ------- |
| [Design Guidelines](/klip-guide/design-guidelines.md) | 클립 및 클립 드롭스에 게시를 위한 각종 디자인 가이드 | 디자인 가이드 |
| [NFT Metadata Standards](/klip-guide/metadata-std.md) | Klip에서 사용하는 NFT 메타데이터 속성 표준    | 개발 가이드  |

이 문서 혹은 Klip에 관한 문의는 [개발자 포럼](https://klipforum.zendesk.com)을 방문해 도움을 받으십시오.


---

# 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.klipwallet.com/klip-guide.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.