docs-page — Claude Code skill: documentation and setup
The docs-page skill builds a single-file HTML documentation page with navigation, an article, and a table of contents. Use it for guides, tutorials, or API references.
Apache-2.0 248 installs ★ 108,855 updated 2026-10-25
npx skills add nexu-io/open-design --skill docs-page -a claude-codeWhat docs-page does
The skill lays out three columns: navigation on the left, the article in the middle, and a table of contents on the right. It adds section headings, code blocks, notes, and links, with anchors for headings. Logical CSS directions let the layout flip for right-to-left reading.
The output is one HTML document with inline CSS. The page includes a table, a shell command, and a code sample; its copy-button is visual and needs no JavaScript. The skill reads the active DESIGN.md and follows its design tokens. Without that file, it cannot draw on your project’s design system.
What it helps with
- build a documentation page as one HTML file
- place navigation and a table of contents beside an article
- add code samples and a table to an API reference
- adapt a documentation layout for RTL reading
Example prompts for the agent
- Create an API documentation page with navigation and a table of contents.
- Build a guide as one HTML file using the active
DESIGN.md. - Draft a tutorial with a shell command, code sample, and table.
How to install docs-page
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill docs-page -a claude-code2Manually: put the files in place
~/.claude/skills/docs-page/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/docs-page/
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill docs-page -a codex2Manually: put the files in place
.agents/skills/docs-page/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill docs-page -a cursor2Manually: put the files in place
.cursor/skills/docs-page/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install nexu-io/open-design design-templates/docs-page/SKILL.md2Manually: put the files in place
.github/skills/docs-page/SKILL.md1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill docs-page -a gemini-cli2Platform CLI
gemini skills install https://github.com/nexu-io/open-design --path design-templates/docs-pageManually: put the files in place
.devin/skills/docs-page/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill docs-page -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about docs-page
How do I install docs-page in Claude Code?
Run npx skills add nexu-io/open-design --skill docs-page -a claude-code. The skill file will be at ~/.claude/skills/docs-page/SKILL.md.
What does docs-page do?
It creates a single-file HTML documentation page with navigation, an article, and a table of contents. The page includes code samples, a table, and a callout.
Does docs-page use a DESIGN.md file?
It reads the active DESIGN.md to apply the project’s typography tokens and design-system rules. The file gives the skill a design system to follow.
Source text
SKILL.md · Apache-2.0
---
name: docs-page
description: |
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".
triggers:
- "docs"
- "documentation"
- "guide"
- "tutorial"
- "api reference"
- "文档"
od:
mode: prototype
platform: desktop
scenario: engineering
preview:
type: html
entry: index.html
design_system:
requires: true
sections: [color, typography, layout, components]
craft:
requires: [typography, typography-hierarchy, typography-hierarchy-editorial, rtl-and-bidi]
---
# Docs Page Skill
Produce a single, three-column documentation page in one HTML file.
## Workflow
1. **Read the active DESIGN.md** (injected above). Use the body type token for
prose; the mono token for code; respect line-height and max-width rules.
2. **Pick a topic** from the brief — the page should look like real docs, not
a generic wireframe. Concrete API names, command examples, plausible
parameters.
3. **Lay out** three regions, expressed on the inline axis so the
layout flips correctly under `dir="rtl"`:
- **Inline-start nav** (240–280px, sticky): grouped link list, current
page bolded with an `inline-start`-edge accent stripe. 3–5 groups
of 4–8 links.
- **Article body** (max-width ~720px, centered in the middle column):
H1, lede paragraph, H2 sections, code blocks, callout boxes (note /
warning), inline links, lists.
- **Inline-end TOC** (200–240px, sticky): "On this page" with the
H2/H3 anchors, current section highlighted as the user scrolls.
4. **Write** a single HTML document:
- `<!doctype html>` through `</html>`, all CSS inline.
- CSS Grid for the three columns; sticky positioning for the rails.
- Code blocks: monospace token, soft surface fill, copy-button affordance
(visual only — no JS needed).
- Anchor IDs on every H2/H3 so the TOC links work.
- `data-od-id` on the nav, article, and TOC.
5. **Prose**: write at least 350 words of believable docs. Include at least
one shell command, one code snippet (5–15 lines), one callout, one table.
6. **Self-check**:
- Body text wraps at the DS line-length sweet spot (60–75 chars).
- Code uses the DS mono token, not generic `monospace`.
- Accent is restrained — used for active nav item, links, one callout
border. Not on body text.
- Page is readable at 1280w and collapses gracefully below 900w (TOC drops
out, nav becomes a top drawer).
- Use logical CSS (`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"`.
## Output contract
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.
© nexu-io · Apache-2.0 · nexu-io/open-design