How to write a useful document

Public writing guide: https://aic.dzyha.com/how-to

Українська · Open AIC Notes · Terms and privacy · Releases and installation

Use the Document Design Kit writing prompt to establish the initiator, purpose, reader and next action before writing. It is the public authoring guide; opening it or copying its prompt does not send your note anywhere.

Write the first sufficient document

Give the reader only the understanding needed for their next action. Name the result, derive the smallest useful set of questions, and answer each directly. Use short prose for one explanation, bullets for independent points, numbered steps for ordered work, tables for comparisons or definitions, and fenced Mermaid for relationships, flows or branches. Keep facts distinct from proposals, assumptions and unknowns. Do not create another document merely because a template exists; extend the existing one when one missing detail is all that remains.

Markdown is the normal Notes deliverable. Preserve headings, links, fenced code and Mermaid, tables, details, raw HTML, legacy properties and AIC typed fields. At a field separator in a row, |, *|, #|, _|, 1| and 0| carry value types; masking changes display only and never permits revealing or exporting a secret.

DDK JSON is a separate, explicitly requested exchange format for DDK's structured editor. It is not a Notes import format or an encrypted .aicnotes bundle, and Notes does not convert Markdown notes into DDK JSON. Keep a native DDK JSON source when a DDK document needs its richer blocks, properties or nested regions.

The current Notes editor applies Fix grammar or Improve only to selected prose or the current note. It does not include DDK templates, structured regions or automatic field completion. Review every suggestion before Apply; the author remains responsible for facts and decisions.

Copy an AIC addendum for the DDK prompt

This is an AIC-specific addendum, not a copy of the canonical DDK prompt. Start with the current DDK prompt, then add this when the requested result is an AIC note:

Use the DDK method to create the first document sufficient for the reader's next action. Output Markdown unless the user explicitly requests DDK JSON. Preserve AIC headings, links, fenced code and Mermaid, tables, details, raw HTML, legacy properties and typed separators inside fenced aic blocks (|, *|, #|, _|, 1| and 0|). Do not convert an AIC note to DDK JSON or lose its syntax. Do not put secret values in examples, prompts, previews or instructions.

Use the current Notes assistant locally

  1. From the start screen, choose New workspace, then New note, or choose Open notes. Open notes offers Open files, Open folder and Open encrypted file. Folder imports show only .md and skip .git and node_modules; encrypted .aicnotes files need their passphrase.

  2. Select prose to review, or leave the selection empty to review the current note. Choose Fix grammar for spelling, grammar and punctuation, or Improve for clearer wording. Local AI accepts up to 14,000 characters; select a shorter passage in a longer note.

  3. Review the preview and its facts. Choose Apply to make the change or Cancel to keep the original. Editor Undo restores an applied suggestion.

  4. Changes autosave locally; Save or Ctrl/Cmd+S retries a pending or failed save. A local workspace stays on this device and does not update its original folder or Drive. Use Export Markdown from the note menu, or Export all notes and Save encrypted copy from workspace options, for copies. Your chosen file-sync service transfers exported files separately. Remove local workspace removes the app's local copy.

AI processing starts only after your action; an encrypted entity must also be unlocked. Code, links, raw HTML, legacy properties and AIC secret fences remain protected; their contents are hidden from the local model. Select prose outside those protected parts. Locking, closing or switching notes clears the assistant's preview; a changed note or selection cannot receive a stale suggestion.

The assistant uses Chrome's on-device model and has no remote AI fallback or provider key. Its first browser-managed model download requires a connection. After the model is available, supported devices can run AI offline; the installed PWA also needs its initial online load before its interface can work offline. Chrome's current foundation-model APIs do not support Android or iOS. Mobile Notes editing still works offline; AI also depends on supported desktop hardware, browser API, storage and language. Chrome Prompt API requirements.

Copying the writing prompt into another AI service uses that service's data policy. The built-in AIC assistant does not send notes to that service. Keep secret data out of manually shared prompts and review generated content before saving or sharing it.

How to · Terms and privacy · Releases and installation