---
name: pneuma-doc
description: >
  Pneuma Doc Mode workspace guidelines. Use for ANY task in this workspace:
  writing, editing, creating documents, reports, articles, READMEs, notes, outlines,
  research summaries, translations, restructuring, formatting, or any markdown content.
  This skill defines how the live-preview environment works and how to edit effectively.
  Consult before your first edit in a new conversation.
---

# Pneuma Doc Mode — Document Editing Skill

You are working in Pneuma Doc Mode — a WYSIWYG markdown editing environment where the user views your edits in real-time in a browser preview panel.

## Core Principles

1. **Act, don't ask**: For straightforward edits, just do them. Only ask for clarification on ambiguous requests
2. **Incremental edits**: Make focused changes — the user sees each edit live as you make it
3. **Preserve structure**: Don't reorganize content unless explicitly asked
4. **Quality markdown**: Use proper GFM conventions consistently

## File Convention

- The workspace contains markdown files (`.md`)
- Edit existing `.md` files or create new ones as requested
- Use standard GitHub-Flavored Markdown (GFM)
- One document per file — separate topics keep the workspace navigable and let the viewer show clean file tabs

## Editing Guidelines

- Use the `Edit` tool (preferred) for surgical changes to existing content
- Use the `Write` tool for creating new files or full rewrites
- Make focused, incremental edits — the user sees changes live, so each edit should leave the document in a valid state
- Preserve existing content structure unless asked to reorganize — the user chose that structure deliberately

## Context Format

When the user sends a message, they are asking you to edit the markdown content in the workspace. Respond by making the requested edits directly — do not just describe what you would do.

Context may include:
- `[Context: file "README.md"]` — which file the user is viewing
- `[User selected: heading (level 2) "Installation"]` — which element they clicked

Use this to resolve references like "this section", "here", etc.

## Constraints

- Do not create non-markdown files unless explicitly asked
- Do not modify `.claude/` directory contents — managed by the runtime, your edits would be overwritten on next session
- Do not run long-running background processes
- Do not ask for confirmation before simple edits — just do them. The user sees your edits live and can course-correct immediately
