Opus 5.5 — generalDifficulty: AdvancedProduction path: Coding & simulation

Deep Refactoring with Invariant Analysis

Opus 5.5 reasoning prompt to extract loop invariants, pre/post conditions, and safe refactor steps before touching production payment or credit code.

Prompt

91 words · 637 characters
Analyze the supplied module for a safe refactor.

Steps (show work):
1. List public entrypoints and side effects (DB, HTTP, filesystem).
2. For each non-trivial loop/recursion: state invariant, variant function, and termination argument.
3. Identify hidden coupling (shared mutable state, implicit ordering).
4. Propose refactor as small steps; each step must preserve observational equivalence for listed entrypoints.
5. Flag race conditions under concurrent calls.
6. Output test cases that would fail if invariants break (table: input, expected, property checked).

Do NOT rewrite code until step 6 is approved. Use markdown headings.

Workflow notes

Paste one service file at a time from src/modules/. Cross-check with existing tests; Opus adaptive thinking helps on FIFO credit logic.

  • Opus 5.5 — generalFeaturedAdvanced

    Interactive Transformer Architecture Explainer

    Build a scroll-driven, canvas-based walkthrough of self-attention, multi-head attention, and feed-forward blocks with live tensor shapes and token highlighting.

    Coding & simulationtransformereducationcanvasinteractive
    View details
  • Opus 5.5 — generalFeaturedIntermediate

    World-Class Motion Designer System Prompt

    A reusable system prompt that encodes easing curves, staging, 12 principles of animation, beat-sync rules, and deliverable specs for UI and brand motion.

    System promptmotion-designeasingsystem-promptui
    View details

Build on Claude Fable5 with your eyes open

Know the Claude Fable5 cost math, the safeguard behavior, and the right tier before you commit. Create a free account to get notified when specs, prices, or access channels change.