Skip to main content

Claude Sonnet 5.5

Clearer sentences, a stronger structure, and revisions with a purpose.

Describe what you want to make, or drop a reference
Try a prompt:
Claude Sonnet 5.5 · 2026-10-21 · same reply · Q1/3

How should I prevent duplicate animation loops and input listeners when restarting a small HTML canvas brick-breaker game? Give a minimal lifecycle pattern, list the game state that must reset, and provide four checks that expose restart bugs. Do not produce a complete game or claim the pattern has been run.

Four checks: Restart 10 times quickly, then log one counter per frame. It should rise by one per frame, not by ten. Press the paddle key once after several restarts. The paddle should move one step. Move speed multiplying means listeners are duplicated. Hold a key, restart, and release. The paddle must not stay stuck or drift. Restart from game-over and from mid-play. Compare the full state to a fresh page load. Check for stale bricks, speed, lives, or a huge first-frame jump.

View source
Claude Sonnet 5.5 · 2026-10-21 · same reply · Q2/3

How should a small React team choose between BlockNote and Tiptap for a Notion-style first version with paragraphs, headings, lists and reliable save-and-reload? Give a conditional initial choice, separate editor functionality from storage and permissions we must implement, and identify what must be verified before adding collaboration or comments.

Conditional initial choice (my recommendation): If you want Notion-style blocks working fast with minimal UI work, start with BlockNote. If you need heavy custom schema, custom UI, or fine control over behavior, start with Tiptap. For a first version with only paragraphs, headings and lists, BlockNote is probably faster. That is a judgment, not a measurement.

View source
Claude Sonnet 5.5 · 2026-10-21 · same reply · Q3/3

For an online-first issue tracker with occasional disconnects and concurrent edits, when should a small team use server-first optimistic updates rather than local-first sync? Explain retry idempotency, conflict handling, reload recovery and server-side authorization. Identify which scaling problems in Linear's August 2026 delta-sync article do not, by themselves, justify copying its architecture.

Retry idempotency: The client generates a mutation ID for each action. The server stores it with the result and returns the stored result if the same ID arrives again. This makes retries after a timeout safe from duplicate comments or double status changes.

View source

How it works

Try it now
  1. 01

    Say what you want

    A sentence or two is enough.

  2. 02

    Work with HowWorks Agent

    Describe the result you want. The Agent works with the tools you choose.

  3. 03

    Make it

    Start creating, then keep working with HowWorks.

Claude Sonnet 5.5 at a glance

Good at
Polish drafts and presentations with quick, natural revisions.
Max output
128,000 tokens
Attachments
Images 5 MB · PDF 20 MB

About

Bring a draft that is close but not quite working: an introduction that takes too long, slides without a clear point, or wording that sounds unlike you. Tell Claude Sonnet 5.5 who it is for and what should stay. Work on the argument and sequence first, then the sentences. For a presentation, ask for a slide-by-slide narrative and speaker notes rather than assuming a finished deck file. Compare edits with the original to catch altered facts or promises. Sonnet 5.5 is the Agent conversation model; creating media or a file through a tool is a separate action.

Questions

How can I preserve my voice during editing?

Provide a short sample of your writing and describe what you like about it. Ask the Agent to keep those qualities, preserve specific phrases and explain edits that change emphasis rather than just grammar.

Can it help with a presentation?

Share the audience, purpose and evidence, then ask for a slide outline, concise slide text or speaker notes. Review the narrative before requesting a finished file through an available tool; an outline is not a presentation file.

What if the rewritten version sounds generic?

Point to the sentences that lost character and explain the problem: too formal, abstract or promotional. Ask for concrete details from the original instead of another complete rewrite.

What should I check before using the text?

Compare dates, names, numbers, quotations and commitments with the original. Confirm that stronger phrasing has not become a claim your evidence cannot support, and read the result aloud for tone.