Declare which fiat↔crypto rails a ramp provider supports. Implement discovery or an explicit static distiller in @sdp/payments, then regenerate the committed provider snapshot and shared support matrix.
Register a new ramp provider across the SDP payments package, API schemas and dispatch, availability/setup, environment contract, shared quote types, webhooks, and dashboard catalog. Step 1 for a provider-owned ramp integration PR.
File an SDP bug to Linear as a sub-issue of the ongoing bug-bash epic PRO-1482, with concise numbered repro steps and a browser screenshot attached. Use only when explicitly invoked for an SDP dashboard or API bug. Not for feature requests or planning tickets.
ADHD-friendly digest of a change set in the SDP repo — what changed product-wise, how it's technically implemented, which domains are touched, and which packages are used — plus a reuse/zod/transaction review pass and product-obligation checks (policy coverage, encryption, Kora budgets, metered quota). Use when…
Use when designing, prototyping, reviewing, or implementing UI for the Solana Distribution Platform (SDP), especially payments, wallets, counterparties, or issuance flows. Applies SDP-specific design rules, prototype constraints, typography, navigation, table, wizard, and issuance guidance before making UI changes.
Instructions for solana-foundation/solana-developer-platform, covering solana developer platform, repo layout, source of truth, generated files and public vs internal surfaces.
Explain, plan, and prototype tokenization workflows on Solana Developer Platform using the supported public docs and API surface. Use when a consumer wants to issue a stablecoin, tokenized security, loyalty token, or other asset with SDP.