> For the complete documentation index, see [llms.txt](https://zh.chanyuan8.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zh.chanyuan8.org/xue-feng-wen-ji-chan-yuan-pian/fei-fan-de-jia-yuan-gong-xun-ehuang-cao.md).

# 非凡的家园功勋——娥皇草

娥皇草：导游助手，生命禅院第二家园首次驻地奠基者，家园仙韵公司门市设计者和具体操作者，雪峰和生命禅院名称奠基者。

生命禅院的每一步发展都浸透了娥皇草的心血，导游雪峰的名称是娥皇草提出并确定的，生命禅院原先叫“超时空之路”，是娥皇草将“超时空之路”修改为“生命禅院”。

娥皇草是生命禅院导游的妻子，生命禅院理论体系创建之初，导游得到了大智大慧大勇的娥皇草全力支持，一个人基本承担了原先家庭的主要工作和金冠市场营销公司的主要工作，没有娥皇草的付出，就没有今天的生命禅院。

太原游戏期间，家园派遣先遣组三人前往云南寻找驻地，娥皇草是先遣组成员之一，为家园在云南创建付出了辛劳，家园仙韵公司的门市部是娥皇草一手策划，配合恒德院长购置门市所需设施并亲自设计布置准时对外营业。

娥皇草是家园的艺术监制，今天我们能拥有干净整洁的第二家园，这完全是娥皇草精心设计并严格要求的结果。

作为导游的妻子，娥皇草承受了巨大的感情折磨，导游是“花心大萝卜”，一路走来洒下一路情，作为妻子，亲身体验到了导游情感的不专一，这是对娥皇草情感上的巨大折磨和虐待，尤其是进驻第二家园后解体夫妻关系，这更是对娥皇草沉重的打击，但是，大智大慧大勇的娥皇草为了家园的利益，为了全体人类的幸福，默默地承受了这一切。

最近，由于天国客栈仙韵公司门市缺少人手，娥皇草毅然决然提出前往公司门市工作，离开了凤凰峡，离开了导游，这是多么非凡的举动啊！

娥皇草，雪峰爱你！家园爱你！你是一位非凡的女性，你是生命禅院伟大的功勋！

2010/11/17


---

# 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://zh.chanyuan8.org/xue-feng-wen-ji-chan-yuan-pian/fei-fan-de-jia-yuan-gong-xun-ehuang-cao.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.