agentleFS
Sign inStart free
korniakornia/kornia-rs/.claude/skills/kornia-bindings/SKILL.md

kornia-bindings

Skill748 starsChanged 7 days agoApache-2.0View on GitHub

Use when changing Python (kornia-py, PyO3/Maturin) or C++ (kornia-cpp) bindings in kornia-rs, or Rust APIs they wrap. Covers build/test commands, parity rules and free-threaded Python.

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Add binding-side tests for every new exposed function.

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Python and C++ bindings

Python (kornia-py/)

  • Build: pixi run py-build (maturin develop); test: pixi run py-test (pytest in kornia-py/tests, auto-builds). Threaded stress: pixi run py-test-threaded.
  • Free-threaded 3.14t environment uses scripts/build-py314t.sh.
  • Stubs/python sources live under kornia-py/python; update them with Rust changes. Read kornia-py/CONTRIBUTING.md.
  • Release wheels are built with --features cuda (dynamic loading, CPU fallback); do not break import on machines without CUDA.
  • Errors map to Python exceptions; never unwrap() in binding code.

C++ (kornia-cpp/)

  • Build/test: pixi run cpp-test; format: pixi run cpp-fmt / cpp-fmt-check; sanitizers: pixi run cpp-test-sanitizers.
  • Headers in include/, Rust FFI in src/, tests in tests/.

Rules

  • Public Rust API changes that are exposed must be reflected in both bindings (or explicitly noted as not exposed in the PR).
  • Add binding-side tests for every new exposed function.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free