cudnn-frontend / samples
AGENTS.md994 starsChanged 10 days agoApache-2.0View on GitHub
Usage examples for the C++ graph API and the Python API. Build commands: ../AGENTS.md. Samples need a GPU + cuDNN backend at runtime; individual cases SKIP() on unsupported arch or backend version.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,439 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- include/cudnn_frontend/AGENTS.mdAGENTS.md
- python/cudnn/AGENTS.mdAGENTS.md
- python/cudnn/sdpa/AGENTS.mdAGENTS.md
- test/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- cutedsl-kernel-integrationSkill
- determinism-testsSkill
The file
We split this AGENTS.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 27
Follow the existing pattern: build graph → validate() → build_operation_graph() → plans → check_support() (skip gracefully if unsupported) …
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
samples — Agent Guide
Usage examples for the C++ graph API and the Python API. Build commands: ../AGENTS.md.
Layout
| Path | What |
cpp/ | Current C++ graph-API samples, grouped by topic (convolution/, matmul/, sdpa/, norm/, moe_grouped_matmul/, ...) — Catch2 cases in binary build/bin/samples |
legacy_samples/ | Frozen samples for the legacy flat API — binary build/bin/legacy_samples. Don't add here. |
python/ | Numbered Jupyter notebooks (00_introduction.ipynb ...) — the Python tutorial sequence |
frost/ | Standalone Python scripts for the FROST engines and blocks: gemm/, linear_attention/ and gated_attention_block/, numbered, each self-checking against a reference |
llama/, llm_coverage/ | End-to-end LLaMA tie-out scripts and per-op coverage scripts (plain .py, see their READMEs) |
Running
./build/bin/samples --list-tests
./build/bin/samples "Cached sdpa" # run one Catch2 case by nameSamples need a GPU + cuDNN backend at runtime; individual cases SKIP() on unsupported arch or backend version.
Conventions for new samples
- New C++ samples go under
samples/cpp/<topic>/as a Catch2TEST_CASEadded tosamples/cpp/CMakeLists.txt; reuse helpers fromsamples/cpp/utils/. - Follow the existing pattern: build graph →
validate()→build_operation_graph()→ plans →check_support()(skip gracefully if unsupported) → execute → verify. - Python notebooks are formatted by
black-jupyter(pre-commit run); keep the numbered-prefix naming so the tutorial order stays obvious. - A new public feature should come with a sample here and a doc page under
docs/.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.