plugins/compact-core/skills/clone-examples/SKILL.md
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.
npx skillsauth add aaronbassett/midnight-knowledgebase compact-core:clone-examplesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Catalog of cloneable Compact contract examples and starter projects
Read references/catalog.yaml to browse available examples.
Filter by tags, source, or compatibility requirements.
Always use shallow clone to minimize download size:
git clone --depth 1 <clone_url> <destination>
Before cloning: If the user hasn't specified a destination directory, ask where they'd like to clone the repository.
For examples where path is not /, guide the user to the specific file or directory after cloning.
Before recommending an example, use /midnight-tooling:midnight-compatibility to verify the user's environment matches the example's compatibility requirements. Warn if versions differ or are incompatible.
tools
Use when setting up Midnight development environment, installing Compact compiler and developer tools, configuring proof server, verifying prerequisites, or getting started with Midnight development.
tools
--- name: midnight-tooling:midnight-debugging description: Use when encountering Midnight errors like "compact: command not found", "ERR_UNSUPPORTED_DIR_IMPORT", version mismatches, proof server failures, "@midnight-ntwrk" package errors, or compilation failures. --- # Midnight Environment Debugging Expert knowledge for identifying and resolving common Midnight development toolchain issues. ## Diagnostic Approach When encountering Midnight-related errors, follow this systematic approach: 1.
tools
Use when checking Midnight version compatibility, understanding pragma language_version, verifying compiler and runtime version relationships, or troubleshooting version mismatch errors between Midnight components.
tools
Use when setting up CI/CD for Midnight projects, configuring GitHub Actions for Compact contract compilation, running TypeScript tests in CI, validating version consistency, or automating contract builds.