Pumpfun

Pump.fun Skill Suite

Use this skill first for Pump.fun requests, then load the narrow skill that matches the task. Treat the focused pump-* skills as the canonical local playbooks; the pumpfun-* skills are quick operational shortcuts.

Route by Task

Operating Rules

• Start with read-only state fetches, quotes, and simulations before building live transactions.
• Before any real transaction, confirm network, wallet, mint, amount, slippage, priority fee, and maximum SOL/token exposure.
• Use integer lamports/token base units with BN, bigint, or equivalent exact arithmetic. Do not use JavaScript number for balances, reserves, quotes, or fees.
• Keep instruction builders composable: return TransactionInstruction[] and let callers assemble, sign, and submit transactions.
• Use the Pump SDK package actually installed in the target repo. Examples may show @nirholas/pump-sdk; align imports with the repo's package.json.
• Never log, paste, or persist private keys except to explicitly requested keypair files with owner-only permissions.
• Query RPC for current bonding-curve, AMM, fee, claim, and wallet state. Do not assume prices, balances, graduation status, or claimability from stale context.

Program IDs