openwhisper-project-principles

Codify OpenWhisper product principles for feature and UX decisions.

2|Updated Apr 22, 2026

Search Tags:#design #cross-platform #principles #ux #local-first #hotkeys

Ready to run

npx skills add https://github.com/jimmi-joensson/OpenWhisper --skill openwhisper-project-principles

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openwhisper-project-principles
Source: https://github.com/jimmi-joensson/OpenWhisper/tree/main/.claude/skills/openwhisper-project-principles
Command: npx skills add https://github.com/jimmi-joensson/OpenWhisper --skill openwhisper-project-principles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenWhisper project principles define the durable rules that govern feature proposals, UX consistency, monetization boundaries, and platform-specific behavior to ensure the product remains open, local-first, and easy to reason about.

Core Features & Use Cases

Enforces activation semantics (toggle activation, no wake-word) and cross-platform visual identity to maintain a cohesive user experience.
Provides decision guardrails for monetization, cloud features, and BYO-keys semantics to avoid paywalls on local features.
Serves as a reference for product managers, designers, and engineers to validate feature ideas, settings changes, and UX decisions before implementation.

Quick Start

Read these principles before proposing any feature, setting, or behavior change that could affect how the app feels to users; apply the guidelines to ensure consistency with OpenWhisper's open, local-first UX.

Frequently Asked Questions about openwhisper-project-principles

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

FAQPage Schema

How do I validate cross-platform UX decisions for a local-first app?▼

Cross-platform UX decisions for a local-first app are validated by checking feature proposals against codified product principles governing activation semantics, visual identity, and monetization boundaries. This ensures cohesive user experience without paywalls on local features.

What are local-first monetization policies and how do they affect feature design?▼

Local-first monetization policies restrict paywalls on local features by providing decision guardrails for cloud capabilities and BYO-keys semantics. They affect feature design by ensuring monetization boundaries avoid restricting native local processing functionality.

How do I maintain cross-platform visual identity when designing app settings?▼

Cross-platform visual identity is maintained by applying project-wide design tokens and activation rules to settings changes. Designers evaluate UX decisions against these durable rules to ensure the app feels consistent across all platforms.

Can I propose a wake-word activation feature for a cross-platform voice app?▼

Wake-word activation features cannot be proposed because the product principles enforce toggle activation semantics exclusively. Cross-platform activation rules strictly prohibit wake-word interactions to maintain an open, easy-to-reason-about user experience.

When do I need to apply product principles before implementing a new feature?▼

Product principles must be applied before implementing any feature, setting, or behavior change that affects how the app feels to users. Product managers and engineers read these guidelines to validate ideas against local-first UX constraints.

What is the best way to govern BYO-keys semantics in a local-first application?▼

The best way to govern BYO-keys semantics is using codified decision guardrails that evaluate monetization boundaries and cloud features. This approach prevents paywalls on local features and aligns with open-source product principles.