How this command is triggered — by the user, by Claude, or both
Slash command
/prose:init [--global]The summary Claude sees in its command listing — used to decide when to auto-load this command
# /prose:init - Initialize Style Configuration Create unified style configuration directories for prose and copyedit plugins. ## Usage ## What This Creates ### Project Configuration (.style/) Running `/prose:init` creates: ### Global Configuration (~/.claude/style/) Running `/prose:init --global` creates: ## Configuration Hierarchy **Merge behavior:** - **Thresholds**: Project overrides global - **Wordlists**: Both combined (all terms active) - **Stoplists**: Both combined (all words blocked) - **Styleguides**: Both enforced (rules appended) - **Voice**: Project voice takes...
Create unified style configuration directories for prose and copyedit plugins.
/prose:init # Initialize .style/ in current project
/prose:init --global # Initialize ~/.claude/style/ for all projects
Running /prose:init creates:
.style/
├── config.yaml # Style thresholds and settings
├── styleguide.md # Project-specific style rules
├── wordlist.txt # Preferred terminology
├── stoplist.txt # Forbidden words
└── voice.yaml # Project voice profile (optional)
Running /prose:init --global creates:
~/.claude/style/
├── config.yaml # Global thresholds
├── styleguide.md # Personal style rules
├── wordlist.txt # Your preferred terms
├── stoplist.txt # Words you never use
└── voices/ # Voice profile library
├── technical.yaml
└── conversational.yaml
Plugin defaults (built-in)
↓ overridden by
Global config (~/.claude/style/)
↓ overridden by
Project config (.style/)
Merge behavior:
Both cc-prose and cc-copyedit plugins support legacy paths:
| New Path | Legacy Fallback |
|---|---|
.style/ | .copyedit/, .prose/ |
~/.claude/style/ | ~/.claude/copyedit/config/, ~/.claude/prose/ |
Existing configurations continue to work. New configurations should use the unified paths.
Initialize project configuration:
/prose:init
Output:
Created .style/ directory with:
- config.yaml
- styleguide.md
- wordlist.txt
- stoplist.txt
- voice.yaml
Next steps:
1. Edit .style/stoplist.txt to add blocked words
2. Edit .style/wordlist.txt to add preferred terms
3. Edit .style/styleguide.md for project-specific rules
Initialize global configuration:
/prose:init --global
Output:
Created ~/.claude/style/ directory with:
- config.yaml
- styleguide.md
- wordlist.txt
- stoplist.txt
- voices/technical.yaml
- voices/conversational.yaml
These settings apply to ALL projects by default.
When this command is invoked:
--global flag# For project initialization
python3 "$PLUGIN_ROOT/scripts/init_style_config.py" --init
# For global initialization
python3 "$PLUGIN_ROOT/scripts/init_style_config.py" --init-global
npx claudepluginhub rhuss/cc-prose --plugin prose/create-output-styleGenerates custom output style Markdown files for Claude Code with YAML frontmatter, instructions, behaviors, and principles. Saves to user (~/.claude/output-styles) or project (.claude/output-styles) directories with status output.
/writingInjects writing style rules from $ARGUMENTS into the current context to enforce consistent tone, voice, and formatting in responses.
/style-learnAnalyzes exemplar text files to extract writing style profile in YAML, including voice tone, vocabulary metrics, sentence stats, and representative passages. Supports custom names, merging, and interactive selection.
/output-style-setupPrompts for project or user-level choice, then installs bkit output styles by copying 4 .md files to .claude/output-styles/ or ~/.claude/output-styles/. Lists files and suggests activation.
/settingsView and manage global settings including article word limits and companion project defaults for code, document, diagram types. Supports show [type], set, reset subcommands.
/COMMANDConfigures session defaults for writing workflows: vault path for knowledge capture, default content type (article, tutorial, etc.), SEO preferences. Interactive setup if no args; saves to config.json.