lightsparkdev
- 4 skills
- 0 followers
- 11 hours ago last updated
- ▌ Grid API · lightsparkdev bundleThis skill should be used when the user asks to "send a payment", "check balance", "list transactions", "create a quote", "manage customers", "create external account", "what currencies does Grid support", "how do I use the Grid API", "send money to [country]", "pay [UMA address]", "send to CLABE", "send to PIX", "send to IBAN", "send to UPI", "fund sandbox account", "test a payment", "on-ramp", "off-ramp", "convert crypto to fiat", "convert fiat to crypto", "look up UMA", "real-time quote", "JIT funding", "check exchange rate", "FX rate", "payment corridor", "what rate will I get", "estimate withdrawal fee", "crypto withdrawal fee", "USDB", "USDB offramp", "embedded wallet", "embedded wallet sign", "Grid-Wallet-Signature", "Turnkey stamp", "payloadToSign", "EMAIL_OTP credential", "HPKE bundle", "decrypt credential bundle", or any payment operations using the Grid API CLI.
- ▌ Liquid Glass · lightsparkdevBuild and reuse the "liquid glass" refraction UI in components/grid-wallet-demo (the LiquidGlass / Glass / GlassOver components). Use this skill when the user asks for a glass / liquid-glass / frosted / refraction / squircle UI element — e.g. "make a glass button", "glass tab bar", "glass card", "glass panel", "glass nav", "make this glass", "glass border that expands on hover", "frosted surface", or to tune the glass effect (refraction, chroma, specular, blur, corner smoothing, shadow).
- ▌ Writing Style · lightsparkdevStyle guide for all prose authored in this repo: mintlify docs pages, OpenAPI field and endpoint descriptions, changelog entries, READMEs, PR descriptions, PR review comments, and commit messages. Read BEFORE drafting, not after. Based on the Google developer documentation style guide (developers.google.com/style). Triggers: writing or editing any .mdx page, schema description, guide, PR description, or review comment.
- ▌ Partner Dev Guide · lightsparkdev bundleUse when asked to write a one-off developer guide, integration guide, or implementation walkthrough for a named partner from a rough funds flow, numbered step list, or AM notes. Triggers: "create a dev guide for", "write up the integration for", "turn this funds flow into a guide", a pasted step list with "1. 1. 2. 2. 3." numbering, or a request to add a section to an existing partner guide.