Shared Infrastructure First

Before implementing an operation, find and use the platform's existing shared infrastructure for that operation. Commands must execute subprocesses through shared terminal helpers rather than directly importing child-process APIs. Apply the same rule to logging, filesystem operations, networking, validation, IDs, and other shared mechanisms. Native APIs and external libraries belong inside the owning infrastructure implementation. If an existing helper lacks required behavior, extend that helper rather than bypassing it or duplicating its mechanism in a caller.

Philosophy

Shared infrastructure owns mechanisms so callers remain small, consistent, and declarative.

Fix

Find the shared helper that owns the operation and replace direct native or library calls with that helper. Extend the existing helper when required behavior is missing, preserving its contract and updating its tests. Obtain approval before introducing a new shared abstraction, as required by the maximize-reuse policy.