Use the Error intent of the Skeuomorphic button for the confirming action, and keep Cancel as the neutral secondary beside it . Put the destructive button on the right, where the primary sits in every other modal .
AI chat is the surface an assistant answers through: a thread of questions and replies, a composer to ask in, and the states in between that say the assistant is working. Orvain's AI Chat family holds three blocks: a thread whose reply streams in with numbered sources, a prompt library opened on the composer, and a toolbar that rewrites a selection of text.
What separates a chat people trust from one they second-guess is mostly in the in-between states. A thinking line that names what is being searched, a reply that arrives word by word with a way to stop it, sources numbered against the sentences that use them, and a rewrite shown beside the original before it replaces anything. Each block here carries those states, and drops the animation when a reader asks for reduced motion.
A panel beside the documentation that answers questions from it. Each reply cites the pages it used as numbered cards under the answer, so a reader can check the claim before they rely on it, and rate the reply when it misses.
A toolbar that appears over selected text in a document, offering to improve, shorten or translate it. The rewrite appears under the original with Replace, Try again and Discard, so nothing a person wrote is lost to a click they did not mean.
A reply can take several seconds to generate, and streaming turns that wait into visible progress: the reader can start reading after the first words and stop the reply if it is going the wrong way. The block marks the message as busy while it streams, so a screen reader announces the reply once it is complete rather than word by word, and it shows the whole reply at once for readers who prefer reduced motion.
Number the sources and put the numbers in the sentences that rely on them, then list the sources as cards under the reply with a title and where they live. A list of links at the end with no numbers in the text tells a reader that sources exist but not which claim each one supports, which is the question they actually have.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
AI chat is the surface an assistant answers through: a thread of questions and replies, a composer to ask in, and the states in between that say the assistant is working. Orvain's AI Chat family holds three blocks: a thread whose reply streams in with numbered sources, a prompt library opened on the composer, and a toolbar that rewrites a selection of text.
What separates a chat people trust from one they second-guess is mostly in the in-between states. A thinking line that names what is being searched, a reply that arrives word by word with a way to stop it, sources numbered against the sentences that use them, and a rewrite shown beside the original before it replaces anything. Each block here carries those states, and drops the animation when a reader asks for reduced motion.
A panel beside the documentation that answers questions from it. Each reply cites the pages it used as numbered cards under the answer, so a reader can check the claim before they rely on it, and rate the reply when it misses.
A toolbar that appears over selected text in a document, offering to improve, shorten or translate it. The rewrite appears under the original with Replace, Try again and Discard, so nothing a person wrote is lost to a click they did not mean.
A reply can take several seconds to generate, and streaming turns that wait into visible progress: the reader can start reading after the first words and stop the reply if it is going the wrong way. The block marks the message as busy while it streams, so a screen reader announces the reply once it is complete rather than word by word, and it shows the whole reply at once for readers who prefer reduced motion.
Number the sources and put the numbers in the sentences that rely on them, then list the sources as cards under the reply with a title and where they live. A list of links at the end with no numbers in the text tells a reader that sources exist but not which claim each one supports, which is the question they actually have.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
Which button should I use for a destructive action in a modal?
Use the Error intent of the Skeuomorphic button for the confirming action, and keep Cancel as the neutral secondary beside it . Put the destructive button on the right, where the primary sits in every other modal, so the order never changes with the risk .
Which button should I use for a destructive action in a modal?
Use the Error intent of the Skeuomorphic button for the confirming action, and keep Cancel as the neutral secondary beside it . Put the destructive button on the right, where the primary sits in every other modal .
Answers come from your docs and can be wrong. Check the sources.
Which button should I use for a destructive action in a modal?
Use the Error intent of the Skeuomorphic button for the confirming action, and keep Cancel as the neutral secondary beside it . Put the destructive button on the right, where the primary sits in every other modal, so the order never changes with the risk .
Which button should I use for a destructive action in a modal?
Use the Error intent of the Skeuomorphic button for the confirming action, and keep Cancel as the neutral secondary beside it . Put the destructive button on the right, where the primary sits in every other modal .
Answers come from your docs and can be wrong. Check the sources.