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

# 記事の内容

記事の内容は、要約欄の下にあるドラッグ＆ドロップ式のビルダーで作成できます。ページビルダーと同じように、ブロックやカラムを追加したり、ウィジェットメニューから好きなウィジェットを配置したりできます。

また、\[高品質記事を作成]ボタンから、AIに本文作成を任せることも可能です。

![ビルダー画面１](/files/1OnKHGBWZ9lP6yqJommW)

![ビルダー画面２](/files/uMBrgTRyxBYBEqMyehZB)

<figure><img src="/files/oFR5sqa2I17f5E1LuAwS" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.opusbooster.com/blog/getting-started/article-content.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
