Clank’s documentation is available as model-friendly Markdown. Describe what you want to build, copy the prompt below into your preferred coding model, and let it read the current docs before it writes code.
Give your model this prompt
Replace the first placeholder with your app, bot, or integration idea, then copy the whole prompt.
Build this with Clank V2:
[Describe the app, bot, or integration you want.]
Before writing code, read https://developer.clank.trade/llms-full.txt and use it as the source of truth for the Clank protocol. Follow its links to individual Markdown pages when you need more detail.
Requirements:
- Use Viem for EVM reads and transactions.
- Use the current factory, configuration, contract addresses, ABIs, fees, and lifecycle behavior from the docs. Do not guess or invent missing protocol details.
- Use launchToken and pairToken terminology throughout.
- Detect the token lifecycle state and route trades to the bonding curve or graduated Uniswap V4 pool accordingly.
- Keep quote code separate from buy and sell execution so the UI can display expected output, fees, refunds, and slippage before wallet confirmation.
- Support both native ETH and ERC-20 pair tokens where the requested feature requires them.
- Simulate state-changing contract calls before submitting them.
- State any product assumptions, then provide the implementation and explain how to run and verify it.
If you cannot access the documentation URL, stop and ask me to attach llms-full.txt instead of guessing.Choose the right docs feed
Complete context
Use llms-full.txt when the
model should build an entire integration from one document.
Documentation index
Use llms.txt when the model can
browse links and should load only the pages relevant to the task.
Every documentation page also has a Markdown version. Add /index.md to a page
path—for example,
/quickstart/index.md—when
the model only needs one focused guide.
Review before shipping
AI-generated transaction code still needs human review. Confirm that it uses the documented chain and current contracts, checks the curve state, applies slippage protection, simulates writes, and handles wallet rejection and reverted transactions.