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

flow-dev-setup

스타5

포크1

업데이트2026년 4월 14일 01:13

Guide for setting up a local Flow blockchain development environment from scratch. Covers installing and configuring the Flow CLI, emulator, Cadence MCP server, dev wallet, Cadence VS Code extension, testing framework, frontend SDKs (FCL/React), and EVM tooling (Hardhat/Foundry). Each tool has its own reference with self-contained install and setup instructions. TRIGGER when: setting up Flow development tools, installing Flow CLI, starting emulator for the first time, "how do I install flow", "set up my dev environment", "flow dev setup", "install flow-cli", "cadence extension", "set up emulator", "flow testing setup", "FCL install", "EVM on Flow", "Hardhat with Flow", "Foundry with Flow", "new to Flow development", "getting started with Flow", "cadence MCP", "set up MCP for Cadence", "flow mcp". DO NOT TRIGGER when: configuring flow.json or deployments (use flow-project-setup), writing Cadence code (use cadence-lang), querying on-chain data (use flow-cli-query), building token contracts (use cadence-tokens),

설치

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

Manus에서 실행

출처

onflow

onflow/flow-ai-tools

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

다운로드

Manus에서 실행

Flow Dev Environment Setup

Install and configure the tools needed for Flow blockchain development. Each reference below is self-contained — read only the ones relevant to your task.

Tool Overview

Tool	Purpose	Required?
Flow CLI	Core tool — project init, contract deploy, transactions, testing, emulator	Yes — everything depends on this
Flow Emulator	Local Flow blockchain for development (bundled with CLI)	Yes — for local development
Cadence VS Code Extension	Syntax highlighting, code completion, type checking for `.cdc` files	Recommended for VS Code users
Flow Testing Framework	Cadence-native tests with coverage and fork testing	Yes — for writing/running tests
Flow Dev Wallet	Mock FCL-compatible wallet for local frontend auth testing	Only for frontend development
FCL / React SDK	Frontend libraries for wallet auth, transactions, and queries	Only for frontend development
Cadence MCP Server	MCP server giving AI agents Cadence type checking, code review, and on-chain queries	Recommended for AI-assisted development
EVM Tooling	Hardhat, Foundry, or Remix for Solidity development on Flow	Only for EVM/Solidity development

Navigation Map

Task	Reference
Install Flow CLI (brew, script, Windows), verify, upgrade	flow-cli.md
Start and configure the Flow Emulator (ports, persistence, fork mode)	emulator.md
Install Cadence VS Code extension for editor support	vscode-extension.md
Set up testing framework, run tests, coverage, fork testing	testing.md
Set up dev wallet for local frontend auth testing	dev-wallet.md
Install FCL or React SDK for frontend integration	frontend-sdk.md
Set up Cadence MCP server for AI-assisted development	cadence-mcp.md
Set up Hardhat, Foundry, or Remix for Solidity on Flow EVM	evm-tooling.md

Typical Setup Order

For most Cadence projects: Flow CLI → Emulator → VS Code Extension → Cadence MCP → Testing.

Add Dev Wallet + Frontend SDK when building a frontend. Add EVM Tooling only for Solidity work.

이 저장소의 다른 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-dev-setup

description

Flow Dev Environment Setup

Install and configure the tools needed for Flow blockchain development. Each reference below is self-contained — read only the ones relevant to your task.

Tool Overview

Tool	Purpose	Required?
Flow CLI	Core tool — project init, contract deploy, transactions, testing, emulator	Yes — everything depends on this
Flow Emulator	Local Flow blockchain for development (bundled with CLI)	Yes — for local development
Cadence VS Code Extension	Syntax highlighting, code completion, type checking for `.cdc` files	Recommended for VS Code users
Flow Testing Framework	Cadence-native tests with coverage and fork testing	Yes — for writing/running tests
Flow Dev Wallet	Mock FCL-compatible wallet for local frontend auth testing	Only for frontend development
FCL / React SDK	Frontend libraries for wallet auth, transactions, and queries	Only for frontend development
Cadence MCP Server	MCP server giving AI agents Cadence type checking, code review, and on-chain queries	Recommended for AI-assisted development
EVM Tooling	Hardhat, Foundry, or Remix for Solidity development on Flow	Only for EVM/Solidity development

Navigation Map

Task	Reference
Install Flow CLI (brew, script, Windows), verify, upgrade	flow-cli.md
Start and configure the Flow Emulator (ports, persistence, fork mode)	emulator.md
Install Cadence VS Code extension for editor support	vscode-extension.md
Set up testing framework, run tests, coverage, fork testing	testing.md
Set up dev wallet for local frontend auth testing	dev-wallet.md
Install FCL or React SDK for frontend integration	frontend-sdk.md
Set up Cadence MCP server for AI-assisted development	cadence-mcp.md
Set up Hardhat, Foundry, or Remix for Solidity on Flow EVM	evm-tooling.md

Typical Setup Order

For most Cadence projects: Flow CLI → Emulator → VS Code Extension → Cadence MCP → Testing.

Add Dev Wallet + Frontend SDK when building a frontend. Add EVM Tooling only for Solidity work.