Define a Custom Style once so every future chat gets the same tone by default

Write a Custom Style definition I can save in Claude's settings, so this formatting and tone applies automatically to future chats without me re-explaining it or pasting samples each time. A saved Style is a short standing description Claude reads before every reply, not a one-off instruction, so word choice here matters more than in a normal prompt — vague adjectives left in a saved Style get applied vaguely forever, not just once.

WHAT THIS STYLE IS FOR
Internal Slack-style status updates to a technical team that reads a lot of these and has no patience for preamble.

CONCRETE PATTERNS TO ENCODE
Lead with the outcome or blocker in the first sentence. Use short paragraphs, no more than 3 sentences. State numbers and dates exactly, never 'recently' or 'soon.' End with a clear next action or 'no action needed' if there genuinely isn't one. State these as instructions Claude can act on directly ("open with the direct answer before any context," "never use more than one exclamation point per response, and only when something genuinely surprising happened"), not as adjectives ("be punchy") that leave the actual behavior underspecified.

WHAT THIS STYLE SHOULD AVOID
No 'I hope this finds you well' or similar opener. No hedging phrases like 'just wanted to check in' before the actual point. No exclamation points. No emoji. Naming the specific thing to avoid matters as much as naming what to do — a Style that only says what to do leaves Claude free to drift back toward whatever its own default happens to be for everything it doesn't explicitly cover.

BEFORE / AFTER EXAMPLE
Write one short example (2-4 sentences) in Claude's typical unstyled default voice, then rewrite the same content applying every rule above. The contrast should make each rule's effect visible and checkable, not just asserted — a Style description that never gets demonstrated against a concrete example is much easier to write vaguely without noticing.

CONSTRAINTS
- Keep the whole Style description itself under 150 words for the Style description itself — a Style that is too long to actually be read as a standing rule defeats its own purpose, and the discipline of fitting the pattern into a tight description is itself a good check on whether the pattern is concrete enough to state briefly.
- Do not describe a Style so specific it would look wrong applied to a very different kind of request — if someone pastes an unrelated creative writing request into a chat with this Style active, the output should just be plain, direct prose — not forced into a fake status-update shape — a Style meant for Internal Slack-style status updates to a technical team that reads a lot of these and has no patience for preamble. should still produce something sensible if applied to an unrelated question, even if it's not the ideal use case, rather than producing broken or bizarre output outside its intended lane.

IF I ALREADY HAVE ANOTHER SAVED STYLE FOR A DIFFERENT PURPOSE
Do not try to reconcile the two into one universal style — a Style is meant to be switched between per chat, not merged, so keep this one narrowly true to Internal Slack-style status updates to a technical team that reads a lot of these and has no patience for preamble. even if it means having more than one saved Style for different situations.

OUTPUT
The Style description, ready to paste into Custom Style settings as-is, followed by the before/after example clearly labeled as a demonstration, not part of the saved Style text itself.