> 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/intro-jp/update-note/2026/202605/20260514.md).

# \[2026.05.14] エディター機能を刷新

#### 1. ダッシュボード

**（新規）Archisketch AI機能を追加**

ダッシュボードメニューにArchisketch AIページが新たに追加されました。これからは、図面検索から家具配置、レンダリング撮影まで、プロジェクトに必要な作業を一か所で行えます。

![](https://1206381844-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMWuDtKHjyUXqBIf7Q6Zw%2Fuploads%2Fgit-blob-1e775434a1bf6377a604d91d5f831508abf72c1b%2F202605_20260514-1.png?alt=media)

#### 2. エディタ

**（新規）ミニマップ機能を追加**

エディタにミニマップ機能が追加されました。左下のハンドルをドラッグしてお好みのサイズに調整でき、天井・仕上げ材・パラメトリックエディタを含む2D/3D図面エディタ全般でご利用いただけます。

![](https://1206381844-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMWuDtKHjyUXqBIf7Q6Zw%2Fuploads%2Fgit-blob-faa720c13c978cfb1e1acbceb6ad188e35229efc%2F202605_20260514-2.png?alt=media)

#### 3. モジュラー

**（バグ改善）製品タイプ設定**

モジュラーで設定した製品タイプが2D/3D図面エディタで正常に動作しなかった問題を修正しました。これで、両エディタ間の設定が同じように適用されます。

![](https://1206381844-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMWuDtKHjyUXqBIf7Q6Zw%2Fuploads%2Fgit-blob-f93bc08af5082ccd6bc18c037bd73780696bd547%2F202605_20260514-3.png?alt=media)


---

# 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/intro-jp/update-note/2026/202605/20260514.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.