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

# 02 · 设计

系统架构设计与 UI 设计两个维度的实践规范，共同目标是让 AI 在设计层面安全、稳定地参与工作。

***

## 本章节文档

### 系统架构

| 文档                                                                             | 内容                              |
| ------------------------------------------------------------------------------ | ------------------------------- |
| [architecture-patterns.md](/haiqing-docs/02-design/architecture-patterns.md)   | 分层边界、接口契约、AI 可读性、边界标注等架构模式      |
| [domain-knowledge-layer.md](/haiqing-docs/02-design/domain-knowledge-layer.md) | 领域知识层的三类构成（产品需求、工程规约、领域规约）及注入方式 |

### UI 设计

| 文档                                                                   | 内容                             |
| -------------------------------------------------------------------- | ------------------------------ |
| [ui-design-with-ai.md](/haiqing-docs/02-design/ui-design-with-ai.md) | AI 辅助 UI 设计的方法论，含风格学习与项目资产管理   |
| [ui-style-guide.md](/haiqing-docs/02-design/ui-style-guide.md)       | UI 风格指南模板（色彩、字体、间距、圆角、动效等基准维度） |
| [design-decisions.md](/haiqing-docs/02-design/design-decisions.md)   | 设计决策日志，记录架构与 UI 两类重要决策         |


---

# 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://zhouhao4221.gitbook.io/haiqing-docs/02-design.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.