Research a Dify feature before writing or optimizing documentation. Use when starting any doc task that requires understanding a feature's implementation, user pain points, or community feedback. Triggers: 'research this feature', 'investigate the code for',…
Audit terminology consistency across documentation against the codebase UI labels and the glossary — in prose and in the UI strings shown in screenshots. Covers full files, not just diffs; excludes env var docs. Use after finalizing a draft, or when the user…
Rule pack for the Dify CLI (`difyctl`) doc set: en/cli/ and the Enterprise develop/cli/ trees. Readers, source of truth, house style, page shape, and content ownership. Loaded by dify-docs-write.
Rule pack for the Service API specs ({en,zh,ja}/api-reference/openapi_service.json): spec conventions, app-type scoping, code-verification rules, and the audit machinery. Writing and editing run under dify-docs-write; the standalone audit of an existing spec…
Judge a finished draft as the docs owner would: a fresh agent reads it against the style guide and the reference page in its genre, marks the sentences that fall short, and returns a ship verdict on the work of this round. Runs in the pipeline's Check stage…
Check formatting compliance in changed documentation against writing-guides/formatting-guide.md and tools/translate/formatting-{zh,ja}.md. Routes by path: en/ files get the English linter and rules; zh/ and ja/ files get the CJK linter and rules. Use after…
Post-writing verification from the reader's perspective. Invoke after completing any documentation task to simulate a real user reading the document for the first time.
Judge a zh or ja page as the owner of that edition would: a fresh agent reads it beside its English source against the language's formatting guide and the glossary, marks the sentences that fall short, and returns a ship verdict on the work of this round.…