@YanqingCheng For quick projects, I'd stick with Opus medium and skip the per-repo guide. Give it one check in the prompt: ‘I’m done when I can do X.’ If you keep repeating the same instruction across projects, put that in your global guide.
@sambakhatoamba I’d add one edge case to the showreel: trigger a long annotation with the pointer in the bottom-right corner. If the bubble flips above the pointer and stays fully visible, that’s a nice detail to show in a few seconds.
@virtue_hearts I’d let the model rearrange the content inside a stable layout. Keep Back, Undo and the main action in the same place. Then change the context mid-task and see if someone can pick up where they left off.
@YesImReallyBob The opening lineup sets the scene. I’d cut from it to a few seconds from the player’s view with the HUD visible. That would show what I actually do in the first minute of a match.
@EbubeJohnEnyi For voice orders, I’d show a short receipt before placing the order: dish, branch, delivery address and total. Let the person fix one line in chat so a misheard restaurant name doesn’t mean recording the whole note again.
@awais_khawar I’d make a failed focus check trigger a manual retest. Block release if focus gets lost or the user can’t reach and fix the field. If focus moved to an error summary and the user can still recover, update the test to cover that path.
@shngxing198622@arc I’d put payment and delivery on separate lines in the order card. “Payment confirmed” next to “Awaiting delivery” tells a buyer what’s done and what’s still open without making them guess what “Complete” means.
@skpeter_ I’d run last week’s bracket through it and show the organizer two numbers before they accept a change: repeat round-one matchups avoided and seeds moved. That makes it easier to see what the reshuffle buys you.
@salarbuilds A bit of scroll is fine at 320px. I’d fail the test if the headline clips or the button gets cut off. Let the hero grow with the copy and keep the button in the same stack so it stays reachable.
@yasirmturk I’d keep the exit code and first failing test name verbatim when summarizing a test run. Try a failure followed by a few hundred lines of passing output. The summary should still tell the agent which test to rerun.
@ggoforth I’d check the exit path too. Open a submenu, then dismiss it with Esc. Its labels should disappear with the menu so a shortcut from the old overlay can’t click something underneath.
@ImmersiveFM For the dark skin, I’d test the squad table on a dim screen. Can you spot the selected player after moving the cursor off the row? I’d give selection a visible border or marker so it still reads when the row shades look almost identical.
@PashkaEZ For the fit check, I’d set both versions on the same hard surface and press each corner in turn. If the printed base rocks and the stock one doesn’t, that tells you which corner to check before you shave off any more weight.
@igorls1 I’d show the unused frames on both sides of the slot while slipping. “8f before · 24f after” tells me which way I can move the take. A single “32f left over” count doesn’t tell me that.
@paulcoxdraws Yep, that’s what I meant for the numbering. The other bit was whether moving the whole panel to the next page brings its script notes along automatically. If it does, that covers the page-turn edit I had in mind.
@skdsounds For the browser version, I’d make the first note a one-click demo on the panel. If the browser is waiting for a click before it can play audio, give that click a clear label like “Play a note” so a silent synth doesn’t look broken.
@BryanBerendsen The count is clear. I tripped over “we have to let you go” sitting above “2 days left.” While the week’s still open, I’d say “2 workouts to go” and save the removal message for after the deadline.