Loading...
Loading...
Found 872 Skills
Interview user in-depth to create a detailed spec. Use when user wants to define requirements, spec out a feature, or needs help articulating product details.
9-section product specification template for defining software projects. Use when drafting a new spec.md, converting an idea into a structured specification, or reviewing spec completeness. Ensures consistent, comprehensive project definitions.
DeFi fundamentals and cross-chain analytics using DefiLlama-style data. Use when you want to find undervalued protocols, screen by TVL/revenue growth vs token price, compare sectors, or run data-driven crypto research beyond pure memes.
Use at the start of product strategy to define or refine desired outcomes and success metrics (e.g., for Opportunity Solution Trees or continuous discovery) before selecting opportunities or solutions.
Expert skill for integrating the hydric Gateway SDK (@hydric/gateway) in JavaScript and TypeScript. Use this skill to orchestrate multi-chain liquidity, resolve token identities, and build high-fidelity DeFi dashboards with institution-grade precision.
Expert skill for integrating the hydric Gateway API. Use this skill to search cross-chain liquidity, resolve multi-chain and single chain token identities, get token prices, and build high-fidelity DeFi dashboards.
Use to define schemas, topic tags, and lineage metadata for enriched signals.
Core guide for interacting with Euler Finance V2 protocol. This skill should be used when building DeFi integrations, managing lending positions, or understanding Euler architecture. Triggers on tasks involving lending, borrowing, collateral, liquidation, EVC, EVK, or core Euler operations. For specialized topics, see companion skills.
Master metrics definition, KPI tracking, dashboarding, A/B testing, and data-driven decision making. Use data to guide product decisions.
Guide for authoring comprehensive PRDs with parallel planning support. Use for drafting technical specifications, defining requirements, and synthesizing planner outputs. Use proactively when creating PRDs, architecture designs, or implementation plans. Examples: - user: "Draft a PRD for user auth" → create PRD with purpose, requirements, and scenarios - user: "Analyze these PRD requirements" → verify SHALL/MUST usage and scenario structure - user: "Synthesize planner outputs" → merge the strongest parts of multiple generated PRDs - user: "Create a PRD template" → setup standard sections and placeholder content
Generate Product Requirements Documents through structured discovery. 3 phases: Discovery interview, Analysis & Scoping, Technical Drafting. Use when: defining new products, planning features, documenting requirements. Triggers on "create PRD", "define product", "product requirements", "write PRD".
Electronics project architecture and constraint definition. Guides users through defining project requirements, power systems, interfaces, and physical constraints.