> For the complete documentation index, see [llms.txt](https://docs.rome.builders/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rome.builders/ko/resources/community.md).

# 커뮤니티

Rome Protocol에서 개발할 때 도움을 받을 수 있는 곳 — Discord, Telegram, GitHub, 그리고 Rome Academy 강좌.

## 채널

| 채널           | 링크                                                           | 목적              |
| ------------ | ------------------------------------------------------------ | --------------- |
| Discord      | [discord.gg/vZ9rnCdNSB](https://discord.gg/vZ9rnCdNSB)       | 개발자 지원, 커뮤니티 토론 |
| Telegram     | [t.me/+tdnr-M6kcngxYzhk](https://t.me/+tdnr-M6kcngxYzhk)     | 공지 및 업데이트       |
| GitHub       | [github.com/rome-protocol](https://github.com/rome-protocol) | 소스 코드, 이슈, 기여   |
| Rome Academy | [schola.rome.builders](https://schola.rome.builders/)        | Rome에서 개발하는 강좌  |
| 웹사이트         | [rome.builders](https://www.rome.builders)                   | 개요 및 문서 링크      |

## 도움 받기

1. **문서를 확인하세요** — 이 문서는 가장 흔한 질문들을 다룹니다
2. **Discord에서 검색** — 이미 답변이 있을 수 있습니다
3. **Discord에 질문하세요** — 개발자 커뮤니티는 활발하고 도움이 됩니다
4. **GitHub 이슈를 여세요** — 버그, 기능 요청 또는 문서 개선을 위해

## 기여하기

Rome Protocol 저장소는 GitHub의 다음 위치에 있습니다 [github.com/rome-protocol](https://github.com/rome-protocol). 풀 리퀘스트를 통한 기여를 환영합니다.


---

# 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.rome.builders/ko/resources/community.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.