> For the complete documentation index, see [llms.txt](https://docs-embed.anyflow.jp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-embed.anyflow.jp/wizard-editor/advanced-setting/markdown.md).

# Markdown記法

ウィザードエディタにて、説明文を記載する箇所（スクリーンの説明 や フィールドの説明 等）は、\
以下のMarkdown記法を利用できます。

## 強調

### 斜体

```markdown
*斜体* または _斜体_
```

### 太字

```markdown
**太字** または __太字__
```

## 打ち消し線

```markdown
~~打ち消し線~~
```

## リスト

### 番号なしリスト

```markdown
- 項目1
- 項目2
  - サブ項目1
  - サブ項目2
```

### 番号付きリスト

```markdown
1. 項目1
2. 項目2
  a. サブ項目1
  b. サブ項目2
```

## 引用

```markdown
> これは引用です。
```

## コード

### インラインコード

```markdown
`コード`
```

### コードブロック

````markdown
```
コード
コード
```
````

## リンク

```markdown
[リンクテキスト](http://example.com)
```

## 画像

```markdown
![代替テキスト](http://example.com/image.jpg)
```


---

# 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-embed.anyflow.jp/wizard-editor/advanced-setting/markdown.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.