Agentic Design Patterns: a Chinese translation tracked across 32 Markdown files

A translation project, not something you install

The repository is a Chinese translation of a book. Its primary language is recorded as HTML, its homepage is https://adp.xindoo.xyz, and it is deployed to GitHub Pages so the text can be read online rather than built from source. The book being translated is Agentic Design Patterns, and xindoo is named as the initiator and main maintainer of the translation project rather than as the author of the material.

There is no package to install and no API to call. The deliverable is 32 files of translated Markdown, which the README itemises as 21 core chapters, 7 appendices, and 4 other entries consisting of a frequently asked questions page, a glossary, an index of terms, and a conclusion.

The practical consequence is that there are two ways to use this repository and they have nothing in common. As a reader you open the published site or read the chapter files. As a contributor you translate or proofread text. Anyone expecting a runnable tool here will find a documentation project.

Twenty-one chapters, with the spaces encoded in the file names

Twenty-one chapters form the core of the book, running from prompt chaining through to exploration and discovery, and the README links each one to a file under chapters/.

The file names deserve a second look, because they encode their own separators. A chapter link resolves to a path of the form chapters/Chapter%201_%20Prompt%20Chaining.md, where %20 is an encoded space and an underscore follows the chapter number. The pattern holds across the whole list, from routing and parallelization through to prioritization.

For a reader browsing on GitHub this mostly does not matter. For anyone writing a script that walks the chapter list, a link checker, or a status tool, it does. The names contain percent encoding. PROJECT_STRUCTURE.md is the file to consult for how the directory is meant to be organised.

One appendix is marked as existing only online

Seven appendices extend the chapters, and one of them carries a qualification inside its own title. Appendix D is Building an Agent with AgentSpace, labelled on-line only. That label is the whole difference between it and the six beside it, though the README still links it to a file under chapters/.

The other six cover advanced prompting techniques, agentic interaction moving from a graphical interface to real world environments, a quick overview of agentic frameworks, agents on the command line, an inside look at the reasoning engines of agents, and coding agents.

The consequence for an offline reader is small but worth knowing before you clone and expect a complete book. Like every other item, it is linked to a file under chapters/, so check that file before relying on it offline.

The tree beside chapters/ explains the setup, and the one in the README is cut off

The top level carries more than chapter files. Alongside chapters/ there is original/, bilingual/ and images/, plus the Jekyll pieces _config.yml, _includes/, _layouts/ and CNAME, and the GitBook table of contents in SUMMARY.md. Two agent instruction files, AGENTS.md and CLAUDE.md, sit at the top level, and OPTIMIZE_README.md sits next to the README itself.

The README draws this out as a tree, and the drawing stops partway through the chapter listing.

agentic-design-patterns/
├── README.md                    # 项目说明文档（本文件）
├── SUMMARY.md                   # GitBook 目录文件
├── CONTRIBUTING.md              # 贡献指南
├── translation-guide.md         # 翻译规范指南
├── progress.md                  # 翻译进度追踪
├── glossary.md                  # 术语对照表
├── PROJECT_STRUCTURE.md         # 项目结构说明
├── _config.yml                  # Jekyll 配置文件
├── Gemfile                      # Ruby 依赖管理
├── CNAME                        # 自定义域名配置
├── chapters/                    # 翻译后的章节目录
│   ├── README.md                # 章节说明
│   ├── Agentic Design Patterns.md
│   ├── Chapter

The block ends on an incomplete line, at the first chapter file, so it shows the shape of the repository without finishing the job. Two directory names carry the real explanation: one is called original/ and the other bilingual/, which indicates that the untranslated text and a side-by-side reading are both kept in the repository rather than existing only in the published output.

Translating a chapter is three git commands and a pull request

The contribution path is set out as five steps, three of which are git commands you can run directly.

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

The branch name carries the chapter number, and the commit message template repeats that number in Chinese. A branch is created from a fork, the change is committed with the -am flags that stage all modifications and deletions at once, the branch is pushed to the fork, and the work becomes a pull request. The remaining two steps, forking the repository and opening the pull request, happen on GitHub rather than in a terminal.

The note underneath the list matters more than the commands. The README states that all translation files are already complete at first pass and that the main remaining task is a second round of review and quality checking. The mechanical route is therefore fully open, while the work the project actually wants is proofreading.

The guide keeps code in English and terminology in the glossary

Before translating anything, the project asks you to read translation-guide.md, and the rules it sets are specific about what must not change.

Paragraphs and heading levels stay as the original has them. Code samples and command lines stay in English, which is stated as a rule rather than left to judgement. Image references have to keep pointing at the images/ directory. Markdown formatting conventions apply, and a contributor is asked to proofread their own work before submitting. For terminology there is a single authority, glossary.md, described as a term-by-term mapping table.

Two consequences follow for the reader. A chapter mixes languages by design, with Chinese prose sitting beside English code, so the code cannot be read out of a translation without already knowing English. And when two chapters translate the same term differently, the glossary rather than the surrounding chapter settles it, which is the reason that file exists.

The progress checklist and the progress prose disagree

Two statements about translation status sit within a few lines of each other, and they do not match. The prose says that all 32 files, being 21 core chapters, 7 appendices and 4 other entries, have completed their initial translation and are currently awaiting review. A status checklist immediately below reports 32 of 32 translated and 32 of 32 reviewed. A later note says the main task now is a second round of review and quality checking.

Read together the checklist and the prose cannot both be right, since a project cannot be awaiting review and fully reviewed at the same moment. Nothing in the README reconciles the two statements.

For a reader the consequence is small and practical. Do not read 32 of 32 reviewed as a statement about polish, and do not read it as a defect either. progress.md is the file that tracks status, so check the chapter you actually depend on rather than generalising from the headline numbers.

Integer release tags, and a licence that names no terms

Two things worth checking before depending on this repository are both unsatisfying, and both are easy to see in the repository itself.

The release tags are integers. The three most recent are v76 published on 2026-08-30, v75 on 2026-08-24, and v74 on 2026-07-03. There is no major or minor component, so a tag tells you a position in a sequence and nothing about what changed. The last push to the repository was 2026-08-30, the same day as v76, so the newest tag does track the newest commit rather than trailing behind it.

The licence is the other gap. The repository metadata carries no licence value, and the README states that the translation project follows the licence terms of the original book, that the translated content is for study and exchange only, and that any copyright concern should be raised with the maintainer, who publishes an email address for exactly that purpose.

So the terms you would want to quote appear nowhere in the repository. If you intend to republish a translation, mirror the text, or build something on it, find the original book's licence first, because neither a tag nor this repository answers the question.

Editorial conclusion

Use this repository as a reading reference if you work in Chinese and want the Agentic Design Patterns material gathered in one place, and treat it as a documentation project rather than a tool. It will not tell you which patterns to adopt, because a translated book does not make that judgement, and its own progress numbers disagree about how far the review has gone. Before building on it, check progress.md for the specific chapter you care about, read the original book's licence instead of assuming this repository grants one, and remember that the integer release tags give you a sequence number and nothing about what changed. If your team does not read Chinese, the translation solves nothing the original does not.

Frequently asked questions

Official sources

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