メニュー
Wrap a chunk of Markdown in a `<div>` with custom CSS classes and HTML attributes. Use for layout helpers (center, max-width, background tint) and one-off styling without leaving Markdown.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | container |
| description | Wrap a chunk of Markdown in a `<div>` with custom CSS classes and HTML attributes. Use for layout helpers (center, max-width, background tint) and one-off styling without leaving Markdown. |
Generic block wrapper that emits a <div> with custom classes and attributes.
:::
Plain container — just a wrapping div.
:::
:::text-center
Centered content.
:::
:::callout-soft { #my-anchor .extra }
Extra classes and an id.
:::
The first token after the opening ::: becomes the primary CSS class. An
optional { … } block can add an #id and additional .classes.
Inside { … }:
#anchor-id — id attribute..foo .bar — extra classes.key="value" — arbitrary HTML attributes (use sparingly).:::text-center
This text is centered.
:::
:::bg-zinc-100 dark:bg-zinc-900 rounded-lg p-4
A soft panel with Tailwind utilities.
:::
:::grid { #features .gap-4 .grid-cols-3 }
Three columns of children.
:::
#id for cross-page anchors.Avoid containers for things that have a dedicated component — use
card, panel,
column, tab, or
alert instead.
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.