「defi」の検索結果

OKX-aggregated DeFi (no specific DApp named) — product discovery, deposit/withdraw/claim execution, AND positions viewing. **If the user names ANY third-party protocol/DApp (Aave, Lido, PancakeSwap, Uniswap, Curve, Compound, Morpho, Pendle, Kamino, Raydium, Hyperliquid, Polymarket, …), route to okx-dapp-discovery — NOT here, even for 'show my Aave positions'.** INVEST triggers: 'invest in DeFi', 'earn yield', 'find best APY', 'deposit/stake for yield', 'search DeFi products', 'redeem/withdraw position', 'claim DeFi rewards', 'borrow against asset', 'repay loan', 'add/remove CLMM liquidity', 'APY/TVL history', 'depth chart', yield farming, lending, staking, liquidity pools. PORTFOLIO triggers: 'check my DeFi positions', 'view DeFi holdings/portfolio', 'my staking/lending positions', 'DeFi balance', 'DeFi 持仓', '我的DeFi资产'. Do NOT use for: DEX swaps (okx-agentic-wallet), token prices (okx-dex-market), wallet token balances (okx-agentic-wallet).

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user mentions connect/disconnect wallet, sign in, sign out, web3 wallet, wallet address, check balance, how much crypto do I have, send BNB/USDT/crypto, transfer tokens, swap tokens, buy/sell token, DEX trade, limit order, market order, cancel order, get a quote, transaction history, wallet settings, daily limit, slippage, MEV protection, supported chains, available networks, prediction market, predict.fun, YES/NO market, place a prediction, redeem winnings, claim payout, prediction portfolio, prediction PnL, x402 payment, HTTP 402 Payment Required, pay a known x402 API, check approvals, view token approvals, revoke approval, manage approvals, wallet approvals, authorization management, token authorization, DeFi protocols, DeFi position, DeFi portfolio, staking, liquidity pool, LP, yield farming, health factor, APY, TVL, DeFi investment, DeFi deposit, DeFi redeem, DeFi stake, DeFi unstake, add liquidity, remove liquidity, claim rewards, claim fees, or any on-chain wallet operation.

日本語の概要は準備中です。原文の説明を表示しています。

加密链上交易 (加密 / 链上交易 (Crypto & On-chain Trading) — 以加密资产为标的、强调链上活动的主动交易认知操作系统：从「看叙事/选赛道 → 找标的 → 链上尽调与风控 → 选场所(DEX/CEX/链上合约) → 建仓与仓位管理 → 监控链上流向与情绪 → 退出与复盘」的完整决策链。覆盖 (a) 第一性张力 — **链上 on-chain (DEX 现货/AMM、钱包追踪 wallet tracking、资金流向 flow、MEV、memecoin、链上衍生品 Hyperliquid/GMX、自托管 self-custody, 'not your keys not your coins') ⇄ 链下 CEX (中心化交易所现货/合约 Binance/OKX/Bybit、订单簿、托管、出入金法币)**; **合约/杠杆/衍生品 (perps 永续、资金费率 funding、清算 liquidation、爆仓、做多做空、高频/择时) ⇄ 现货/价值/长持 (spot、HODL、定投 DCA、基本面/估值、'time in market > timing the market')**; **价值/基本面派 (协议收入、TVL、代币经济学 tokenomics、真实使用、估值模型) ⇄ meme/叙事/情绪派 (memecoin、narrative rotation 叙事轮动、attention is the asset、纯博弈/PvP、Ponzinomics)**; **链上数据/量化/客观 (on-chain analytics, Nansen/Arkham/Dune、聪明钱 smart money、链上指标、系统化/机械化) ⇄ 直觉/盘感/叙事阅读 (narrative、KOL alpha、社群情绪、tape reading)**; **自托管/去中心化/抗审查 (DeFi、自托管钱包、抗审查、'be your own bank') ⇄ 便利/合规/中心化 (CEX、合规出入金、KYC、托管、ETF)**; **主动交易/择时/高换手 (trading、波段、合约、撸毛/空投 airdrop farming、套利 arbitrage) ⇄ 被动配置/低换手 (配置 BTC/ETH、ETF、长期叙事 beta)**; (b) 核心工作流 / pipeline (最标准、最易蒸高质量 + CLI 化) — 通用链: 叙事/赛道判断 (宏观周期/减半/流动性/板块轮动) → 标的发现 (链上扫链/聪明钱跟单/新币/叙事映射) → 尽调 due diligence (代币经济学/解锁 unlock/团队/合约审计/honeypot 检测/流动性与持仓分布) → 风控前置 (仓位 sizing/最大回撤/止损/相关性) → 场所与执行 (CEX vs DEX、滑点/MEV/gas、限价 vs 市价、TWAP) → 持仓监控 (链上流向/巨鲸/资金费率/解锁日历/情绪指标) → 退出与复盘 (止盈分批/再平衡/记录交易日志); 子流派 SOP: 链上 degen 打新与 memecoin 流程、合约交易者的资金费率与清算地图、空投/撸毛 farming、套利与 MEV、被动配置与定投; (c) 工具栈 — 链上分析 (Nansen 聪明钱/Arkham 实体标注/Dune 自建仪表盘/Dexscreener & DEX Screener 新币/GMGN & Photon & BullX memecoin 终端/Etherscan & Solscan 区块浏览器/DeBank 钱包总览/Token Terminal 协议基本面/DefiLlama TVL/Glassnode & CryptoQuant 链上指标)、交易场所 (CEX: Binance/OKX/Bybit/Coinbase; 链上现货 DEX: Uniswap/Jupiter/Raydium/Aerodrome; 链上衍生品: Hyperliquid/GMX/dYdX)、钱包与安全 (MetaMask/Rabby/Phantom 热钱包、Ledger/Trezor 硬件冷钱包、Revoke.cash 授权管理、honeypot/合约扫描)、行情与图表 (TradingView、CoinGecko/CoinMarketCap)、信息与聚合 (Twitter/X、Telegram、DeFiLlama、RootData/ICO 日历、解锁日历 Token Unlocks)、自动化 (交易机器人、链上 bot/sniper、Telegram trading bot); (d) 知识正典 — 注意加密交易 canon 偏少且新: 通用交易/风控经典 (Edwin Lefèvre 'Reminiscences of a Stock Operator'、Van Tharp 'Trade Your Way to Financial Freedom' 仓位管理、Mark Douglas 'Trading in the Zone' 交易心理、Michael Mauboussin、Nassim Taleb 'Fooled by Randomness/Antifragile')、加密原生 (Bitcoin whitepaper 中本聪、'The Bitcoin Standard' Saifedean、Vitalik 博客与 Ethereum whitepaper、'DeFi and the Future of Finance'、Lyn Alden 宏观、a16z crypto 文章、Messari/Delphi/Bankless 研报)、链上分析方法 (Glassnode/CryptoQuant 教程、Nansen/Arkham/Dune 文档、Dune Analytics SQL)、交易方法论散见于 podcast/Substack/Twitter thread 而非书; (e) figures/流派 — 价值/基本面派 (Vitalik Buterin 以太坊、Hasu/Su Zhu(争议)、Arthur Hayes BitMEX 创始人/宏观+衍生品、Raoul Pal、Lyn Alden 宏观、Cobie/Jordan Fish UpOnly podcast、DeFi 研究 Bankless Ryan Adams/David Hoffman); 链上分析派 (Nansen Alex Svanevik、Arkham、Adam Cochran、Ansem(blknoiz06) 链上交易、Murad memecoin supercycle、链上侦探 ZachXBT 反诈); 合约/衍生品派 (Arthur Hayes、GCR(GiganticRebirth) 传奇合约、Pentoshi、CryptoCred 技术分析、Tyler Durden); meme/叙事派 (Ansem、Murad、Cobie、各 Solana memecoin KOL); 宏观/周期派 (Raoul Pal、Lyn Alden、PlanB stock-to-flow(争议)、Benjamin Cowen 数据/周期); 量化/系统化 (各匿名量化、Hyperliquid 生态); 中文圈 (链上分析/合约 KOL、币圈大 V、播客如 '无人之境'/'Web3 佛学院'、研究机构如 Foresight/PANews/律动 BlockBeats); 反诈/安全 (ZachXBT、SlowMist 慢雾、go+ 安全); (f) 行业话术/黑话 — 现货 spot / 合约 perps 永续 / 杠杆 leverage / 多空 long-short / 爆仓 liquidation 清算 / 资金费率 funding rate / 开多开空 / 止损 SL 止盈 TP / 仓位 position sizing / 满仓梭哈 ape in / 梭 / FOMO / FUD / 钻石手 diamond hands / 纸手 paper hands / 韭菜 / 镰刀 / 庄 / 出货 / 拉盘砸盘 / 插针 wick / 针 / 上车下车 / 埋伏 / 潜伏 / 链上 on-chain / 钱包 wallet / 地址 / 聪明钱 smart money / 巨鲸 whale / 跟单 copy-trade / 老鼠仓 / 貔貅盘 honeypot / 貔貅 / rug 跑路 rug-pull / 归零 / 土狗 (memecoin/小币) / 金狗 (暴涨百倍) / meme 币 / 叙事 narrative / 赛道 / 板块轮动 / 撸毛 撸空投 airdrop / 女巫 sybil / 交互 / 解锁 unlock / 砸盘解锁 / 代币经济学 tomomics / TVL / APY APR / 无常损失 IL / 滑点 slippage / MEV / 三明治 sandwich / gas / 抢跑 frontrun / 貔貅检测 / 授权 approve / 撤销授权 revoke / 私钥 助记词 seed phrase / 冷钱包 热钱包 / 自托管 / 减半 halving / 牛熊 / 山寨季 altseason / 比特币市占率 BTC.D / 山寨 alt / 主流币 / DeFi 暑期 / GM / WAGMI / NGMI / 归零归零 / PvP / Ponzi 庞氏; (g) 争议/批

日本語の概要は準備中です。原文の説明を表示しています。

工程ごとの完了判定、品質ゲート、証跡、標準検証コマンド、例外運用を設計するスキル。 実装完了・テスト実施・品質確認完了・出荷可能を分離し、再利用可能な gate matrix を作る。 「全OK」「完了」などの曖昧な完了表現を排除し、証跡に基づく退出条件を定義する。 Use when defining Definition of Done, quality gates, exit criteria, release readiness gates, evidence requirements, exception handling, or standardized verification commands. Covers: definition of done, quality gate, exit criteria, release readiness, 完了判定, 品質ゲート. Distinct from project-completeness-scorer (which scores) -- this skill designs the gates and criteria themselves.

Builds a DRAFT data dictionary from a schema export, table definition, sample rows or a partial existing dictionary: one row per field with the name as stated, type as stated or observed, meaning quoted from the documentation supplied, owner, allowed values, and UNKNOWN wherever no source defines the field, plus a gap list for the data owner. Never infers a definition from a column name. Use when the user asks to "build a data dictionary for this table", "document these columns", "what does each field mean", "turn this schema export into a dictionary" or "fill in the field definitions from these documents". Do not use for profiling values or finding patterns in the data, use dataset-insight-pack instead; for metric definitions, use kpi-definition-sheet; for logging data defects, use data-quality-issue-log. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Build and deploy full-stack web and mobile apps with AWS Amplify Gen2 (TypeScript code-first). Covers auth (Cognito), data (AppSync/DynamoDB), storage (S3), functions, APIs, and AI (Amplify AI Kit with Bedrock). Supports React, Next.js, Vue, Angular, React Native, Flutter, Swift, and Android. Always use this skill for Amplify Gen2 topics — even for questions you think you know — it contains validated, version-specific patterns that prevent common mistakes. TRIGGER when: user mentions Amplify Gen2; project has amplify/ directory or amplify_outputs; code imports @aws-amplify packages; user asks about defineBackend, defineAuth, defineData, defineStorage, defineFunction, or npx ampx. SKIP: Amplify Gen1 (amplify CLI v6), standalone SAM/CDK without Amplify (use aws-serverless), direct Bedrock without Amplify AI Kit (use bedrock).

日本語の概要は準備中です。原文の説明を表示しています。

Facilitate a structured conversation to define requirement standards for a project — epic and feature definitions, scenario structure, AC format, priority notation, status workflow, and naming conventions. Produces a formal requirement-standards.md that the requirement-quality atom reads via config resolution, customising its embedded defaults for the team's product process. Use when setting up a new project, defining product standards, or when the user says 'set up requirement standards', 'define feature standards', 'configure requirement forge', 'define how features should be structured', or 'requirement forge refiner'.

日本語の概要は準備中です。原文の説明を表示しています。

Facilitate a structured conversation to define architecture principles for a repository. Supports multiple architecture styles: clean architecture (default), hexagonal / ports & adapters, modular monolith, or custom. Produces a formal architecture document that the corresponding atom will use. Use when setting up a new project, defining architecture standards, or when the user says 'setup architecture', 'define layers', 'architecture principles', 'help me define my architecture', 'hexagonal architecture', 'modular monolith', 'ports and adapters', or 'define my architecture style'.

日本語の概要は準備中です。原文の説明を表示しています。

Map user missions from trigger to value moment, organizing features into coherent paths during PRD v0.4 User Journeys. Triggers on requests to map user journeys, define user flows, describe how users accomplish goals, or when user asks "map user journeys", "define user flows", "user missions", "how do users accomplish X?", "journey mapping", "what steps do users take?", "pain to value flow". Consumes PER- (Persona Definition), FEA- (Feature Value Planning), KPI- (Outcome Definition). Outputs UJ- entries with step flows, pain points, and value moments. Feeds v0.4 Screen Flow Definition.

日本語の概要は準備中です。原文の説明を表示しています。

Turns a list of KPIs or metrics into a DRAFT definition sheet: one row per KPI with the name as stated, formula quoted from a source, source system, owner, refresh cadence, unit, filters and known caveats, with UNKNOWN in every cell no source fills and a gap list grouped by data owner. Never composes a formula, sets a target or names an owner the sources do not state. Use when the user asks to "define these KPIs", "build a metrics definition sheet", "document how each KPI is calculated", "which of our KPIs have no owner or formula" or "reconcile the two KPI lists". Do not use for the weekly numbers report, use kpi-weekly-report-writer instead; for field-level definitions of a table, use data-dictionary-builder; for logging a wrong figure as a defect, use data-quality-issue-log. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Interactive guide for integrating new DeFi modules or protocols into OneKey. Use when adding new DeFi features like staking protocols, lending markets, or entirely new DeFi modules. Triggers on DeFi, protocol, integration, Earn, Borrow, staking, lending, supply, borrow, withdraw, repay, claim, new module, Pendle, Aave, Compound.

日本語の概要は準備中です。原文の説明を表示しています。

AIによる開発の成功条件を実装前に定義し、コード・ルール・モデル・人の評価で新機能と既存機能を確認しながら、複数回の試行から信頼性を記録するスキル。

• AI実装前に成功条件を決めたいとき
• プロンプトやエージェント変更後の回帰確認
• 複数回の試行で信頼性を測りたいとき

AIエージェントが使うツールの種類や入出力、エラーからの復帰手順を設計・見直します。文脈の情報量も整理し、作業完了率や再試行回数で改善を評価します。

• エージェントのツールや入力形式の設計
• ツールの結果と次の行動を明確にしたいとき
• 安全な再試行と停止条件を定めたいとき

Build, scaffold, and deploy Power Automate cloud flows using the FlowStudio MCP server. Your agent constructs flow definitions, wires connections, deploys, and tests — all via MCP without opening the portal. Load this skill when asked to: create a flow, build a new flow, deploy a flow definition, scaffold a Power Automate workflow, construct a flow JSON, update an existing flow's actions, patch a flow definition, add actions to a flow, wire up connections, or generate a workflow definition from scratch. Requires a FlowStudio MCP subscription — see https://mcp.flowstudio.app

日本語の概要は準備中です。原文の説明を表示しています。

Multi-AI requirements scoping using available external providers (Double Diamond Define phase). Priority triggers: octo define, octo scope, co-define, co-scope. DO NOT use for implementation, research, review/validation, or built-in commands.

日本語の概要は準備中です。原文の説明を表示しています。

Use when asked to compare two annual reports, put two companies from the same sector side by side, or check whether two companies' adjusted numbers mean the same thing. Takes two uploaded annual reports from one sector and compares them on five ratios computed with identical definitions from audited figures, flagging every place the companies define a metric differently. Produces a page-referenced comparison table, a definitions-differ section (adjusted vs statutory, inside vs outside the audited statements), and three questions to ask before believing either company's highlights. Educational, not financial advice.

日本語の概要は準備中です。原文の説明を表示しています。

Build and deploy full-stack web and mobile apps with AWS Amplify Gen2 (TypeScript code-first). Covers auth (Cognito), data (AppSync/DynamoDB including schema modeling, enum types, relationships, authorization rules), storage (S3), functions, APIs, and AI (Amplify AI Kit with Bedrock). Supports React, Next.js, Vue, Angular, React Native, Flutter, Swift, and Android. Always use this skill for Amplify Gen2 topics — even for questions you think you know — it contains validated, version-specific patterns that prevent common mistakes. TRIGGER when: user mentions Amplify Gen2; project has amplify/ directory or amplify_outputs; code imports @aws-amplify packages; user asks about defineBackend, defineAuth, defineData, defineStorage, or npx ampx. SKIP: Amplify Gen1 (amplify CLI v6), standalone SAM/CDK without Amplify (use aws-serverless), direct Bedrock without Amplify AI Kit (use bedrock).

日本語の概要は準備中です。原文の説明を表示しています。

Guides the creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories. Use when the user wants to create an agile epic, define large bodies of work, break down features into user stories, or document strategic initiatives. This should trigger for requests such as Create an agile epic; Write an epic; I need to create an epic; Define an epic; Epic definition. Part of Plinth Toolkit

日本語の概要は準備中です。原文の説明を表示しています。

Define database models with clear naming, appropriate data types, constraints, relationships, and validation at multiple layers. Use this skill when creating or modifying database model files, ORM classes, schema definitions, or data model relationships. Apply when working with model files (e.g., models.py, models/, ActiveRecord classes, Prisma schema, Sequelize models), defining table structures, setting up foreign keys and relationships, configuring cascade behaviors, implementing model validations, adding timestamps, or working with database constraints (NOT NULL, UNIQUE, foreign keys). Use for any task involving data integrity enforcement, relationship definitions, or model-level data validation.

日本語の概要は準備中です。原文の説明を表示しています。

Facilitate a structured conversation to define clean code principles for a repository. Produces a formal clean-code.md document that the clean-code atom will use as its override. Use when setting up coding standards, defining code quality rules, or when the user says 'setup clean code', 'define coding standards', 'code quality principles', 'coding guidelines', or 'help me define my code standards'.

日本語の概要は準備中です。原文の説明を表示しています。

Facilitate a structured conversation to define DDD guardrails for domain design within a repository. Produces a formal ddd-principles.md document that the domain-driven-design atom will use as its override. Use when setting up domain design principles, defining aggregate rules, or when the user says 'setup DDD', 'define domain rules', 'DDD principles', or 'help me define my domain patterns'.

日本語の概要は準備中です。原文の説明を表示しています。

Connect user journeys to screens, defining the UI structure and navigation paths during PRD v0.4 User Journeys. Triggers on requests to define screens, design screen flows, map UI structure, plan navigation, or when user asks "what screens do we need?", "define screens", "screen flow", "UI structure", "information architecture", "navigation design", "wireframe planning". Consumes UJ- (User Journey Mapping), FEA- (Feature Value Planning), BR- (constraints). Outputs SCR- entries for screens and DES- entries for design system elements. Feeds v0.5 Red Team Review.

日本語の概要は準備中です。原文の説明を表示しています。

Define measurable success metrics (KPIs) tied to product type during PRD v0.3 Commercial Model. Triggers on requests to define success metrics, set KPI targets, determine what to measure, establish go/no-go thresholds, or when user asks "how do we measure success?", "what metrics matter?", "what's our target?", "how do we know if this works?", "define KPIs", "success criteria". Consumes Product Type Classification (BR-) from v0.2. Outputs KPI- entries with thresholds, evidence sources, and downstream gate linkages.

日本語の概要は準備中です。原文の説明を表示しています。

DeFi protocol specialist for AMMs, lending protocols, yield strategies, and economic securityUse when "defi, amm, liquidity pool, lending protocol, yield farming, oracle, liquidation, tokenomics, tvl, impermanent loss, defi, amm, lending, yield, liquidity, oracle, tokenomics, protocol, ethereum, web3" mentioned.

日本語の概要は準備中です。原文の説明を表示しています。