light-token-client

Imported from Azumizeus/PromptDeck (skill/skills/lightprotocol-skills/skills/light-token-client/SKILL.md). Install upstream with npx skills add Azumizeus/PromptDeck --skill light-token-client. Copyright stays with the author.

Light Token Client SDKs

Client-side cookbook for @lightprotocol/compressed-token (TypeScript) and light_token_client (Rust). Covers all token operations: create mints, associated token accounts, transfer, approve, revoke, burn, wrap, unwrap, freeze, thaw, close, and load.

Prerequisites

Examples show both localnet and devnet configurations. For devnet, set:

• API_KEY env var — Helius or Triton RPC API key. In production, load from a secrets manager.
• ~/.config/solana/id.json — local Solana keypair (solana-keygen new). In production, load from a secrets manager.

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 domain 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.

Domain references

Operations overview

External references

Security

This skill does not pull, store, or transmit external secrets. It provides code patterns, documentation references, and development guidance only.

• Declared dependencies. Devnet and mainnet examples require API_KEY (Helius or Triton RPC key) and read ~/.config/solana/id.json for the payer keypair. Neither is needed on localnet. In production, load both from a secrets manager.
• User-provided configuration. RPC endpoints, wallet keypairs, and authentication tokens are configured in the user's application code. The skill demonstrates patterns — it does not store or transmit secrets.
• Install source. npx skills add Lightprotocol/skills installs from the public GitHub repository (Lightprotocol/skills). Verify the source before running.
• Subagent scope. When stuck, the skill asks to spawn a read-only subagent with Read, Glob, and Grep scoped to skill references, example repos, and docs.
• Audited protocol. Light Protocol smart contracts are independently audited. Reports are published at github.com/Lightprotocol/light-protocol/tree/main/audits.