flow-dev-setup

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),

Ir para a instalação

Repositório: onflow/flow-ai-tools
Última atividade na origem: 14 de abril de 2026 às 01:13
Idioma detectado do SKILL.md: inglês
Estrelas: 6
Forks: 2

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/onflow/flow-ai-tools --skill flow-dev-setup

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Explorador de arquivos

9 arquivos

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

cadence-lang

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 (including checks-effects-interactions, trust-boundary validation, and bounded loops), anti-patterns to avoid, proven design patterns, style and readability rules, and numeric precision with checked arithmetic. 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, optional binding, if let, guard let, force-unwrap, string templates, UFix128, Fix128, fixed-point precision, overflow, checks-effects-interactions, reentrancy, "how do I write cadence", "cadence error", "compile error in .cdc", "what does access(self) mean", "how do resources work",

2026-07-31

cadence-scaffold

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-07-31

cadence-testing

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-07-31

Ver todas deste repositório

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.

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.

flow-dev-setup

Informações da origem

Opções de instalação

Revise os arquivos de origem

Mais deste repositório

Mais deste repositório

Flow Dev Environment Setup

Tool Overview

Navigation Map

Typical Setup Order

Flow Dev Environment Setup

Tool Overview

Navigation Map

Typical Setup Order