> For the complete documentation index, see [llms.txt](https://book.funcd.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://book.funcd.org/wen-zhang/posts.md).

# 全部文章

文章按主题归档，而不是按时间。找旧文时用主题更快，写新文时也不用纠结"该放哪一年"。

## 分类

| 分类 | 写什么                | 入口                                     |
| -- | ------------------ | -------------------------------------- |
| 技术 | 工程实践、排障复盘、源码阅读、工具链 | [posts/tech](/wen-zhang/posts/tech.md) |
| 随笔 | 工作方法、阅读感想、职业思考     | [posts/life](/wen-zhang/posts/life.md) |

还没成形的碎片放在 [笔记本](/bi-ji/notes.md)，攒够了再升级成正式文章。

## 标签约定

GitBook 没有内建标签系统，所以标签写在每篇文章 frontmatter 的 `description` 之后的正文首行，形如：

```markdown
> `Kubernetes` · `排障` · 2026-07-27
```

这样在站内搜索关键词就能把同类文章捞出来。常用标签：

* `Kubernetes` `可观测性` `PostgreSQL` `Go` `Python`
* `排障` `复盘` `源码` `工具` `方法论`

{% hint style="info" %}
新增分类时记得同步改三处：新建 `posts/<分类>/README.md`、在本页表格补一行、在根目录 [SUMMARY.md](https://github.com/MRZHUH/website/tree/main/SUMMARY.md) 挂上导航。漏掉 SUMMARY 的话页面不会出现在侧边栏。
{% endhint %}


---

# 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://book.funcd.org/wen-zhang/posts.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.