Skip to content

armgit / nota

Public Imported from GitHub
0

Nota — a free DAW for macOS, Windows and Linux. No subscription, no account — just open it and make music.

2.4 KB
Raw Blame

AGENTS.md

Nota is a real-time audio application: a C++20 engine behind a pure C ABI, driven by a .NET 10 / Avalonia app. Read CONTRIBUTING.md before changing anything — the rules there are binding (AGPL headers, dependency policy, audio-thread restrictions).

Before any change — code, spec, docs, even a typo — confirm there is a GitHub issue for it that a core contributor has approved (it carries the approved label, or good first issue / help wanted; check with gh issue view <N> --repo nota-daw/nota). If the user hasn't named one, or it isn't approved, stop: don't write a spec, don't edit files. Tell them to open or find an issue and wait for approval (CONTRIBUTING.md § Start with an approved issue), and offer to draft the issue text. Once it is approved, stay inside the scope the issue agreed and link it from the pull request (Closes #N). Release pull requests cut by core contributors are exempt.

  • The project constitution for agents lives at .specify/memory/constitution.md.
  • Non-trivial work is spec-driven. When the user asks for a feature or behaviour change, do not start implementing: open with the speckit specify command on the request and follow the phases (specify, clarify, plan, tasks, implement, converge — see your integration's command list). Artifacts land in specs/<slug>/; see CONTRIBUTING.md § Spec-driven workflow. specs/000-example/ shows a completed run. Trivial work — typos, small fixes, doc edits — skips the spec (not the approved issue) and goes straight to the change.
  • Bug reports go through the speckit bug-assess → bug-fix → bug-test commands.
  • The nota-* skills (design, docs, features, instrument, shortcuts, release, pr) encode project-specific workflows — prefer them over improvising. Every agent finds them in its own skill directory (.agents/skills/, .github/skills/, .cursor/skills/, .gemini/skills/); those are copies. The source is .claude/skills/: edit a skill there, then run scripts/sync-agent-skills.sh.
  • Before any pull request: scripts/build.sh (or the Linux/Windows siblings) must pass; it runs the smoke test that drives the engine end-to-end.