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

# \[生活] 在香檳的日子

Last update: April 20th, 2025

如果你問我誰把香檳的日子寫的最好，我會私心推薦 [『入境大廳』](https://www.books.com.tw/products/0010913533?srsltid=AfmBOoqML6xEopdSY8P09rWPXmH8-t3eMhqpcJGtKEjzhhRDwslMzQCP) 這本書。我把在香檳的生活簡單分類成兩篇來寫: \
(一) 抵達香檳之前或之初: 可以參考生活指南，用生活的角度切入這邊的生活樣態，順便幫助你整理你的行李\
(二) 開始在香檳生活之後有哪些地方可以去探索呢?

歡迎你跟我分享你的香檳生活


---

# 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://uiuc-docs.tichung.com/life.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.