Agent skill
pneuma-doc
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.
Install this agent skill to your Project
npx add-skill https://github.com/pandazki/pneuma-skills/tree/main/modes/doc/skill
SKILL.md
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
- Act, don't ask: For straightforward edits, just do them. Only ask for clarification on ambiguous requests
- Incremental edits: Make focused changes — the user sees each edit live as you make it
- Preserve structure: Don't reorganize content unless explicitly asked
- Quality markdown: Use proper GFM conventions consistently
File Convention
- The workspace contains markdown files (
.md) - Edit existing
.mdfiles 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
Edittool (preferred) for surgical changes to existing content - Use the
Writetool 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
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
pneuma-illustrate
Pneuma Illustrate Mode workspace guidelines. Use for ANY task in this workspace: generating images, creating illustrations, editing visuals, managing content sets, organizing rows, crafting prompts, adjusting styles, or any image generation task. This skill defines the generation workflow, manifest format, prompt engineering, and content set organization for the AI illustration studio. Consult before your first edit in a new conversation.
pneuma-preferences
Persistent user preference memory across sessions. Consult this skill BEFORE making any design, style, or aesthetic decisions — choosing colors, themes, layouts, fonts, tone of voice, content density, or visual direction. Also consult when starting a new creative task in any mode, when the user corrects your style choices, or when asked to analyze or refresh user preferences. Even if you think you know what to do, check preferences first — the user may have recorded specific constraints.
pneuma-webcraft
Pneuma WebCraft Mode workspace guidelines with Impeccable.style design intelligence. Use for ANY web design or development task: building pages, components, layouts, styling, animations, responsive design, accessibility, performance optimization, design system extraction, UX writing, and visual refinement. This skill defines how the live-preview environment works, the Impeccable design principles to follow, and the 20 design commands available. Consult before your first edit in a new conversation.
skill
pneuma-{{modeName}}
TODO: Describe what this mode's agent does and when it should activate. Example: "Expert at creating and editing [content type] in Pneuma {{displayName}} Mode. Works in a WYSIWYG environment where the user sees edits live in a browser preview panel."
pneuma-mode-maker
Pneuma Mode Maker workspace guidelines. Use for ANY task in this workspace: creating modes, editing manifest.ts, pneuma-mode.ts, viewer components, skill prompts, seed files, publishing, forking, or any mode package development. This skill defines the ModeManifest reference, ViewerContract patterns, and publishing workflow. Consult before your first edit in a new conversation.
Didn't find tool you were looking for?