document-design

Designs paginated documents with semantic hierarchy, reading order, and accessible PDF structure.

1|Updated Sep 11, 2026
One-click install
npx skills add https://github.com/rebuildup/my-web-2026 --skill document-design-rebuildup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: document-design
Source: https://github.com/rebuildup/my-web-2026/tree/main/skills/document-design
Command: npx skills add https://github.com/rebuildup/my-web-2026 --skill document-design-rebuildup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long-form documents like reports, proposals, and white papers often end up as unstructured text dumps with broken pagination, inconsistent headings, and inaccessible PDF exports. This Skill treats documents as designed artifacts with deliberate information hierarchy, page architecture, and reading order. ## Core Features & Use Cases - Semantic-first design workflow: Classifies content into title, summary, section, body, table, figure, caption, and reference types before applying any visual styling, ensuring heading levels reflect document outline rather than font sizes. - Pagination and page architecture control: Prevents orphaned headings, split tables, detached captions, and bad page breaks by adjusting heading-figure-caption relationships per page. - Accessible export verification: Validates tagged PDF structure, heading tags, table markup, reading order, and alt text using W3C WCAG PDF techniques and accessibility checkers. - Use Case: When producing a 40-page technical white paper as a PDF, use this Skill to structure the hierarchy, keep figures near their captions, and verify the exported PDF passes tagged-structure and reading-order checks. ## Quick Start Use the document-design skill to structure and review my report draft so its headings, tables, figures, and exported PDF reading order are properly designed.

Frequently Asked Questions about document-design

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

FAQPage Schema
How do I design an accessible report or white paper PDF?

Start with semantic structure: classify content into headings, body, tables, figures, and captions before styling. Then verify the exported PDF has tagged headings, correct reading order, table header markup, and alt text using accessibility checkers or screen readers.

How to fix bad page breaks and orphaned headings in documents?

Adjust heading, figure, caption, and table relationships per page instead of letting breaks happen automatically. Review page thumbnails to spot orphaned headings, split tables, detached captions, and excessive whitespace, then rebalance content flow.

Does a clean Word document guarantee an accessible PDF export?

No. A well-structured source document does not guarantee tagged PDF output. You must separately verify the exported PDF's heading tags, reading order, table structure, links, and alt text with accessibility tools.

When should I avoid multi-column layouts in documents?

Avoid multi-column layouts when you cannot verify the exported reading order, since columns frequently break logical sequence in PDFs. Single-column layouts with clear hierarchy are preferred for public-facing accessible documents.

Why should tables not be used for page layout?

Layout tables confuse assistive technologies because they lack meaningful row and column header relationships. Reserve tables for genuine tabular data with clear header structure, and control layout through page grids, margins, and spacing instead.