Output styles

Adapts answers for newcomers by defining jargon, explaining why each step matters and avoiding assumed knowledge, from light glossing to full guidance. Use when the reader is new to the topic.

Makes any answer more conversational, from relaxed everyday wording to a chatty, friend-over-coffee voice, while keeping every fact, number and warning accurate.

Shortens answers by leading with the result and cutting preamble, recaps and filler, from light trimming to bare answers. Use when you want less reading and the same substance.

Leads with concrete examples, from one illustrative case after the explanation to an example before every rule, so readers see the idea in action before the abstraction.

Structures answers as ordered, numbered steps the reader can follow and check, from a short numbered list to detailed steps with expected results. Use for procedures, setups and how-to answers.

Shapes answers visually, from tables where they help to diagrams, timelines and structured layouts throughout, so relationships and comparisons are seen rather than read.

Shapes code answers as minimal changes to existing code instead of whole rewritten files, from a diff with a short note to a bare unified diff. Use when reviewing or applying code edits.

Shifts any answer toward a formal, professional register, from lightly polished wording to fully formal correspondence and ceremonial language, without changing the content.

Lowers the reading effort of any answer, from swapping jargon for everyday words to a grade 6 reading level, keeping every fact accurate. Use for the general public or second-language readers.

Shapes any answer for skimming, from bolded key sentences and short paragraphs to headed sections, bullets first, and a strict table-first layout.

Increases the depth of any answer, from adding the key reasoning behind it to exhaustive coverage with alternatives, edge cases, trade-offs and sources. For readers who want the full picture.

Makes any answer warmer and more personal, from simply friendly to deeply empathetic, while keeping the substance, accuracy and honesty of the answer intact.

Raises the technical depth of any answer, from precise terminology to expert density that assumes domain knowledge, skips basics and states mechanisms, units and limits exactly.