agentleFS
OpentronsOpentrons/opentrons/.cursor/skills/robot-python-projects/SKILL.md

robot-python-projects

Skill525 starsChanged 2 months agoApache-2.0View on GitHub

Guidelines for robot Python projects — api/, robot-server/, hardware/, auth-server/, shared-data/, server-utils/, system-server/, update-server/, usb-bridge/. Use when working with Python files in these directories or their pyproject.toml files.

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 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.

  • 2

    Very specific

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

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

    Shared Make includes: all Makefiles include ../scripts/python-uv.mk which provides common targets

    line 30
  2. Distinctive:

    Prefer running tests scoped to the project where your changes are:

    line 34
  3. Very specific:

    After changing dependencies, commit both pyproject.toml and uv.lock.

    line 95

≈ “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

Robot Python Projects

The following directories contain the robot Python projects — packages that run on or support Opentrons robots:

ProjectDirectoryDescription
opentronsapi/Core Opentrons Python API for protocol execution
robot-serverrobot-server/HTTP API server that runs on the robot
opentrons-hardwarehardware/Low-level hardware control and CAN bus communication
auth-serverauth-server/Authentication server for Flex
opentrons-shared-datashared-data/Shared data definitions (labware, pipettes, modules)
server-utilsserver-utils/Common utilities for Python servers
system-serversystem-server/System-level server for robot management
otupdateupdate-server/Server for software and firmware updates
ot3usbusb-bridge/USB bridge daemon for Flex

Common Patterns

  • Build system: pyproject.toml with hatchling (hatchling==1.27.0)
  • Dependency management: uv with uv.lock files (not pipenv or poetry)
  • Python version: 3.12 (set via UV_PYTHON = 3.12 in scripts/python-uv.mk)
  • Testing: pytest 9+ with config in [tool.pytest] section of pyproject.toml
  • Linting: ruff (replaces flake8 + isort) with config in [tool.ruff] sections of pyproject.toml
  • Type checking: mypy with config in [tool.mypy] section of pyproject.toml (not mypy.ini)
  • Shared Make includes: all Makefiles include ../scripts/python-uv.mk which provides common targets

Running Tests

Prefer running tests scoped to the project where your changes are:

# From the project directory
cd api && make test

# Or from the monorepo root
make -C api test

Each project has a Makefile with a test target. The exception is shared-data, which uses test-py:

make -C shared-data test-py

Checking Types and Linting

Each project has a Makefile with a lint target (runs ruff check + mypy). shared-data uses lint-py:

make -C api lint
make -C shared-data lint-py

Formatting

Each project has a Makefile with a format target (runs ruff format + isort fix). shared-data uses format-py:

make -C api format
make -C shared-data format-py

Setup and Teardown

Each project has setup and teardown targets. Setup runs uv sync --frozen --group dev --python 3.12. shared-data uses setup-py and teardown-py:

make -C api setup
make -C shared-data setup-py

Or from the monorepo root for all robot Python projects at once:

make setup-py      # setup all
make teardown-py   # teardown all

Dependency Management

cd api  # or any robot Python project

uv add <package>              # add production dependency
uv add --group dev <package>  # add dev dependency
uv remove <package>           # remove dependency
uv lock                       # re-resolve after manual pyproject.toml edits

After changing dependencies, commit both pyproject.toml and uv.lock.

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.