agentleFS
Sign inStart free
open-edge-platformopen-edge-platform/training_extensions/.github/copilot-instructions.md

training_extensions

Copilot instructions1.4k starsChanged 17 days agoApache-2.0View on GitHub

Monorepo with three components — different languages, toolchains, and conventions. The application can be built and deployed in three ways: The library is consumed by the backend (getitune[cpu|xpu|cuda] extras). - Assume the virtual environment is already activated — do not prepend uv run or activate a venv in every command. - Assume the working directory is already the component root you are working on (e.g. application/backend/). Do not cd into it at the start of every command. - When the…

1 other project uses a version of this.

Trending

More talk lately.about the whole repository

Dec 2025: 1 mentionJan 2026: 4 mentionsFeb 2026: 2 mentionsMar 2026: 2 mentionsApr 2026: 7 mentionsMay 2026: 2 mentionsJun 2026: 3 mentionsJul 2026: 2 mentionsAug 2026: 3 mentionsSep 2026: 4 mentionsOct 2026: 9 mentionsNov 2026: 5 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the open-edge-platform/training_extensions repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about open-edge-platform/training_extensions

The biggest 5 of 50 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 50

Talked about on GitHub (50 times).

On GitHub · 50

45 more on GitHub

The file

We split this copilot-instructions.md into the rules it gives an agent

10 rules. About 0 are common, 6 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When the user is on Windows with WSL2, generate plain Linux commands — do not wrap them in wsl -d … -- bash -c "…" or use Windows paths …

    line 26
  2. Distinctive:

    Do not mix code or conventions between the three sub-projects.

    line 29
  3. Distinctive:

    Prefer absolute imports within each Python package.

    line 30
  4. Distinctive:

    Prefer editing existing files over creating new ones.

    line 32
  5. Very specific:

    Never invent ad-hoc uv / docker commands when a recipe exists.

    line 44
  6. Very specific:

    Prefer pathlib.Path over os.path.

    line 50
  7. Distinctive:

    Write code that is portable across the main platforms (Linux, Windows, macOS).

    line 51
  8. Very specific:

    Running tests: after writing or modifying tests, run the specific new test file (e.g.

    line 61
  9. Distinctive:

    Do not change Python version pins (they ensure CI reproducibility).

    line 67
  10. Distinctive:

    Do not add new third-party dependencies when stdlib or already-declared dependencies can solve the problem.

    line 68

≈ “Common” is an estimate: at least 1 in 5 of the 3,779 Copilot instructions 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
copilot-instructions.md

Repository layout

Monorepo with three components — different languages, toolchains, and conventions.

PathWhat it isPrimary stack
libraries/getitune/getitune — low-code transfer-learning CV library (PyPI).Python 3.11+, PyTorch 2.10, OpenVINO, Lightning, Datumaro
application/backend/Geti™ app server (geti package).Python 3.14, FastAPI, SQLAlchemy 2 (async), Pydantic v2, Alembic
application/ui/Geti™ web/desktop UI.Node 24.2+, React, TypeScript, rsbuild, Tauri

The application can be built and deployed in three ways:

  1. As a single Docker container.
  2. As a desktop app for Windows (MSIX).
  3. With server and UI as standalone processes, for development only.

The library is consumed by the backend (getitune[cpu|xpu|cuda] extras).

General rules

  • Assume the virtual environment is already activated — do not prepend uv run or activate a venv in every command.
  • Assume the working directory is already the component root you are working on (e.g. application/backend/). Do not cd into it at the start of every command.
  • When the user is on Windows with WSL2, generate plain Linux commands — do not wrap them in wsl -d … -- bash -c "…" or use Windows paths like /mnt/wsl.localhost/. The terminal is already inside WSL.
  • Do not mix code or conventions between the three sub-projects.
  • Prefer absolute imports within each Python package. Relative imports are acceptable when they help avoid circular dependencies.
  • Prefer editing existing files over creating new ones; match surrounding style.
  • Code must pass pre-commit checks (see .pre-commit-config.yaml). Run them locally with prek.
  • Conventional Commits: feat:, fix:, chore:, docs:, refactor:, test:, ci:.

  • New source files require a copyright + SPDX header (current year, # for Python/shell, // for TS/JS/Rust):

    # Copyright (C) 2026 Intel Corporation
# SPDX-License-Identifier: Apache-2.0
  • Use just for developer workflows (application/ui/ uses npm scripts instead). Never invent ad-hoc uv / docker commands when a recipe exists.

Python conventions (libraries/getitune/ and application/backend/)

  • Type-hint every public function, method, and module-level variable.
  • Modern typing: list[int], X | None — not List, Optional.
  • Prefer pathlib.Path over os.path.
  • Write code that is portable across the main platforms (Linux, Windows, macOS).
  • No bare print.
  • Google-style docstrings (Args, Returns, Raises).
  • Logging: libraries/getitune/ uses stdlib logging; application/backend/ uses loguru. Do not mix them.
  • Tests use pytest; new features require unit tests.
  • Test placement: unit tests live next to the code they test in tests/unit/ (mirroring the source tree); integration tests go in tests/integration/. Do not duplicate fixtures across directories — reuse existing conftest.py fixtures at the appropriate scope.
  • Running tests: after writing or modifying tests, run the specific new test file (e.g. pytest tests/unit/path/to/test_foo.py). Running the full suite is optional and not required for validation.

Things to avoid

  • Do not change Python version pins (they ensure CI reproducibility).
  • Do not add new third-party dependencies when stdlib or already-declared dependencies can solve the problem.

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