菜单
Draft a new conceptual documentation page or update an existing one. Use for pages that explain what something is, why it exists, and how it works — without step-by-step procedures. Examples include product overviews, architecture explanations, and design philosophy pages.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/warpdotdev/docs --skill draft-conceptual命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | draft_conceptual |
| description | Draft a new conceptual documentation page or update an existing one. Use for pages that explain what something is, why it exists, and how it works — without step-by-step procedures. Examples include product overviews, architecture explanations, and design philosophy pages. |
Draft a conceptual documentation page that explains what a feature or concept is, why it matters, and how it works at a high level.
Follow the workflow in .agents/skills/draft_docs/SKILL.md, using the conceptual template at .agents/templates/conceptual.md.
One sentence, 50-160 characters, saying what the concept is and why it matters. Start with the subject.
Environments give cloud agents the same toolchain and setup on every run, no matter what triggers them.Learn about environments and why they are useful.See "Descriptions by content type" under Frontmatter in AGENTS.md for the full rules.
These rules are specific to conceptual pages (from the "Drafting by content type" section of AGENTS.md):
All headings (H1–H4) must use sentence case: capitalize only the first word and proper feature names.
## How it works## When to use Codebase Context## How It Works## When To Use Codebase ContextRead 2-3 of these strong examples to match the existing pattern:
src/content/docs/platform/deployment-patterns.mdsrc/content/docs/platform/index.mdxFind documentation gaps in Warp's Astro Starlight docs by auditing coverage against code surfaces in the public warp client repo and warp-server and against the weekly release changelog, decide which gaps actually warrant docs, then draft only those. Use when asked to find missing docs, audit documentation coverage, identify undocumented features, draft docs for new features, detect doc-impacting code changes since the last audit, or do a docs coverage check. Runs a Python audit script (coverage + snapshot-based change detection), gates every candidate against the documentation-worthiness criteria, then researches source code and writes first-pass doc pages for the ones that pass. Can run audit-only, draft-only, drift-watch (release-triggered recurring agent), or end-to-end.
Scan Warp Astro Starlight documentation for UI menu paths and Command Palette command names, then validate them against the public warp client codebase for accuracy. Catch and surface outdated steps automatically.
Scan Warp Astro Starlight documentation for style guide violations including formatting issues (Settings path format, UI element format, link quality, VideoEmbed titles, header case, missing frontmatter, image alt text, standardized screenshot widths, callout syntax) and terminology issues (product name casing, Oz terms to avoid, deprecated terms). Run with --changed for PR workflows or --all for periodic audits. Optionally auto-fix high-confidence issues with --fix.
