Menu
Render a downloadable file card with icon, label, and optional file size. Use for attaching docs, PDFs, sample assets, archives.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | file |
| description | Render a downloadable file card with icon, label, and optional file size. Use for attaching docs, PDFs, sample assets, archives. |
A download card that displays a file with icon, name, and optional metadata. Visually heavier than a plain Markdown link — use when the download itself is the main thing on the line.
[!file](path/file.pdf)
[!file Friendly Label](path/file.pdf)
[!file text="Project Proposal" link="/assets/proposal.pdf" size="1.2 MB"]
[!file icon="rocket" text="Download"](path/file.pdf)
[!file icon=":rocket:" text="Launch"](path/file.pdf)
| Attribute | Notes |
|---|---|
text | Display label. Defaults to the filename if omitted. |
link | File path (same as the ( ) form). |
size | Optional human-readable size ("1.2 MB", "450 KB"). |
icon | UIcon name, :emoji:, <svg>, or image path. Auto-picks an icon by extension if omitted. |
[!file](/assets/whitepaper.pdf)
[!file "Sample CSV"](/assets/data.csv)
[!file text="Annual report 2026" link="/assets/report.pdf" size="3.4 MB" icon="file-pdf"]
[link](path) would feel underwhelming.For inline file mentions inside prose, a plain Markdown link is still better.
For embedded PDF preview, see pdf.
Author the YAML frontmatter block of a Neko Markdown page — label, icon, order, tags, visibility, permalink, redirect, redirectSlug, layout, meta, nav, toc, backlinks, password. Use when configuring an individual page.
Author the project-level `neko.yml` — input/output paths, URL, branding, theme, meta tags, top navigation, banner, footer, snippets. Use when configuring or editing a Neko site at the project level.
Render a Mermaid diagram (flowchart, sequence, class, ER, state, gantt, journey, mindmap, sankey, XY, architecture) from a fenced ```mermaid``` block. Use for any structured diagram in docs.
Workflow for updating Neko documentation — base every page on the real source code, never invent APIs, warn loudly when the source isn't available, and check that the page (and any changed `tesserae` sample) renders correctly with Playwright / snapframe / a visual check. Use whenever you add or edit docs that describe code, APIs, components, or live samples.
Render a live Tesserae C# UI block — Neko compiles and executes the C# at build time and shows both the code and a working preview side-by-side. Use only when the project documents Tesserae or runs live C# samples.
Render C# API docs from a code block with XML doc comments (`/// <summary>`, `<param>`, `<returns>`, etc.). Use to embed API reference inline without a separate generator.