Add Cadence plugin marketplace with 7 skills for Flow development#18
Add Cadence plugin marketplace with 7 skills for Flow development#180xLisanAlGaib merged 7 commits intomainfrom
Conversation
Set up this repository as a Claude Code plugin marketplace for the Flow ecosystem. Convert onflow/cadence-rules into structured skills with progressive disclosure (metadata → SKILL.md → reference files). Plugin: cadence (7 skills, 37 files) - cadence-lang: Language fundamentals (13 reference files covering access control, resources, contracts, transactions, interfaces, accounts, references, capabilities, conditions, security, anti-patterns, patterns) - cadence-tokens: NFT/FT token development (2 references) - cadence-defi-actions: DeFi Actions framework composition (5 references) - cadence-audit: Security audit with severity-rated review format (2 references) - cadence-scaffold: Interactive code generation templates (3 references) - flow-cli-query: Blockchain data queries via Flow CLI and findapi (2 references) - flow-project-setup: Project configuration and deployment workflow (2 references)
Extract entitlements content from access-control.md into new entitlements.md with full coverage of entitlement mappings, Identity mapping, include composition, owned-values-are-fully-entitled rule, and account entitlements from official Cadence docs.
High severity: - Remove all `defer` references (5 files) — Cadence does not have defer - Fix insecure public minting capability labeled "Secure" in nft-standards.md - Restrict access(all) on resource-typed fields in token-patterns.md Medium severity: - Replace pre-1.0 address imports with string imports (3 files) - Rewrite non-functional FT pattern with Minter, Burner.burn(), events - Fix cadence-lang reference count: 13 → 14 in CLAUDE.md and README.md
Fixes for 6 correctness issues across skill reference filesHigh Severity
Medium Severity
|
plugins/cadence/skills/flow-cli-query/references/query-findapi.md
Outdated
Show resolved
Hide resolved
Covers @onflow/react-sdk with 4 reference files: - setup: FlowProvider, Next.js integration, theming, dark mode - hooks: 20 Cadence hooks (query, mutate, auth, events, accounts, blocks, NFT metadata, scheduled transactions, randomness) - cross-vm: 7 Cross-VM hooks (batch EVM transactions, token/NFT bridging between Cadence and Flow EVM, cross-chain balances) - components: 7 UI components (Connect, TransactionButton, TransactionDialog, NftCard, Profile, ScheduledTransactionList)
Delete skill directory and remove all references from SKILL.md descriptions, README, and CLAUDE.md.
New skill: flow-cli with 3 reference files (commands-overview, accounts, project) covering the full Flow CLI command reference. Add "Companion Skills" sections to all 8 SKILL.md files, pointing to cadence-lang as the foundation skill and cross-referencing related skills for each domain. Add "See also" cross-references within key reference files (nft-standards, safety-testing, scaffold-contract, scaffold- transaction, hooks, accounts, project, audit-checklist) to guide Claude to the most relevant skill for each task context.
turbolent
left a comment
There was a problem hiding this comment.
Nice! I mostly had a look at the cadence-audit and especially cadence-lang skill and they overall look good to me. We probably need to try these out and iteratively improve them based on feedback
| @@ -0,0 +1,179 @@ | |||
| # Flow React SDK — UI Components | |||
There was a problem hiding this comment.
what do you think about putting this in a different plugin? e.g. dapp or something higher level. it doesn't seem like it should exist under cadence. same for the flow-project-setup
There was a problem hiding this comment.
alternatively, we could rename the plugin so something more general and include all of the skills under the single plugin
There was a problem hiding this comment.
All these skills are very intertwined. I want to make sure that they trigger each other. A separate plugin might make this more difficult.
There was a problem hiding this comment.
I can create a separate plugin later and AB test how they trigger each other, but for now I will dump everything here
There was a problem hiding this comment.
that's fair. maybe we just rename it to something like flow-dev?
Verified against official Cadence docs (cadence-lang.org). Fixes: 1. Entitlement declarations: remove erroneous access(all) prefix from all entitlement declarations (correct: `entitlement E`, not `access(all) entitlement E`) — 11 occurrences across 7 files 2. Capability controller deletion: change from incorrect account.capabilities.storage.delete(id) to correct controller.delete() — 4 occurrences across 3 files 3. Account entitlement names: replace non-existent IssueStorageCapabilityController with StorageCapabilities, PublishCapability with Capabilities — 10 occurrences across 8 files. Add correct fine-grained names: AddContract, UpdateContract, RemoveContract, PublishInboxCapability, ClaimInboxCapability 4. Contract updatability rules: correct major errors per official docs. Removing fields IS valid (was listed as invalid). Reordering fields IS valid (was listed as invalid). Adding new fields is NOT valid (init doesn't re-run). Updated in contracts.md, workflow.md, accounts.md 5. Transaction post-conditions: add note that `result` is only available in function post-conditions, not transaction post-conditions (transactions don't return values)
Summary
Plugin:
cadence— 7 skills, 41 files, 4,636 linescadence-langcadence-tokenscadence-defi-actionscadence-auditcadence-scaffoldflow-cli-queryflow-project-setupArchitecture
TRIGGER whenandDO NOT TRIGGER whensections for accurate skill routingTest plan
/plugin marketplace add onflow/flow-ai-tools/plugin install cadence@flow-claude-code-pluginscadence-langtriggers on Cadence syntax questionscadence-tokenstriggers on NFT/FT contract questionscadence-audittriggers on "review my contract" promptscadence-scaffoldtriggers on "create a new contract" promptsflow-cli-querytriggers on "check account balance" promptsflow-project-setuptriggers on "configure flow.json" prompts