| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 2 | 3 | 0% |
| Commands | 0 | 0 | 5 | 0% |
| Section tags | 1 | 3 | 1 | 20% |
What each file covers
Sections
0 shared · 2 only in A · 3 only in B- − Frontend Workflow
- − Package Contracts
- + API Agent Guide
- + Commands
- + Architecture And Boundaries
Commands
0 shared · 0 only in A · 5 only in B- + make lint
- + make type-check
- + make test
- + make test TARGET_TESTS=./api/tests/<path>
- + uv run --project api
Section tags
1 shared · 3 only in A · 1 only in B- − test
- − code-style
- − testing-strategy
- + api
- agent-behaviour
Line diff
langgenius/dify · web/AGENTS.md
@@ −1 @@
1## Frontend Workflow
2
3- Read `docs/test.md` only for frontend test work and `docs/lint.md` only when running or changing static checks.
4- Use the repo-local `how-to-write-component` skill when implementation requires component ownership, state, data-flow, effect, or interaction-boundary decisions. Do not load it for test-only, copy-only, or styling-only changes.
5- Use `frontend-code-review` only for explicit frontend review or audit requests, including test reviews. Use `frontend-testing` when writing or changing Vitest or React Testing Library tests.
6
7## Package Contracts
8
9- User-facing strings must use `web/i18n/en-US/` keys. When adding or renaming a key, update every supported locale with the correct localized value.
10- For new backend calls and migrated surfaces, use generated `consoleQuery` / `consoleClient` APIs from `@/service/client`. Do not add handwritten REST helpers or DTO mirrors, mock-backed app state, or direct edits to generated contracts.
11- Prefer `@langgenius/dify-ui/*` primitives, data attributes, and design tokens. Preserve a visible focus indicator on the final focusable element.
12- Follow `docs/overlay.md` for overlay selection and migration. Migrate a legacy overlay only when the current behavior change actually involves that overlay boundary.
13- For custom SVG icons, follow `../packages/iconify-collections/README.md`; do not add generated React icons under `app/components/base/icons/src/`.
14- `docs/test.md` is the single source of truth for frontend automated-test policy. Skills may route and execute that policy but must not redefine it.
15
langgenius/dify · api/AGENTS.md
@@ +1 @@
1# API Agent Guide
2
3Read surrounding module, class, and function docstrings plus non-obvious comments before changing backend behavior. They are local contracts; update them only when their owned behavior changes, and keep them aligned with the current code.
4
5## Commands
6
7Run backend checks from the repository root:
8
9- Format and lint: `make lint`
10- Type check: `make type-check`
11- Unit tests: `make test`
12- Targeted tests: `make test TARGET_TESTS=./api/tests/<path>`
13
14Run direct Python commands through `uv run --project api`. Docker-backed integration suites are normally CI-owned. Do not start long-running services as part of routine agent work.
15
16## Architecture And Boundaries
17
18- Keep transport parsing and serialization in controllers, orchestration in services, and domain policy in `core/` or its domain owner. Keep `libs/` business-agnostic and reuse existing owners before adding abstractions.
19- Before changing controller schemas, generated API contracts, or `SystemFeatureModel`, read `controllers/API_SCHEMA_GUIDE.md`. Treat `/system-features` as a minimal unauthenticated bootstrap allowlist, not a general configuration registry.
20- Scope tenant-owned reads and writes by the complete owner chain, and propagate `tenant_id` across every affected layer. Reconstruct trusted internal references from validated database state after payload or async boundaries.
21- Keep write transactions explicit and bounded. Do not perform external I/O inside an open transaction unless a documented consistency contract requires it.
22- Read configuration through `configs.dify_config`, access storage through `extensions.ext_storage.storage`, and route outbound HTTP through the existing SSRF-safe owner in `core.helper.ssrf_proxy`.
23- Use Pydantic v2 for request and response models. Reuse domain-specific exceptions and translate them at the controller boundary.
24- Use existing Celery task and queue owners for asynchronous work; do not route unrelated jobs through workflow-specific services.
25- Celery tasks that may be retried or redelivered must keep side effects idempotent and log affected resource identifiers.
26
@@ −1 +1 @@
1−## Frontend Workflow
1+# API Agent Guide
22
3−- Read `docs/test.md` only for frontend test work and `docs/lint.md` only when running or changing static checks.
4−- Use the repo-local `how-to-write-component` skill when implementation requires component ownership, state, data-flow, effect, or interaction-boundary decisions. Do not load it for test-only, copy-only, or styling-only changes.
5−- Use `frontend-code-review` only for explicit frontend review or audit requests, including test reviews. Use `frontend-testing` when writing or changing Vitest or React Testing Library tests.
3+Read surrounding module, class, and function docstrings plus non-obvious comments before changing backend behavior. They are local contracts; update them only when their owned behavior changes, and keep them aligned with the current code.
64
7−## Package Contracts
5+## Commands
86
9−- User-facing strings must use `web/i18n/en-US/` keys. When adding or renaming a key, update every supported locale with the correct localized value.
10−- For new backend calls and migrated surfaces, use generated `consoleQuery` / `consoleClient` APIs from `@/service/client`. Do not add handwritten REST helpers or DTO mirrors, mock-backed app state, or direct edits to generated contracts.
11−- Prefer `@langgenius/dify-ui/*` primitives, data attributes, and design tokens. Preserve a visible focus indicator on the final focusable element.
12−- Follow `docs/overlay.md` for overlay selection and migration. Migrate a legacy overlay only when the current behavior change actually involves that overlay boundary.
13−- For custom SVG icons, follow `../packages/iconify-collections/README.md`; do not add generated React icons under `app/components/base/icons/src/`.
14−- `docs/test.md` is the single source of truth for frontend automated-test policy. Skills may route and execute that policy but must not redefine it.
7+Run backend checks from the repository root:
8+
9+- Format and lint: `make lint`
10+- Type check: `make type-check`
11+- Unit tests: `make test`
12+- Targeted tests: `make test TARGET_TESTS=./api/tests/<path>`
13+
14+Run direct Python commands through `uv run --project api`. Docker-backed integration suites are normally CI-owned. Do not start long-running services as part of routine agent work.
15+
16+## Architecture And Boundaries
17+
18+- Keep transport parsing and serialization in controllers, orchestration in services, and domain policy in `core/` or its domain owner. Keep `libs/` business-agnostic and reuse existing owners before adding abstractions.
19+- Before changing controller schemas, generated API contracts, or `SystemFeatureModel`, read `controllers/API_SCHEMA_GUIDE.md`. Treat `/system-features` as a minimal unauthenticated bootstrap allowlist, not a general configuration registry.
20+- Scope tenant-owned reads and writes by the complete owner chain, and propagate `tenant_id` across every affected layer. Reconstruct trusted internal references from validated database state after payload or async boundaries.
21+- Keep write transactions explicit and bounded. Do not perform external I/O inside an open transaction unless a documented consistency contract requires it.
22+- Read configuration through `configs.dify_config`, access storage through `extensions.ext_storage.storage`, and route outbound HTTP through the existing SSRF-safe owner in `core.helper.ssrf_proxy`.
23+- Use Pydantic v2 for request and response models. Reuse domain-specific exceptions and translate them at the controller boundary.
24+- Use existing Celery task and queue owners for asynchronous work; do not route unrelated jobs through workflow-specific services.
25+- Celery tasks that may be retried or redelivered must keep side effects idempotent and log affected resource identifiers.
1526
