opentrons
- 20 skills
- 0 followers
- 6 hours ago last updated
- ▌ Operate Kansasflex · opentronsOperates the local Opentrons Flex KansasFLEX through flex-testing-agent CLI and Python APIs only (never curl/ad-hoc robot HTTP). Use when inspecting robot state, status (instruments/door/subsystems), waiting for health after install, probing read-only endpoints, taking camera pictures, listing Flex OS releases, installing a robot OS build with ALLOW_MUTATIONS, running Pyro / protocol-subprocess validation, using the FTDI serial console (`flex-test serial`) instead of Tabby, running LPC jog timing (`flex-test lpc-jog-timing --confirm-clear-deck`), or archiving/reviewing diagnostic robot logs after seed-runs / api-suite (`flex-test logs archive`).
- ▌ Extend Flex Harness · opentronsExtends the flex-testing-agent harness by adding typed robot API clients, capabilities, CLI commands, and read-only endpoint coverage. Use when adding Flex HTTP endpoints, new inspect/probe/install/status/wait-health behavior, camera features, release tooling, or when the user asks to grow the harness instead of calling the robot ad hoc (no curl).
- ▌ E2e Testing · opentronsE2E testing conventions for Protocol Designer and Labware Library using Playwright + pytest in e2e-testing/. Use when writing, running, or modifying end-to-end tests, page objects, or Playwright tests.
- ▌ Grill Frontend Code · opentrons bundleDeep-dive review of frontend diffs against Opentrons architecture, UI layers, a11y, and prop design patterns.
- ▌ Documented Mutations · opentronsMigrate react-api-client useMutation hooks to useDocumentedMutation and update app callsites, tests, api-client userNotes, and audit_log keys. Use when converting mutations to documented mutations, wiring documentationState, or adding audit log actions for access control.
- ▌ Docs · opentronsAuthoring and styling guidelines for the Opentrons /docs MkDocs project. Covers file conventions, frontmatter, page titles, header IDs, image formats, tables, code blocks, Python API reference (mkdocstrings, autorefs, macros), and CSS patterns (parts lists, screenshots, icons, instruction lists, side-by-side figures, fonts, colors). Use when writing, editing, or reviewing any file in the docs/ directory, or when the user asks about MkDocs conventions, docstrings, CSS classes, or the Python API reference.
- ▌ AI Client · opentronsConventions for the opentrons-ai-client React/TypeScript frontend — project structure, API integration, state management (Jotai), feature flags, types, and testing. Use when working with files in opentrons-ai-client/ or discussing the AI client application.
- ▌ AI Server · opentronsConventions for the opentrons-ai-server FastAPI service — project structure, uv dependency management, settings, testing, Docker, and deployment. Use when working with files in opentrons-ai-server/ or discussing the AI server API.
- ▌ CSS Modules · opentronsCSS Modules conventions, Stylelint rules, design tokens (spacing, colors, typography, border-radius), and patterns for the Opentrons monorepo. Use when working with .module.css files or styling React components in app/, components/, protocol-visualization/, protocol-designer/, or other JS packages.
- ▌ Locize Sync · opentronsLocize i18n synchronization workflow for pushing and downloading translations in the Opentrons monorepo. Use when working with locize_sync.py, localization files in app/src/assets/localization/ or components/src/assets/localization/, or syncing translations.
- ▌ Static Deploy · opentronsConventions for static deploy automation Python CLIs in scripts/static-deploy/. Use when working with deployment scripts, AWS S3/CloudFront automation, or Python CLIs in the static-deploy directory.
- ▌ Protocol Designer · opentronsProtocol Designer (PD) application architecture, Redux slices, step/timeline system, domain concepts, and dev workflow. Use when working with files in protocol-designer/ or discussing PD features, steps, timelines, or protocol design.
- ▌ JS Package Testing · opentronsVite demo and Playwright + Applitools tests for packed @opentrons JS packages in js-package-testing/. Covers components, shared-data, step-generation, and protocol-visualization. Use for integration testing, package linking, or visual testing.
- ▌ Protocol Authoring · opentrons bundleCreate valid Opentrons Python API protocols for OT-2 and Flex robots. Use when creating, writing, editing, or helping with protocol files, liquid handling automation, or Opentrons protocol development. Also use when debugging protocol errors to trace into API source code.
- ▌ Opentrons Typescript · opentronsTypeScript conventions, React patterns, testing, styling, and import rules for the Opentrons monorepo JS/TS packages. Use when working with TypeScript or React files in app/, components/, shared-data/, step-generation/, protocol-designer/, protocol-visualization/, opentrons-ai-client/, or other JS/TS packages.
- ▌ Protocol Verification · opentronsSimulate and analyze Opentrons protocols to verify correctness. Use when asked to verify, simulate, analyze, validate, or check a protocol, or when needing to confirm a newly created protocol works.
- ▌ Robot Python Projects · opentronsGuidelines for robot Python projects — api/, robot-server/, hardware/, auth-server/, shared-data/, server-utils/, system-server/, update-server/, usb-bridge/, g-code-testing/. Use when working with Python files in these directories or their pyproject.toml files.
- ▌ React Component Creation · opentronsComponent creation checklist and ai-client-specific patterns for React .tsx files in opentrons-ai-client/ and protocol-designer/. Use when creating new React components in these packages.
- ▌ Analyses Snapshot Testing · opentronsConventions for the analyses snapshot testing framework in analyses-snapshot-testing/. Use when working with protocol analysis snapshots, adding protocols, updating snapshots, or running snapshot tests.
- ▌ App E2e · opentronsOpentrons desktop app (Electron) Playwright E2E tests in this standalone workspace. Use when writing, running, or modifying tests under tests/app/, page objects in automation/app_pages/, helpers in automation/app_helpers/, or make test-app* targets.