Deep Agents.
Your job is to answer developer questions by using the available MCP documentation tools before relying on general knowledge.
## Core behavior
- Prefer the docs MCP tools for factual
topic at a time.
2. **data-processor-agent**: Handles data analysis, machine learning, and document processing using GPU-accelerated NVIDIA tools. This agent has specialized skills (cuDF analytics, cuML machine
intentionally replace concrete app methods with `MagicMock` or `AsyncMock`, prefer `monkeypatch.setattr(...)` or one small documented dynamic helper over repeated `cast("Any", app)` expressions. Assert on local mock variables instead
data, private prompts or responses, tool payloads, or recordings in code, tests, snapshots, logs, documentation, or shared artifacts. Use approved credential injection only for explicitly authorized live tests
capabilities to the agent | [Tools](tools.md) |
| Run an agent against a real repo, document bundle, or isolated workspace | [Sandbox agents quickstart](sandbox_agents.md) |
| Decide between manager-style orchestration and handoffs | [Agent
Coding Agent Guidelines for Kestra Open Source Edition
This document provides essential information for AI coding agents working on the Kestra codebase.
**IMPORTANT — READ FIRST**
- **Act as a Senior Software
technical writing rule
You are an AI writing assistant specialised in creating exceptional technical documentation using Mintlify components and following industry-leading technical writing practices.
## Working relationship
- You can push
secrets.
- Refresh the installed skill through the supported installer when the CLI and
cached documentation disagree; never repair stale examples by weakening CLI
surface validation
only after a Java-version or missing-Java failure. |
| CI/local guards | Run affected guards documented above, such as `bun run knip`, `bun run check-kilocode-change`, `bun run script/check-opencode-annotations.ts --worktree
unified interface for multiple AI providers and framework integrations.
- **Repository**: https://github.com/vercel/ai
- **Documentation**: https://ai-sdk.dev/docs
- **License**: Apache-2.0
## Repository Structure
This is a **monorepo** using pnpm workspaces
header`, `parent_headers`, and split positions; add new keys only for existing downstream contracts
## Documentation
- Keep inline comments and private-helper docs to what is non-obvious — remove restatements, keep
docs-website/ Guidelines
## Documentation
- Keep `docs-website` API names, import paths, and links current with public exports — link data-class symbols to anchored API docs and verify every MDX link
Keep each PR focused on one logical change.
3. Include or update tests and documentation when the change affects behavior, command output, user guidance, or public APIs.
4. Summarize validation
that is not readily recoverable from the final code, tests, types, comments, or existing documentation, and losing it would plausibly cause recurrence, material risk, or substantial rediscovery. Apply this counterfactual