> For the complete documentation index, see [llms.txt](https://docs.theseaai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.theseaai.com/main/jp/tsru/riakushon.md).

# リアクション

リアクションを使うと、シーンに「スタンプ」で印を付けられます。承認状況の表示、優先候補の強調、問題点やその他の重要なメモのフラグ付けに使えます。

<figure><img src="https://3749661168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOUQ3EAPIPziQuBKQgmTy%2Fuploads%2FmbCkZMj7SmCBLZgbm4vl%2Fgitbook_reaction.png?alt=media&amp;token=e5e824f8-039f-407c-8be3-ed173bd8044a" alt=""><figcaption></figcaption></figure>

***

## 使い方

{% stepper %}
{% step %}

#### 「リアクション」ツールを選択

シーンの下で、次を選択します <i class="fa-stamp" style="color:$primary;">:stamp:</i> <kbd><mark style="color:$primary;">**リアクション**<mark style="color:$primary;"></kbd> ツールメニューから、またはショートカットで <kbd><mark style="color:$primary;">**C**<mark style="color:$primary;"></kbd> .
{% endstep %}

{% step %}

#### リアクションステッカーを選択

次の4種類から選べます:

* ❤️&#x20;
* ☀️&#x20;
* 📍&#x20;
* ⚠️&#x20;
  {% endstep %}

{% step %}

#### リアクションをスタンプする

プレイグラウンドのどこにでもリアクションをスタンプできます。&#x20;

ステッカーの種類が選択されている限り、再選択せずに複数箇所へすばやくスタンプできます。
{% endstep %}

{% step %}

#### リアクションの管理

* **リアクションを移動**：スタンプをクリックしてドラッグします。&#x20;
* **リアクションを削除:** スタンプを削除するには、 <kbd><mark style="color:$primary;">**Delete**<mark style="color:$primary;"></kbd> キー
  {% endstep %}
  {% endstepper %}


---

# 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.theseaai.com/main/jp/tsru/riakushon.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.
