$npx -y skills add sendaifun/solana-new --skill solana-beginnerTeach Solana fundamentals to developers new to the ecosystem. Use when a user says "what is Solana", "why Solana", "new to Solana", "explain Solana to me", "Solana basics", "EVM to Solana", "getting started with Solana", or "Solana fundamentals". Adapts to user's background — EVM
| 1 | ## Preamble (run first) |
| 2 | |
| 3 | ```bash |
| 4 | _TEL_TIER=$(cat ~/.superstack/config.json 2>/dev/null | grep -o '"telemetryTier": *"[^"]*"' | head -1 | sed 's/.*"telemetryTier": *"//;s/"$//' || echo "anonymous") |
| 5 | _TEL_TIER="${_TEL_TIER:-anonymous}" |
| 6 | _TEL_PROMPTED=$([ -f ~/.superstack/.telemetry-prompted ] && echo "yes" || echo "no") |
| 7 | _TEL_START=$(date +%s) |
| 8 | _SESSION_ID="$$-$(date +%s)" |
| 9 | mkdir -p ~/.superstack |
| 10 | echo "TELEMETRY: $_TEL_TIER" |
| 11 | echo "TEL_PROMPTED: $_TEL_PROMPTED" |
| 12 | if [ "$_TEL_TIER" != "off" ]; then |
| 13 | _TEL_EVENT='{"skill":"solana-beginner","phase":"idea","event":"started","ts":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'"}' |
| 14 | echo "$_TEL_EVENT" >> ~/.superstack/telemetry.jsonl 2>/dev/null || true |
| 15 | _CONVEX_URL=$(cat ~/.superstack/config.json 2>/dev/null | grep -o '"convexUrl":"[^"]*"' | head -1 | cut -d'"' -f4 || echo "") |
| 16 | [ -n "$_CONVEX_URL" ] && curl -s -X POST "$_CONVEX_URL/api/mutation" -H "Content-Type: application/json" -d '{"path":"telemetry:track","args":{"skill":"solana-beginner","phase":"idea","status":"success","version":"0.2.0","platform":"'$(uname -s)-$(uname -m)'","timestamp":'$(date +%s)000'}}' >/dev/null 2>&1 & |
| 17 | true |
| 18 | fi |
| 19 | ``` |
| 20 | |
| 21 | If `TEL_PROMPTED` is `no`: Before starting the skill workflow, ask the user about telemetry. |
| 22 | Use AskUserQuestion: |
| 23 | |
| 24 | > Help superstack get better! We track which skills get used and how long they take — |
| 25 | > no code, no file paths, no PII. Change anytime in `~/.superstack/config.json`. |
| 26 | |
| 27 | Options: |
| 28 | - A) Sure, help superstack improve (anonymous) |
| 29 | - B) No thanks |
| 30 | |
| 31 | If A: run this bash: |
| 32 | ```bash |
| 33 | echo '{"telemetryTier":"anonymous"}' > ~/.superstack/config.json |
| 34 | _TEL_TIER="anonymous" |
| 35 | touch ~/.superstack/.telemetry-prompted |
| 36 | ``` |
| 37 | |
| 38 | If B: run this bash: |
| 39 | ```bash |
| 40 | echo '{"telemetryTier":"off"}' > ~/.superstack/config.json |
| 41 | _TEL_TIER="off" |
| 42 | touch ~/.superstack/.telemetry-prompted |
| 43 | ``` |
| 44 | |
| 45 | This only happens once. If `TEL_PROMPTED` is `yes`, skip this entirely and proceed to the skill workflow. |
| 46 | |
| 47 | > **Wrong skill?** See [SKILL_ROUTER.md](../../SKILL_ROUTER.md) for all available skills. |
| 48 | |
| 49 | # Solana Foundation |
| 50 | |
| 51 | Teach Solana fundamentals adaptively. This skill interviews the user about their background first, then teaches at the right level — whether they're an EVM developer, a backend engineer, or completely new to crypto. |
| 52 | |
| 53 | ## Overview |
| 54 | |
| 55 | Not everyone arrives at Solana from the same place. An Ethereum dev needs to unlearn storage patterns and think in accounts. A backend dev needs to understand why blockchains matter before diving into PDAs. A complete beginner needs the "why" before the "how." |
| 56 | |
| 57 | This skill adapts. It asks first, then teaches. |
| 58 | |
| 59 | ## Workflow |
| 60 | |
| 61 | ### Step 1: Interview the User |
| 62 | |
| 63 | **Always start here. Never skip this step.** |
| 64 | |
| 65 | Use the `AskUserQuestion` tool to determine the user's background. Ask: |
| 66 | |
| 67 | 1. **What's your development background?** |
| 68 | - New to programming entirely |
| 69 | - Backend/systems developer (Python, Go, Rust, Node.js) |
| 70 | - Frontend developer (React, Vue, etc.) |
| 71 | - EVM/Ethereum developer (Solidity, Hardhat, Foundry) |
| 72 | - Other blockchain developer (Cosmos, Sui, Aptos) |
| 73 | |
| 74 | 2. **What are you trying to build?** (DeFi app, NFT project, payments, AI agent, just learning, etc.) |
| 75 | |
| 76 | 3. **How familiar are you with crypto concepts?** (wallets, transactions, smart contracts, tokens) |
| 77 | |
| 78 | ### Step 2: Read References Based on Background |
| 79 | |
| 80 | Based on the user's answers, read the appropriate references: |
| 81 | |
| 82 | - **EVM developers** → Start with `references/solana-vs-evm.md` |
| 83 | - Focus on the account model vs storage model difference |
| 84 | - Explain why programs are stateless and data lives in accounts |
| 85 | - Cover PDAs, CPIs, and the instruction model |
| 86 | - Highlight common gotchas (rent, account size, transaction limits) |
| 87 | |
| 88 | - **New to crypto / complete beginners** → Start with `references/why-solana-for-builders.md` |
| 89 | - Explain what a blockchain is and why it matters (briefly) |
| 90 | - Focus on Solana's practical advantages: speed, cost, scale |
| 91 | - Use concrete numbers: 400ms blocks, $0.00025 fees, 65k TPS |
| 92 | - Make it tangible — compare to web2 experiences they know |
| 93 | |
| 94 | - **Backend / systems developers** → Start with `references/why-solana-for-builders.md`, then `references/solana-vs-evm.md` |
| 95 | - They'll appreciate the systems-level design of Solana |
| 96 | - Emphasize: Rust-based, parallel execution (Sealevel), no EVM overhead |
| 97 | - Compare to building APIs — programs are like microservices, accounts are like database rows |
| 98 | |
| 99 | - **Other blockchain developers** → Start with `references/solana-vs-evm.md` (the model differences apply broadly) |
| 100 | |
| 101 | ### Step 3: Walk Through the Ecosystem |
| 102 | |
| 103 | For all users, walk through relevant sections of `references/ecosystem-map.md`: |
| 104 | |
| 105 | - If they want to build DeFi → highlight major protocols by categor |