noir
Skill1 starsChanged 2 months agoMITView on GitHub
Zero-knowledge circuit design with Noir (Aztec's ZK DSL). TRIGGER when: working with .nr files, Nargo.toml, ZK circuits/proofs, Aztec contracts, zoir extension, or discussing zero-knowledge proof design. Covers circuit architecture, constraint optimization, ZK-specific security, and Aztec integration. DO NOT TRIGGER when: only Noir language syntax is needed (droo-stack handles that), working with Solidity only (use solidity-auditor skill), or hybrid Solidity + Noir projects with both foundry.toml and Nargo.toml (use zk-x-ray skill).
Files
noir
Domain knowledge for zero-knowledge circuit design with Noir. For Noir language syntax patterns (types, modules, generics), see droo-stack's noir-patterns rule. This skill covers the why of ZK: circuit architecture, security pitfalls, Aztec integration, and testing strategy.
What You Get
- Circuit architecture and constraint optimization patterns
- ZK-specific security: privacy leaks, oracle safety, nullifier attacks
- Systematic circuit audit methodology (spec-to-constraint mapping, completeness, privacy analysis)
- Aztec contract integration (notes, storage, account abstraction)
- Testing strategy: nargo tests, e2e setup, cross-chain messaging
- Constrained vs unconstrained computation guidance
When to use
This skill activates when working on ZK circuit design, proof systems, or Aztec contracts. It complements droo-stack (which covers Noir syntax) with domain knowledge that requires ZK expertise.
When NOT to use
- For Noir language syntax only (types, modules, generics) -- use droo-stack
- For Solidity smart contracts -- use solidity-auditor
- For general Ethereum tooling -- use ethskills
See also
droo-stack-- for Noir language syntax (types, modules, generics)solidity-auditor-- for Solidity verifier contracts that consume Noir proofszk-x-ray-- for pre-audit reports on ZK + EVM hybrid protocols (Noir + Solidity)ethskills-- for Ethereum ecosystem tooling and standards
Reading guide
| Working on | Read |
| Circuit design, constraint optimization | circuits/constrained |
| Oracle calls, unconstrained computation | circuits/unconstrained |
| Privacy leaks, public/private input design | security/privacy |
| Unconstrained return safety, oracle verification | security/oracle-safety |
| Circuit audit methodology, spec compliance | security/circuit-audit |
| Aztec-specific attacks: nullifiers, MEV, leakage | security/aztec-contracts |
| Aztec contract structure, notes, storage | aztec/contracts |
| Account abstraction, access control, keys | aztec/accounts |
| Testing with nargo, proof vs execution | testing/nargo |
| Aztec e2e test setup, accounts, deployment | testing/e2e-setup |
| Token testing, AuthWit, balance assertions | testing/e2e-token |
| Cross-chain L1/L2, event testing | testing/e2e-messaging |
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- austintgriffith/ethskills★ 295same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository61 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- adversarial-reviewerSkill
- agent-designerSkill
- architectSkill
- autoresearchSkill
- blockscoutSkill
- ci-cd-pipeline-builderSkill
- claude-apiSkill
- codebase-onboardingSkill
- code-reviewSkill
- coingeckoSkill
- database-designerSkill
- dependency-auditorSkill
- design-uxSkill
- digestSkill
- droo-stackSkill
- env-secrets-managerSkill
- ethskillsSkill
- ffmpeg-asmSkill
- focused-fixSkill
- frontend-slop-auditSkill
- git-guardrailsSkill
- git-worktree-managerSkill
- humanizerSkill
- interface-designerSkill
- llm-cost-optimizerSkill
- local-browser-inspectorSkill
- mcp-server-builderSkill
- native-codeSkill
- nixSkill
- observability-designerSkill
- patchbotSkill
- performance-profilerSkill
- playwrightSkill
- polymathSkill
- prd-to-planSkill
- prepperSkill
- property-testingSkill
- qaSkill
- rag-architectSkill
- raxol-paymentsSkill
- raxolSkill
- raxol-symphonySkill
- recallSkill
- refactoring-strategySkill
- regenSkill
- releaseSkill
- security-auditorSkill
- self-improving-agentSkill
- sentinelSkill
- signozSkill
- skill-creatorSkill
- solidity-auditorSkill
- tddSkill
- tech-debt-trackerSkill
- ubiquitous-languageSkill
- watchdogSkill
- web-asset-generatorSkill
- writing-voiceSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.