From e34a3dfc7d29f2a8295ce995060eefd610685c8e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Yanli=20=E7=9B=90=E7=B2=92?= Date: Mon, 26 Jan 2026 23:37:56 +0800 Subject: [PATCH] remove the Skill Index section due to its deletion by #31334 --- api/AGENTS.md | 70 --------------------------------------------------- 1 file changed, 70 deletions(-) diff --git a/api/AGENTS.md b/api/AGENTS.md index 97b7877d1e..13adb42276 100644 --- a/api/AGENTS.md +++ b/api/AGENTS.md @@ -43,76 +43,6 @@ In this section, “notes” means module/class/function docstrings plus any rel - Remove or rewrite any comments that could be mistaken as current guidance but no longer apply. - Keep docstrings and comments concise and accurate; they are meant to prevent repeated rediscovery. -## Skill Index - -Start with the section that best matches your need. Each entry lists the problems it solves plus key files/concepts so you know what to expect before opening it. - -### Platform Foundations - -#### [Infrastructure Overview](agent_skills/infra.md) - -- **When to read this** - - You need to understand where a feature belongs in the architecture. - - You’re wiring storage, Redis, vector stores, or OTEL. - - You’re about to add CLI commands or async jobs. -- **What it covers** - - Configuration stack (`configs/app_config.py`, remote settings) - - Storage entry points (`extensions/ext_storage.py`, `core/file/file_manager.py`) - - Redis conventions (`extensions/ext_redis.py`) - - Plugin runtime topology - - Vector-store factory (`core/rag/datasource/vdb/*`) - - Observability hooks - - SSRF proxy usage - - Core CLI commands - -### Plugin & Extension Development - -#### [Plugin Systems](agent_skills/plugin.md) - -- **When to read this** - - You’re building or debugging a marketplace plugin. - - You need to know how manifests, providers, daemons, and migrations fit together. -- **What it covers** - - Plugin manifests (`core/plugin/entities/plugin.py`) - - Installation/upgrade flows (`services/plugin/plugin_service.py`, CLI commands) - - Runtime adapters (`core/plugin/impl/*` for tool/model/datasource/trigger/endpoint/agent) - - Daemon coordination (`core/plugin/entities/plugin_daemon.py`) - - How provider registries surface capabilities to the rest of the platform - -#### [Plugin OAuth](agent_skills/plugin_oauth.md) - -- **When to read this** - - You must integrate OAuth for a plugin or datasource. - - You’re handling credential encryption or refresh flows. -- **Topics** - - Credential storage - - Encryption helpers (`core/helper/provider_encryption.py`) - - OAuth client bootstrap (`services/plugin/oauth_service.py`, `services/plugin/plugin_parameter_service.py`) - - How console/API layers expose the flows - -### Workflow Entry & Execution - -#### [Trigger Concepts](agent_skills/trigger.md) - -- **When to read this** - - You’re debugging why a workflow didn’t start. - - You’re adding a new trigger type or hook. - - You need to trace async execution, draft debugging, or webhook/schedule pipelines. -- **Details** - - Start-node taxonomy - - Webhook & schedule internals (`core/workflow/nodes/trigger_*`, `services/trigger/*`) - - Async orchestration (`services/async_workflow_service.py`, Celery queues) - - Debug event bus - - Storage/logging interactions - -## General Reminders - -- All skill docs assume you follow the coding style rules below—run the lint/type/test commands before submitting changes. -- When you cannot find an answer in these briefs, search the codebase using the paths referenced (e.g., `core/plugin/impl/tool.py`, `services/dataset_service.py`). -- If you run into cross-cutting concerns (tenancy, configuration, storage), check the infrastructure guide first; it links to most supporting modules. -- Keep multi-tenancy and configuration central: everything flows through `configs.dify_config` and `tenant_id`. -- When touching plugins or triggers, consult both the system overview and the specialised doc to ensure you adjust lifecycle, storage, and observability consistently. - ## Coding Style This is the default standard for backend code in this repo. Follow it for new code and use it as the checklist when reviewing changes.