pneuma-preferences

Maintain persistent user preferences across sessions to guide design decisions.

154|15|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/pandazki/pneuma-skills --skill pneuma-preferences
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pneuma-preferences
Source: https://github.com/pandazki/pneuma-skills/tree/main/modes/_shared/skills/pneuma-preferences
Command: npx skills add https://github.com/pandazki/pneuma-skills --skill pneuma-preferences

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Persistent memory of user preferences across sessions to guide design decisions and maintain consistency across modes, eliminating repeated constraint corrections.

Core Features & Use Cases

  • Cross-mode memory of aesthetics, language, and collaboration style, enabling consistent design choices in every task.
  • Per-mode preferences (mode-{name}.md) that tailor behavior for slide, doc, or evolve-like workflows.
  • Living-document approach with full refresh capability and changelog tracking to adapt to evolving user needs.

Quick Start

Consult the stored preferences at ~/.pneuma/preferences/ before starting any design task to apply the user's remembered constraints.

Frequently Asked Questions about pneuma-preferences

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain design consistency across multiple sessions?

Persistent user preferences preserve design choices across sessions by storing aesthetics, language, and collaboration style locally. This eliminates repeated constraint corrections and maintains consistency across slide, doc, and webcraft workflows.

What is a living-document approach for user preference management?

A living-document approach for user preference management continuously adapts to evolving needs using a three-layer model with cross-mode settings, deep profiles, and per-mode configurations. It supports full refresh capabilities and tracks all changes via a changelog.

Can I set different design preferences for slide, doc, and webcraft modes?

Yes, you can set different design preferences for slide, doc, and webcraft modes. The system uses per-mode preference files (mode-{name}.md) to tailor behavior specifically for each workflow while maintaining a core cross-mode profile.

How do I initialize design preferences when correcting style choices?

Design preferences are initialized automatically whenever you correct style choices during a creative task. The system captures these corrections to update your deep profile and per-mode settings before starting subsequent tasks.

Where are user profile and design preference files stored?

User profile and design preference files are stored locally at the ~/.pneuma/preferences/ directory. Consulting this directory before starting a design task ensures your remembered constraints are properly applied.