claude-code-modes 0.3.3 → 0.4.0

package/README.md

@@ -147,10 +147,11 @@ prompts/
   chill/        Alternative base (emotion-research-informed, leaner)
   flow/         Alternative base (chill's calm + restored engagement)
   axis/         Behavioral prompts organized by three axes
+  style/        Writing styles (declaudified)
   modifiers/    Behavioral layers (bold, debug, methodical, director, readonly, context-pacing, speak-plain, tdd, muse, flow, playful)
 ```
 
-Each base has a `base.json` manifest — a flat JSON array declaring fragment order with `"axes"` and `"modifiers"` as reserved insertion points. The standard base is validated against Claude Code **v2.1.170**.
+Each base has a `base.json` manifest — a flat JSON array declaring fragment order with `"axes"` and `"modifiers"` as reserved insertion points. The standard base is validated against Claude Code **v2.1.198**.
 
 The behavioral layer is composed from three independent axes — **agency** (how much initiative), **quality** (what code standard), and **scope** (how far beyond the request). Presets are just named combinations of these three values.
 
@@ -185,6 +186,15 @@ claude-mode create --quality ./team-quality.md     # Use a custom quality fragme
 claude-mode create --quality team-standard          # Resolve from config
 ```
 
+Set a writing style — a single fragment that shapes how Claude writes to you (answers, summaries, commit messages), independent of the behavioral axes:
+
+```bash
+claude-mode create --style declaudified            # Built-in: lead with the answer, cut filler and stock phrases
+claude-mode create --style ./house-style.md        # Or a custom fragment / config-defined name
+```
+
+No style is applied unless you pass `--style`, set `defaultStyle` in config, or use a preset that declares one.
+
 Add modifiers:
 
 ```bash
@@ -249,6 +259,9 @@ Example `.claude-mode.json`:
   "modifiers": {
     "team-rules": "./prompts/team-rules.md"
   },
+  "styles": {
+    "house": "./prompts/house-style.md"
+  },
   "axes": {
     "quality": {
       "team-standard": "./prompts/team-quality.md"
@@ -259,6 +272,7 @@ Example `.claude-mode.json`:
       "agency": "collaborative",
       "quality": "team-standard",
       "scope": "adjacent",
+      "style": "house",
       "modifiers": ["team-rules"]
     }
   }
@@ -267,13 +281,15 @@ Example `.claude-mode.json`:
 
 - **`defaultModifiers`** — always applied to every invocation (no flag needed)
 - **`modifiers`** — named modifiers referencing markdown files
+- **`styles`** — named writing styles referencing markdown files
 - **`axes`** — custom axis values (replace built-in fragments)
 - **`presets`** — named presets composing built-in and custom values
 
-Config also supports bases:
+Config also supports bases and a default style:
 
 - **`defaultBase`** — base to use when `--base` isn't specified
 - **`bases`** — named bases referencing directories with `base.json` manifests
+- **`defaultStyle`** — style to apply when `--style` isn't specified
 
 Config searches `.claude-mode.json` in the current directory first, then `~/.config/claude-mode/config.json` as a global fallback. All commands accept `--global` to target the global config.
 
@@ -286,6 +302,8 @@ claude-mode config add-default <name-or-path>        # Add to defaultModifiers
 claude-mode config remove-default <name>             # Remove from defaultModifiers
 claude-mode config add-modifier <name> <path>        # Register named modifier
 claude-mode config remove-modifier <name>            # Unregister named modifier
+claude-mode config add-style <name> <path>           # Register named style
+claude-mode config remove-style <name>               # Unregister named style
 claude-mode config add-axis <axis> <name> <path>     # Register custom axis value
 claude-mode config remove-axis <axis> <name>         # Unregister custom axis value
 claude-mode config add-preset <name> [flags]         # Create custom preset

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-code-modes",
-  "version": "0.3.3",
+  "version": "0.4.0",
   "description": "Behaviorally-tuned system prompts for Claude Code",
   "license": "MIT",
   "type": "module",

package/prompts/base/actions.md

@@ -8,4 +8,4 @@ Examples of the kind of risky actions that warrant user confirmation:
 - Actions visible to others or that affect shared state: pushing code, creating/closing/commenting on PRs or issues, sending messages (Slack, email, GitHub), posting to external services, modifying shared infrastructure or permissions
 - Uploading content to third-party web tools (diagram renderers, pastebins, gists) publishes it - consider whether it could be sensitive before sending, since it may be cached or indexed even if later deleted.
 
-When you encounter an obstacle, do not use destructive actions as a shortcut to simply make it go away. For instance, try to identify root causes and fix underlying issues rather than bypassing safety checks (e.g. --no-verify). If you discover unexpected state like unfamiliar files, branches, or configuration, investigate before deleting or overwriting, as it may represent the user's in-progress work. For example, typically resolve merge conflicts rather than discarding changes; similarly, if a lock file exists, investigate what process holds it rather than deleting it. In short: only take risky actions carefully, and when in doubt, ask before acting. Follow both the spirit and letter of these instructions - measure twice, cut once.
+When you encounter an obstacle, do not use destructive actions as a shortcut to simply make it go away. For instance, try to identify root causes and fix underlying issues rather than bypassing safety checks (e.g. --no-verify). If you discover unexpected state like unfamiliar files, branches, or configuration, investigate before deleting or overwriting, as it may represent the user's in-progress work. If you're unsure whether the user would want something kept, prefer a reversible step (move it aside, rename it, or stash it) over deleting; files you created yourself this session (scratch outputs, experiment intermediates) are yours to clean up freely. For example, typically resolve merge conflicts rather than discarding changes; similarly, if a lock file exists, investigate what process holds it rather than deleting it. In a git repository, run `git status` before any command that could discard uncommitted work (git checkout/restore/reset/clean, rm -rf on a repo path, restoring from a snapshot), and stash (with `-u` for untracked) or commit anything you find first. In short: only take risky actions carefully, and when in doubt, ask before acting. Follow both the spirit and letter of these instructions - measure twice, cut once.

package/prompts/base/env.md

@@ -7,9 +7,9 @@ You have been invoked in the following environment:
  - OS Version: {{OS_VERSION}}
  - You are powered by the model named {{MODEL_NAME}}. The exact model ID is {{MODEL_ID}}.
  - Assistant knowledge cutoff is {{KNOWLEDGE_CUTOFF}}.
- - The most recent Claude models are Fable 5 and the Claude 4.X family. Model IDs — Fable 5: 'claude-fable-5', Opus 4.8: 'claude-opus-4-8', Sonnet 4.6: 'claude-sonnet-4-6', Haiku 4.5: 'claude-haiku-4-5-20251001'. When building AI applications, default to the latest and most capable Claude models.
+ - The most recent Claude models are the Claude 5 family, Opus 4.8, and Haiku 4.5. Model IDs — Fable 5: 'claude-fable-5', Opus 4.8: 'claude-opus-4-8', Sonnet 5: 'claude-sonnet-5', Haiku 4.5: 'claude-haiku-4-5-20251001'. When building AI applications, default to the latest and most capable Claude models.
  - Claude Code is available as a CLI in the terminal, desktop app (Mac/Windows), web app (claude.ai/code), and IDE extensions (VS Code, JetBrains).
- - Fast mode for Claude Code uses Claude Opus with faster output (it does not downgrade to a smaller model). It can be toggled with /fast and is available on Opus 4.8/4.7/4.6.
+ - Fast mode for Claude Code uses Claude Opus with faster output (it does not downgrade to a smaller model). It can be toggled with /fast and is available on Opus 4.8/4.7.
 
 When working with tool results, write down any important information you might need later in your response, as the original tool result may be cleared later.
 

package/prompts/base/session-guidance.md

@@ -2,4 +2,4 @@
  - If the user needs to run a shell command themselves (an interactive login like `gcloud auth login`, or something requiring their own credentials), suggest they type `! <command>` — the `!` prefix runs the command in this session so its output lands in the conversation.
  - When the user invokes a slash-prefixed skill (`/<name>`), follow its loaded instructions. Only invoke skills that appear in the session's available list — don't guess at names.
  - Use sub-agents to keep the main context lean. Delegate broad codebase exploration or research that'll take more than ~3 queries to an Explore-style agent (e.g. spawn Agent with `subagent_type=Explore`); otherwise use `find` or `grep` via the Bash tool directly. Don't duplicate searches a delegated agent is already doing.
- - If the user asks about "ultrareview" or how to run it, explain that /code-review ultra launches a multi-agent cloud review of the current branch (or /code-review ultra <PR#> for a GitHub PR); /ultrareview is a deprecated alias for the same command. It is user-triggered and billed; you cannot launch it yourself. It needs a git repository (offer to "git init" if not in one); the no-arg form bundles the local branch and does not need a GitHub remote.
+ - If the user asks about "ultrareview" or how to run it, explain that /code-review ultra launches a multi-agent cloud review of the current branch (or /code-review ultra <PR#> for a GitHub PR); /ultrareview is a deprecated alias for the same command. It is user-triggered and billed; you cannot launch it yourself, so do not attempt to via Bash or otherwise. It needs a git repository (offer to "git init" if not in one); the no-arg form bundles the local branch and does not need a GitHub remote.

package/prompts/style/declaudified.md

@@ -0,0 +1,16 @@
+# Style: Declaudified
+
+How to write everything the user reads — answers, summaries, explanations, commit messages, docs.
+
+- Lead with the answer. State the point first, then support it.
+- Cut filler and metadiscourse — language that narrates the communicating instead of communicating: "let me lay out," "it's worth noting," "as mentioned above." Say the thing; don't say you're about to say it.
+- Delete your opening sentence. The real first sentence is usually the second or third — cut the runway that sets up the answer instead of giving it.
+- Do add relevant surrounding context that hasn't already been established in the conversation — don't assume the user has perfect repo or domain knowledge. Adding context they lack is welcome; restating what they just told you is not.
+- Don't signpost structure. A list or table is self-evident; don't preface it with "here's a table of."
+- Plain language: real names for real things, minimal jargon, no padding adjectives. Use real terminology; don't invent labels ("status," not "milestones").
+- Drop dead tech-metaphors and stock phrases ("ship," "load-bearing," "first-class," "surface" as a verb, "seamless," "leverage," "robust"). Use the plain word or cut it; keep "ship" only for releasing software (else deliver / finish / send / hand off).
+- Don't state a cause without evidence — label speculation or leave it out.
+
+In short: say the thing; don't say you're about to say it, and don't say you understood the question.
+
+References: George Orwell, "Politics and the English Language" (his plain-English rules); Strunk & White, *The Elements of Style* ("omit needless words"); Joseph Williams, *Style: Toward Clarity and Grace* (on cutting metadiscourse).

package/src/args.ts

@@ -3,6 +3,7 @@ import { parseArgs } from "node:util";
 export interface ParsedArgs {
   base?: string;
   preset: string | null;
+  style?: string;
   overrides: {
     agency?: string;
     quality?: string;
@@ -34,6 +35,7 @@ export function parseCliArgs(argv: string[]): ParsedArgs {
       agency: { type: "string" },
       quality: { type: "string" },
       scope: { type: "string" },
+      style: { type: "string" },
       modifier: { type: "string", multiple: true },
       readonly: { type: "boolean" },
       print: { type: "boolean" },
@@ -78,7 +80,7 @@ export function parseCliArgs(argv: string[]): ParsedArgs {
 
   // Collect unknown flags for passthrough
   const knownFlags = new Set([
-    "base", "agency", "quality", "scope", "modifier", "readonly", "print", "context-pacing",
+    "base", "agency", "quality", "scope", "style", "modifier", "readonly", "print", "context-pacing",
     "append-system-prompt", "append-system-prompt-file",
     "system-prompt", "system-prompt-file", "help", "version",
   ]);
@@ -102,6 +104,7 @@ export function parseCliArgs(argv: string[]): ParsedArgs {
   return {
     base: values.base as string | undefined,
     preset,
+    style: values.style as string | undefined,
     overrides,
     modifiers: {
       readonly: values.readonly === true,

package/src/assemble.ts

@@ -116,6 +116,15 @@ export function getFragmentOrder(mode: ModeConfig, promptsDir: string): string[]
           }
         }
       }
+      // Style fragment rides the axes insertion point but applies even in
+      // none mode — an explicit --style is honored like explicit modifiers
+      if (mode.style) {
+        if (isAbsolute(mode.style)) {
+          fragments.push(mode.style);
+        } else {
+          fragments.push(`style/${mode.style}.md`);
+        }
+      }
     } else if (entry === "modifiers") {
       // All modifiers are fragment paths — just add them
       for (const modPath of mode.modifiers) {

package/src/build-info.ts

@@ -12,6 +12,6 @@ export interface BuildInfo {
 export const BUILD_INFO: BuildInfo = {
   "repo": "https://github.com/nklisch/claude-code-modes",
   "branch": null,
-  "commit": "967d10b",
+  "commit": "91f6069",
   "dirty": false
 };

package/src/config-cli.ts

@@ -8,6 +8,7 @@ import {
   checkModifierNameCollision,
   checkPresetNameCollision,
   checkAxisValueCollision,
+  checkStyleNameCollision,
 } from "./config.js";
 import { AXIS_BUILTINS } from "./types.js";
 const VALID_AXES = Object.keys(AXIS_BUILTINS) as Array<"agency" | "quality" | "scope">;
@@ -120,6 +121,33 @@ function configRemoveModifier(configPath: string, name: string): void {
   );
 }
 
+function configAddStyle(configPath: string, name: string, mdPath: string): void {
+  checkStyleNameCollision(name);
+  const config = readConfig(configPath);
+  config.styles = { ...config.styles, [name]: mdPath };
+  writeConfig(configPath, config);
+  process.stdout.write(
+    `Registered style "${name}" in ${configFileName(configPath)}\n`
+  );
+}
+
+function configRemoveStyle(configPath: string, name: string): void {
+  const config = readConfig(configPath);
+  const styles = config.styles ?? {};
+  if (!(name in styles)) {
+    throw new Error(
+      `Style "${name}" not found in ${configFileName(configPath)}`
+    );
+  }
+  const updated = { ...styles };
+  delete updated[name];
+  config.styles = updated;
+  writeConfig(configPath, config);
+  process.stdout.write(
+    `Unregistered style "${name}" from ${configFileName(configPath)}\n`
+  );
+}
+
 function configAddAxis(configPath: string, axis: string, name: string, mdPath: string): void {
   if (!VALID_AXES.includes(axis as ValidAxis)) {
     throw new Error(
@@ -173,6 +201,7 @@ function configAddPreset(configPath: string, name: string, flags: string[]): voi
       agency: { type: "string" },
       quality: { type: "string" },
       scope: { type: "string" },
+      style: { type: "string" },
       modifier: { type: "string", multiple: true },
       readonly: { type: "boolean" },
       "context-pacing": { type: "boolean" },
@@ -184,6 +213,7 @@ function configAddPreset(configPath: string, name: string, flags: string[]): voi
   if (values.agency !== undefined) presetDef.agency = values.agency;
   if (values.quality !== undefined) presetDef.quality = values.quality;
   if (values.scope !== undefined) presetDef.scope = values.scope;
+  if (values.style !== undefined) presetDef.style = values.style;
   if (values.modifier !== undefined && values.modifier.length > 0) {
     presetDef.modifiers = values.modifier as string[];
   }
@@ -238,6 +268,8 @@ Subcommands:
   remove-default <name>             Remove from defaultModifiers
   add-modifier <name> <path>        Register a named modifier
   remove-modifier <name>            Unregister a named modifier
+  add-style <name> <path>           Register a named style
+  remove-style <name>               Unregister a named style
   add-axis <axis> <name> <path>     Register custom axis value
   remove-axis <axis> <name>         Unregister custom axis value
   add-preset <name> [flags]         Create a custom preset
@@ -247,6 +279,7 @@ Flags for add-preset:
   --agency <value>
   --quality <value>
   --scope <value>
+  --style <value>
   --modifier <name> (repeatable)
   --readonly
   --context-pacing`;
@@ -287,6 +320,18 @@ Flags for add-preset:
       break;
     }
 
+    case "add-style": {
+      if (rest.length < 2) throw new Error("add-style requires <name> <path>");
+      configAddStyle(configPath, rest[0], rest[1]);
+      break;
+    }
+
+    case "remove-style": {
+      if (rest.length < 1) throw new Error("remove-style requires <name>");
+      configRemoveStyle(configPath, rest[0]);
+      break;
+    }
+
     case "add-axis": {
       if (rest.length < 3) throw new Error("add-axis requires <axis> <name> <path>");
       configAddAxis(configPath, rest[0], rest[1], rest[2]);

package/src/config.ts

@@ -1,7 +1,7 @@
 import { readFileSync, existsSync } from "node:fs";
 import { join, dirname, resolve, isAbsolute } from "node:path";
 import { homedir } from "node:os";
-import { PRESET_NAMES, BUILTIN_MODIFIER_NAMES, AXIS_BUILTINS, BUILTIN_BASE_NAMES, isBuiltinModifier, isPresetName, isBuiltinBase, isBuiltinAxisValue } from "./types.js";
+import { PRESET_NAMES, BUILTIN_MODIFIER_NAMES, AXIS_BUILTINS, BUILTIN_BASE_NAMES, STYLE_VALUES, isBuiltinModifier, isPresetName, isBuiltinBase, isBuiltinAxisValue, isBuiltinStyle } from "./types.js";
 
 /**
  * Matches paths that reference potentially sensitive files (SSH keys, credentials, etc.).
@@ -33,6 +33,8 @@ function validateConfigDefinedPath(path: string, context: string, configPath: st
 export interface UserConfig {
   defaultBase?: string;
   bases?: Record<string, string>; // name → directory path (relative to config dir)
+  defaultStyle?: string;
+  styles?: Record<string, string>; // name → .md path (relative to config dir)
   defaultModifiers?: string[];
   modifiers?: Record<string, string>;
   axes?: {
@@ -48,6 +50,7 @@ export interface CustomPresetDef {
   agency?: string;
   quality?: string;
   scope?: string;
+  style?: string;
   modifiers?: string[];
   readonly?: boolean;
   contextPacing?: boolean;
@@ -76,6 +79,15 @@ export function checkPresetNameCollision(name: string): void {
   }
 }
 
+/** Throws if name collides with a built-in style name. */
+export function checkStyleNameCollision(name: string): void {
+  if (isBuiltinStyle(name)) {
+    throw new Error(
+      `"${name}" is a built-in style name (${STYLE_VALUES.join(", ")}); choose a different name`
+    );
+  }
+}
+
 /** Throws if name collides with a built-in base name. */
 export function checkBaseNameCollision(name: string): void {
   if (isBuiltinBase(name)) {
@@ -204,6 +216,22 @@ function validateConfig(raw: unknown, configPath: string): UserConfig {
     for (const key of Object.keys(bases)) checkBaseNameCollision(key);
   }
 
+  // Validate defaultStyle
+  if (obj.defaultStyle !== undefined && typeof obj.defaultStyle !== "string") {
+    throw new Error(
+      `Invalid config file ${configPath}: "defaultStyle" must be a string`
+    );
+  }
+
+  // Validate styles map
+  if (obj.styles !== undefined) {
+    const styles = validateStringRecord(obj.styles, "styles", configPath);
+    for (const [key, val] of Object.entries(styles)) {
+      checkStyleNameCollision(key);
+      validateConfigDefinedPath(val, `"styles.${key}"`, configPath);
+    }
+  }
+
   // Validate defaultModifiers
   if (obj.defaultModifiers !== undefined) {
     const defaultModifiers = validateStringArray(obj.defaultModifiers, "defaultModifiers", configPath);
@@ -262,7 +290,7 @@ function validateConfig(raw: unknown, configPath: string): UserConfig {
           `Invalid config file ${configPath}: preset "${presetName}.base" must be a string`
         );
       }
-      for (const field of ["agency", "quality", "scope"] as const) {
+      for (const field of ["agency", "quality", "scope", "style"] as const) {
         if (def[field] !== undefined && typeof def[field] !== "string") {
           throw new Error(
             `Invalid config file ${configPath}: preset "${presetName}.${field}" must be a string`

package/src/embedded-prompts.ts

@@ -45,7 +45,7 @@ Examples of the kind of risky actions that warrant user confirmation:
 - Actions visible to others or that affect shared state: pushing code, creating/closing/commenting on PRs or issues, sending messages (Slack, email, GitHub), posting to external services, modifying shared infrastructure or permissions
 - Uploading content to third-party web tools (diagram renderers, pastebins, gists) publishes it - consider whether it could be sensitive before sending, since it may be cached or indexed even if later deleted.
 
-When you encounter an obstacle, do not use destructive actions as a shortcut to simply make it go away. For instance, try to identify root causes and fix underlying issues rather than bypassing safety checks (e.g. --no-verify). If you discover unexpected state like unfamiliar files, branches, or configuration, investigate before deleting or overwriting, as it may represent the user's in-progress work. For example, typically resolve merge conflicts rather than discarding changes; similarly, if a lock file exists, investigate what process holds it rather than deleting it. In short: only take risky actions carefully, and when in doubt, ask before acting. Follow both the spirit and letter of these instructions - measure twice, cut once.
+When you encounter an obstacle, do not use destructive actions as a shortcut to simply make it go away. For instance, try to identify root causes and fix underlying issues rather than bypassing safety checks (e.g. --no-verify). If you discover unexpected state like unfamiliar files, branches, or configuration, investigate before deleting or overwriting, as it may represent the user's in-progress work. If you're unsure whether the user would want something kept, prefer a reversible step (move it aside, rename it, or stash it) over deleting; files you created yourself this session (scratch outputs, experiment intermediates) are yours to clean up freely. For example, typically resolve merge conflicts rather than discarding changes; similarly, if a lock file exists, investigate what process holds it rather than deleting it. In a git repository, run \`git status\` before any command that could discard uncommitted work (git checkout/restore/reset/clean, rm -rf on a repo path, restoring from a snapshot), and stash (with \`-u\` for untracked) or commit anything you find first. In short: only take risky actions carefully, and when in doubt, ask before acting. Follow both the spirit and letter of these instructions - measure twice, cut once.
 `,
   "base/tools.md": `# Using your tools
  - Use your dedicated tools instead of shell equivalents. Read works better than cat or grep. Editing via sed or awk is error-prone and slow compared to Edit or your global search-and-replace tools. Using pgrep or echo for process monitoring just slows us down without adding control. Bash tools require user approval and may be rejected, especially in a sequence — calling them when a dedicated tool would do is a cost we don't need to pay.
@@ -75,7 +75,7 @@ In code: default to writing no comments. Never write multi-paragraph docstrings
  - If the user needs to run a shell command themselves (an interactive login like \`gcloud auth login\`, or something requiring their own credentials), suggest they type \`! <command>\` — the \`!\` prefix runs the command in this session so its output lands in the conversation.
  - When the user invokes a slash-prefixed skill (\`/<name>\`), follow its loaded instructions. Only invoke skills that appear in the session's available list — don't guess at names.
  - Use sub-agents to keep the main context lean. Delegate broad codebase exploration or research that'll take more than ~3 queries to an Explore-style agent (e.g. spawn Agent with \`subagent_type=Explore\`); otherwise use \`find\` or \`grep\` via the Bash tool directly. Don't duplicate searches a delegated agent is already doing.
- - If the user asks about "ultrareview" or how to run it, explain that /code-review ultra launches a multi-agent cloud review of the current branch (or /code-review ultra <PR#> for a GitHub PR); /ultrareview is a deprecated alias for the same command. It is user-triggered and billed; you cannot launch it yourself. It needs a git repository (offer to "git init" if not in one); the no-arg form bundles the local branch and does not need a GitHub remote.
+ - If the user asks about "ultrareview" or how to run it, explain that /code-review ultra launches a multi-agent cloud review of the current branch (or /code-review ultra <PR#> for a GitHub PR); /ultrareview is a deprecated alias for the same command. It is user-triggered and billed; you cannot launch it yourself, so do not attempt to via Bash or otherwise. It needs a git repository (offer to "git init" if not in one); the no-arg form bundles the local branch and does not need a GitHub remote.
 `,
   "base/env.md": `# Environment
 You have been invoked in the following environment: 
@@ -86,9 +86,9 @@ You have been invoked in the following environment:
  - OS Version: {{OS_VERSION}}
  - You are powered by the model named {{MODEL_NAME}}. The exact model ID is {{MODEL_ID}}.
  - Assistant knowledge cutoff is {{KNOWLEDGE_CUTOFF}}.
- - The most recent Claude models are Fable 5 and the Claude 4.X family. Model IDs — Fable 5: 'claude-fable-5', Opus 4.8: 'claude-opus-4-8', Sonnet 4.6: 'claude-sonnet-4-6', Haiku 4.5: 'claude-haiku-4-5-20251001'. When building AI applications, default to the latest and most capable Claude models.
+ - The most recent Claude models are the Claude 5 family, Opus 4.8, and Haiku 4.5. Model IDs — Fable 5: 'claude-fable-5', Opus 4.8: 'claude-opus-4-8', Sonnet 5: 'claude-sonnet-5', Haiku 4.5: 'claude-haiku-4-5-20251001'. When building AI applications, default to the latest and most capable Claude models.
  - Claude Code is available as a CLI in the terminal, desktop app (Mac/Windows), web app (claude.ai/code), and IDE extensions (VS Code, JetBrains).
- - Fast mode for Claude Code uses Claude Opus with faster output (it does not downgrade to a smaller model). It can be toggled with /fast and is available on Opus 4.8/4.7/4.6.
+ - Fast mode for Claude Code uses Claude Opus with faster output (it does not downgrade to a smaller model). It can be toggled with /fast and is available on Opus 4.8/4.7.
 
 When working with tool results, write down any important information you might need later in your response, as the original tool result may be cleared later.
 
@@ -533,6 +533,23 @@ Stay strictly within the bounds of what was requested.
 - Do not refactor, rename, or reorganize anything that isn't directly required by the task.
 - If the request is to change function X, change function X. Do not also update its callers, its tests, or its documentation unless the request explicitly includes those.
 - If completing the request requires changing more code than expected, pause and confirm the scope with the user before proceeding.
+`,
+  "style/declaudified.md": `# Style: Declaudified
+
+How to write everything the user reads — answers, summaries, explanations, commit messages, docs.
+
+- Lead with the answer. State the point first, then support it.
+- Cut filler and metadiscourse — language that narrates the communicating instead of communicating: "let me lay out," "it's worth noting," "as mentioned above." Say the thing; don't say you're about to say it.
+- Delete your opening sentence. The real first sentence is usually the second or third — cut the runway that sets up the answer instead of giving it.
+- Do add relevant surrounding context that hasn't already been established in the conversation — don't assume the user has perfect repo or domain knowledge. Adding context they lack is welcome; restating what they just told you is not.
+- Don't signpost structure. A list or table is self-evident; don't preface it with "here's a table of."
+- Plain language: real names for real things, minimal jargon, no padding adjectives. Use real terminology; don't invent labels ("status," not "milestones").
+- Drop dead tech-metaphors and stock phrases ("ship," "load-bearing," "first-class," "surface" as a verb, "seamless," "leverage," "robust"). Use the plain word or cut it; keep "ship" only for releasing software (else deliver / finish / send / hand off).
+- Don't state a cause without evidence — label speculation or leave it out.
+
+In short: say the thing; don't say you're about to say it, and don't say you understood the question.
+
+References: George Orwell, "Politics and the English Language" (his plain-English rules); Strunk & White, *The Elements of Style* ("omit needless words"); Joseph Williams, *Style: Toward Clarity and Grace* (on cutting metadiscourse).
 `,
   "modifiers/readonly.md": `# Read-only mode
 

package/src/env.ts

@@ -44,8 +44,8 @@ export function detectEnv(): EnvInfo {
 }
 
 // Hardcoded model info — update when Claude Code updates
-const MODEL_NAME = "Claude Opus 4.8";
-const MODEL_ID = "claude-opus-4-8";
+const MODEL_NAME = "Fable 5";
+const MODEL_ID = "claude-fable-5";
 const KNOWLEDGE_CUTOFF = "January 2026";
 
 export function buildTemplateVars(env: EnvInfo): TemplateVars {
@@ -63,7 +63,8 @@ export function buildTemplateVars(env: EnvInfo): TemplateVars {
   }
 
   const worktreeNotice = env.isWorktree
-    ? "\n - This is a git worktree — an isolated copy of the repository. Run all commands from this directory. Do NOT `cd` to the original repository root."
+    ? "\n - This is a git worktree — an isolated copy of the repository. Run all commands from this directory. Do NOT `cd` to the original repository root." +
+      "\n - The git stash stack is shared with the main checkout and all other worktrees, and other Claude sessions may push or pop it concurrently. Never use bare `git stash` / `git stash pop` — you could pop another session's changes. Prefer a temporary WIP commit to set work aside; if you must stash, use `git stash push -u -m \"<unique-tag>\"`, immediately capture your entry's SHA via `git stash list --format='%H %gs'`, restore with `git stash apply <sha>` (not pop), and afterwards drop the entry, re-finding its current `stash@{n}` by tag first."
     : "";
 
   return {

package/src/inspect.ts

@@ -66,6 +66,13 @@ function collectConfigDefinedPaths(loadedConfig: LoadedConfig | null): Set<strin
     }
   }
 
+  // Style definitions
+  if (config.styles) {
+    for (const val of Object.values(config.styles)) {
+      paths.add(resolveConfigPath(configDir, val));
+    }
+  }
+
   // Axis definitions
   if (config.axes) {
     for (const axisName of ["agency", "quality", "scope"] as const) {

package/src/presets.ts

@@ -5,6 +5,7 @@ export interface PresetDefinition {
   axes: AxisConfig | null;
   readonly: boolean;
   base?: string;       // default base for this preset
+  style?: string;      // default style for this preset
   modifiers: string[]; // built-in modifier names to apply
 }
 

package/src/resolve.ts

@@ -7,11 +7,13 @@ import {
   AGENCY_VALUES,
   QUALITY_VALUES,
   SCOPE_VALUES,
+  STYLE_VALUES,
   BUILTIN_MODIFIER_NAMES,
   BUILTIN_BASE_NAMES,
   PRESET_NAMES,
   isBuiltinModifier,
   isBuiltinBase,
+  isBuiltinStyle,
 } from "./types.js";
 import { resolve as pathResolve, isAbsolute } from "node:path";
 
@@ -128,6 +130,51 @@ function applyModifiers(
   }
 }
 
+/**
+ * Resolves a style value to either a built-in name or an absolute path.
+ * Resolution order: built-in values → config-defined names → file path heuristic.
+ * Throws with descriptive error if unresolvable.
+ */
+function resolveStyleValue(raw: string, loadedConfig: LoadedConfig | null): string {
+  // 1. Built-in value
+  if (isBuiltinStyle(raw)) return raw;
+
+  // 2. Config-defined custom name
+  const configStyles = loadedConfig?.config.styles;
+  if (configStyles && raw in configStyles) {
+    return resolveConfigPath(loadedConfig!.configDir, configStyles[raw]);
+  }
+
+  // 3. File path
+  if (looksLikeFilePath(raw)) {
+    return isAbsolute(raw) ? raw : pathResolve(raw);
+  }
+
+  // 4. Unknown
+  const configHint = loadedConfig
+    ? ` Config loaded from: ${loadedConfig.configDir}`
+    : " No config file found.";
+  throw new Error(
+    `Unknown --style value: "${raw}". ` +
+    `Must be one of: ${STYLE_VALUES.join(", ")}, ` +
+    `a name defined in your config, or a file path.${configHint}`
+  );
+}
+
+/**
+ * Resolves the active style, or null when none applies.
+ * Priority: CLI --style > config defaultStyle > preset style > none
+ */
+function resolveStyle(
+  raw: string | undefined,
+  loadedConfig: LoadedConfig | null,
+  presetStyle: string | undefined,
+): string | null {
+  const value = raw ?? loadedConfig?.config.defaultStyle ?? presetStyle;
+  if (value === undefined) return null;
+  return resolveStyleValue(value, loadedConfig);
+}
+
 /**
  * Resolves a base reference to a built-in name or absolute directory path.
  * Priority: CLI --base > config defaultBase > preset base > "standard"
@@ -190,12 +237,14 @@ export function resolveConfig(
   // 3. CLI --modifier flags — appended after defaults
   applyModifiers(parsed.customModifiers, loadedConfig, modifierPaths, "append");
 
-  // Handle "none" preset — resolve base before early return
+  // Handle "none" preset — resolve base before early return.
+  // Explicit --style (or config defaultStyle) still applies, like modifiers.
   if (parsed.preset === "none") {
     const base = resolveBase(parsed.base, loadedConfig, undefined);
     return {
       base,
       axes: null,
+      style: resolveStyle(parsed.style, loadedConfig, undefined),
       modifiers: modifierPaths,
     };
   }
@@ -204,6 +253,7 @@ export function resolveConfig(
   let quality: string;
   let scope: string;
   let presetBase: string | undefined;
+  let presetStyle: string | undefined;
 
   if (parsed.preset) {
     // Check built-in presets first, then config presets
@@ -220,6 +270,7 @@ export function resolveConfig(
         ? resolveAxisValue(parsed.overrides.scope, "scope", SCOPE_VALUES, loadedConfig)
         : preset.axes.scope;
       presetBase = preset.base;
+      presetStyle = preset.style;
 
       // Apply preset's readonly flag as a modifier
       if (preset.readonly) {
@@ -233,6 +284,7 @@ export function resolveConfig(
       // Config-defined preset
       const customPreset = config.presets[parsed.preset];
       presetBase = customPreset.base;
+      presetStyle = customPreset.style;
       agency = parsed.overrides.agency
         ? resolveAxisValue(parsed.overrides.agency, "agency", AGENCY_VALUES, loadedConfig)
         : customPreset.agency
@@ -284,10 +336,12 @@ export function resolveConfig(
   }
 
   const base = resolveBase(parsed.base, loadedConfig, presetBase);
+  const style = resolveStyle(parsed.style, loadedConfig, presetStyle);
 
   return {
     base,
     axes: { agency, quality, scope },
+    style,
     modifiers: modifierPaths,
   };
 }

package/src/types.ts

@@ -7,6 +7,13 @@ export type Quality = (typeof QUALITY_VALUES)[number];
 export const SCOPE_VALUES = ["unrestricted", "adjacent", "narrow"] as const;
 export type Scope = (typeof SCOPE_VALUES)[number];
 
+// Built-in style names — writing styles applied on top of any base/axes
+export const STYLE_VALUES = ["declaudified"] as const;
+export type Style = (typeof STYLE_VALUES)[number];
+export function isBuiltinStyle(value: string): value is Style {
+  return (STYLE_VALUES as readonly string[]).includes(value);
+}
+
 export const PRESET_NAMES = [
   "create",
   "extend",
@@ -69,6 +76,7 @@ export interface AxisConfig {
 export interface ModeConfig {
   base: string; // built-in name ("standard", "chill") or absolute path to base directory
   axes: AxisConfig | null; // null for "none" mode
+  style: string | null; // built-in name or absolute path to a custom fragment; null = no style
   modifiers: string[]; // ordered list of modifier fragment paths (embedded keys or absolute paths)
 }
 

package/src/update.ts

@@ -159,11 +159,13 @@ export function classifyInstall(
   execPath: string = process.execPath,
   buildInfo: BuildInfo = BUILD_INFO,
 ): InstallClassification {
-  // 1. Runtime interpreter → source mode
-  if (SOURCE_EXEC_NAMES.has(basename(execPath))) {
+  // 1. Runtime interpreter → source mode. The npm distribution of bun names
+  // its binary "bun.exe" on every platform, so strip the suffix before matching.
+  const execName = basename(execPath).replace(/\.exe$/, "");
+  if (SOURCE_EXEC_NAMES.has(execName)) {
     return {
       kind: "source",
-      reason: `Running as ${basename(execPath)} runtime (source mode)`,
+      reason: `Running as ${execName} runtime (source mode)`,
     };
   }
 

package/src/usage.ts

@@ -42,6 +42,11 @@ Axis overrides:
   --scope <value>         Built-in: unrestricted, adjacent, narrow
   Axis values can also be config-defined names or file paths (.md files).
 
+Style:
+  --style <value>         Writing style for output. Built-in: declaudified
+  Style can also be a config-defined name or a file path (.md file).
+  No style is applied unless set via --style, config defaultStyle, or a preset.
+
 Modifiers:
   --readonly              Prevent file modifications
   --context-pacing        Include context pacing prompt
@@ -60,6 +65,7 @@ Examples:
   claude-mode create
   claude-mode create --base chill             # use the chill base
   claude-mode create --quality pragmatic
+  claude-mode create --style declaudified      # lead-with-the-answer writing, no filler
   claude-mode create --modifier ./my-rules.md
   claude-mode --agency autonomous --quality ./team-quality.md
   claude-mode team-default                    # custom preset from config