pneuma-modename

Solid

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."

AI & Automation 154 stars 15 forks Updated today MIT

Install

View on GitHub

Quality Score: 85/100

Stars 20%
73
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
76
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Pneuma {{displayName}} Mode Skill You are working in Pneuma {{displayName}} Mode — a live editing environment where a 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 3. **Preserve structure**: Don't reorganize content unless explicitly asked ## File Convention - TODO: Describe the workspace file types (e.g., `.md`, `.html`, `.json`) - TODO: Describe file naming conventions - TODO: Describe any special files (manifests, configs, themes) ## Editing Guidelines - Use the `Edit` tool (preferred) or `Write` tool to modify files - Make focused, incremental edits — the user sees changes live - Preserve existing content structure unless asked to reorganize - Do not ask for confirmation on simple edits — just do them ## Workflow - TODO: Describe the typical workflow for creating new content - TODO: Describe how to edit existing content - TODO: List common operations (add, remove, reorder, etc.) ## Context Format When the user sends a message, context may include: - File they are currently viewing - Element they have selected Use this context to resolve references like "this", "here", etc. ## Constraints - Do not modify `.claude/` or `.pneuma/` directory contents - Do not run long-running background processes - Do not ask for confirmation before simp...

Details

Author
pandazki
Repository
pandazki/pneuma-skills
Created
5 months ago
Last Updated
today
Language
TypeScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Solid

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.

154 Updated today
pandazki
AI & Automation Solid

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.

154 Updated today
pandazki
AI & Automation Solid

create-mode

Author a new Pneuma mode end-to-end — manifest + viewer + skill + seed + showcase. Use this skill whenever the user says they want to create a new mode, fork an existing one for a different domain, scaffold mode files, design a new viewer, or asks "how should I build a mode for X". Walks the user through a discovery interview, produces a design brief that names every key choice (Source kind, ViewerAddress vocabulary, action space, seed strategy, external integrations, evolution directive), and only then generates the directory skeleton. Encodes the practice rules pulled from webcraft / slide / diagram / illustrate / remotion / kami. Pneuma Skills project only; Claude Code only.

154 Updated today
pandazki