Long-form writing and research synthesis
Give Claude Opus 5.5 interview notes, reading excerpts and a central argument. Organize the themes before drafting paragraphs, so each source has a purpose in the finished piece.

Turn ideas and source material into work you can use. Develop an article, reason through a decision, build a webpage or explore motion in code, then refine the result in conversation.
Give Claude Opus 5.5 interview notes, reading excerpts and a central argument. Organize the themes before drafting paragraphs, so each source has a purpose in the finished piece.

Use Claude Opus 5.5 to explain a function, identify edge cases or turn page requirements into HTML, CSS and interaction code. Develop one important flow before adding the rest.

Ask Claude Opus 5.5 to tighten an opening, shorten a section or explain an idea to a different audience. Name the facts, terminology and point of view that should remain unchanged.

Long-context reasoning, visual understanding and text generation for writing and software work with Claude Opus 5.5.
Claude Opus 5.5 has a 1M-token context window. Bring related notes, documents and code into the same discussion to compare ideas without treating each passage in isolation.
Claude Opus 5.5 supports a maximum output of 128K tokens, giving extended reports, code explanations and chapter-based drafts room to develop. Start with a structure, then expand the sections that matter.
Claude Opus 5.5 accepts text and images and produces text. Discuss an interface screenshot alongside its requirements, or connect a chart to the research question behind it.
Claude Opus 5.5 uses adaptive thinking for complex coding and knowledge work. Supply the goal, constraints and current approach so the analysis can connect the different parts of the task.
Explore Claude Opus 5.5 prompts and find a starting point for your next webpage.
Create a video of Portland, OR's bus service on a random Tuesday! Showcase Portland's different neighborhoods at a high level and then zoom in on specific routes in each quadrant (absorbing North Portland into NE and South Portland into SW for brevity). Use a light theme. Slow down the speed of the bus animation when zoomed in, without increasing the total duration too much so the viewer can appreciate some of the landscape and streets it travels through in a given loop.
Give it one picture and have it create a decomposable robot octopus in code. Include 8 arms, 202 joints, and 480 wheels. At around 16 seconds, everything flies apart and returns to normal while rotating 330 degrees. Compare the still image with the original and fix it 3 times. Move the parts one by one.
<inputs>
Ask me for: 8 to 12 UI states I want the shape to become (e.g. button, loader, player, slider, toggle, tabs, chart, command palette, toast), pure black and white or one accent color, and a royalty-free song around 120 BPM (e.g. Mixkit, free for commercial use).
</inputs>
<direction>
Dribbble-level UI motion. One shape, never cut: every state is the same element morphing its size, radius and color while its content swaps with a short blur. A cursor drives every change with real clicks and drags. Light warm-gray canvas, black and white components, one clean UI font (Geist). Springs everywhere, a tiny overshoot at most. The camera zooms so each state fills the frame. The last frame is the first frame, so it loops.
Banned: bouncy easing, particle bursts, glows, gradients on UI chrome, mismatched icon strokes, dead time, anything that looks like a template.
</direction>
<structure>
120 BPM, 7 bars, something happens on every beat.
Button → loader → check → dynamic island → music player with a play/pause morph → scrub the progress bar → it becomes a volume slider that stretches when dragged past max → a toggle flips on the beat → the knob becomes a liquid tab indicator → the tabs open into a chart that draws itself, with a tooltip on hover → it collapses into ⌘K → type to filter → enter → toast → back to the button.
</structure>
<build>
1. One HTML file, square 1440x1440. Every style is computed from time inside seek(t): no CSS transitions, no timers, no state carried between frames.
2. Springs are closed-form step responses. A value that changes target many times is the sum of one spring per change, so it stays a pure function of time.
3. The tab indicator's two edges ride different springs, so the leading edge stretches ahead of the trailing one. Same trick for the toggle knob.
4. Drags are direct manipulation: while the cursor is held, the value is computed from its position. On release it springs back from wherever it was.
5. Analyze the song with numpy for the beat grid and start on a downbeat. Place every UI sound by its measured peak.
6. Render with Playwright: 4 subframes per frame, blended with ffmpeg tmix for motion blur at 60fps.
7. Render one frame per beat before the full render. Fix anything off the grid, cramped or hard to read.
</build>
<gotchas>
Never put will-change on anything the camera scales or the text renders blurry. Text that swaps inside a morphing container needs its own enter and exit timing or it overlaps. Make the last frame identical to the first, cursor position and speed included, or the loop stutters.
</gotchas>
<start>
Ask me for the inputs, then show me the state list on the beat grid before you write any code.
</start>
Create an atmospheric 3D laundromat scene in Blender using Python scripting. Include realistic lighting, washing machines with rotating drums, and a cozy ambiance. Do not use manual UI operations; generate all geometry, materials, and animations via code.
Make the model: Turn one picture into a robot octopus I can take apart piece by piece. Use three.js code for every petal, lens and link. Render one still next to the picture and fix gaps for 3 rounds before creating the film. Pack 202 links and 480 wheels into 8 arms, each arm as one draw call posed every frame. Animate something opening every 2-3 seconds (lens unscrews, mantle hinges, pump rises spinning). At 0:16 blow the whole thing apart on a 330° turntable and reassemble before the turn ends. Output a 25-second video.
Third-person perspective miniature 3D model with free drag/rotate/zoom capabilities, no UI elements, square base.
The main subject is a Japanese convenience store street corner, complete with glass display windows, automatic doors, eaves rain shelters, vending machines, bicycles, and umbrella racks.
The interior must be bright and warm, with neatly arranged shelves and rich details including bento areas, drink fridges, cash registers, and oden counters, clearly visible through the large glass.
The exterior is a damp, dim rainy night, creating a strong warm-cool contrast to evoke a classic anime-style rainy night atmosphere.
Art style: High-fidelity modeling + cel-shaded cartoon rendering, clear outlines, wet reflections, slice-of-life anime aesthetic.
Animation accents: Continuous rainfall, dripping from eaves, ripples in puddles, flickering signs, occasional opening of automatic doors, road reflections, etc., adding just the right amount of life within stillness.
<inputs>
Ask me for: one topic as a "what if" question (default: "{argument name="topic" default="What if the Sun vanished?"}"), the length (default {argument name="length" default="30 seconds"}), and whether I have an ElevenLabs key (if not, use a free local voice).
</inputs>
<direction>
A Kurzgesagt-style animated explainer at 1920x1080, 30fps, drawn entirely in code: one 2D canvas plus one WebGL canvas for planets.
Space: a vertical gradient #081d2c to #102348, five huge parallax nebula blobs (teal rgb 24,150,160 at 20%, blue 40,95,195 at 16%, coral 220,95,110 at 10%, indigo 60,70,175 at 15%), three star layers at parallax depths .12/.35/.6 that twinkle, 40% of the near stars drawn as 4-point sparkles.
The Sun: radius 300px, half off the left edge. A radial gradient #fff7dc to #ffc857 to #ff8f4a with an offset highlight, additive halo rings at 1.23/1.48/1.76/2.1x the radius, 18 faint rotating ray wedges, 28 drifting glowing granules on its surface.
Earth: an orthographic sphere in a fragment shader, 4x supersampled, from a 2048x1024 map painted from longitude/latitude polygons: land #5fc47a, forest #48ad6b, desert #f5c75f, rainforest #3a9d62, ice #f1f8ff, ocean gradient #4dc7eb to #1a66b8, white capsule clouds. Tilt .26 rad, spin .55 degrees per second. Day/night uses smoothstep(-.12, .24, N·L) with the light direction recomputed from Sun to Earth every frame. Navy night side with ~380 warm city lights, a coral band on the terminator, a cyan rim, ocean specular, an atmosphere halo that is stronger on the lit side.
A small astronaut mascot (~180px) built from rounded rectangles: suit #f3f7fb, orange #ff8f4a boots, a visor gradient #1f5a73 to #0a1c2c with glowing cyan eyes that look at whatever matters, a blinking antenna light, an idle bob, squash and stretch on every pose.
Type: Fredoka 600/700 only. Captions in caps with 3-6px letter spacing in teal #8fd8e6, gold #ffd98a or white, sitting in rounded pills of rgb(6,20,40) at 62%. Every line of text rises 1.3x its own height through a clip on an ease-out-quint.
Finish: a vignette to rgba(4,4,20,.45) and a 6% film grain re-randomized 24 times per second.
Banned: outlines, flares or loops on the Sun's edge, static infographic strips, full stops in on-screen text, text that fades in whole, AI images or AI video, Kurzgesagt's own characters, bird or music.
</direction>
<structure>
30 seconds, every line of narration gets a camera move or a transformation, nothing ever holds still.
Tight on the Sun at 2.25x (0s) → on the word "vanished" it swells 6% for 0.22s, collapses in 0.33s, then a white flash and a shockwave ring (1s) → pull back to 1x revealing Earth still lit and the astronaut staring at the empty spot (1.6-3s) → on "eight" an 8:20 countdown slams in from 1.7x to 1x and starts ticking, a "LAST LIGHT" label rides the edge of the growing dark disc (3.2s) → dive to 2.3x on Earth with light streaks flowing in (5.6s) → on "you" a YOU pin drops (7s) → on "left" a photon lands on the pin with "THIS LIGHT LEFT THE SUN / 8 MIN 20 SEC AGO" (7.5s) → on "play" the pin morphs into a play button, "YOU PRESSED PLAY / 15 SEC AGO" (8.8s) → one pull-back from 2.4x to a 0.3x orbit view, "LAST LIGHT" and "GRAVITY" riding the ring (9.6-12.5s) → on "nothing" a dotted circle at the empty centre (13.4s) → on "hits" the darkness sweeps Earth in 0.7s, city lights pop on, the countdown turns gold at 0:00 (15.8s) → on "black" the background fades almost to black (17.4s) → Jupiter appears, "STILL SHINING FOR 1 HOUR+" (17.9s) → zoom out, a dashed tangent line, "30 KM/S" as Earth flies straight off (20.8s) → a thermometer counts 15 to -70°C while frost grows from the poles (22.8s) → a 0.8s rewind on a separate story clock (24.3s) → sunglasses drop onto the astronaut (25.2s) → a photon tagged "8:20 OLD", then the title (27.7s).
For any other topic, keep the same shape: the event happens on its word, pull back to show scale, dive in to make it personal ("you"), pull back out, the consequence with a live counter, an escalation, a funny beat with the mascot, a callback and the title.
</structure>
<build>
1. One HTML file. Every frame is a pure function of time: https://t.co/lT4Z2IvSIB(t) draws frame t. No timers, no CSS animation.
2. Camera moves on easeInOutCubic, zoom is interpolated in log space, every pop is a damped spring (damping .42-.5, frequency 12-16).
3. Voice: ElevenLabs eleven_v4 with a designed voice (calm, warm, curious male, late 30s, crisp, light neutral European English), stability .5, similarity .75, generated with timestamps. Without a key, use kokoro-onnx locally and get word times with faster-whisper. Every animation event fires on its word. About 165 words per minute, 0.24s between sentences, a 0.36s beat before the big reveal.
4. The darkness front: any pixel within the front's radius from the Sun turns to night with a 30px soft edge. The front moves at ~47px/s and ramps to 700px/s near Earth.
5. Keep two clocks: ambient time for twinkle, spin and bob, and a separate story clock for events, so a rewind stays consistent.
6. Render with Playwright in headless Edge with the GPU: seek every frame at 30fps and blend 2 subframes (shutter 0.6) for motion blur, then encode with libx264 at CRF 16 for the master and CRF 20 for delivery.
7. Sound: a calm royalty-free space music bed 7dB under the voice, timed so its natural ending lands on the title, swelling 5dB under the title. One downloaded royalty-free sound effect per event kind (collapse, impact, pull-back whoosh, countdown tick, dive, pin tap, photon land, play click, light hit, reveal, frost, rewind), each peak-aligned to its frame and 4-10dB under the voice. Master with gain plus a limiter to -14 LUFS, -2.2dB true peak.
</build>
<gotchas>
Make the WebGL globe canvas at least 2 x radius x zoom x 1.18 pixels or the sphere clips flat in close-ups. Never draw prominences on the Sun's edge, they read as white hooks. Never pad the voice to fit the visuals, tighten the read instead. Speed the darkness front up near Earth or it takes 13 seconds to cross the planet. Show me a contact sheet of every beat before rendering.
</gotchas>
<start>
Ask me the inputs, write the narration with the beat each word triggers, show it to me, then build and render the video.
</start>
Build me a full teardown of this, every part in code.
The picture set the look, every shell, gear and hose is three.js code
Match its render to the picture side by side for 3 rounds before any video
Include 260 tiny pistons, hoses, screws and wires under the big gears
Make something come apart every 2-3 seconds
Pull a leg and its servo bar flips to DETACHED
Make me an animated pixel art Halloween diorama, built to be the looping cover for a 10 hour lofi music video. Build the palette on strong warm/cold contrast: a cold, rainy night against warm pockets of firelight and glowing windows. Bring it to life with great effects: rain, fire sparks, drifting smoke and flickering light. It should look crisp full screen at 1080p and loop smoothly for hours.
Opus 5.5: a hand-drawn story. a little agent wakes up at its desk, gets feedback notes, fixes them, ends on heart eyes and a green check. 53 s
Sonnet 5.5: a kinetic type showreel. six easing curves, a morphing star, particles, blurred type, "every frame written in code". 15 s
Haiku 5.5: a step-by-step White Russian recipe. ice, vodka, coffee liqueur, cream, with live counters and a checklist. 30 s
Convert this into an animation using Canvas 2D in the best creative way you can, without using any image generation model. Topic: In 1638, Galileo asked: Which path is the fastest for a ball to descend from point A to point B? His solution was a straight ramp, which is the shortest path but not the fastest! Galileo showed that a circular arc is faster. The actual answer (cycloid) was found by Bernoulli in 1696.
Build one you can actually watch. Trucks reverse onto the dock, forklifts unload and boxes slide down chutes onto the right truck.
Describe what you want to make, who it is for and what a useful result should contain. Include the purpose and constraints in your starting brief.
Choose Try in YouMind to open the task with this model and your brief. Add the notes or documents you need there, then ask for a specific deliverable such as an article, decision brief or webpage.
Read the argument, check the sources or open the rendered artifact. Give feedback on a specific part, then verify the revised work before sharing it.
Explore related workflows for articles, webpages, presentations and motion design.
Both support image input and long context. Compare their output capacity, reasoning and task focus before choosing a starting point.
Scroll horizontally to compare all models
Writing and research benchmarks, compared with model list prices.
Compare the factual accuracy of model-generated research reports to choose a model for tasks that need reliable information.
See how models turn a vague request into writing choices. Compare the results and try a reading case yourself.