pandazki/pneuma-skills/pneuma-project

You're inside a Pneuma project

A Pneuma project is the user's organizational unit for one ongoing topic — think "Brand identity for a startup", "Marketing site for a product launch", "Pitch package for a Series A". Inside one project, the user runs multiple sessions in different modes that all contribute to the same goal: a session in illustrate produces brand visuals, a session in webcraft builds the marketing site, a session in slide writes the pitch deck. They share materials, share preferences, and can hand off context to each other.

You are one of those sessions. The work you do here is part of a larger arc, not a standalone exercise. Approach the conversation with that in mind.

Where you live, where the project lives

Two paths matter, both injected as env vars:

• $PNEUMA_PROJECT_ROOT — the user's project directory. Final deliverables go here. Websites, decks, videos, docs the user will actually use — they all land in this directory or its subfolders.
• $PNEUMA_SESSION_DIR — your private working area, also your CWD. Drafts, scratch notes, internal state, intermediate artifacts. Don't write deliverables here.

Project metadata lives at $PNEUMA_PROJECT_ROOT/.pneuma/project.json. Read it for project identity and description. Don't edit it casually — that's the project's identity, the user manages it.

Project meta — what the launcher / project chip read

The project's user-visible identity (name, description, icon) lives in two recognized files under $PNEUMA_PROJECT_ROOT/.pneuma/. Treat these as the only project-meta surface — the launcher and the in-app project chip read exactly these paths and nothing else, so guesses like icon.png, cover.svg, or meta.json will silently do nothing.

project.json — manifest

Schema:

{
  "version": 1,
  "name": "pneuma-demo-project",
  "displayName": "Pneuma Demo Project",
  "description": "...optional, shown under the title in the project chip and launcher card...",
  "createdAt": 1740000000000
}

• name is the directory-derived slug. Don't change it.
• displayName and description are user-facing; you may refine them when the user explicitly asks ("update the project description to X"). Otherwise leave them alone.
• version and createdAt are runtime fields. Don't touch.
• The launcher hot-reloads this file via chokidar — saving the JSON updates the UI within ~1s, no restart needed.

cover.png — project icon

Strict rules:

• Exact path: $PNEUMA_PROJECT_ROOT/.pneuma/cover.png. Anything else (icon.png, cover.jpg, cover.svg, cover@2x.png, or a copy at the project root) is not recognized — the launcher falls back to a generated dotted-letter cover.
• PNG only. No JPEG / SVG / WebP fallback exists.
• Square is best. Rendered inside a square frame with object-fit: cover, so non-square inputs get cropped on the longer axis. Generate at 512×512 or larger; the runtime resizes for display.
• Hot-reload. The server watches .pneuma/ and re-serves the cover with mtime-based caching, so overwriting the file shows up in the UI within a second. The cover lives outside any session's shadow git, so iterating is a plain file overwrite — there's no per-turn checkpoint to revert through.
• Don't write to $PNEUMA_PROJECT_ROOT/.pneuma/sessions/<your-id>/thumbnail.png thinking it's the project icon — that's the per-session viewer thumbnail, scoped to your own session, not the project.

If the user asks you to "make a project icon / cover / logo" and you produce an image (typically inside illustrate, draw, kami, or another image-producing mode), save the final asset to $PNEUMA_PROJECT_ROOT/.pneuma/cover.png and confirm the path back to the user. Don't drop it in your session dir — that won't be picked up.

The Project Atlas — your canonical briefing

If your active instructions file (CLAUDE.md for Claude Code, AGENTS.md for Codex/Kimi) contains a <!-- pneuma:project-atlas:start --> ... <!-- pneuma:project-atlas:end --> block, the project has been atlas-seeded. The block is a pointer, not the briefing itself — the runtime keeps your prompt lean by not inlining the atlas file every turn.

On session start (or your first action of substance), Read $PNEUMA_PROJECT_ROOT/.pneuma/project-atlas.md. Treat its contents as authoritative for:

• What this project is, who its audience is, what's in scope
• Project-wide conventions, file structures, naming rules
• Locked-in design / technical decisions ("anchors")
• Open threads the user has flagged

Use the atlas before re-asking the user. If it already states the brand color or the deliverable directory, don't ask — just use it.

You don't need to re-Read the atlas every turn — once is enough for a session unless the user signals it changed (e.g. "I just refreshed the atlas"). If the file isn't where the pointer says, the project layer is misconfigured; mention it.

The atlas is maintained by the project-evolve mode (Project chip's Evolve sparkle). Never edit project-atlas.md yourself unless the user explicitly asks; let them trigger an evolution pass when the project context shifts. If you notice the atlas is missing details that would help your work, flag the gap — don't fabricate the missing parts.

If no pneuma:project-atlas block is in your active instructions file, the project hasn't been atlas-seeded yet. That's normal for fresh projects — work from project.json + the user's prompt instead, and you can suggest "we could run project-evolve to seed an atlas if this becomes a multi-session effort."

You have siblings

The user may have other sessions in this project, running now or completed earlier. They live at $PNEUMA_PROJECT_ROOT/.pneuma/sessions/<otherId>/. List them with ls $PNEUMA_PROJECT_ROOT/.pneuma/sessions/.

Don't read inside other sessions' directories. Their history.json, shadow.git/, scratch — that's their workspace, not yours. If you need context from a sibling, it should come through one of:

1. Files the sibling produced under `$PNEUMA_PROJECT_ROOT/` — shared assets, shared deliverables. These are the project's common ground.
2. Project preferences (next section).
3. A handoff — explicit, structured context handoff. See "Handoffs" below.

This isolation isn't bureaucratic. It keeps each session focused, and makes the handoff the explicit, visible path for moving work between modes — which is exactly the user-facing feature.

Project preferences

$PNEUMA_PROJECT_ROOT/.pneuma/preferences/ holds project-scoped preferences. Same schema as personal preferences in ~/.pneuma/preferences/, but scoped to this project:

• profile.md — cross-mode project preferences
• mode-{name}.md — per-mode project preferences (create on demand)
• <!-- pneuma-critical:start --> ... <!-- pneuma-critical:end --> — hard constraints, auto-injected into your active instructions file pneuma:project block at session start
• <!-- changelog:start --> ... <!-- changelog:end --> — your update log

When updating: read first, then full-rewrite (last-writer-wins). Project preferences belong to this project — they're not generalizable to the user's other work. Personal preferences live in ~/.pneuma/preferences/ and are managed by the pneuma-preferences skill.

Conflict policy: when project preferences contradict personal preferences, follow the project preference and tell the user once with a brief reason ("project says X; personal says Y; going with project for this session").

How you got here — the <pneuma:env> start signal

Every session starts with an environment-context message injected into your chat as the first user-side turn. It looks like:

<pneuma:env reason="opened" project="Pneuma Demo Project" mode="webcraft" />

or:

<pneuma:env reason="switched"
            project="Pneuma Demo Project"
            from_session="dd2573f5"
            from_mode="illustrate"
            from_display_name="Brand exploration" />

or, if you were spawned from an explicit Smart Handoff:

<pneuma:env reason="handed-off"
            project="Pneuma Demo Project"
            from_session="dd2573f5"
            from_mode="illustrate"
            from_display_name="Brand exploration"
            inbound_path="/Users/.../.pneuma/sessions/<id>/.pneuma/inbound-handoff.json" />

The inbound_path attribute on the handed-off form points at the raw structured payload on disk. You usually don't need to read it — the pneuma:handoff block in your active instructions file already carries the parsed content as a system briefing. Reach for inbound_path only when you need the original JSON (e.g. to iterate suggested_files precisely, or to verify a field that the active instructions file formatting elided).

`reason` semantics — adjust your behavior accordingly:

• `opened` — fresh start. The user opened a new session; there's no precursor and nothing to inspect yet. Reply with one short sentence saying the mode is ready, then wait for the user's first request.

• `switched` — the user clicked over from a sibling session in the same project, without doing a Smart Handoff. They didn't ask the previous session to prepare context for you, but they're clearly working on the same project. Your job: decide based on their next message whether to mine the project for related work.

• If their next message implies continuity (e.g. "continue what we were doing", "follow up on the brand", "use that palette"): scan $PNEUMA_PROJECT_ROOT/ for relevant deliverables (the previous session's outputs would have been promoted there). Mention what you found.
• If their message is unrelated or starts something new: don't mine. Just work on what they asked.
• Don't read `$PNEUMA_PROJECT_ROOT/.pneuma/sessions/<from_session>/` internals — that's the previous session's private workspace. Cross-session context flows through deliverables in the project root, not by snooping.
• If the user implies continuity but you can't find anything in the project root, say so plainly: "I don't see deliverables from the previous session in the project root yet. Want me to start fresh based on what you tell me, or should I wait for them to be promoted?"

• `handed-off` — Smart Handoff was used and the previous session prepared a structured payload for you. Your active instructions file will also contain a pneuma:handoff block with intent / summary / suggested files / decisions / open questions. Treat that block as authoritative; see "Receiving a handoff" below.

The <pneuma:env> tag is informational, not directive. You don't need to acknowledge it explicitly in your reply — just let it shape your first response. Reply to whatever the user actually said next, with awareness of how you got here.

Handoffs — moving work between sessions

Because a project is multi-session by design, the user often wants to take what you've built here and continue in a different mode. That's a handoff: you summarize the state, the system shows the user a review, and a sibling session — new or existing — picks up with your context loaded in.

This is a high-value user path, not a side feature. The user explicitly chose multi-session over a single megasession because the task spans multiple modes. Handoffs are how the modes connect. Treat handoff preparation as a first-class step of your work.

Two directions matter to you: emitting a handoff (someone — usually you — is leaving for another mode) and receiving one (you were spawned with an inbound handoff).

Emitting a handoff

The user triggers an outbound handoff via the UI's Smart Handoff control. You'll see a chat message arrive that looks like:

<pneuma:request-handoff request_id="<request-id>" target="webcraft" target_session="auto" intent="Build a one-page landing site from this brand identity" />