development-session

To apply engineering conventions for refactoring, invoke development-session to enforce root-cause thinking, simplification, and abstraction-level checks before changing code. It aligns your approach with repo principles and points to ARCHITECTURE.md for structural invariants.

Managing Python dependency drift requires using the repo-pinned uv virtual environment and running commands via uv run. This development-session context reinforces consistent environment conventions to prevent avoidable dependency version mistakes.

You need to check architecture invariants before fixing bugs when changes might violate system design rules. Development-session points you to ARCHITECTURE.md to verify layering guidance and ensure bug fixes fit the established codebase conventions.

Yes, the uv virtual environment works with documentation and tooling updates. Development-session supports typo fixes, dependency updates, and infra changes by defaulting to uv run, ensuring all codebase modifications remain consistent with repo engineering principles.

You establish development-mode context for codebase edits by invoking development-session at the start of any task. It provides lightweight engineering principles and environment conventions, reducing wasted time from avoidable mistakes during skill edits or refactors.