Noir Developer

Develop Noir (.nr) codebases. Use when creating a project or writing code with Noir.

Security Scan

The skill is an instruction-only helper for developing Noir projects and its requirements and instructions align with that purpose.

Purpose & Capability

Name/description (Noir development) match the instructions: compilation (nargo), witness generation, proving and verification. No unrelated binaries, env vars, or config paths are requested.

Instruction Scope

SKILL.md stays on-topic: it describes using nargo commands, testing, choosing a proving backend, and points to a local reference file for Barretenberg. It does not instruct reading unrelated files, exfiltrating data, or contacting unexpected endpoints.

Install Mechanism

No install spec and no code files — instruction-only skills have minimal disk footprint and no install-time risks.

Credentials

The skill requests no environment variables, credentials, or config paths. This is proportionate for a development helper that relies on local tooling such as nargo and optional proving backends.

Persistence & Privilege

Skill is not forced-always, is user-invocable, and does not request persistent privileges or modify other skills or system-wide settings.

Assessment

This is an instruction-only helper for Noir development and appears internally consistent. Before using it, ensure you have the expected local tooling (nargo and any proving backend) installed and that you only run commands in project directories you trust — compilation, testing, and proving operate on local source files. Because the skill is instructions-only, its safety depends on how the agent is permitted to execute commands and access your filesystem; avoid granting broad filesystem or credential access unless necessary. If you plan to use the Barretenberg backend, the skill points to an external Barretenberg doc URL and a local reference file (no hidden endpoints).

Workflow

1. Compile (nargo compile) Noir program into ACIR.
2. Generate witness (nargo execute or NoirJS execute) based on ACIR and user inputs.
3. Prove using ACIR and witness with the selected proving backend.
4. Verify proof with the selected proving backend.

Task Patterns

Environment

If the environment is unsupported by nargo (e.g. native Windows), guide the user to using GitHub Codespaces (https://noir-lang.org/docs/tooling/devcontainer#using-github-codespaces) or a supported setup (WSL, Docker, or VM).

Plan

Define private inputs, public inputs (if any), and public outputs (if any) for each Noir program.

Project Creation

When creating a Noir project, use nargo new or nargo init to scaffold it.

Compilation

Use nargo (not noir_wasm) for compilation; it is the maintained path.

Validation

Run nargo test to validate Noir implementations.

Proving Backend

Confirm the proving backend choice before implementation details. If the user selects Barretenberg, read references/barretenberg.md.

References

• Run nargo --help for the full list of commands.
• Read https://noir-lang.org/docs/ for language syntax, dependencies, and tooling.
• Proving backends:
  • For Barretenberg specifics, read references/barretenberg.md.