Run any Skill in Manus with one click

draft-conceptual

Stars39

Forks17

UpdatedJune 30, 2026 at 19:12

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

warpdotdev

warpdotdev/docs

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Technical WritersArts, Design, Entertainment, Sports, and Media Occupations·SOC 27-3042

SKILL.md

readonly

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 conceptual page

Draft a conceptual documentation page that explains what a feature or concept is, why it matters, and how it works at a high level.

Workflow

Follow the workflow in .warp/skills/draft_docs/SKILL.md, using the conceptual template at .warp/templates/conceptual.md.

Content type rules

These rules are specific to conceptual pages (from the "Drafting by content type" section of AGENTS.md):

Explain "what" and "why" before "how"
Define new terms when they first appear
Use diagrams or architecture descriptions where they clarify relationships
Do NOT include step-by-step procedures — link to a procedural or quickstart page instead
Show real-world scenarios, not just abstract descriptions
Title convention: noun or "About [subject]"

Heading case

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 Context

Existing examples

Read 2-3 of these strong examples to match the existing pattern:

src/content/docs/platform/deployment-patterns.md
src/content/docs/platform/index.mdx

More from this repository

same repository

sync-error-docs

warpdotdev/docs

Detect new platform error codes in warp-server that are missing documentation pages in the docs repo. Creates doc pages, astro.config.mjs (sidebar config) entries, and redirects for any gaps. Use on a weekly schedule or when error codes change.

2026-07-1039

sync-openapi-spec

warpdotdev/docs

Sync the public Oz Agent API OpenAPI spec from warp-server into the docs repo, regenerating `developers/agent-api-openapi.yaml` (the file that powers the Scalar API reference at `docs.warp.dev/api`). Use when the warp-server public API has changed, when the Scalar reference looks stale, or on a scheduled cadence to keep the public API docs aligned with the canonical spec.

2026-07-1039

sync-terminology

warpdotdev/docs

Sync the Warp terminology glossary from the Notion Dictionary to the repo. Fetches the Notion Dictionary page, compares with .warp/references/terminology.md, and opens a PR for any additions or changes. Flags repo-only terms that are missing from Notion. Use on a weekly schedule or manually when terminology changes.

2026-07-1039

update-changelog

warpdotdev/docs

Update the public changelog at docs.warp.dev/changelog with the latest stable release. Fetches changelog data from channel-versions, formats a new entry, and opens a PR. Use after a stable release ships (typically Fridays).

2026-07-1039

afdocs-audit

warpdotdev/docs

Audit docs.warp.dev for agent-friendly documentation issues using the AFDocs scorecard. Checks llms.txt, markdown availability, content negotiation, page size, URL stability, and content structure. Use when asked to check agent readiness, run an AFDocs audit, improve the docs score, or verify llms.txt and markdown support.

2026-07-1039

release-updates

warpdotdev/docs

Run weekly release docs updates with standalone scripts for changelog, licenses, and telemetry, plus Linux/Oz Warp artifact preparation. Defaults to running all tasks in order, and supports running only selected tasks.

2026-07-0939

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 conceptual page

Draft a conceptual documentation page that explains what a feature or concept is, why it matters, and how it works at a high level.

Workflow

Follow the workflow in .warp/skills/draft_docs/SKILL.md, using the conceptual template at .warp/templates/conceptual.md.

Content type rules

These rules are specific to conceptual pages (from the "Drafting by content type" section of AGENTS.md):

Explain "what" and "why" before "how"
Define new terms when they first appear
Use diagrams or architecture descriptions where they clarify relationships
Do NOT include step-by-step procedures — link to a procedural or quickstart page instead
Show real-world scenarios, not just abstract descriptions
Title convention: noun or "About [subject]"

Heading case

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 Context

Existing examples

Read 2-3 of these strong examples to match the existing pattern:

src/content/docs/platform/deployment-patterns.md
src/content/docs/platform/index.mdx