xindoo/agentic-design-patterns: a Chinese translation of the 21-pattern agent book

What xindoo/agentic-design-patterns actually is

The repository is a Chinese translation of a book titled Agentic Design Patterns. The README describes the source book as covering 21 core patterns and several appendix chapters, moving from basics such as prompt chaining, routing and parallelization, through reflection, tool use and planning, up to multi-agent collaboration, memory management and knowledge retrieval, and finishing with guardrails, evaluation and monitoring.

The people this is for are Chinese-reading engineers, architects and product managers who want the pattern vocabulary without working through the English original. That framing matters because the repository is a text corpus, not a library. There is no package to import, no server to start, no API to call. If you arrived expecting a framework that implements reflection or routing for you, the README does not offer one, and the top-level entries confirm it: chapters, images, layouts, a glossary and a translation guide.

One structural detail is easy to miss. The repository keeps a parallel original/ directory holding the untranslated source files, and the README lists it as the original backup. That gives the project a property most translation efforts lack: the English source sits in the same tree as the Chinese text, so a reviewer can diff them without leaving the repository.

How the book is laid out across chapters, appendices and the site

The content lives in Markdown files under chapters/, named after the English pattern titles, for example Chapter 5_ Tool Use.md and Chapter 18_ Guardrails_Safety Patterns.md. Appendices A through G sit alongside them, covering advanced prompting, agentic interaction from GUI to real-world environments, a quick overview of agentic frameworks, AgentSpace, agents on the CLI, agent reasoning engines, and coding agents. Four further files round out the set: a FAQ, a glossary, an index of terms and a conclusion.

The README counts 32 files in total, made up of 21 core chapters, 7 appendices and 4 other items, and states that all 32 have completed a first translation pass and are in a review state. The progress table in progress.md is the file to check for the current per-file status, since the README's own summary is a snapshot of that table.

Navigation is handled two ways. SUMMARY.md is the GitBook table of contents, and the site is served through Jekyll, with _config.yml, a Gemfile, _includes/navigation.html and _layouts/default.html in the tree. The CNAME file points the GitHub Pages build at a custom domain, and the README gives the reading address as adp.xindoo.xyz. The same README mentions PDF and EPUB downloads in the repository description, though the file listing shown here does not include a build directory for them, so treat the online edition as the reliable artefact.

Translating a chapter: the glossary and the review pass

There is nothing to install. The README gives the contribution path directly, and it is the same flow you would use to fix a translation or add a review note. Fork the repository, branch, commit, push, open a pull request.

The example branch, commit and push commands from the README look like this:

git checkout -b feature/translate-chapter-xx
git commit -am '完成第XX章翻译'
git push origin feature/translate-chapter-xx

After pushing, the README says to open a pull request against the repository. The commit message in that example is in Chinese, matching the translation work.

Before editing any prose, the README points to translation-guide.md and glossary.md. The guide's stated rules are worth reading literally: keep the paragraph and heading structure of the original, use the glossary for terminology, leave code samples and command lines in English, keep image references pointing at the images/ directory, follow Markdown formatting, and self-proofread before submitting. The README also notes that the first pass is finished, so the remaining work is second-pass review and quality checking rather than fresh translation.

A practical first task is to open progress.md, pick a file marked as reviewed, and compare it against its counterpart under original/ for terminology drift against glossary.md. That comparison is the workflow the repository is built around.

Where this repository stops being the right tool

The project is a translation, and the README states that it follows the licence terms of the original book, with the translated content described as being for study and exchange. That is the boundary. There is no licence identifier recorded for the repository itself in the metadata available here, and the README does not spell out redistribution terms beyond that sentence. If you plan to reuse chapters inside training material or a commercial product, the repository does not give you a clear answer, and you would need to resolve the original book's terms first. This is a description of what the files say, not legal advice.

The second boundary is maintenance shape. The last push was on 2026-08-30, and the releases are numbered sequentially up to v76, which suggests frequent small snapshots rather than milestone versions. The README's own progress section says the translation is complete but under review, so a chapter can change under you between reads. Pin a commit if you are citing a passage.

The third boundary is language. The repository is organised around the Chinese edition. The original/ directory holds English source files as a backup for comparison, and there is a bilingual/ directory in the tree, but the README does not describe bilingual/ as a published English edition. If you need the English text as your primary reading copy, this is not the project for that.

Reading it against the English original and other agent references

The obvious alternative is the English source book itself, which the README names as Agentic Design Patterns and which the repository preserves under original/. The difference in approach is not quality, it is role. The English files are the reference text; the Chinese files under chapters/ are a derived reading copy with a glossary that fixes terminology across all 32 files. That glossary is the thing a loose collection of translated blog posts does not have, and it is the reason to prefer this repository over scattered Chinese write-ups of the same patterns.

A second comparison point is the appendix on agentic frameworks, which the README lists as Appendix C, a quick overview of agentic frameworks. That chapter surveys frameworks rather than being one. So the honest split is: read this repository to decide which pattern you need, then go to a framework to implement it. The book describes prompt chaining, routing and reflection as patterns; it does not ship a runtime for them.

A third option is simply reading the online edition at adp.xindoo.xyz without cloning anything. That is the lowest-friction path and it is the one the README leads with. Cloning only pays off if you want to diff against original/ or send a correction.

Frequently asked questions about the Chinese edition

The repository ships its own FAQ file at chapters/Frequently Asked Questions_ Agentic Design Patterns.md, separate from the questions below. That file is part of the translated set and is the place to look for questions about the book's content. The entries here are limited to what the README and the repository structure can support, so several common questions about the book's substance are deliberately left out rather than guessed at.

On cost and upkeep: the project publishes numbered releases, with v76 dated 2026-08-30, v75 dated 2026-08-24 and v74 dated 2026-07-03. Those dates are the only maintenance signal available, and they show a burst of activity in late August after a quieter July. There is no changelog content in the repository, so what changed between v74 and v76 is not documented.

On the site build: the presence of _config.yml, Gemfile, _includes/ and _layouts/ indicates a Jekyll site, and CNAME indicates a custom domain, which matches the adp.xindoo.xyz address in the README. The README does not document how to build the site locally, so anyone wanting to preview changes would need to infer the Jekyll setup from those files.

Editorial conclusion

Adopt it as a Chinese reading companion if you are studying agent architecture and want the patterns in your own language, and check the online edition at adp.xindoo.xyz plus progress.md before relying on any single chapter, because the README states the text is translated but still moving through review. Do not treat it as an SDK, and do not expect an English version, since the repository is built around the Chinese translation and keeps the original English files only as a backup. Before quoting a chapter, open the matching file under original/ and compare it line by line.

Frequently asked questions

Official sources

1. Issues
2. Project website
3. README
4. Releases
5. xindoo/agentic-design-patterns on GitHub