comark-ui 0.7.1 → 0.7.4

package/dist/skills/visual-explanation/references/example.md

@@ -0,0 +1,25 @@
+# How a Comark document becomes HTML
+
+Parsing and rendering are two separate calls, and the plugins do their work in the first. That's why a block's problems are known before any HTML exists.
+
+```mermaid
+flowchart LR
+  md[Markdown] --> tokens[Tokens]
+  tokens --> tree[Node tree]
+  tree --> doc[Nodes and issues]
+  doc --> html[HTML]
+```
+
+A plugin can join at three points: its Markdown rules while the text becomes tokens, `markdownItPost` on the tokens, and `post` on the tree. The last arrow is the renderer, which only maps each node to a component.
+
+In code, the diagram is three lines:
+
+```ts
+const document = await parseMarkdown(source, { plugins }); // <1>
+if (document.meta.issues.length) refuse(document.meta.issues); // <2>
+const html = await renderHtmlFromDocument(document, { components }); // <3>
+```
+
+1. Every plugin runs here, in the order of `plugins`.
+2. Each issue is one sentence naming the block and the fix, so a host can refuse a document before it renders.
+3. Components only draw: `screenshot` maps to the figure's HTML, and nothing is parsed again.

package/dist/skills.d.mts

@@ -0,0 +1,18 @@
+//#region src/skills.d.ts
+/** One file of a skill, at its path from the skill's folder, such as `SKILL.md` or `references/example.md`. */
+export interface SkillFile {
+  path: string;
+  text: string;
+}
+/** An Agent Skill: its folder's name, its frontmatter, and every file in it, `SKILL.md` first. */
+export interface Skill {
+  name: string;
+  description: string;
+  frontmatter: Record<string, unknown>;
+  files: SkillFile[];
+}
+/** Every agent skill this version of comark-ui ships, in the order of their names. */
+export declare const skills: Skill[];
+/** The comark-ui version the skills come from, for a host's cache key or a digest. */
+export declare const version: string;
+//#endregion