القائمة
Render a lesson/curriculum header that auto-discovers sibling Markdown files as steps and tracks completion in localStorage. Use to build interactive courses, tutorials, and learning tracks.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
| name | lesson |
| description | Render a lesson/curriculum header that auto-discovers sibling Markdown files as steps and tracks completion in localStorage. Use to build interactive courses, tutorials, and learning tracks. |
A lesson block is a curriculum-style header. Place it at the top of an index
page in a folder; Neko picks up the sibling .md files as steps and renders a
progress tracker. Completion is stored per-visitor in localStorage.
[!lesson
title="Course Title"
description="One-paragraph course description."
badge="Course completion badge"
prerequisites="Item 1 | Item 2 | Item 3"
up-next-title="Next steps"
up-next-summary="Where to go after finishing this track."
up-next-link="/next/course"
]
| Attribute | Notes |
|---|---|
title | Course / track title. |
description | Intro sentence shown under the title. |
badge | Label of the badge awarded on completion. |
prerequisites | ` |
up-next-title | Heading of the "what's next" card shown on completion. |
up-next-summary | Body of the "what's next" card. |
up-next-link | Destination of the "what's next" card. |
guides/
├── learn-neko/
│ ├── index.md ← contains [!lesson …]
│ ├── 01-install.md
│ ├── 02-first-page.md
│ ├── 03-add-components.md
│ └── 04-deploy.md
The order of steps follows the same rules as the sidebar
(order: in each step's frontmatter, then alphabetical).
Each generated step page automatically gets a "Go back: …" /
"Next step: …" navigation block at the bottom, linking to its siblings in
the same curriculum order. No configuration needed — it appears whenever the
folder's index.md/README.md contains [!lesson …].
[!lesson
title="Learn Neko"
description="Hands-on track from install to deployment in under 30 minutes."
badge="Neko Apprentice"
prerequisites=".NET 10 | Familiarity with Markdown | A terminal"
up-next-title="Advanced Neko"
up-next-summary="Now that you know the basics, try the advanced track."
up-next-link="/guides/learn-neko-advanced"
]
[!lesson …] at the very top of the folder's index.md.