From noma
Use when reading, validating, or editing Noma (.noma) documents or book manifests (book.noma.yml) — structured plain-text docs with stable block IDs that agents patch block-by-block instead of rewriting files. Triggers: any task touching a .noma file, "update the docs" in a repo containing .noma sources, or requests to render/export/validate Noma documents.
How this skill is triggered — by the user, by Claude, or both
Slash command
/noma:noma-docsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Noma documents are plain text with addressable blocks. You edit them with
Noma documents are plain text with addressable blocks. You edit them with patch operations targeting block IDs — never by rewriting the file.
All commands need @ferax564/noma-cli (npm install -g @ferax564/noma-cli,
or npx -p @ferax564/noma-cli noma …).
noma ids <file.noma> # every addressable block ID
noma render <file.noma> --to llm # deterministic context export
noma check <file.noma> # validation diagnostics (with fixits)
content — not body:
{ "op": "replace_body", "id": "overview", "content": "New body text." }
noma proof <file.noma> --op '<json>' --to markdown --out proof.md
Exit 1 or Noma Proof: FAIL means do not apply; read proof.md for why.noma patch <file.noma> --op '<json>' --inplace
noma check <file.noma>
| Intent | Op |
|---|---|
| Edit a block's text | replace_body (id, content) |
| Replace a whole block incl. fences | replace_block (id, content) |
| Rename a heading, keep its ID | update_heading (id, title) |
| Change one attribute | update_attribute (id, key, value) |
| Add a new block under a parent | add_block (parent, content, position?) |
| Review comment / reply | add_comment (id, target, content, reply_to?) |
| Table/dataset cells, rows, columns | update_table_cell, insert_dataset_row, … |
Full schema: noma schema patch-op. Multi-op transactions: --ops <file.json>
(applied all-or-nothing).
When a human may edit the same file, include a baseHash precondition:
read the block's hash (blockSourceHash() from the library, or hash from
the MCP server's read_doc), attach it to the op, and a sha_mismatch
rejection means re-read before retrying.
For multi-file books, patch the manifest and ops route to the owning chapter:
noma patch book.noma.yml --ops tx.json --inplace
.noma file with Write/Edit when a patch op can express
the change — whole-file writes destroy the reviewable diff and skip proofs.noma ids.Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Applies a firm's KYC/AML rules grid to parsed onboarding records: assigns risk rating, checks required documents, outputs rule outcomes with citations, and routes for escalation.
Generates daily or weekly digests of activity from connected sources (chat, email, docs, tasks, CRM), highlighting action items, decisions, mentions, and project updates.
npx claudepluginhub ferax564/noma --plugin noma