AI Resources
Make Cursor, Claude Code, Copilot, and other AI assistants write correct CKB/CCC code — set them up, prompt them well, and verify the result.
This section is for developers who use an AI coding assistant (Cursor, Claude Code, GitHub Copilot, Windsurf, ChatGPT, …) to build on CKB with CCC. Its only goal: make your assistant write correct CCC code instead of confidently wrong code.
Why the extra effort is needed: CKB uses the Cell model (a generalized UTXO model), which barely appears in the Ethereum-heavy data most LLMs were trained on. Left unguided, an assistant will produce CCC code that looks right but isn't — wrong transaction ordering, invented methods, number where CKB needs bigint, EVM-style assumptions. CCC ships a set of machine-readable Agent Skills — one hub skill (ckb-ccc-fundamentals) plus a spoke skill per task area (signer setup, transactions, UDT, Spore, playground, examples) — that encode the CCC-specific rules; these pages show you how to feed them to your tool and get reliable output.
Do this once, then it just works
- Set up your tool — one-time config so your assistant always loads CCC's rules (under 2 minutes).
- Verify it worked — ask one canary question to confirm the rules actually loaded. Don't skip this: a silently-failed setup looks configured but isn't.
- Prompt it well — per request, name the exact package and point it at the relevant guide.
New here? Start with Set Up Your AI Tools and do the 2-minute setup for the tool you use — everything else builds on it.
Pages in this section
Set Up Your AI Tools
Copy-paste config for Cursor, Claude Code, GitHub Copilot, Windsurf, and ChatGPT — plus which CCC links to point your assistant at.
Prompting Best Practices
A before/after example, prompt templates by task, and the specific CKB mistakes AI makes — with the one-line correction for each.
Verify & Troubleshoot
Canary questions to confirm your setup actually works, and a step-by-step decision tree for when the assistant still gets CKB wrong.