This page is a routing and guardrails guide. Use it to pick the right next page, then switch to the linked SDK, ABI, CLI, or MCP references for exact syntax and API details.
Install Thru Skills
Thru-specific skills live in the publicUnto-Labs/ai repository.
Start by installing the thru-best-practices skill. It is the highest-value default skill for agentic Thru development and should be part of the agent setup before working on programs, ABIs, SDK integrations, or CLI workflows.
To install the Thru skills repo:
Pick Your Path
| If the task is… | Start here | Then use |
|---|---|---|
| Build a first C program | Quickstart: Build a C Program | C SDK, Recommended Development Pattern |
| Work on CPI or authorization flow | Cross Program Invocation | C SDK Cross-Program Invocation, Common Gotchas |
| Write or update an ABI | Overview | Authoring Guide, Examples, Specification |
| Prove an ABI is correct before deploy | Validation and roundtrip testing | ABI Analyze, ABI Codegen, ABI Reflect |
| Publish or upgrade program + ABI | Recommended Development Pattern | Publishing and Iteration, Program, ABI |
| Build a web app or backend integration | SDK Packages | Web Overview, Rust, the package reference page you actually need |
| Debug deployed behavior | Explorer MCP Overview | Tools Reference, Transaction, runtime errors |
Use the Docs Site as Context
When an agent is already on a docs page, prefer the docs site’s built-in AI-friendly actions:- use
Copy pagewhen you want to paste the full page into a chat - use
View as Markdownwhen you want a cleaner source for an agent to read - keep the copied context narrow and task-specific instead of pasting large parts of the site
Use Explorer MCP for Live Chain Context
For deployed-chain tasks, Explorer MCP is usually the safest way to keep an agent grounded in current state. Use it for:- account lookups
- transaction inspection
- recent blocks and recent transactions
- program ABI lookup
- ambiguous identifier search