
Secure Solana frontends against phishing, bad prompts, and unsafe signing requests. Use for audits of wallet UX and dApp sites.
--- name: program-security-basics description: Baseline security checklist for Solana programs: authority checks, input validation, upgrade keys, unsafe patterns, and attack surfaces. Use for design reviews and pre-deploy audits. --- # Program Security Basics Role framing: You are a Solana security reviewer. Your goal is to catch common vulnerabilities before deployment. ## Initial Assessment - Program upgradeability status and key custody? - What assets/value does the program control? Token
Automate posting/monitoring social signals (X/Telegram) with rate-limit awareness and safe templates. Use for content cadence or alerts.
Implement Token-2022 (Token Extensions) features - transfer fees, permanent delegate, metadata pointer, confidential transfers, and more. Use when creating advanced tokens or analyzing Token-2022 tokens.
--- name: tokenomics-design-for-memecoins description: Craft pragmatic tokenomics for Solana memecoins: supply narrative, burns/sinks, incentives, and realism checks. Use during concepting and pre-launch docs. --- # Tokenomics Design for Memecoins Role framing: You are a memecoin tokenomics designer. Your goal is to make the supply story fun, simple, and credible. ## Initial Assessment - Meme theme and symbols? Target community vibe? - Supply size preference (fixed vs huge supply)? Decimals?
--- name: pda-design-playbook description: Patterns for designing PDAs: seed strategy, collision avoidance, upgrade considerations, and bump handling. Use when creating or auditing PDAs. --- # PDA Design Playbook Role framing: You are a PDA strategist. Your goal is to design deterministic, safe PDA schemes that survive upgrades and user mistakes. ## Initial Assessment - What entities need PDAs? (global state, user state, vaults, authorities) - Are seeds user-controlled? Any variable-length or
Evaluate and configure SPL token authorities (mint/freeze/close) with risk implications and best practices. Use for audits, rotations, or disclosures.
--- name: launch-readiness-checklist description: End-to-end pre-flight checklist for launching a Solana token/app: infra, wallets, liquidity, comms, security, and rollback planning. Use before mainnet launch or major release. --- # Launch Readiness Checklist Role framing: You are a Solana launch operator. Your goal is to verify the build, infra, liquidity, and comms are ready, with clear abort criteria. ## Initial Assessment - Launch scope: token only, dApp, or both? What chain (mainnet/devn
Understand sniper bots in Solana launches and implement defensive measures without harming fair access. Use before token or LP go-live.
Decide when and how to index Solana data vs direct RPC reads. Covers event design, backfill, storage, and performance. Use for data architecture decisions.
--- name: post-launch-stabilisation-playbook description: Stabilize a token/dApp after launch: monitoring, comms, liquidity adjustments, and product milestones. Use during first 72 hours and beyond. --- # Post-Launch Stabilisation Playbook Role framing: You are a post-launch stabilizer. Your goal is to keep the system healthy, transparent, and responsive right after go-live. ## Initial Assessment - Current metrics: price, liquidity depth, tx success rate, error classes? - Incidents open? User
--- name: monitoring-and-alerting description: Monitoring plan for Solana apps: RPC health, tx success, program errors, and liquidity signals. Use to set up dashboards and alerts. --- # Monitoring and Alerting Role framing: You are an observability lead. Your goal is to ensure early detection of issues across RPC, programs, and markets. ## Initial Assessment - What components exist? (frontend, backend, programs, bots, LPs) - SLOs for latency/success? On-call structure? - Tools available (Graf
Design Solana/Anchor instructions with clear inputs, constraints, authority checks, and invariants. Use when defining or reviewing instruction APIs.
--- name: anchor-project-scaffold description: Set up a production-ready Anchor workspace: program/client layout, env config, testing, and build hygiene. Use when starting new Anchor projects or re-baselining repos. --- # Anchor Project Scaffold Role framing: You are an Anchor setup expert. Your goal is to create a clean, reproducible project scaffold with reliable builds and tests. ## Initial Assessment - Target cluster(s) and program upgradeability plan? - Rust/Anchor versions pinned? Toolc
--- name: automation-governance description: Governance and guardrails for automation/bots: permissions, logging, kill-switches, and ethics. Use before deploying bots that move funds or post publicly. --- # Automation Governance Role framing: You are a risk officer for bots. Your goal is to set guardrails so automation is safe and auditable. ## Initial Assessment - What actions can the bot take? (post, trade, transfer?) - Who approves changes? Where are keys stored? - Blast radius if bot misb
--- name: common-anchor-errors-debugger description: Troubleshoot frequent Anchor runtime errors: discriminator mismatch, constraint failures, account deserialization, and CPI issues. Use when tests or txs fail with Anchor errors. --- # Common Anchor Errors Debugger Role framing: You are an Anchor debugger. Your goal is to quickly identify and fix common Anchor runtime failures. ## Initial Assessment - Which error code or message is returned? (ConstraintSeeds, AccountDidNotSerialize, etc.) -
--- name: community-ops-playbook description: Moderate and grow Solana communities (TG/Discord): rules, mod actions, FUD handling, legitimacy cues. Use for community operations. --- # Community Ops Playbook Role framing: You are a community operations lead. Your goal is to keep channels safe, informative, and aligned with trust messaging. ## Initial Assessment - Platforms (TG/Discord) and existing mod team size? - House rules and enforcement tools? Bot support? - Typical volume and timezones?
Build with Solana compressed NFTs (cNFTs) - Merkle trees, minting at scale, transfers, and metadata. Use when creating large NFT collections or reducing mint costs.
--- name: cost-planning-for-solana-apps description: Estimate and control costs for Solana apps: RPC, indexing, storage, bots, and on-chain fees. Use for budgeting and scaling. --- # Cost Planning for Solana Apps Role framing: You are a cost engineer. Your goal is to forecast and manage spend while maintaining reliability. ## Initial Assessment - User and transaction volume forecasts? Peak vs average? - Components: RPC providers, indexers, storage, bots, CDNs? - On-chain fee sensitivity? Prio
--- name: fair-launch-patterns description: Operational patterns for fair token launches: definitions, mechanics, tradeoffs, and execution steps. Use when planning fair/transparent launches. --- # Fair Launch Patterns Role framing: You are a launch architect. Your goal is to design a fair, transparent launch that buyers can verify. ## Initial Assessment - Definition of “fair” for this project (no presale? equal price? anti-bot?) - Supply and pricing method (flat mint, bonding curve, auction)?
Master Jito bundles for MEV protection and priority fee optimization on Solana - bundle submission, tip strategies, and transaction landing. Use for trading bots, high-priority transactions, and MEV-aware applications.
Integrate Jupiter aggregator for swaps - API usage, route optimization, slippage handling, and frontend/bot implementation. Use when building swap UIs or trading bots.
Build a bot that detects new Solana launches (mints/LPs) and sends safe alerts. Use for discovery and monitoring without shilling scams.
--- name: launch-announcement-structures description: Templates for Solana launch announcements: X threads, pinned TG messages, FAQs with addresses and disclosures. Use for Day 0 comms. --- # Launch Announcement Structures Role framing: You are a comms lead. Your goal is to announce launches clearly with verifiable info and risk disclosures. ## Initial Assessment - Launch type and time (UTC)? Addresses ready (mint, program, LP)? - Channels to post (X, TG, Discord, site)? - Promised disclosure
--- name: legitimacy-signals description: How to project legitimacy for Solana projects: disclosures, address registry, audits, comms patterns, red-flag avoidance. Use for project pages, announcements, and community trust work. --- # Legitimacy Signals Role framing: You are a trust & safety operator for Solana launches. Your goal is to surface credible signals, avoid scams cues, and give buyers clear risk context. ## Initial Assessment - Project type (token, dApp, NFT, bot) and stage (pre-lau
Explain Solana AMM liquidity, slippage, volatility, and LP mechanics for tokens. Use to brief teams or design initial liquidity.
--- name: memecoin-narrative-engine description: Build a meme narrative system: frames, symbols, story arcs, and content hooks tailored for Solana memecoins. Use for brand/story development. --- # Memecoin Narrative Engine Role framing: You are a meme creative director. Your goal is to craft a sticky narrative that aligns with token operations. ## Initial Assessment - Meme theme, mascot, and cultural references? - Audience segments (degens, builders, normies)? - Tone (wholesome/chaotic/ironic
--- name: post-launch-content-cadence description: Plan content cadence day 0–30 after launch: updates, proofs, community loops, and ethical hype management. Use to keep attention sustainably. --- # Post-Launch Content Cadence Role framing: You are a content ops lead. Your goal is to keep the community informed and engaged without overpromising. ## Initial Assessment - Channels in use? Team bandwidth for daily posts? - Upcoming milestones (features, listings, burns)? - Availability of on-chai
--- name: post-launch-token-ops description: Runbook for token operations after launch: treasury moves, unlock communications, LP adjustments, and monitoring. Use for weeks 1–4 post launch. --- # Post-Launch Token Ops Role framing: You are a token ops lead. Your goal is to operate treasury and liquidity transparently after launch. ## Initial Assessment - Current liquidity positions and custodians? - Upcoming unlocks/airdrops? Schedule? - Monitoring in place for price/liquidity/volume? - Commu
Deep technical understanding of pump.fun bonding curves, graduation mechanics, migration to Raydium, and trading dynamics. Use for building, analyzing, or trading pump.fun tokens.
--- name: reading-onchain-state description: Patterns for reading Solana on-chain state efficiently: getAccountInfo, getProgramAccounts, caching, and reactivity. Use for frontends and services. --- # Reading On-Chain State Role framing: You are a Solana data access engineer. Your goal is to fetch on-chain state efficiently and reliably. ## Initial Assessment - Data types needed (accounts, token balances, logs)? - Volume and freshness requirements? (real-time vs periodic) - Is indexing availab
--- name: reputation-recovery-playbook description: Recover credibility after mistakes: incident comms, restitution, roadmap resets, and monitoring sentiment. Use after exploits, missteps, or comms errors. --- # Reputation Recovery Playbook Role framing: You are a crisis manager. Your goal is to respond to incidents transparently and rebuild trust. ## Initial Assessment - What happened? Impacted users/funds? Root cause known? - Current status (contained/ongoing)? - Evidence available (txids,
Playbook for selecting Solana RPC providers and building resilient client access (fallbacks, timeouts, rate limits, caching, cost control). Use when designing infra or debugging RPC issues.
Comprehensive rug detection for Solana tokens - red flags, contract analysis, LP verification, insider patterns, and escape routes. Use before buying any token to protect against scams.
--- name: solana-account-model description: Expert guide to Solana's account model: ownership, signers, rent, PDAs, CPIs, and state layout decisions. Use when modeling accounts, auditing account flows, or debugging account-related errors. --- # Solana Account Model Role framing: You are a Solana core developer who designs and audits account flows. Your goal is to produce safe, rent-efficient account plans, validate ownership/signers, and prevent runtime account errors. ## Initial Assessment -
--- name: spl-token-create-and-configure description: SOP for creating and configuring SPL tokens: mint creation, authorities, decimals, freeze/mint revoke flows, multisig custody, and validation steps. Use for new token setup or authority changes. --- # SPL Token: Create and Configure Role framing: You are a Solana token engineer. Your goal is to create an SPL mint safely, set authorities correctly, and document irreversible choices. ## Initial Assessment - Token purpose (utility, meme, gove
Comprehensive token analysis for rug detection - LP analysis, authority checks, holder distribution, insider patterns, and red flags. Use before buying any Solana token.
Plan wallet splits, allocations, vesting, and transparency for SPL token launches. Use when designing distribution charts or multisig treasuries.
Design and build Solana trading bots - execution engine, position management, risk controls, and operational infrastructure. Use when building swap bots, arbitrage bots, or automated trading systems.
--- name: transaction-signing-and-feedback description: Design transaction signing UX on Solana: pending/confirmed states, retries, fee prompts, and error messaging. Use when building tx flows. --- # Transaction Signing and Feedback Role framing: You are a UX engineer for Solana tx flows. Your goal is to make signing reliable and understandable. ## Initial Assessment - Types of transactions (simple transfer, swap, complex CPI)? - Expected confirmation level? (processed/confirmed/finalized) -
--- name: transparency-and-disclosures description: Write clear disclosures for Solana projects: risks, unlocks, authority states, and data sources. Use for websites, docs, and announcements. --- # Transparency and Disclosures Role framing: You are a disclosures officer. Your goal is to communicate risks and facts plainly with verifiable links. ## Initial Assessment - What products/tokens are live? What risks exist (smart contract, market, custodial)? - Upcoming events (unlocks, upgrades)? -
Framework for deciding whether to keep a Solana program upgradeable or make it immutable, including trust, operations, and governance tradeoffs. Use before deployment or key rotation.
--- name: wallet-connection-ux description: Best practices for Solana wallet connect flows (Phantom, Solflare, Backpack): connect/disconnect, state handling, error UX, safety prompts, and edge-case handling. Use when building or reviewing frontend wallet UX. --- # Wallet Connection UX Role framing: You are a Solana frontend lead focused on wallet flows. Your goal is to make connect/sign UX fast, clear, and safe across major wallets. ## Initial Assessment - Target frameworks (React/Next/Svelte
Build a Solana wallet monitoring bot (inflows/outflows, threshold alerts) with safe rate limits and privacy guardrails. Use for treasury monitoring, whale tracking, or security alerts.
Design webhook/event pipelines for Solana activity with idempotency, dedupe, retries, and ordering. Use when consuming RPC/webhook feeds.
Track and analyze whale wallets on Solana - identify smart money, cluster related wallets, detect accumulation/distribution patterns, and filter signal from noise. Use for alpha generation and risk assessment.