Skip to main content
Open HowWorks

Claude Opus 5

Explore the material, connect the ideas, then build a story a reader can follow.

Describe what you want to make, or drop a reference
Try a prompt:
Claude Opus 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.

Recommendation (pattern, not run): give the game a single owner of two resources: the requestAnimationFrame handle and the listener registrations. Expose one start() guarded by an isRunning flag (returning early if already true) and one stop() that calls cancelAnimationFrame(handle), sets it to null, and tears down listeners. Register input through an AbortController's signal, or keep named handler references you remove explicitly — .addEventListener(..., {signal}) makes controller.abort() clean up all of them at once. Restart is then always stop() → resetState() → start(), never start() alone. Also clamp delta time per frame so a backgrounded tab doesn't resume with a 10-second step.

View source
Claude Opus 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.

Yours to build either way: the editor is not your product. You must implement (a) storage — document table, debounced autosave, a version column for optimistic locking, and a schema-version field; (b) the load path — parse stored JSON, handle older versions, fall back rather than crash; (c) permissions — authentication, per-document ACLs, and enforcement on the server, never trusting client-sent roles; (d) a round-trip test asserting save → reload yields equivalent JSON, including nodes your current UI doesn't render.

View source
Claude Opus 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.

Idempotency: each mutation carries a client-generated UUID; the server stores it with the result under a unique constraint. Retrying returns the original outcome; the same id with a different body is a 409. Conflicts: send the version you read. The server rejects stale writes with the current row, and the client rebases the user's field change or shows a diff. Field-level patches keep conflicts narrow. Reload recovery: persist the pending queue with ids and base versions before sending; replay it on load, deduplicated by id. Treat "sent, outcome unknown" as retryable. Authorization: re-check permission against the resource as it exists at write time, inside the same transaction, so a stale client can't write past a role change.

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 Opus 5 at a glance

Good at
Explore a topic in depth and build detailed presentations.
Max output
128,000 tokens
Attachments
Images 5 MB · PDF 20 MB

About

A substantial explanation needs more than a list of facts. Give Claude Opus 5 the topic, audience and material you want to explore. Ask it to map the ideas, identify tensions and choose a narrative that leads toward a useful conclusion. Develop a presentation outline or detailed explanation from that structure. Review whether each section earns its place and whether sources support the connections between ideas. Opus 5 handles the Agent conversation; research access and tool-created files remain separate parts of the work.

Questions

How should I start an in-depth exploration?

Describe what you want to understand and why it matters to the audience. Share sources or notes, name competing views and ask which questions are worth exploring before requesting a full explanation.

How can I turn research into a presentation?

Choose the takeaway first. Ask for a slide sequence with a purpose, evidence and transition for each slide. Add speaker notes after the sequence works, then use a suitable available tool if you need a file.

What should I do with an unsupported connection?

Ask which source supports it and whether it is a finding or an interpretation. If evidence is missing, label it as a hypothesis, find a source or leave it out of the final narrative.

Can I bring images or PDF documents?

The current catalog includes image and PDF inputs for Opus 5. Attach relevant material within the displayed limits and explain whether it is evidence to analyze or a reference for the presentation.