Comparison

A · AGENTS.md · langgenius/dify B · AGENTS.md · langgenius/dify

What each file covers, counted
Dimension	Only in A	Only in B	Overlap
Sections	2	2	0%
Commands	0	5	0%
Section tags	4	0	0%

What each file covers

Sections

0 shared · 2 only in A · 2 only in B

− @langgenius/dify-ui
− Component Authoring Rules
+ AGENTS.md
+ Repository Gotchas

Commands

0 shared · 0 only in A · 5 only in B

+ docker/
+ uv run --project api <command>
+ docker/.env.example
+ docker/envs/*.env.example
+ docker/.env

Section tags

0 shared · 4 only in A · 0 only in B

− code-style
− security
− ui
− do-not

Line diff

+6 added−28 removed4 unchanged12.5% identical

langgenius/dify · packages/dify-ui/AGENTS.md

@@ −1 @@

1# @langgenius/dify-ui

3This package owns shared design tokens, CSS-first Tailwind styles, the `cn()` utility, and headless primitives consumed by `web/`. Read only the matching topic in [`README.md`] for public imports, forms, typed values, pickers, overlays, tokens, or tests.

5## Component Authoring Rules

7- Build primitives from `@base-ui/react`, `cva`, and `cn`.

8- Use relative cross-component imports inside the package and subpath exports such as `@langgenius/dify-ui/button` from consumers. Add a matching `package.json#exports` entry for each public primitive.

9- Keep one primitive per `src/<name>/` folder with optional colocated stories and tests.

10- Do not import from `web/` or depend on Next.js, i18n, application state, or data-fetching libraries.

11- Preserve upstream Base UI anatomy and generic value contracts. Use discriminated unions when one prop changes the valid shape of related props; do not flatten those relationships or hard-code selectable values to `string`.

12- Export shared public types from the owning component subpath.

13- Prefer Base UI data attributes and CSS variables for visual states; do not mirror primitive state in React solely to add classes.

14- When a Base UI API or selector contract is unclear, read the current official documentation and local `@base-ui/react` type declarations before coding.

16Use the README sections as the detailed owners:

18- [Imports and public boundaries]

19- [Typed value contracts]

20- [Search and picker selection]

21- [Tailwind and Figma radius mapping]

22- [Overlay and portal contracts]

23- [Development and test boundaries]

25[Development and test boundaries]: README.md#development

26[Imports and public boundaries]: README.md#imports

27[Overlay and portal contracts]: README.md#overlay--portal-contract

28[Search and picker selection]: README.md#search-and-picker-selection

29[Tailwind and Figma radius mapping]: README.md#tailwind-css-v4-integration

30[Typed value contracts]: README.md#typed-value-contracts

31[`README.md`]: README.md

langgenius/dify · AGENTS.md

@@ +1 @@

1# AGENTS.md

3Dify is an open-source platform for building LLM applications, agentic workflows, and RAG pipelines. This monorepo contains the backend API (`api/`), frontend application (`web/`), deployment assets (`docker/`), standalone agent backend (`dify-agent/`), CLI (`cli/`), and end-to-end suite (`e2e/`). Follow the nearest scoped `AGENTS.md` for the files being changed.

5## Repository Gotchas

7- Run backend commands through `uv run --project api <command>`.

8- Backend integration tests are CI-only and are not expected to run locally.

9- Keep `docker/.env.example` limited to variables required for a default Docker Compose deployment to start. Put optional and provider-specific settings in the matching `docker/envs/*.env.example` file; `docker/.env` overrides those service-specific env files.

@@ −1 +1 @@

1−# @langgenius/dify-ui

1+# AGENTS.md

3−This package owns shared design tokens, CSS-first Tailwind styles, the `cn()` utility, and headless primitives consumed by `web/`. Read only the matching topic in [`README.md`] for public imports, forms, typed values, pickers, overlays, tokens, or tests.

3+Dify is an open-source platform for building LLM applications, agentic workflows, and RAG pipelines. This monorepo contains the backend API (`api/`), frontend application (`web/`), deployment assets (`docker/`), standalone agent backend (`dify-agent/`), CLI (`cli/`), and end-to-end suite (`e2e/`). Follow the nearest scoped `AGENTS.md` for the files being changed.

5−## Component Authoring Rules

5+## Repository Gotchas

7−- Build primitives from `@base-ui/react`, `cva`, and `cn`.

8−- Use relative cross-component imports inside the package and subpath exports such as `@langgenius/dify-ui/button` from consumers. Add a matching `package.json#exports` entry for each public primitive.

9−- Keep one primitive per `src/<name>/` folder with optional colocated stories and tests.

10−- Do not import from `web/` or depend on Next.js, i18n, application state, or data-fetching libraries.

11−- Preserve upstream Base UI anatomy and generic value contracts. Use discriminated unions when one prop changes the valid shape of related props; do not flatten those relationships or hard-code selectable values to `string`.

12−- Export shared public types from the owning component subpath.

13−- Prefer Base UI data attributes and CSS variables for visual states; do not mirror primitive state in React solely to add classes.

14−- When a Base UI API or selector contract is unclear, read the current official documentation and local `@base-ui/react` type declarations before coding.

15−

16−Use the README sections as the detailed owners:

17−

18−- [Imports and public boundaries]

19−- [Typed value contracts]

20−- [Search and picker selection]

21−- [Tailwind and Figma radius mapping]

22−- [Overlay and portal contracts]

23−- [Development and test boundaries]

24−

25−[Development and test boundaries]: README.md#development

26−[Imports and public boundaries]: README.md#imports

27−[Overlay and portal contracts]: README.md#overlay--portal-contract

28−[Search and picker selection]: README.md#search-and-picker-selection

29−[Tailwind and Figma radius mapping]: README.md#tailwind-css-v4-integration

30−[Typed value contracts]: README.md#typed-value-contracts

31−[`README.md`]: README.md

7+- Run backend commands through `uv run --project api <command>`.

8+- Backend integration tests are CI-only and are not expected to run locally.

9+- Keep `docker/.env.example` limited to variables required for a default Docker Compose deployment to start. Put optional and provider-specific settings in the matching `docker/envs/*.env.example` file; `docker/.env` overrides those service-specific env files.

3210