Moment

destructive_action

Delete, cancel, irreversible. Explicit consequences, friction OK.

Destructive

Weights

ContentRX adjusts how strictly each standard is enforced in this moment. Cross-reference any standard by its ID to read the full rule.

Emphasized — flag more aggressively

  • CLR-01 — Use plain language. Avoid jargon, technical terms, or insider language unless the audience requires it.
    Consequences must be stated in plain, unambiguous language.
  • VT-05 — Show empathy in error and failure states, scaled to the severity of the problem. High-impact errors (payment failures, data loss) should acknowledge the frustration and reassure the user. Low-impact errors (failed upload, timeout) should be clear and helpful without over-dramatizing.
    Acknowledge the weight of the action. Don't be flippant.

Relaxed — minor deviations acceptable

  • STR-02 — Keep paragraphs short. 2-3 sentences max for UI copy and help content.
    Extra content density is acceptable — friction prevents mistakes.
  • CLR-03 — Use short sentences. Aim for 15-20 words per sentence. Sentences over 25 words should almost always be split.
    Longer sentences are fine when explaining irreversible consequences.

Example pairs

Concrete "this, not that" examples observed in 1 style guides. Attribution is inline — see /ethics for the commitment and /sources for the full list.

  • VT-05 · short_ui_copyall-rights-reserved

    Not this. Are you sure you want to proceed with this dangerous action?

    But this. Delete 'My Document' permanently? This can't be undone.

    Apple HIG: name the specific object + the specific consequence. 'Dangerous action' is abstract; the actual outcome is what the user needs. — Apple HIG · Alerts

  • ACT-01 · button_ctaall-rights-reserved

    Not this. OK

    But this. Delete

    Apple HIG: prefer specific verbs over generic affirmatives, especially on destructive confirmations. — Apple HIG · Buttons

← The content model