compact-core

Validate Compact code patterns and suggest improvements

Use this agent when queries don't match specific skills, for architecture guidance, pattern composition, or advanced Compact development questions. <example> Context: User needs to compose multiple contract patterns together user: "I want to build a contract that combines a voting system with a Merkle tree for voter eligibility and token-gated access. How do I compose these patterns safely?" assistant: "I'll use the compact-expert agent to guide you through composing voting, Merkle tree, and token patterns together." <commentary> Pattern composition across multiple domains requires deep expertise that goes beyond any single skill. The compact-expert synthesizes knowledge from contract-patterns, ledger-adts, and privacy-disclosure. </commentary> </example> <example> Context: User is migrating from another smart contract language user: "In Solidity I use mappings with msg.sender for access control. What's the Compact equivalent?" assistant: "Let me use the compact-expert agent to explain how Compact handles access control differently from Solidity." <commentary> Migration questions from Solidity, Rust, or Cadence require comparing paradigms and explaining Compact's unique privacy-first approach. The compact-expert handles these cross-language comparisons. </commentary> </example> <example> Context: User has an edge case not covered by standard docs user: "Can I use recursive types in Compact? I'm trying to model a tree structure but the compiler keeps rejecting it." assistant: "I'll use the compact-expert agent to investigate this edge case around type composition and circuit constraints." <commentary> Edge cases around type system limitations, circuit constraints, and unusual scenarios not covered by standard documentation are the compact-expert's specialty. </commentary> </example>

Use when starting a new Midnight project, cloning example contracts (counter, tokens, NFTs, DEX), scaffolding from OpenZeppelin templates, or bootstrapping a Compact contract development environment with working starter code.

Use when working with the Compact compiler (compactc), configuring build settings, understanding zkir/prover/verifier output artifacts, setting up COMPACT_PATH, or integrating VS Code language server support for Midnight smart contract development.

Use when implementing common Compact contract patterns such as voting systems, escrow, token transfers, access control, auctions, registries, or when looking for reusable contract templates and design patterns for Midnight blockchain development.

Use when writing Compact smart contracts and need reference for primitive types (Field, Boolean, Uint), composite types (struct, enum, Vector, Bytes), circuit/witness syntax, control flow (if/else, for loops, assert), or module system (import, include, export).

Use when working with Compact on-chain state management using ledger ADTs including Cell, Counter, Map, Set, List, MerkleTree, or HistoricMerkleTree, or when needing to understand which operations are available in Compact vs TypeScript.