> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nvidia.com/cuvs/llms.txt.
> For full documentation content, see https://docs.nvidia.com/cuvs/llms-full.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/cuvs/_mcp/server.

# Coding Guidelines

Use these pages when changing NVIDIA cuVS APIs, implementation code, bindings, packaging, or developer-facing documentation. They collect the conventions that keep NVIDIA cuVS predictable for contributors and downstream projects.

## Language Guidelines

- [C Guidelines](/developer-guide/coding-guidelines/c-guidelines): design ABI-stable C APIs, manage opaque handles, and keep lifecycle, error handling, and documentation patterns consistent.
- [C++ Guidelines](/developer-guide/coding-guidelines/cpp-guidelines): design public C++ APIs, manage CUDA resources, follow stateless API patterns, and write implementation code that fits NVIDIA cuVS conventions.
- [Java Guidelines](/developer-guide/coding-guidelines/java-guidelines): update Java APIs, Panama bindings, native resource ownership, Maven packaging, and Java-facing documentation consistently.
- [Python Guidelines](/developer-guide/coding-guidelines/python-guidelines): update Python APIs, Cython bindings, packaging, formatting, and Python-facing documentation consistently.