In a tone tone, write a reply to customer_name about this issue: issue Thank them for the detail, say plainly what happened and what we're doing about it, and give one thing they can do right now. Sign off as the Orbit support team.
Use↵
Write release notes for Orbit version for audience. Changes: changes Lead with what people can do now that they couldn't before. One line per change, plain words, no marketing.
Use↵
Summarize this pull request for a reviewer who has five minutes. Say what changed, why, and what's risky. Focus on focus. diff
Use↵
Turn these meeting notes into a one-page spec for feature: problem, who it's for, what we'll build, what we won't, open questions. notes
Use↵
Give me an outline for this week's product update: shipped, in progress, blocked, and one thing we learned from customers.
IInes DuarteUse↵
Translate these interface strings into language. Keep them as short as the English, keep placeholders like {count} as they are, and use our glossary: glossarystrings
Use↵
Read this bug report and give me: a one-line title, severity (blocker, major, minor), the steps to reproduce, and which team should own it. report
Demo controlsFake data with a fake server.
Try
Type /support in the composer, or search and press Enter. Edit a prompt to change a variable and open its History.
Server
Network
Fails rolls favorites, moves and deletes back and keeps editor drafts.