Nudo for coding agents — agents.md, agent integration, stable diagnostics
Launch series (4/5) — published together on 2026-09-21. Read in order: Day 0 — observe JavaScript without rewriting it · Contracts are JS — Day 1 with sidecar *.nudo.js · Nudo vs TypeScript — when a JS-first gate is the right tool · Nudo for coding agents — agents.md, agent integration, stable diagnostics · The 22-file smear: how call-site attribution almost shipped fake precision
Nudo’s observation output is already structured. Agents need a stable product contract too.
Read Agents (human docs) and the machine entrypoint agents.md. Curated index: llms.txt.
Agent rules in one screen
Primary gate: npx nudojs check <path>
Contracts: *.nudo.js / @nudo:contract
@nudo:case is debug-only — not the contract product
Entry params print as any; unknown = inference failed
check validates; export projects (lossy)
Tooling surface
- LSP:
@nudojs/lsp - Agent executeCommand / tools: API · agent
- Agent integration: Agent integration guide
- JSON face:
npx nudojs check file.js --json - Diagnostic IDs: glossary
Why this matters
2026 tooling docs are judged by whether a coding agent can set up and gate a project without guessing product nouns. Nudo publishes agents.md + llms.txt so “welcome back to JavaScript” is also machine-actionable.
