> For the complete documentation index, see [llms.txt](https://docs.wicle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wicle.io/other/usecase.md).

# ユースケース

- [特定の行動をしたユーザーの操作フローを見て、UI/UXの改善ポイントを見つける](https://docs.wicle.io/other/usecase/specific-behavior.md)
- [一連の行動フローの中で改善が必要な箇所を見つける](https://docs.wicle.io/other/usecase/funnel.md)
- [打ち合わせ前に顧客の状況を把握し、事前準備の質を高める](https://docs.wicle.io/other/usecase/meeting.md)
- [プロダクトをよく利用してくれている人（ファン）の特徴を見つける](https://docs.wicle.io/other/usecase/fan.md)
- [顧客の変化に素早く気づいて、アクションを取る](https://docs.wicle.io/other/usecase/changing-point.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 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.wicle.io/other/usecase.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.