Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

flow-project-setup

Sterne5

Forks1

Aktualisiert20. April 2026 um 18:57

Guide for setting up and configuring Flow blockchain projects. Covers flow.json structure (networks, accounts, contracts, dependencies, deployments), FCL frontend integration with React, Flow CLI workflow, emulator setup, testnet/mainnet deployment, environment-based configuration, and multi-network strategies. TRIGGER when: setting up a Flow project, configuring flow.json, setting up FCL, deploying contracts, switching networks, debugging deployment issues, "flow init", "flow emulator", "flow project deploy", "flow.json", "FCL config", "testnet deploy", "mainnet deploy", "contract deployment", "network configuration", "flow dependencies install", "emulator setup", "how to deploy to testnet", "configure FCL with React". DO NOT TRIGGER when: writing Cadence code or asking about syntax (use cadence-lang), building token contracts (use cadence-tokens), generating new contracts (use cadence-scaffold), auditing code (use cadence-audit).

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

onflow

onflow/flow-ai-tools

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

Datei-Explorer

3 Dateien

SKILL.md

readonly

name

flow-project-setup

description

Flow Project Setup

Configure and deploy Flow projects across emulator, testnet, and mainnet.

Quick Start

flow init              # Initialize project
flow emulator          # Start emulator
flow project deploy    # Deploy contracts
flow test              # Run tests

Navigation Map

Task	Reference
flow.json, FCL config, contract addresses, dependencies, CLI commands	configuration.md
Dev workflow, deployment, debugging, gas optimization, testnet validation	workflow.md

Companion Skills

cadence-lang — Consult for Cadence language rules when debugging contract compilation errors or transaction failures. Understanding access control and resource handling is essential for diagnosing deployment issues.
flow-cli — Consult for detailed CLI command syntax, flags, and account management operations used during the development workflow.
flow-react-sdk — Consult when integrating the deployed project with a React frontend via FCL.
cadence-audit — Run an audit before deploying to testnet/mainnet as part of the validation checklist.

Mehr aus diesem Repository

gleiches Repository

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-project-setup

description

Flow Project Setup

Configure and deploy Flow projects across emulator, testnet, and mainnet.

Quick Start

flow init              # Initialize project
flow emulator          # Start emulator
flow project deploy    # Deploy contracts
flow test              # Run tests

Navigation Map

Task	Reference
flow.json, FCL config, contract addresses, dependencies, CLI commands	configuration.md
Dev workflow, deployment, debugging, gas optimization, testnet validation	workflow.md

Companion Skills

cadence-lang — Consult for Cadence language rules when debugging contract compilation errors or transaction failures. Understanding access control and resource handling is essential for diagnosing deployment issues.
flow-cli — Consult for detailed CLI command syntax, flags, and account management operations used during the development workflow.
flow-react-sdk — Consult when integrating the deployed project with a React frontend via FCL.
cadence-audit — Run an audit before deploying to testnet/mainnet as part of the validation checklist.