A documentation page — inline-start nav, scrollable article body, inline-end table of contents. Use when the brief mentions "docs", "documentation", "guide", "API reference", or "tutorial".
Produce a single, three-column documentation page in one HTML file.
dir="rtl":
inline-start-edge accent stripe. 3–5 groups
of 4–8 links.<!doctype html> through </html>, all CSS inline.data-od-id on the nav, article, and TOC.monospace.margin-inline-start, border-inline-start,
inset-inline-end, text-align: start) on the rails and accent
stripe so the layout flips correctly under dir="rtl".Emit between <artifact> tags:
<artifact identifier="docs-slug" type="text/html" title="Docs — Page Title">
<!doctype html>
<html>...</html>
</artifact>
One sentence before the artifact, nothing after.
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/docs-page · pinned to the source commit
git clone https://github.com/nexu-io/open-design.git
cd open-design
git checkout d488b1aa87917daee40d7c61efd7decbb28b5455
mkdir -p ".claude/skills/docs-page"
cp -r "design-templates/docs-page" ".claude/skills/docs-page"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit d488b1aa8791. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.