Docs Page Skill

SkillDocs & knowledge

docs-page is a skill that generates a complete documentation web page with navigation sidebar, article content, and table of contents. It builds a single self-contained HTML file styled as a documentation site, with a sticky left-side navigation, a central article, and a right-hand outline that tracks scrolling. The skill follows the project's design system tokens and writes realistic example content such as commands and parameter tables.

Use Docs Page Skill in Claude, ChatGPT or Ahel Desktop

Free. Sign in, add Docs Page Skill and connect your AI. About a minute.

Also: Claude Code · Cursor · Codex

Then ask your AI: use the Docs Page Skill skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Make sure the project has a design system with tokens for fonts, colors, and spacing.

Docs Page SkillStart free

What your AI can do with it

  • Generates a single self-contained HTML documentation page
  • Adds a sticky left-side navigation menu
  • Builds a central article with headings, code snippets, tables, and callouts
  • Creates a right-hand 'on this page' outline that tracks scrolling
  • Follows the project's design system tokens for fonts, colors, and spacing
  • Checks readability at different screen widths, including RTL layouts

Getting started

  1. Make sure the project has a design system with tokens for fonts, colors, and spacing.
  2. Add the docs-page skill to your agent's available skills.
  3. Provide a brief that mentions docs, documentation, guide, API reference, or tutorial.
  4. Let the agent generate the HTML file and review the output at different screen widths.

What this skill tells your AI

The instructions your AI receives, as published by nexu-io/open-design in design-templates/docs-page/SKILL.md and read by ahel’s review.

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.

Signals

GitHub stars
99k
Forks
11k
Last commit
Oct 2026

ahel review

  • K1info
    remote-installer-piped-to-shell (in example.html)
  • K1binfo
    installs-packages (in example.html)

Automated review, not a security audit. Ruleset v1+k2.

Questions

What kind of output does docs-page produce?
A single self-contained HTML file styled as a documentation site, with a sticky left-side navigation, a central article, and a right-hand outline that tracks scrolling.
When should I use this skill?
Use it when the brief mentions docs, documentation, guide, API reference, or tutorial.
Does it support right-to-left layouts?
Yes, the skill checks readability at different screen widths including RTL layouts.
Advanced
Item type
skill
Key
docs-page-2
Source
github.com/nexu-io/open-design