> For the complete documentation index, see [llms.txt](https://godomall-help.nhn-commerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://godomall-help.nhn-commerce.com/design-editor/start.md).

# PART III : 에이전시와 함께 시작하기

디자인 에디터의 혜택은 에이전시와 방향을 맞추는 것에서 시작됩니다. 이 파트에서는 미팅 준비부터 요청 문구, 에이전시와의 대화 방법까지 실전 가이드를 안내합니다.

***

### 이 파트에서 다루는 내용

* 에이전시 미팅 전 준비 체크리스트 — 미팅 전 반드시 확인할 5가지 항목
* 핵심 요청 문구 — 이 문장을 그대로 전달하세요 — 바로 사용할 수 있는 미팅 스크립트
* 에이전시와 방향을 맞추는 대화 가이드 — 처음 논의할 때 참고할 수 있는 대화 포인트


---

# 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://godomall-help.nhn-commerce.com/design-editor/start.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.
