lightprotocol/testing

Light Protocol testing

Workflow

1. Clarify intent
   • Recommend plan mode, if it's not activated
   • Use AskUserQuestion to resolve blind spots
   • All questions must be resolved before execution
2. Identify references and skills
   • Match task to test references below
   • Locate relevant documentation and examples
3. Write plan file (YAML task format)
   • Use AskUserQuestion for anything unclear — never guess or assume
   • Identify blockers: permissions, dependencies, unknowns
   • Plan must be complete before execution begins
4. Execute
   • Use Task tool with subagents for parallel research
   • Subagents load skills via Skill tool
   • Track progress with TodoWrite
5. When stuck: ask to spawn a read-only subagent with Read, Glob, Grep, and DeepWiki MCP access, loading skills/ask-mcp. Scope reads to skill references, example repos, and docs.

Routing

| Task | Reference | |------|-----------| | Start local validator | references/local.md | | Test on devnet | references/devnet.md | | Test Pinocchio programs | cargo test-sbf -p <program-name> (no Anchor required) |

Program addresses

These addresses are identical on devnet and mainnet.

| Program | Address | |---------|---------| | Light System | SySTEM1eSU2p4BGQfQpimFEWWSC1XDFeun3Nqzz3rT7 | | Compressed Token | cTokenmWW8bLPjZEBAUgYy3zKxQZW6VKi7bqNFEVv3m | | Account Compression | compr6CUsB5m2jS4Y3831ztGSTnDpnKJTKS95d64XVq | | Light Registry | Lighton6oQpVkeewmo2mcPTQQp7kYHr4fWpAgJyEmDX |

Pre-initialized accounts

See references/accounts.md for state trees, address trees, and protocol PDAs.

See references/addresses.md for devnet-specific addresses and lookup tables.

SDK references

| Package | Link | |---------|------| | light-program-test | docs.rs | | @lightprotocol/stateless.js | API docs | | light-client | docs.rs |

Security

This skill provides test patterns and configuration references only.

• Declared dependencies. Devnet testing requires HELIUS_API_KEY (RPC provider key). Localnet testing needs no credentials. In production, load from a secrets manager.
• Subagent scope. When stuck, the skill asks to spawn a read-only subagent with Read, Glob, Grep scoped to skill references, example repos, and docs.
• Install source. npx skills add Lightprotocol/skills from Lightprotocol/skills.
• Audited protocol. Light Protocol smart contracts are independently audited. Reports are published at github.com/Lightprotocol/light-protocol/tree/main/audits.