yogurtandjam

#general aliases
alias c="cursor"

#claude aliases
alias claude-settings="c ~/.claude/settings.json"

#git aliases
alias gs="git status"
alias gch="git checkout"
alias gsh="git stash"

yogurtandjam

Global instructions

Debugging on-chain / smart contract interactions

When a contract call reverts, ALWAYS check for ABI mismatches before investigating runtime state. This is the single most important debugging step.

1. Verify the on-chain ABI matches what the frontend sends. Different deployments of the "same" contract can have different function signatures. Do NOT assume a local ABI file is correct for all contracts — check the block explorer (Etherscan/Worldscan "Read/Write as Proxy" tab) for the specific contract address.

2. Compare function selectors. If a function with the same name exists but different parameters, the 4-byte selector will be completely different and the call will revert with no useful error. Compute the selector from the ABI you're sending and verify it exists on-chain.

yogurtandjam

using @turf/intersect on these two features results in an incorrectly formatted feature
 {
  type: 'Feature',
  properties: {
    entity_type: 'geofence',
    area_sqm: 149855.00957942175,
    lat: 45.49998747388729,
    lng: -73.56712921691815,
  },
  bbox: [-73.5708342, 45.4969652, -73.563561, 45.5027965],