write-a-docs-page

Writes documentation pages under docs/ following the repository's documentation standards.

Updated Sep 20, 2026
One-click install
npx skills add https://github.com/AmirOssanloo/helix-game --skill write-a-docs-page-amirossanloo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-a-docs-page
Source: https://github.com/AmirOssanloo/helix-game/tree/main/.claude/skills/write-a-docs-page
Command: npx skills add https://github.com/AmirOssanloo/helix-game --skill write-a-docs-page-amirossanloo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing documentation that violates a project's standards creates duplicated rules, broken links, and pages that answer multiple questions at once. This Skill enforces the order of operations and the checks people skip when adding or rewriting pages under docs/. ## Core Features & Use Cases - Page type selection: Forces exactly one of five page types (architecture, standards, decision record, runbook, product) so each page answers a single question. - Rule ownership checks: Verifies which existing page owns each rule before restating it, using one sentence and a link elsewhere. - Standards enforcement: Applies the page skeleton (entry point breadcrumb, Anti-patterns, Quick reference, Related documentation), sentence-case headings, relative links, and index updates in folder README files. - Use Case: When adding a new ADR, the Skill directs you to copy docs/adr/0000-template.md, take the next number, and register the page in the folder index. ## Quick Start Use the write-a-docs-page skill to add a new architecture page under docs/ that follows the documentation standards.

Frequently Asked Questions about write-a-docs-page

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a documentation page that follows project standards?▼

Read the documentation standards contract first, pick exactly one of the five page types, and follow the page skeleton: title, entry point breadcrumb, purpose, sections, then Anti-patterns, Quick reference, and Related documentation for architecture and standards pages.

How do I create a new ADR decision record?▼

Copy docs/adr/0000-template.md, take the next available number, and never reuse or change a number. After writing, add the page to the folder's README.md index and verify all links resolve.

What are the five documentation page types?▼

The five types are architecture pages, standards pages, decision records (ADRs), runbooks, and product pages. Each page must answer exactly one question; if it answers two, it should be split into two pages.

When should a rule be restated on another documentation page?▼

A rule should only be fully stated on the page that owns it, determined by the 'Where a rule belongs' section of the standards. Other pages get one sentence and a link to the owning page.

Why should documentation avoid facts the code owns?▼

Facts owned by code drift out of date when the code changes. The standards require writing a pointer instead, and adding a row to the where-to-look page if the pointer is missing.