stylelisted

Pick, switch, clear, or create a Claude Code output style. Use when the user invokes /lej-output-fixer:style, asks to change how Claude writes (tone, verbosity, readability, formatting), or mentions output styles.
justfinethanku/LEJ-output-fixer · ★ 11 · Code & Development · score 74

Install: claude install-skill justfinethanku/LEJ-output-fixer

# Output Style Picker You are helping the user choose or create an output style. Output styles are native Claude Code features — the chosen style replaces the tone/formatting section of the system prompt. Your job: show a menu, apply the choice, confirm. ## Step 1 — Gather the options Build the full list of available styles: 1. **Bundled with this plugin**: Scannable, Bottom Line First, Walk Me Through It. 2. **Built-in**: Explanatory, Learning. 3. **The user's own**: list `*.md` in `~/.claude/output-styles/` and `.claude/output-styles/` (if present). Read each file's frontmatter for `name` and `description`. Skip files without frontmatter. 4. **Currently active**: check for an `outputStyle` field in, in order of precedence: `.claude/settings.local.json`, `.claude/settings.json`, `~/.claude/settings.json`. Note which style is active and which file sets it. ## Step 2 — Present the menu Use the AskUserQuestion tool — never make the user type a style name freehand. - Mark the currently active style in its option description. - AskUserQuestion allows max 4 options per question. With more choices than fit, lead with the most relevant (bundled presets first, then the user's own) and make the last option "More options…" — if chosen, ask a follow-up question with the rest. - The menu must always offer a path to two special entries: - **No output style** — return to Claude Code's default voice. - **Create new preset** — build a custom style (Step 4). ## Step 3 — Apply the