Prompt to hook.

The deploy-uni-hook skill turns a one-line brief into a live Uniswap v4 hook: generate the Solidity, derive the flags, mine the CREATE2 salt, then audit, behavioral-test, and fork-simulate before it ever broadcasts. Every hook below is live on Base Sepolia - written by aeon, verifiable onchain.

Three skills, one chain
  1. 01hook-ideaBrainstorms 5 buildable v4 hooks using the xAI API, deduped against everything already tried.
  2. 02deploy-uni-hookTurns one brief into a live hook - audit, behavioral test, fork sim, then broadcast.
  3. 03hook-frontendShips a wallet-connectable demo dapp so the hook's mechanic is visible onchain.
10Hooks liveAll on Base Sepolia (84532), each verifiable at its address.
3Live demo dappsConnect a wallet, faucet test tokens, and swap to trigger the hook.

Every hook here is DEPLOYED and live on Base Sepolia, verifiable at its address; a DEMO badge marks the ones that also have a wallet-connectable dapp. The colored strip is the hook's on-chain fingerprint - which swap steps it hooks into, tinted by what it can do (all 10 as of Aug 3, 2026).

  • VALUE (moves tokens)
  • FEE (dynamic)
  • GATE (allow / reject)

How it works

  1. 01

    Generate

    A brief becomes Solidity. Templates cover fee-surge, no-op, and skim-a-cut; anything novel is written freeform as a single Hook contract. The flags are derived from which callbacks it implements, never hand-set.

  2. 02

    Gate

    Three gates run before any deploy: a static audit (names, onlyPoolManager, no selfdestruct/delegatecall), an agent-written behavioral forge test that asserts the hook's actual rule, and a fork simulation of deploy + swap. Any failure stops the run.

  3. 03

    Deploy

    Mine a CREATE2 salt so the address carries the right flag bits, broadcast, initialize the pool, add liquidity, and run one swap. Dry-run is the default; a live broadcast needs an explicit arm:, and mainnet needs a triple lock.

  4. 04

    Show

    The best hooks get a hook-frontend demo: a wallet-connectable dapp that faucets test tokens, reads the hook's live state, and swaps through the pool so its mechanic is visible - not just described.

Safe by design

A hook binding is immutable and a bad hook can brick a pool or steal funds, so the gates sit before the deploy. The deploy key is a burner holding gas float only; the demo pools trade MockERC20 tokens, so a broadcast risks gas, never real capital. Everything after the broadcast is just recording what already happened onchain.