Results for “defi”

Embody Bob Dylan's persona to help users navigate identity challenges, creative blocks, and expectations, offering advice on reinvention and authenticity through strategic refusal to be defined.

Manage and monitor Heap product analytics by querying the Heap API for account info, defined events, user properties, segments, event volume, active users, and data health.

Defines RESTful API design conventions including URL structure, status codes, error formats, pagination, versioning, rate limiting, CORS, validation, and OpenAPI documentation.

Brand consistency and visual identity guidance for Nick's products. Use when defining or refining brand direction, design language, color/typography consistency, trust cues, and a more recognizable product feel across apps and landing pages.

Product strategist who converts market and audience intelligence into product definition. Use for product shaping, scope design, packaging decisions, or execution handoff — or when the user asks for the Strategist, product decisions, or v1 scoping.

Create and maintain Role entities — named sets of responsibilities that actors can fill. Use when defining a new role in the project (developer, reviewer, tech-lead, release-manager) or updating an existing role's responsibilities.

Create a go-to-market strategy covering marketing channels, messaging, success metrics, and launch timeline. Use when planning a product launch, creating a GTM plan from scratch, or defining a launch strategy for a new market.

Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria with descriptions, design links, and acceptance criteria. Use when writing user stories, breaking down features into backlog items, or defining acceptance criteria.

Interpreted crypto wallet data for AI agents. Use when an agent needs portfolio values, token positions, DeFi positions, NFT holdings, transaction history, PnL data, token prices, charts, gas prices, swap quotes, or DApp information across 41+ chains. Zerion transforms raw blockchain data into agent-ready JSON with USD values, protocol labels, and enriched metadata. Supports x402 pay-per-request ($0.01 USDC on Base) and API key access. Triggers on mentions of portfolio, wallet analysis, positions, transactions, PnL, profit/loss, DeFi, token balances, NFTs, swap quotes, gas prices, or Zerion.

Build qualified prospect lists for B2B SaaS, general B2B, or local small businesses by defining an ICP, sourcing candidates, qualifying with evidence, scoring, and outputting a lead sheet.

Build, scaffold, and deploy Power Automate cloud flows programmatically via the FlowStudio MCP server, including constructing flow definitions, wiring connections, deploying, and testing.

Plan Uniswap swaps and liquidity positions then execute via deep links — verify tokens on-chain, research market conditions, and generate pre-filled Uniswap interface URLs across 12 chains.

Scans top 24-hour token movers across major chains via GeckoTerminal, applies pump-risk filters, and outputs a chain leaderboard with per-chain top 5 runners.

Monitors EVM blockchain addresses and contracts for large transfers, new approvals, contract upgrades, unusual gas spends, MEV interactions, and first-time interactions with new contracts.

Defines service level objectives, creates error budget policies, designs incident response procedures, develops capacity models, and produces monitoring configurations and automation scripts for production systems.

Rebuild existing site pages with byte-faithful content on a separately-defined donor design system, preserving text, images, and metadata while applying a new visual design.

Ensures scene-to-scene transitions composite correctly on the master timeline by defining render prerequisites, including the white-flash guard and how the injector overlaps wrappers.

Defines brand voice, visual identity, messaging frameworks, and asset management, with scripts to sync guidelines to design tokens and validate assets.

Structures a Request for Comments (RFC) document for proposing significant technical changes that require cross-team input and approval, guiding authors through problem definition, proposed solution, alternatives analysis, and rollout planning.

Build production AI agents with Agno (formerly Phidata) — define Agent with model/tools/instructions/memory/knowledge, compose Agent Teams with coordinator routing, add Storage for persistence, and integrate RAG via built-in KnowledgeBase with PDF/URL/text sources.

Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.

Use when building, refactoring, or documenting Graft apps and proxies, including when asked to create a tool server, API server, dual-protocol server, or MCP-HTTP bridge. Graft's core thesis: define tools once and serve them as both HTTP REST endpoints and MCP tools from the same server, with discovery, docs, and OpenAPI generated automatically. Covers concrete actions such as defining tools and handlers, configuring authentication middleware, setting up HTTP and stdio transports, generating OpenAPI documentation, wrapping existing APIs via proxy mode, and wiring up the full CLI workflow.

Generates a bespoke brand identity for a new project through a short interview, then writes it as a DESIGN.md file (Google Stitch format) in that project's own repo. Use when starting a new project and its visual identity isn't defined yet, when asked "what's the brand for X", "define the brand for this project", "new project design system", or before the first UI work on a fresh project. Do NOT use this to restyle or elevate a project that already has an identity — that's `taste-redesign`.

Defines a vibrant claymation-meets-data design system for Clay.com, including color palette, typography, layout, and elevation tokens for GTM-data interfaces.

Defines a test strategy for Salesforce Flow, combining declarative Flow Tests, debug runs, path matrices, test data, and boundary tests for Apex, LWC, and external services.

Implements sibling communication between Lightning Web Components using Lightning Message Service (LMS) or the legacy pubsub utility, covering message channel definition, publish/subscribe patterns, and scope selection.

Audits Claude Code configuration files for security vulnerabilities, misconfigurations, and injection risks using AgentShield, covering CLAUDE.md, settings.json, MCP servers, hooks, and agent definitions.

Define every visual attribute as structured VGL JSON for deterministic, reproducible image generation with Bria FIBO models, covering objects, lighting, camera settings, composition, and style.

Guides developers through adding new RPC commands to Wave Terminal, covering interface definitions, type conventions, code generation, and implementation across server, Electron, frontend, remote, and terminal components.

Plans and executes disaster recovery and business continuity for critical services, covering RPO/RTO definitions, backup strategies, failover procedures, and DR testing with executable scripts.

Use to finalize Cell Press display items — column-width sizing, minimum fonts, RGB, show-the-data with defined error bars/n/replicate type, scale bars, colorblind-safe palettes, multi-panel discipline, stand-alone legends, and image integrity.

Use when driving a feature prompt to a production-ready PR through discovery, definition, design, spec, issues, and dev phases, or when the user runs /feature or /feature resume — orchestrates the A-Team agentic pipeline over a target repo.

Manage Gate entities — validation checkpoints that WorkItems, scopes, or policy applications must pass (code review, security scan, tests). Use when defining or updating a checkpoint for v2 workflow surfaces — code review, tests green, security scan, stakeholder approval.

Plan backend domains, services, jobs, integrations, and failure handling for a product or major feature. Use when UX and product scope are defined and the team needs a production-minded backend design without defaulting to premature microservices.

Define, deploy, and manage cloud infrastructure as code using tools like Terraform, Pulumi, CloudFormation, and CDK, ensuring consistency, repeatability, and version control. Use when the user requests infrastructure as code or provides relevant inputs for this workflow.

Custom board bringup for Zephyr RTOS using Hardware Model v2 (HWMv2). Covers directory structure, board.yml metadata, core configuration files (Kconfig, defconfig, CMake), and revision management. Trigger when creating new board definitions or porting Zephyr to custom hardware.