prompt-optimizer-fablelisted

Fable-variant rigorous prompt optimizer — audits a polished prompt and rewrites it to elicit state-of-the-art output from Claude Fable 5, with surface-aware run settings (chat app, Claude Code, Cowork, harness). Triages into OUT OF PURVIEW / BORDERLINE / IN PURVIEW; decides output architecture (single-turn vs. chained multi-stage) and produces a chain deliverable (README + orchestrator + stage prompts) when signals fire. Fires ONLY on explicit Fable invocation — trigger phrases include "PO this for Fable", "optimize this prompt for Fable 5", "fable-optimize this", "run the fable optimizer". Do NOT trigger on unqualified requests ("PO this", "optimize this prompt") — those route to prompt-optimizer (Opus sibling). Do NOT trigger for messy dictated or flow-state input (use prompt-optimizer-flow), and do NOT trigger when the user wants the prompt EXECUTED rather than optimized.
viktor-milev/claude-skills · ★ 1 · AI & Automation · score 72

Install: claude install-skill viktor-milev/claude-skills

# Prompt Optimizer — Fable 5 Edition ## CHANGELOG **v1.0-fable — Jul 2026.** Standalone fork of `prompt-optimizer` v4.2 (Opus 4.8), recalibrated for **Claude Fable 5**. Produced through an internal maintenance-review process (staged review against two empirical exhibits); ruling standards: the official Anthropic *Prompting Claude Fable 5* guide and the Jul 2026 effort documentation. The Opus sibling remains in use, unchanged. **Lockstep contract (governance).** The architecture decision module — the seven signals, verdict logic, and guards — plus its threshold constants are bound in lockstep with `prompt-architect-fable`: any change there propagates to both Fable skills. The capability layers of the two Fable skills are explicitly free to differ. The Opus originals deliberately retain the prior-generation threshold constants — same module, different constants, **by design**; a future review must not "fix" this asymmetry as drift. Changes vs. v4.2: - **Effort model rewritten** for the Fable 5 ladder (low / medium / high / xhigh / max; high default) with bidirectional calibration and counter-instruction pairing (Step 9.5). - **Surface parameter added** (chat / code / cowork / harness) gating RUN SETTINGS and agentic techniques (Intake, Step 9.5). - **Architecture thresholds recalibrated (LOCKSTEP):** fidelity test primary; provisional numeric backstop, VALIDATE-marked; prior-generation bands retired on direct empirical disconfirmation (Step 3 signal 7, Step 7a). - **Capabil