← ClaudeAtlas

diataxis-checklisted

Review one existing technical-documentation page or small fragment using Diátaxis as a content-design framework. Use when the user asks whether a documentation page is well structured, logically scoped, organized around the intended reader's need, appropriate for its audience, or how it could be improved according to Diátaxis. Establish the intended reader and desired outcome from requester-provided context when available; otherwise infer them from the page as hypotheses rather than ground truth. Compare the page's apparent purpose with its intended purpose before applying the Diátaxis compass and mode-specific diagnostic guidance. Identify the most important page-level problem and recommend one focused improvement. Classification is an intermediate reasoning step, not the goal of the review.
warstellar/agent-skills · ★ 1 · AI & Automation · score 62
Install: claude install-skill warstellar/agent-skills
# Diátaxis Check Review one existing documentation page or small fragment. The goal is to determine: - what the page appears to help its intended reader do or understand; - what kind of documentation would best serve that need; - whether the page's scope, structure, and content support that purpose; - what single change would improve it most. Use Diátaxis as a reasoning framework, not as a compliance checklist. ## Terminology Keep these roles distinct: - **Requester** — the person asking for the review. - **Reader** or **intended reader** — the person the documentation itself is meant to serve. When reasoning about needs, competence, work, study, goals, or understanding, refer to the documentation reader, not the requester. ## Scope By default, review one page or a small supplied fragment. Focus on page-level content design: - purpose; - reader need; - scope; - grouping; - sequence or organization; - fit between the reader need and the documentation form; - placement of supporting material; - interruptions to the reader's current purpose. Do not automatically expand the review into a site-wide information architecture analysis. If only a fragment is supplied, make claims only about that fragment unless the surrounding page is visible. ## Establish the reader situation Do not treat the page as authoritative evidence of its own intended purpose. Keep two things distinct: - **Intended reader and outcome** — who the documentation is supposed to serve and wha