What problem does it solve? Writing integration tests for DeFi contracts that depend on live liquidity, routers, oracles, and gauges is error-prone without a consistent structure. This Skill enforces the repository's fork test conventions so generated tests match existing patterns for directory layout, inheritance, naming, and chain setup. ## Core Features & Use Cases - Standardized Test Structure: Generates fork tests following the shared/concrete directory layout with the correct inheritance chain from Base through BaseFork to concrete test contracts. - Interface-Only Testing: Enforces interface imports, vm.deployCode deployment via tests/utils/Artifacts.sol, and canonical addresses from tests/utils/Addresses.sol. - Scope Filtering: Applies a litmus test to decide which behaviors belong in fork tests (AMO pools, router swaps, oracle reads, rebases) versus unit tests (setters, access control, pure math). - Use Case: When adding a new OETH strategy that interacts with a Curve pool, use this Skill to generate fork tests covering deposits, withdrawals, and reward flows against a Mainnet fork. ## Quick Start Generate Foundry fork tests for the OETHVault deposit and withdraw flows against a Mainnet fork.