configuration, or policy here.
## Authority and boundaries
`docs/specification.mdx` is authoritative for format requirements.
Explanatory documentation, examples, tests, and implementations do not add
requirements to the format. Preserve the distinction between
treat the high star count, package name, Docker image, release history, or old documentation as evidence that this is the current implementation.
## Use the current Letta implementation
The current Letta
v1.x]` title prefix; only critical bug fixes and
security fixes land there.
- `README.md` documents v2. The v1 README lives on the `v1.x` branch.
## Package Management
- ONLY use uv, NEVER
components and follow its conventions. Reference https://ant.design/llms.txt for antd's LLM-friendly documentation when needed.
- For frontend components and pages, follow accessibility (a11y) best practices — add appropriate ARIA
design in [`.archon/workflow-language-constitution.md`](.archon/workflow-language-constitution.md), aspirational engineering craft and review values in [`.archon/engineering.md`](.archon/engineering.md), user documentation in the docs site, and machine-checkable rules in code, types, tests, lint
Model Context Protocol server that gives AI assistants access to n8n node documentation, workflow validation, and workflow management. Documentation and validation tools work offline against the bundled SQLite node database
maintainer, and validation plan. `Request changes`, `Defer`, and `Decline` do not authorize implementation. Small documentation corrections and low-risk fixes do not require this decision.
If the product decision
Documentation Agent Guide
## Role
You are a documentation engineer and writer for NemoClaw public-facing documentation.
Treat `docs/` as the source of truth for published content and AI-agent Markdown
Fern Documentation Agent Guide
You are a documentation engineer and writer responsible for the NemoClaw Fern site shell.
Use this guide when editing files under `fern/`.
## Role
- Maintain the Fern
request maintainer direction, or route the integration through [Community Solutions](../../../docs/resources/community-contributions.mdx). Do not document the integration as NemoClaw behavior.
Derive the channel contract from authoritative upstream documentation and source before
that is not clear from the immediate context. Do not narrate obvious code or document the sequence of approaches taken
to reach the current implementation; that history belongs
invocation lifecycle, please refer to the `adk-architecture` skill and the referenced documentation therein.
## ADK Knowledge, Architecture, and Style
Skills related to ADK development are in `.agents/skills/`.
## Project Architecture
agent can implement incremental feature requests, develop additional test suites, and create or update documentation.
* **Prototyping new projects**: The cloud agent and Copilot CLI can greenfield new concepts, helping developers
www.asd-ste100.org/), and keep it short. This covers a comment, KDoc, a commit message, documentation, a spec, and a report to the user. Use the active voice and a simple
Filament AI Coding & Agent Guidelines
This document defines machine-readable instructions and technical guardrails for AI coding assistants, agents, and LLMs working on the Filament repository. All AI-generated code
docs/architecture/design-tokens.md).
2. **Never use `React.FC`.** Always use `ForwardRefComponent` with `React.forwardRef`.
3. **Never access `window`, `document`, or `navigator` directly.** In v9 components, use `useFluent_unstable()` to get `targetDocument` and `targetDocument.defaultView` instead
project and its users
Being an open source library, the public API, abstractions, documentation, and the code itself _are_ the product and deserve careful consideration, as much as the functionality