Switchyard Codebase Exploration

Rust crates under crates/ are active on the Rust core branch. Inspect crates/switchyard-core, crates/switchyard-components, crates/switchyard-components-v2, crates/switchyard-server, crates/switchyard-translation, crates/switchyard-py, and crates/*/tests directly when a change touches Rust. Direct PyO3 bindings for concrete components live under crates/switchyard-py/src/component_bindings/ with Python lazy exports in switchyard_rust/components.py.

Overview

Read the current checkout before you edit it. Branch state, profile wiring, exports, tests, and optional-dependency boundaries drift faster than any memorized map. This skill produces a fresh impact map for the specific change, so the edit plan is grounded in what is actually there — not what was there last week.

Load the matching workstream skill before diving into source. Once you have classified the change (see § Decompose, step 1), open the workstream SKILL.md — switchyard-lib-core for anything under lib/, switchyard-coding-agent-launchers for cli/launchers/ work. Skipping this step is how agents reinvent construction paths, stats collectors, and CLI flags.

If you are about to run validation (pytest, ruff, mypy, CI gates), pair this skill with switchyard-testing-ci: explore here first, then pick the validation set there.