robot-python-projects

Name: robot-python-projects
Availability: InStock
Author: Opentrons

Organize Opentrons robot Python projects with standardized build, test, lint, and type-check configurations.

515|208|Updated Jul 6, 2015

Search Tags:#testing #devops #api #python #software-engineering #robotics #opentrons

Ready to run

npx skills add https://github.com/Opentrons/opentrons --skill robot-python-projects

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: robot-python-projects
Source: https://github.com/Opentrons/opentrons/tree/main/.cursor/skills/robot-python-projects
Command: npx skills add https://github.com/Opentrons/opentrons --skill robot-python-projects

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides centralized guidelines for organizing and maintaining the core robot Python projects—api/, robot-server/, hardware/, auth-server/, shared-data/, server-utils/, system-server/, update-server/, usb-bridge/, g-code-testing/—to streamline development, testing, and collaboration.

Core Features & Use Cases

Project cataloging: clearly documents which directories are part of the robot Python project ecosystem.
Standard patterns: summarizes build, testing, linting, and setup conventions across all projects to ensure consistency.
Use Case: a new contributor references the guidelines to quickly locate where to add a feature to the api/ or update the pyproject.toml.

Quick Start

Follow these guidelines to begin organizing a new robot Python project, starting with creating a pyproject.toml and a small API module.

Frequently Asked Questions about robot-python-projects

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I standardize Python project structure across multiple directories?▼

Standardize Python project structure by applying common patterns for build tooling, testing, linting, and type checking across all robot codebases. This ensures consistent project organization using pyproject.toml, pytest, ruff, and mypy configurations.

What build tooling and linting conventions should I use for Opentrons Python projects?▼

Use pyproject.toml with hatchling for build tooling, pytest for testing, ruff for linting, and mypy for type checking. These common patterns maintain consistency across api/, robot-server/, and hardware/ directories.

Which directories are included in the Opentrons robot Python project ecosystem?▼

The Opentrons robot Python project ecosystem includes api/, robot-server/, hardware/, auth-server/, shared-data/, server-utils/, system-server/, update-server/, usb-bridge/, and g-code-testing/ directories for centralized development guidelines.

Can I use these guidelines to set up a new Python project from scratch?▼

Yes, you can use these guidelines to start organizing a new robot Python project. Begin by creating a pyproject.toml with hatchling configuration and a small API module following the documented standard patterns.

Why do I need consistent build configurations across robot Python codebases?▼

Consistent build configurations streamline development, testing, and collaboration across multiple robot Python directories. Standardizing pyproject.toml, pytest, ruff, and mypy settings ensures new contributors can quickly locate and add features.

Does this skill cover type checking and testing setup for hardware-related Python projects?▼

Yes, this skill covers type checking and testing setup for hardware-related Python projects. It applies mypy for type checking and pytest for testing across hardware/ and related tool directories to maintain code quality.