albumentations-team
- 16 skills
- 0 followers
- 9 hours ago last updated
- ▌ Notebook Metadata · albumentations-teamEnsures Jupyter notebooks have required metadata and nbformat. Use when adding, creating, or modifying .ipynb files, or when the user asks about notebook structure or validation.
- ▌ Augmentation Benchmark Contract · albumentations-teamUse before planning, changing, running, resuming, aggregating, plotting, or interpreting RGB, multichannel, video, or volume augmentation benchmarks in this repository.
- ▌ Albucore Benchmarks · albumentations-teamRunning Albucore micro-benchmarks under benchmarks/, synthetic router timings, and comparing PyPI releases with uv --no-project. Use when adding benchmarks, comparing performance across versions, or documenting benchmark workflow.
- ▌ Albucore Public API · albumentations-teamAlbucore star-exported API (__all__), routers vs albucore.functions shims, and dependents such as Albumentations. Use when changing exports, documenting API, or deciding what belongs in package __all__.
- ▌ Albucore Conventions · albumentations-teamAlbucore image processing conventions - shapes (H,W,C), dtypes (uint8/float32), benchmark-driven backend routing (OpenCV, NumPy, Torch CPU, LUT, NumKong), tests, and lockfile discipline. Use when implementing or modifying albucore modules, writing tests, or reviewing image-processing code.
- ▌ Torch Performance Optimization · albumentations-team bundleOptimize or review eager CPU-only Albucore PyTorch runtime paths with benchmark-backed decisions. Use when adding or changing Torch CPU kernels, Tensor/NumPy bridges, Torch backend routing, tensor layouts, allocations, threading, profiling, memory-format candidates, or Torch performance benchmarks.
- ▌ Benchmark · albumentations-teamMeasure AlbumentationsX runtime changes with paired baseline and candidate benchmarks on the affected routes.
- ▌ Add Transform · albumentations-teamFull checklist for adding a new transform to AlbumentationsX. Use when the user asks to add, implement, or create a new transform/augmentation.
- ▌ Release Notes · albumentations-teamGenerate release notes for AlbumentationsX. Use when the user asks to prepare, draft, or write release notes for a new version (e.g. "prepare release notes for 2.x.y", "draft release X").
- ▌ Review Transform · albumentations-teamReview an AlbumentationsX transform for correctness, public API coherence, performance, documentation, and test coverage.
- ▌ Validate And Fix · albumentations-teamAfter completing code changes, runs tests and pre-commit, then iteratively fixes failures until all pass. Use when finishing a coding task, validating changes, or when the user asks to run tests or fix errors.
- ▌ License Integrity · albumentations-teamMaintain AlbumentationsX license, CLA, provenance notices, and packaged legal artifacts consistently.
- ▌ Mixing Transforms · albumentations-teamPolicy for AlbumentationsX transforms that combine multiple images or objects. Use when implementing, reviewing, or using Mosaic, CopyAndPaste, OverlayElements, HistogramMatching, PixelDistributionAdaptation, or other mixing transforms.
- ▌ Internal Workspace · albumentations-teamUse the repo `_internal/` directory for anything that must not be committed — scratch files, temporary outputs, local demos, Codex artifacts, or one-off scripts. Use when creating temp files, debug dumps, or local-only tooling during a task.
- ▌ Docstring Deep Dive · albumentations-teamReview public AlbumentationsX docstrings for useful descriptions, runnable examples, parameter semantics, and related transforms.
- ▌ Performance Optimization · albumentations-team bundleSystematic performance audit for AlbumentationsX runtime code. Use whenever implementing, reviewing, profiling, or optimizing transforms, functional kernels, apply methods, random generation, reductions, label maps, dtype conversions, batch paths, allocation-heavy code, backend routing, or code that may belong in Albucore.