Skip to content

Build your personal knowledge base with Trilium Notes

chore(skills): shorten over-limit descriptions

Elian Doran78b808771c06
diff --git a/.claude/skills/building-client-ui/SKILL.md b/.claude/skills/building-client-ui/SKILL.md
index 2ca64e2432..34bd1b40ef 100644
--- a/.claude/skills/building-client-ui/SKILL.md
+++ b/.claude/skills/building-client-ui/SKILL.md
@@ -1,6 +1,6 @@
---
name: building-client-ui
-description: Use when building or changing any UI in the Trilium client (`apps/client`) — a dialog, a settings pane, a form, a toolbar, a badge, a link, a dropdown menu, a type widget, a control floating over a note's content (map, mind map, image, diagram, presentation), or any component that reads/writes a note's title, label, relation, blob or option. Catalogues the froca-reactive hooks (useNoteProperty / useNoteLabel / useNoteBlob / useChildNotes / useTriliumOption / useNoteContext) and which `loadResults` filter each already wires, the reusable Preact components under `apps/client/src/widgets/react/` (which one to reach for instead of a hand-rolled `<input>`/`<button>`/`<a>`/pill), when a dropdown is a `Dropdown` menu and when a `DropdownPanel`, the `OverlayControlGroup` / `OverlayToolbar` contract for controls over a canvas, the event-summoned Modal/LazyDialog wiring, and how to boot a login-free fixture instance to inspect real computed styles when a style, placement or stacking bug cannot be read off the stylesheets. The home for client UI guidance that outgrows CLAUDE.md.
+description: Use when building or changing any UI in the Trilium client (`apps/client`) — a dialog, settings pane, form, toolbar, badge, link, dropdown, type widget, or a control floating over a note's content. Catalogues the froca-reactive hooks (useNoteProperty / useNoteLabel / useNoteBlob / useChildNotes / useTriliumOption / useNoteContext) and the `loadResults` filter each wires, the reusable Preact components under `apps/client/src/widgets/react/` (which to reach for instead of a hand-rolled `<input>`/`<button>`/`<a>`/pill), `Dropdown` menu vs `DropdownPanel`, the `OverlayControlGroup` / `OverlayToolbar` contract, Modal/LazyDialog wiring, and how to boot a login-free fixture to inspect computed styles. The home for client UI guidance that outgrows CLAUDE.md.
---
# Building client UI
diff --git a/.claude/skills/ckeditor5-plugin-development/SKILL.md b/.claude/skills/ckeditor5-plugin-development/SKILL.md
index a0bb989257..c9173fcaab 100644
--- a/.claude/skills/ckeditor5-plugin-development/SKILL.md
+++ b/.claude/skills/ckeditor5-plugin-development/SKILL.md
@@ -1,22 +1,6 @@
---
name: ckeditor5-plugin-development
-description: >-
- Write, extend, and review CKEditor 5 plugins in the Trilium (TriliumNext
- Notes) monorepo — the rich-text-note editor under packages/ckeditor5, whose
- plugins live in src/plugins/.
- Use when building or
- reviewing a Trilium CKEditor 5 feature/plugin, or when working with the
- editing engine (model, view, schema, conversion/upcast-downcast), commands,
- the UI library (buttons, dropdowns, dialogs, balloons, toolbars), widgets
- (block/inline, toWidget, nested editables), keystrokes, localization (t()),
- registering a plugin into plugins.ts / the editor classes / toolbar.ts, persisting a
- `data-trilium-*` attribute through the model→view→data→markdown→share pipeline, or
- adding a new plugin folder under src/plugins/, or upgrading `ckeditor5` to a
- new major version (Renovate's major-ckeditor-monorepo branch, broken editor
- styling after a bump, `--ck-*` variables that stopped applying). Covers the
- architecture, idiomatic patterns, Trilium packaging/registration, code-style
- conventions, a review checklist, and ck_css.mjs, which compares CKEditor's
- stylesheets between two versions under Trilium's own CSS.
+description: Use when writing, extending or reviewing a CKEditor 5 plugin in the Trilium monorepo (`packages/ckeditor5`, plugins in `src/plugins/`), or when working with the editing engine (model, view, schema, conversion/upcast-downcast), commands, the UI library (buttons, dropdowns, dialogs, balloons, toolbars), widgets (block/inline, toWidget, nested editables), keystrokes, localization (t()), registering a plugin into plugins.ts / the editor classes / toolbar.ts, persisting a `data-trilium-*` attribute through the model→view→data→markdown→share pipeline, adding a plugin folder, or upgrading `ckeditor5` to a new major version (Renovate's major-ckeditor-monorepo branch, broken styling after a bump, `--ck-*` variables). Covers architecture, idiomatic patterns, packaging/registration, code style, a review checklist and ck_css.mjs, which compares stylesheets between two versions under Trilium's own CSS.
---
# CKEditor 5 plugin development (Trilium monorepo)
diff --git a/.claude/skills/developing-content-embeds/SKILL.md b/.claude/skills/developing-content-embeds/SKILL.md
index e4010fbc60..126fc0dc26 100644
--- a/.claude/skills/developing-content-embeds/SKILL.md
+++ b/.claude/skills/developing-content-embeds/SKILL.md
@@ -1,6 +1,7 @@
---
name: developing-content-embeds
-description: Use when building or changing an embed box in a text note — an included note, an attachment embed such as a canvas drawing (`CanvasDrawing`), or a source embed such as a Mermaid diagram (`MermaidDiagram`, `SOURCE_EMBED_TYPES`) — or adding a new kind of embed (a diagram language, an editor kept in an attachment). Covers the three storage forms (`data-note-id`, `data-attachment-id`, inline `<pre><code class="language-…">`), the editor plugin (`packages/ckeditor5/src/plugins/content_embed/`: `content_embed.ts`, `inline_source.ts`, the toolbar, tools and box-size dropdown), the host contract (`loadEmbeddedAttachment()`, `loadInlineEmbed()`), the client box (`ContentEmbed`, `text/utils.ts`), the content component contract (`useEditableEmbed()`, `ContentEmbedToolProvider`, Editable flag, display modes, fullscreen events), how to reuse the note type's own component as canvas and Mermaid do, the read-only paths (read-only notes, AI chat, Markdown preview, print, share pages), and the traps already hit (content rendered detached, CodeMirror read-only fixed at creation, the CKEditor separator `:first-child` rule, box sizes without a title, class clashes).
+description: >-
+ Use when building or changing an embed in a text note — an included note, an attachment embed such as a canvas drawing (`CanvasDrawing`), or a source embed such as a Mermaid diagram (`MermaidDiagram`, `SOURCE_EMBED_TYPES`) — or adding an embed kind. Covers the storage forms (`data-note-id`, `data-attachment-id`, inline `<pre><code class="language-…">`), the editor plugin (`packages/ckeditor5/src/plugins/content_embed/`: `content_embed.ts`, `inline_source.ts`, toolbar, box-size dropdown), the host contract (`loadEmbeddedAttachment()`, `loadInlineEmbed()`), the client box (`ContentEmbed`, `text/utils.ts`), the content component contract (`useEditableEmbed()`, `ContentEmbedToolProvider`, Editable, display modes, fullscreen), reusing the note type's component as canvas and Mermaid do, the read-only paths (AI chat, Markdown preview, print, share), and traps hit (detached content, CodeMirror read-only fixed at creation, the CKEditor `:first-child` separator rule, untitled box sizes, class clashes).
---
# Developing content embeds
diff --git a/.claude/skills/developing-pdf-viewer/SKILL.md b/.claude/skills/developing-pdf-viewer/SKILL.md
index 16bad7ab0b..21db50a6ea 100644
--- a/.claude/skills/developing-pdf-viewer/SKILL.md
+++ b/.claude/skills/developing-pdf-viewer/SKILL.md
@@ -1,6 +1,7 @@
---
name: developing-pdf-viewer
-description: Use when changing Trilium's built-in PDF viewer — anything under `packages/pdfjs-viewer` (the code injected into Mozilla's PDF.js viewer: `bootstrap.ts`, `annotations.ts`, `pages.ts`, `toc.ts`, `layers.ts`, `attachments.ts`, `persistence.ts`, `editing.ts`), the client side that talks to it (`apps/client/src/widgets/type_widgets/file/Pdf.tsx`, `PdfViewer.tsx`, the sidebar panels in `widgets/sidebar/pdf/`), the postMessage protocol between them, PDF links (`?page=` / `?annotation=`), or a bug where the viewer "does not pick up" a change. Covers the mandatory rebuild after every viewer change, the message protocol, the hidden-but-mounted viewer, the pdf.js timing traps, and how to test at each level.
+description: >-
+ Use when changing Trilium's built-in PDF viewer — anything under `packages/pdfjs-viewer` (the code injected into Mozilla's PDF.js viewer: `bootstrap.ts`, `annotations.ts`, `pages.ts`, `toc.ts`, `layers.ts`, `attachments.ts`, `persistence.ts`, `editing.ts`), the client side that talks to it (`apps/client/src/widgets/type_widgets/file/Pdf.tsx`, `PdfViewer.tsx`, the sidebar panels in `widgets/sidebar/pdf/`), the postMessage protocol between them, PDF links (`?page=` / `?annotation=`), or a bug where the viewer "does not pick up" a change. Covers the mandatory rebuild after every viewer change, the message protocol, the hidden-but-mounted viewer, the pdf.js timing traps, and how to test at each level.
---
# Developing the PDF viewer
diff --git a/.claude/skills/developing-share-pages/SKILL.md b/.claude/skills/developing-share-pages/SKILL.md
index 1dbe2f388f..e4866516b4 100644
--- a/.claude/skills/developing-share-pages/SKILL.md
+++ b/.claude/skills/developing-share-pages/SKILL.md
@@ -1,6 +1,7 @@
---
name: developing-share-pages
-description: Use when working on Trilium's share functionality — shared pages under `/share/`, the static HTML (share-theme) export, the share theme package (`packages/share-theme`: EJS templates, page model, browser scripts and CSS), core's share renderer (`packages/trilium-core/src/share/content_renderer.ts`, `handlers.ts`, shaca), the per-platform share providers, `~shareTemplate` custom templates, `~shareHtml` snippets, or any `#share*` label. Covers where each piece runs (server, desktop, standalone worker, visitor's browser), the render pipeline from note to page, the page model and its template variables, what custom templates are promised, CSS ordering, how to test each layer (both core runners, happy-dom, node:vm), and the traps already hit on this code.
+description: >-
+ Use when working on Trilium's share functionality — shared pages under `/share/`, the static HTML (share-theme) export, the share theme package (`packages/share-theme`: EJS templates, page model, browser scripts and CSS), core's share renderer (`packages/trilium-core/src/share/content_renderer.ts`, `handlers.ts`, shaca), the per-platform share providers, `~shareTemplate` custom templates, `~shareHtml` snippets, or any `#share*` label. Covers where each piece runs (server, desktop, standalone worker, visitor's browser), the render pipeline from note to page, the page model and its template variables, what custom templates are promised, CSS ordering, how to test each layer (both core runners, happy-dom, node:vm), and the traps already hit on this code.
---
# Developing shared pages
diff --git a/.claude/skills/reviewing-pull-requests/SKILL.md b/.claude/skills/reviewing-pull-requests/SKILL.md
index 13e01317c5..e3cc2d8989 100644
--- a/.claude/skills/reviewing-pull-requests/SKILL.md
+++ b/.claude/skills/reviewing-pull-requests/SKILL.md
@@ -1,6 +1,7 @@
---
name: reviewing-pull-requests
-description: Use whenever a Trilium pull request is to be judged — "review PR N", "is #N good?", "which PRs should I merge?", "list the merge candidates", "triage the open PRs", "does this fit Trilium?", "compare #A and #B", "draft feedback for this contributor", or any PR number or link with an evaluative question attached. Also use when asked what is mergeable, what to close, or whether a contributor's fix targets the bug it names. The judgement is about fit and shape (philosophy, targeting, complexity, spec, docs), never about CI, conflicts or the description; every candidate is checked out in a temporary worktree and its specs run red/green against the base. Provides review.mjs (list / dossier / verify / dupes / issue / clean) and references on the philosophy as the maintainers apply it, why PRs get closed here, and what an accepted change looks like. Never writes to GitHub. Not for an uncommitted local diff (/code-review) and not for CKEditor-plugin internals (ckeditor5-reviewing, which this skill delegates to).
+description: >-
+ Use whenever a Trilium pull request is to be judged — "review PR N", "is #N good?", "which PRs should I merge?", "list the merge candidates", "triage the open PRs", "does this fit Trilium?", "compare #A and #B", "draft feedback for this contributor", or any PR number or link with an evaluative question attached. Also use when asked what is mergeable, what to close, or whether a contributor's fix targets the bug it names. The judgement is about fit and shape (philosophy, targeting, complexity, spec, docs), never about CI, conflicts or the description; every candidate is checked out in a temporary worktree and its specs run red/green against the base. Provides review.mjs (list / dossier / verify / dupes / issue / clean) and references on the philosophy as the maintainers apply it, why PRs get closed here, and what an accepted change looks like. Never writes to GitHub. Not for an uncommitted local diff (/code-review) and not for CKEditor-plugin internals (ckeditor5-reviewing, which this skill delegates to).
---
# Reviewing pull requests
diff --git a/.claude/skills/working-with-transcription/SKILL.md b/.claude/skills/working-with-transcription/SKILL.md
index b025859589..57ae35b0d1 100644
--- a/.claude/skills/working-with-transcription/SKILL.md
+++ b/.claude/skills/working-with-transcription/SKILL.md
@@ -1,6 +1,6 @@
---
name: working-with-transcription
-description: Use when working on Trilium's meeting transcription — the desktop pipeline in `apps/desktop/src/services/transcription/` (capture window, Silero VAD segmentation, Parakeet via sherpa-onnx-node, sinks and audio taps), the `transcript` attachment and its `TranscriptView`, the "Transcribe meeting" launcher, the standalone WebAssembly prototype, speaker detection (diarization), or any change to recognition quality — decoding method, beam search, hotwords, VAD settings, a different model — or to audio capture (stutters, clicks, the capture worklet). Includes replay.mjs, which transcribes a development recording again with changed settings, compare.mjs, which diffs two transcripts word by word with an error rate, external.mjs, which scores transcripts against another tool's export of the same meeting, hotwords.mjs, which builds the BPE vocabulary hotwords need and checks a glossary, diarize.mjs, which labels a recording's speakers live and offline and times both, capture-check.mjs, which finds capture damage in a recording, capture-test.mjs, which plays a tone through the real capture code in Electron under load, and worker-test.mjs, which runs a recording through the real transcription process and measures the main process's lag. Don't judge an engine change by ear or from one live meeting; replay a recording and compare.
+description: Use when working on Trilium's meeting transcription — the desktop pipeline in `apps/desktop/src/services/transcription/` (capture window, Silero VAD, Parakeet via sherpa-onnx-node, sinks and audio taps), the `transcript` attachment and `TranscriptView`, the "Transcribe meeting" launcher, the standalone WebAssembly prototype, speaker detection (diarization), any change to recognition quality (decoding method, beam search, hotwords, VAD settings, a different model), or audio capture (stutters, clicks, the capture worklet). Includes replay.mjs (re-transcribes a recording with changed settings), compare.mjs (word-by-word diff with an error rate), external.mjs (scores against another tool's export), hotwords.mjs (builds the BPE vocabulary and checks a glossary), diarize.mjs, capture-check.mjs, capture-test.mjs and worker-test.mjs. Don't judge an engine change by ear or from one live meeting; replay a recording and compare.
---
# Working with transcription
diff --git a/.claude/skills/writing-documentation/SKILL.md b/.claude/skills/writing-documentation/SKILL.md
index 2a7da2bb9b..1282b01690 100644
--- a/.claude/skills/writing-documentation/SKILL.md
+++ b/.claude/skills/writing-documentation/SKILL.md
@@ -1,6 +1,6 @@
---
name: writing-documentation
-description: Use whenever a change is user-facing — a new feature, a moved or removed button, a label, a shortcut, an option, a default, a note type, a collection view, a dialog, an import format — or when asked to write, fix, restructure or audit Trilium's documentation ("document this", "update the User Guide", "add a page for X", "is X documented?", "which page describes X?", "the docs still say…", "rename/move this page", "add a screenshot", "which icon do I use?"). Covers the three docs trees (`docs/User Guide`, `docs/Developer Guide`, `docs/Release Notes`) and the generated in-app help they feed, the `!!!meta.json` note metadata (noteId, shareAlias, iconClass, attachments), the house style of the User Guide (register, page templates, reference-link pills, `<kbd>`, admonitions, figures, the `bx`/`cke`/`tn-brand` icon spans), and `docs.mjs`, which finds and shows pages, scaffolds a page with correct metadata, registers images, renames/moves/deletes pages, maps a code diff to the pages it affects, audits the trees, and regenerates the in-app help headless — so `!!!meta.json` and `apps/server/src/assets/help` never have to be read or hand-edited. A user-facing change is not finished until the User Guide describes it, in the same commit.
+description: Use whenever a change is user-facing — a new feature, a moved or removed button, a label, a shortcut, an option, a default, a note type, a collection view, an import format — or when asked to write, fix, restructure or audit Trilium's documentation ("document this", "update the User Guide", "add a page for X", "is X documented?", "which page describes X?", "the docs still say…", "rename/move this page", "add a screenshot", "which icon do I use?"). Covers the docs trees (`docs/User Guide`, `docs/Developer Guide`, `docs/Release Notes`) and the generated in-app help, `!!!meta.json` (noteId, shareAlias, iconClass, attachments), the User Guide house style (register, templates, reference pills, `<kbd>`, admonitions, figures, `bx`/`cke`/`tn-brand` icon spans), and `docs.mjs` (find/show/scaffold pages, register images, rename/move/delete, map a diff to affected pages, audit, regenerate the in-app help). A user-facing change is not finished until the User Guide describes it, in the same commit.
---
# Writing Trilium's documentation