> 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/floor-plan.md).

# 1. 2D/3D 도면(Floor Plan)

2D/3D 도면 뷰어 소개와 컨텐츠 활용 방법에 대해 소개합니다.

## 2D/3D 도면: 가이드

{% embed url="<https://planner.archisketch.com/?mode=2&projectId=XkhkKDK233D748440524D18>" %}

아키스케치는 다양한 3D/VR/AR 콘텐츠(**2D/3D 도면 뷰어**, **렌더 이미지**, **720°/파노라마 뷰어**, **모델 뷰어**)를 제공합니다.

해당 페이지는 **2D/3D 도면 뷰어**에 대해 소개하고, 이를 활용하는 **활용 방법**에 대하여 안내해 드립니다. 모델 뷰어 가이드 목차는(은) **1️⃣ 하단 목차 테이블** 또는 **2️⃣ 좌측 Content Manual > Model Viewer 내부 메뉴**를(을) 통해 확인할 수 있습니다.

### 📌 2D/3D 도면: 소개

| 제목                              | 가이드 URL                                                                  |
| ------------------------------- | ------------------------------------------------------------------------ |
| **1. 2D/3D 도면(Floor plan): 소개** | [1.1. 2D/3D 도면: 소개](/guide/dev-kr/contents/floor-plan/introduce.md) |

### 📌 2D/3D 도면: 활용 방법

| 제목                                  | 가이드 URL                                                                             |
| ----------------------------------- | ----------------------------------------------------------------------------------- |
| **1. 2D/3D 도면(Floor plan): 공유/임베드** | [1.2. 2D/3D 도면: 공유/임베드](/guide/dev-kr/contents/floor-plan/share-embed.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.archisketch.com/guide/dev-kr/contents/floor-plan.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.