yo-design
Create distinctive, production-grade React + Tailwind v4 interfaces in YO's dark-theme aesthetic (#000 background, #D6FF34 neon accent, Space Grotesk). Use this skill when the user asks to build web components, pages, dashboards, or applications for YO — including vault displays, DeFi interfaces, landing pages, or any UI that should follow the YO brand. Also use when the user mentions "YO theme", "YO style", "YO brand", or asks to style something with the neon-on-black look.
- License 许可
- MIT
- 最近更新
- 2026-06-02
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- yo-design
- author
- yoprotocol
- source
- https://github.com/yoprotocol/yo-protocol-skills/tree/main/skills/yo-design
- homepage
- https://github.com/yoprotocol/yo-protocol-skills
- description
- Create distinctive, production-grade React + Tailwind v4 interfaces in YO's dark-theme aesthetic (#000 background, #D6FF34 neon accent, Space Grotesk). Use this skill when the user asks to build web components, pages, dashboards, or applications for YO — including vault displays, DeFi interfaces, landing pages, or any UI that should follow the YO brand. Also use when the user mentions "YO theme", "YO style", "YO brand", or asks to style something with the neon-on-black look.
02 资源文件 1
- 参考文档references/brand-kit.md2.6 KB
03 SKILL.md 正文
Official Yo Protocol skill. Canonical repository: https://github.com/yoprotocol/yo-protocol-skills
Build production-grade React + Tailwind v4 interfaces that look and feel unmistakably YO. Every output should be dark, precise, and alive with that neon green energy.
Read references/brand-kit.md for exact hex values, vault colors,
typography specs, Tailwind v4 theme config, and brand restrictions.
Stack
- React (functional components, hooks)
- Tailwind v4 with CSS-first
@themeconfig - Space Grotesk via Google Fonts (the only permitted typeface)
- Motion (framer-motion) for animations when available
- Plain CSS for animations when Motion is not available
YO Aesthetic
YO's visual identity is dark, clean, and electric. Black backgrounds, neon green (#D6FF34) as the sole accent, Space Grotesk typography, and generous whitespace. The brand is a DeFi yield protocol — the aesthetic should feel technical, confident, and premium.
Color Rules
The palette is intentionally constrained:
- Background:
#000000(primary) or#2B2C2A(elevated surfaces/cards) - Accent:
#D6FF34(neon green) — for CTAs, highlights, active states, emphasis. This is the only brand accent color. - Text: white for primary, muted gray for secondary
- Vault colors: Each yoVault product has a dedicated color (see
references/brand-kit.md). Use these when displaying vault-specific data, never as generic decoration.
Brand restriction: no gradients on brand colors. The neon green is always flat. Gradients are permitted on non-brand decorative elements (glows, background atmospherics) but never on the YO green itself.
Typography
Space Grotesk is the only typeface. No alternatives, no fallbacks beyond system-ui. Use Semibold/Medium for headings, Regular for body. Generous letter-spacing on headings. Clean hierarchy through weight and size, not through font variety.
Atmosphere & Depth
Dark interfaces need texture to avoid feeling flat. Create depth through:
- Subtle glow effects using the neon green (box-shadow, text-shadow)
- Fine borders (
border-yo-darkorborder-white/10) to separate surfaces - Noise/grain overlays at low opacity for texture
- Strategic use of
backdrop-blurfor layered surfaces - Ambient light effects — a soft neon glow bleeding from interactive elements
Avoid: solid gray backgrounds, heavy drop shadows, gradient meshes with multiple colors, anything that reads as generic dark-mode rather than YO.
Motion
Animations should feel precise and snappy, matching the technical DeFi context. Good patterns:
- Staggered reveals on page load (
animation-delaycascade) - Hover states with glow intensification
- Number counters for yield/APY displays
- Subtle pulse on live data indicators
- Smooth transitions between states (0.2-0.3s ease-out)
Avoid: bouncy/playful easing, slow fades, spinning loaders, anything that feels casual or imprecise.
Layout
- Dark, generous negative space — let elements breathe
- Card-based layouts with
#2B2C2Asurface on#000background - Data-dense sections (tables, charts) with clean grid alignment
- Asymmetric hero sections are welcome for landing pages
- Sticky headers and fixed navigation for dashboards
Frontend Aesthetics Guidelines
Avoid generic AI-generated aesthetics like predictable layouts and component patterns, or cookie-cutter design that lacks context-specific character. Stay true to YO's established visual language.
Interpret creatively and make unexpected choices that feel genuinely designed for the context within YO's dark-theme aesthetic. Vary layouts, compositions, and visual treatments — no two designs should feel identical.
Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details. Elegance comes from executing the vision well.
Remember: Claude is capable of extraordinary creative work. Don't hold back, show what can truly be created when thinking outside the box and committing fully to a distinctive vision.
Implementation Checklist
When building a YO interface:
- Set up the Tailwind v4
@themeblock with YO tokens (see reference file) - Import Space Grotesk from Google Fonts
- Establish the dark background and color hierarchy
- Build the layout with proper spacing and card surfaces
- Add the neon green accent to interactive and emphasis elements
- Layer in atmospheric effects (glows, borders, texture)
- Add motion for key moments (load, hover, state changes)
- Verify: no gradients on brand colors, no off-brand fonts, no light theme
04 同仓库更多 Skills
yo-protocol-sdk
ALWAYS use this skill when the user writes TypeScript or JavaScript code that imports from `@yo-protocol/core`, uses `createYoClient`, or programmatically interacts with Yo Protocol vaults (yoETH, yoUSD, yoBTC, yoEUR, yoGOLD, yoUSDT) via the SDK. This skill covers the complete `@yo-protocol/core` SDK: client initialization (createYoClient, multi-chain publicClients, partnerId), vault reads (getVaultState, previewDeposit, previewRedeem, isPaused), user reads (getUserPosition, getShareBalance, getTokenBalance, getAllowance), prepared transactions (prepareDepositWithApproval, prepareRedeemWithApproval, prepareApprove), REST API queries (getVaultSnapshot, getVaultYieldHistory, getVaultTvlHistory, getUserHistory, getUserPerformance), Merkl reward claims (getClaimableRewards, prepareClaimMerklRewards), and utilities (parseTokenAmount, formatTokenAmount, VAULTS registry, gateway address). Trigger for Node.js scripts, backend services, bots, Safe/AA batch transaction builders, or any non-React TypeScript code that interacts with Yo Protocol. Also trigger when the user mentions the Yo gateway, PreparedTransaction, ERC-4626 vault interactions specific to Yo, or asks about vault addresses and token addresses per chain. Do NOT use for React hooks (use yo-protocol-react) or CLI shell commands (use yo-protocol-cli).
yo-protocol-react-sdk
ALWAYS use this skill when the user is working with React components or hooks that interact with Yo Protocol vaults, or imports from `@yo-protocol/react`. This skill covers the full React SDK: YieldProvider setup, query hooks (useVaultState, useVaultSnapshot, useUserPosition, useTokenBalance, useShareBalance, useAllowance, useMerklRewards, useLeaderboard, usePrices, etc.), action hooks (useDeposit, useRedeem, useApprove, useClaimMerklRewards), and migration from the old API (useVault→useVaultState, useUserBalance→useUserPosition, inputToken→token, account→owner, partnerId string→number, publicClient→publicClients). Trigger whenever the user mentions yo protocol React hooks, vault dashboard components, deposit/redeem UI flows, YieldProvider, useYoClient, @yo-protocol/react, yo-kit, or asks to build React components for yoETH, yoUSD, yoBTC, yoEUR, yoGOLD, or yoUSDT vaults. Also trigger when the user has broken imports or API changes after upgrading @yo-protocol/react. Do NOT use for CLI shell commands (use yo-protocol-cli) or server-side Node.js scripts without React (use yo-protocol-sdk).
yo-protocol-cli
ALWAYS use this skill when the user mentions the YO Protocol CLI, the `yo` command, `@yo-protocol/cli`, or wants to interact with YO Protocol vaults (yoETH, yoUSD, yoBTC, yoEUR, yoGOLD, yoUSDT) from a shell script, terminal, or command line. The `yo` binary is an agent-first interface for ERC-4626 yield vaults on Ethereum (1), Base (8453), and Arbitrum (42161). It outputs structured JSON to stdout, never requires or accepts private keys, and produces unsigned calldata routed through the YO Gateway — ready for Safe/AA wallets and Base MCP `send_calls`. Use it for: building unsigned transactions (`yo prepare {approve,deposit,redeem,deposit-with-approval}`), reading positions and rewards (`yo position`, `yo portfolio`, `yo pending-redeems`, `yo rewards`, `yo yo-rewards`, `yo user-perf`), listing vaults and history (`yo vaults`, `yo vault`, `yo history`, `yo prices`, `yo yield`, `yo tvl`, `yo share-price`, `yo perf`, `yo leaderboard`), self-describing the command surface for an agent (`yo schema`), setting up `YO_RPC_URL`, or piping output into jq or other tools. Do NOT use for React hooks (`@yo-protocol/react`) or TypeScript SDK code (`@yo-protocol/core`) — those have dedicated skills.
yo-base-mcp-plugin
Base MCP plugin for YO Protocol — ERC-4626 yield vaults with ERC-7540 async redemption on Ethereum (1), Base (8453), and Arbitrum (42161). Both deposit and withdraw route through the YO Gateway. Use when the user wants to view YO vaults, check positions/balances/rewards, deposit, request a redeem (instant or async), or claim Merkl rewards via Base MCP's `send_calls`. Triggers on YO Protocol, yoUSD, yoETH, yoBTC, yoEUR, yoGOLD, yoUSDT, "deposit into yo", "withdraw from yo", "yo vault", or "claim yo rewards".
risk-graph
Use Risk Graph's paid agent API (`/api/v1/agent/*`) — a DeFi risk-intelligence graph covering pools, assets, protocols, and chains, monetised via the [x402](https://x402.org) micropayment standard over USDC on Base mainnet (chain id `8453`). Every endpoint costs between $0.001 and $0.75 per call; the payer pays no gas — settlement is EIP-3009 `transferWithAuthorization` via the Coinbase CDP facilitator. Use whenever an agent needs structured, programmatic DeFi-risk data and is willing to pay per call: ranking pools by risk, comparing protocols, fetching chain-level risk signals, mapping dependency chains between pools/assets, extracting subgraphs around a node, explaining why a node is risky, or building an autonomous agent that consumes on-chain risk intelligence. Make sure to use this skill whenever the user mentions Risk Graph, risk-graph, DeFi risk score, pool risk, protocol risk, chain risk, asset risk, node risk explain, subgraph extraction, dependency chain, `/api/v1/agent/`, x402, paid agent API, USDC paywall, EIP-3009 paywall, Coinbase CDP facilitator, or building AI agents that consume on-chain risk intelligence — even if they don't explicitly name "Risk Graph". Triggers on mentions of Risk Graph, risk-graph API, DeFi risk scoring, x402 paywall, USDC micropayments on Base, agent-facing DeFi data, pool/protocol/asset/chain risk lookup, dependency-graph traversal, subgraph extraction, or paid `/api/v1/agent/*` endpoints.
yo-protocol-skills
Official Yo Protocol skills bundle (SDK, CLI, React)