> For the complete documentation index, see [llms.txt](https://ujhhgtgteams.gitbook.io/wekit-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ujhhgtgteams.gitbook.io/wekit-docs/feature-request-guide.md).

# 建议反馈指南

> **⚠️ 在反馈任何建议前, 请先阅读** [**提问的智慧**](https://github.com/ryanhanwu/How-To-Ask-Questions-The-Smart-Way/blob/main/README-zh_CN.md)**。**

## 反馈渠道

**唯一的反馈渠道是** [**GitHub Issues**](https://github.com/Ujhhgtg/WeKit/issues)**。**

请勿通过以下渠道反馈建议, 此类反馈不会被处理:

* Telegram 讨论组
* 开发者的 Telegram 私聊
* 其他任何非 GitHub Issues 的渠道

## 提交 Issue 前的准备

在提交建议前, 请先确认:

1. **你的建议是否已经有人提过？** 搜索 [已有 Issues](https://github.com/Ujhhgtg/WeKit/issues) 和 [常见问题](/wekit-docs/faq.md) 避免重复提交。
2. **是否与模块现有功能重叠？** 确认该功能目前确实不存在, 而非尚未发现已有实现。

## 高质量的建议应当包含

建议越清晰具体, 被采纳和实现的可能性越大。一个高质量的建议通常包含:

* **使用场景**: 你希望解决什么问题, 在什么情况下需要这个功能
* **期望行为**: 详细描述你期望的功能应该怎么工作
* **参考实现**: 如果有其他类似应用或模块实现了类似功能, 提供参考有助于理解
* **可选方案**: 是否考虑过其他实现方式, 各自的优缺点

## Issue 处理流程

1. 提交 Issue 后, 维护者会进行标记和分类
2. 维护者会评估建议的可行性和适用范围, 可能会在 Issue 中讨论方案细节
3. 若决定实现, 将被标记并进入待办; 若决定不采纳, 会说明原因后关闭
4. **请勿在已关闭的 Issue 下继续讨论**——不同建议请开新 Issue
5. **请勿在 Telegram 等渠道催促进度**——维护者会在有空时处理


---

# 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://ujhhgtgteams.gitbook.io/wekit-docs/feature-request-guide.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.