Agent skill · supabase
edit-the-docs
Restructure, reorder, and improve existing Supabase docs pages under apps/docs — clarity, connective text, section grouping, and brevity. Use when asked to edit, reorganize, restructure, tighten prose, or add glue between sections on a page that already exists. Not for net-new feature drafts (use write-the-docs) or PR triage/verification (use review-the-docs).
What it needs
About 3k tokens when loaded.
What this skill does
Edit the docs Improves existing Supabase docs pages: structure, order, connective text, and clarity. Distinct from write-the-docs (draft net-new or product-grounded rewrites from intent + code) and review-the-docs (lint, build, PR triage). Core rules 1. Read before you rewrite. Open the target page and nearby pages of the same type. Name the reader's goal and the page type (explainer, guide, tutorial, troubleshooting) before moving sections. 2. Improve structure and clarity; don't invent product truth. Preserve behavior claims, UI labels, and positioning unless you verify a change against code or product intent. Accuracy gaps or missing net-new content belong with write-the-docs / pm-the-docs, not silent invention here. 3. Follow CONTRIBUTING.md and WORDLIST.md for voice, terminology, and formatting. See apps/docs/CONTRIBUTING.md and apps/docs/WORDLIST.md. 4. Prefer brevity. Prefer broad strokes when mechanical detail doesn't help the reader's task. Cut redundancy; don't over-explain. 5. Reuse sibling skills. IA/architecture via ask-the-docs; validation and self-review via review-the-docs. Shared pitfalls live in write-the-docs/reference/common-pitfalls.md — apply them, don't duplicate them. Phase 1 — Diagnose 1. Identify the document type per CONTRIBUTING.md (explainer, tutorial, guide, reference, or troubleshooting). 2. State the reader's goal and prerequisites in one or two lines. 3. Note structural problems: mixed information types interrupting a procedure, missing intro navigation on a long page, weak transitions, redundancy, or over-explained mechanics. 4. Summarize the diagnosis to the requester before large moves when the restructure would change how the page is read. Phase 2 — Restructure Apply the Mixed information types, Navigation, and Cross-references and glue guidance in apps/docs/CONTRIBUTING.md (Guides section), summarized here: 1. Classify substantial sections as contextual, procedural, or reference content. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills supabase/edit-the-docs