원클릭으로 Manus에서 모든 스킬 실행

flow-defi

스타5

포크1

업데이트2026년 4월 20일 18:57

Architecture guide for building DeFi protocols on the Flow blockchain. Covers Flow's DeFi-specific advantages (MEV-free EVM, cross-VM atomic transactions, on-chain automation), core DeFi primitives (lending health factors, interest rate kink models, AMM type selection), liquidity bootstrapping strategy (veFLOW, Merkl, CL ranges, bootstrapping benchmarks), and the current Flow DeFi ecosystem map (existing protocols, missing primitives, opportunity analysis). TRIGGER when: designing a lending protocol on Flow, choosing AMM type for a DEX, liquidity bootstrapping strategy, veFLOW mechanics, "how does Flow DeFi work", "AMM types on Flow", "liquidity bootstrapping", "Flow DeFi ecosystem", "cross-VM composability for DeFi", "health factors", "interest rate curves", "collateral design", "DEX TVL", "Merkl integration", "missing DeFi primitives on Flow", "perp DEX on Flow", "launchpad on Flow", "COA pattern", "MEV-free EVM". DO NOT TRIGGER when: designing token economics (use flow-tokenomics), asking about Cadence syn

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

onflow

onflow/flow-ai-tools

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Flow DeFi Architecture

Design and build DeFi protocols on Flow — covering architectural advantages, core primitives, liquidity strategy, and the ecosystem landscape.

Navigation Map

Task	Reference
Flow DeFi foundations: COAs, MEV-free EVM, cross-VM atomicity, on-chain automation	protocol-architecture.md
Core primitives: lending models, AMM type selection guide, risk framework	defi-primitives.md
Liquidity bootstrapping: veFLOW, Merkl, CL ranges, failure modes, benchmarks	liquidity-strategy.md
Ecosystem map: current state, missing primitives, opportunity analysis	ecosystem-map.md

Key Principles

MEV-free EVM — Flow's architecture prevents sandwich attacks on the EVM side; LP positions retain more yield
Cross-VM atomicity — A single Cadence transaction can call EVM contracts atomically (no bridges for Cadence↔EVM)
COA pattern — Cadence Owned Accounts bridge Cadence logic and EVM contracts within the same address space
On-chain automation — FlowTransactionScheduler (FLIP 330) enables recurring transactions without keeper bots
Lock-up or lose — Liquidity programs without lock-ups lose 60–80% TVL within 30 days

Companion Skills

flow-tokenomics — Use alongside when designing the token economics for your DeFi protocol (veFLOW-style governance token, fee distribution, etc.).
cadence-lang — Consult for Cadence language rules when implementing protocol contracts.
cadence-audit — Use to audit protocol contracts before deployment.

이 저장소의 다른 Skills

같은 저장소

flow-ecosystem

onflow/flow-ai-tools

Use when a developer is building, analyzing, or shipping on Flow (Cadence or Flow EVM) and needs an ecosystem tool: on-chain analytics, metrics, a query, or a dashboard (Dune); a Flow EVM RPC endpoint, node access, or reading chain state from an app (Alchemy); or swapping tokens, adding liquidity, getting a price quote, or integrating a DEX (PunchSwap / KittyPunch). Routes the builder to the right Flow ecosystem integration and supplies how to call it (MCP server, docs, or on-chain contract). Triggers on requests like "building on Flow and need a tool for X", "how do I get Flow on-chain data or a dashboard", "what should I use to query Flow", "Flow EVM RPC or node provider", "how do I swap or add liquidity on Flow", "integrate a DEX on Flow", or "is there a Flow tool for X". Not for non-Flow chains, and not for Cadence language correctness.

2026-06-235

cadence-lang

onflow/flow-ai-tools

Comprehensive guide for writing correct, secure, and idiomatic Cadence smart contract code on the Flow blockchain. Covers language fundamentals (resources, contracts, transactions, interfaces, accounts, references, imports), access control and entitlements, capabilities, pre/post conditions, security best practices, anti-patterns to avoid, and proven design patterns. TRIGGER when: writing or debugging Cadence code, asking about Cadence syntax, access(self), access(all), entitlements, resources, move operator (<-), capabilities, references, pre/post conditions, storage paths, "how do I write cadence", "cadence error", "compile error in .cdc", "what does access(self) mean", "how do resources work", "capability-based security". DO NOT TRIGGER when: building NFT/FT token contracts (use cadence-tokens), setting up flow.json or FCL (use flow-project-setup), reviewing existing code for vulnerabilities (use cadence-audit), generating new contracts from scratch (use cadence-scaffold).

2026-05-065

cadence-scaffold

onflow/flow-ai-tools

Generate production-ready Cadence smart contracts, transactions, and DeFi transactions from scratch following security-first standards. Scaffolds secure code with proper access control, entitlements, events, storage paths, and phase discipline. TRIGGER when: creating new Cadence contracts, generating transactions, scaffolding DeFi transactions, building smart contracts from scratch, "generate contract", "create transaction", "scaffold", "new contract", "new transaction", "build a contract for", "write me a contract", "help me create a", "template for", "boilerplate", "starter contract", "create an NFT contract", "generate a transfer transaction". DO NOT TRIGGER when: reviewing or auditing existing code (use cadence-audit), asking about Cadence syntax or language rules (use cadence-lang), configuring flow.json (use flow-project-setup).

2026-05-065

cadence-testing

onflow/flow-ai-tools

Guide for writing, running, and debugging unit tests for Cadence smart contracts using the built-in Cadence Testing Framework and `flow test`. Covers test file structure (_test.cdc, setup/beforeEach/tearDown), assertions and matchers, blockchain emulation (accounts, deployments, events, time manipulation), coverage reports, CI integration, and testing patterns. TRIGGER when: writing Cadence unit tests, debugging failing tests, using Test.assert / Test.expect / Test.assertEqual / Test.expectFailure, matchers (Test.equal, Test.beGreaterThan, etc.), Test.createAccount / Test.deployContract / Test.executeTransaction / Test.executeScript in tests, Test.moveTime, Test.eventsOfType in tests, Test.reset, `flow test`, `flow test --cover`, coverage reports, `_test.cdc`, "how do I test this contract", "test is flaky", "mock a capability in a test". DO NOT TRIGGER when: writing contract or transaction code itself (use cadence-lang), generating new contracts/transactions from scratch (use cadence-scaffold), auditing non-t

2026-04-235

cadence-audit

onflow/flow-ai-tools

Comprehensive audit and review skill for Cadence smart contracts on the Flow blockchain. Identifies security vulnerabilities, bugs, code quality issues, and optimization opportunities. Produces severity-rated findings (Critical/High/Medium/Low) with actionable fixes. TRIGGER when: auditing, reviewing, or improving Cadence code, checking for security issues, performing code review on .cdc files, looking for anti-patterns or vulnerabilities, optimizing smart contract code, "review cadence", "audit cadence", "check cadence security", "validate cadence contract", "review my .cdc file", "security review", "code review", "find vulnerabilities", "check this contract", "is this code secure", "audit my project". DO NOT TRIGGER when: writing new contracts from scratch (use cadence-scaffold), asking about Cadence syntax or patterns (use cadence-lang), building token contracts (use cadence-tokens).

2026-04-205

cadence-tokens

onflow/flow-ai-tools

Guide for developing NFT and Fungible Token contracts on the Flow blockchain using Cadence. Covers NonFungibleToken and FungibleToken interface conformance, MetadataViews integration for marketplace compatibility, collection patterns, minting, standard paths, event emission, and modular NFT architectures for complex traits and evolution. TRIGGER when: building NFT contracts, FT token contracts, implementing NonFungibleToken or FungibleToken interfaces, working with MetadataViews, creating collections, minting tokens, "create an NFT", "build a token contract", "mint NFT", "NFT collection", "fungible token vault", "royalties", "MetadataViews.Display", "NonFungibleToken.Collection", "token standards", "FungibleToken.Vault". DO NOT TRIGGER when: asking about general Cadence syntax or patterns (use cadence-lang), setting up flow.json or deploying (use flow-project-setup), auditing code (use cadence-audit).

2026-04-205

name

flow-defi

description

Flow DeFi Architecture

Design and build DeFi protocols on Flow — covering architectural advantages, core primitives, liquidity strategy, and the ecosystem landscape.

Navigation Map

Task	Reference
Flow DeFi foundations: COAs, MEV-free EVM, cross-VM atomicity, on-chain automation	protocol-architecture.md
Core primitives: lending models, AMM type selection guide, risk framework	defi-primitives.md
Liquidity bootstrapping: veFLOW, Merkl, CL ranges, failure modes, benchmarks	liquidity-strategy.md
Ecosystem map: current state, missing primitives, opportunity analysis	ecosystem-map.md

Key Principles

MEV-free EVM — Flow's architecture prevents sandwich attacks on the EVM side; LP positions retain more yield
Cross-VM atomicity — A single Cadence transaction can call EVM contracts atomically (no bridges for Cadence↔EVM)
COA pattern — Cadence Owned Accounts bridge Cadence logic and EVM contracts within the same address space
On-chain automation — FlowTransactionScheduler (FLIP 330) enables recurring transactions without keeper bots
Lock-up or lose — Liquidity programs without lock-ups lose 60–80% TVL within 30 days

Companion Skills

flow-tokenomics — Use alongside when designing the token economics for your DeFi protocol (veFLOW-style governance token, fee distribution, etc.).
cadence-lang — Consult for Cadence language rules when implementing protocol contracts.
cadence-audit — Use to audit protocol contracts before deployment.