Skip to content

guide.mdx

Latest commit

 

History

History
211 lines (154 loc) · 9.13 KB

guide.mdx

File metadata and controls

211 lines (154 loc) · 9.13 KB
title AI Tools Guide
description Guidance to AI tools when working with ZK Compression. Includes Agent Skill, MCP server, DeepWiki, and AI Search guides.

import InstallAgentSkills from "/snippets/setup/install-agent-skills.mdx";

For Docs

  • Docs AI Search - Search documentation with AI in the search bar.
  • Markdown Export - Append .md to any page URL for raw markdown.
  • View /llms.txt for an index of the docs - It lists key pages with descriptions so agents can navigate to answers quickly.

For Development

Agent Skills

View or install /skill.md, a structured capability file that tells agents what they can do with Light Protocol and ZK Compression. If you're building with agents, start here.

Install or view dedicated agent skills:

Use case Skill
Build rent-free Solana programs with Light SDK (Anchor or Pinocchio). Includes router integration. light-sdk
Use Light Token client SDKs (TypeScript and Rust) for mints, ATAs, transfers light-token-client
Stream account state via Laserstream gRPC data-streaming
Wallets and payment flows with light-token. Includes privy, wallet adapter, mobile wallet adapter signing. Optional nullifier to prevent your onchain instruction from being executed more than once. payments-and-wallets
Airdrops, DePIN, token distribution token-distribution
Anti-double-spend nullifiers for Privacy-preserving ZK programs zk-nullifier
Testing programs and clients on localnet, devnet, mainnet testing
For per-user state, DePIN nodes, and infrequently accessed app state with compressed PDAs solana-compression
Help with Debugging and Questions via DeepWiki MCP ask-mcp

View all skills here: https://github.com/Lightprotocol/skills.

All skills are included and are auto-discovered based on context. Ask about light-token, defi, payments, or program migration and the agent uses the relevant skill automatically.

AI Prompts

MCP

The Model Context Protocol (MCP) is an open standard to connect AI apps to data sources and tools. The DeepWiki MCP server provides access to the Light Protocol repository with its search capabilities (AskDevin).

Installation

claude mcp add -s user -t http deepwiki https://mcp.deepwiki.com/mcp
claude mcp add -s user -t http zkcompression https://www.zkcompression.com/mcp
**We recommend to create a command** that includes the tools listed below.
Simply **copy paste this snippet**. 
---
argument-hint: <question>
description: Query Light Protocol repository and Solana resources via DeepWiki MCP for precise technical answers and help with debugging
allowed-tools: mcp__deepwiki__*
---

# /ask-deepwiki

Answer: $ARGUMENTS

Use DeepWiki MCP to provide precise technical answers.

## Step 1: Identify Repository Scope

1. **State understanding and plan**

2. **If question is vague, ask for clarification:**
- What specific component or feature?
- What problem are you solving?
- What level of detail needed (overview vs implementation)?

3. **Repository mapping:**
- ZK Compression/Light Protocol: `Lightprotocol/light-protocol`
- Solana fundamentals: `solana-labs/solana`
- Anchor framework: `solana-foundation/anchor`
- Complex questions: Query multiple repositories

4. **Refine question to use:**
- Exact component names: `CompressedAccountMeta` not "account metadata"
- Specific operations: "verifies proof" not "handles proof"
- Concrete function names or error messages when available

## Step 2: Query DeepWiki

For the identified repository, call in sequence:

1. `mcp__deepwiki__read_wiki_structure("repo-owner/repo-name")`
2. `mcp__deepwiki__read_wiki_contents("repo-owner/repo-name")`
3. `mcp__deepwiki__ask_question("repo-owner/repo-name", refined_question)`

Query multiple repositories if question spans different systems.

## Step 3: Format Response

**Structure:**
1. Direct answer with technical explanation
2. Specific implementations and data structures
3. Code examples with inline comments
4. Source references (`file:line` from DeepWiki)
5. Related concepts if relevant

**Language precision:**

NEVER use vague verbs:
- "handles", "manages", "processes", "enables", "provides"

ALWAYS use exact names:
- Functions: `LightAccount::new_init()`, `derive_address()`
- Types: `CompressedAccountMeta`, `ValidityProof`, `PackedAddressTreeInfo`
- Operations: "nullifies hash", "appends to state tree", "verifies proof"
- Fields: `tree_info`, `address`, `output_state_tree_index`

Include `file:line` references from DeepWiki responses.

## Notes

- Always include source file references from DeepWiki responses
- Provide runnable code examples for implementation questions
- Ask follow-up questions to DeepWiki for clarification when needed
codex mcp add zkcompression -- npx -y mcp-remote@latest https://www.zkcompression.com/mcp
codex mcp add deepwiki -- npx -y mcp-remote@latest https://mcp.deepwiki.com/mcp
```json { "mcpServers": { "deepwiki": { "serverUrl": "https://mcp.deepwiki.com/sse" }, "zkcompression": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://www.zkcompression.com/mcp"] } } } ```

DeepWiki MCP-Tools

  • read_wiki_structure - Get a list of documentation topics for a GitHub repository
mcp__deepwiki__read_wiki_structure("Lightprotocol/light-protocol")
  • read_wiki_contents - View documentation about a GitHub repository
mcp__deepwiki__read_wiki_contents("Lightprotocol/light-protocol")
  • ask_question - Ask any question about the GitHub repository and get a context-grounded response
mcp__deepwiki__ask_question("Lightprotocol/light-protocol", "your question")
You can specify any public GitHub repo that is indexed with DeepWiki. When you connect to the MCP, you specify the repository when calling the tools. Learn more [here](https://docs.devin.ai/work-with-devin/deepwiki-mcp).

If you don't have the MCP installed we recommend to use AskDevin in your browser.

<iframe width="100%" height="420" src="https://drive.google.com/file/d/1irbZC4NpSE6F1XctIel0yXyVmwvRsjaU/preview" title="DeepWiki Video" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen ></iframe>