splitting the prompts into individual files for ease of use (#3981)

* splitting the prompts into individual files for ease of use

Author: Chibuzor-Nwemambu

apps/design-system-docs/docs/tone-guide/friendly-minimalist-blend.md

@@ -0,0 +1,50 @@
+# Prompt
+Rewrite/ write the (following) content in a Friendly Minimalist style.
+Balance approachability with efficiency: write in a professional but warm tone that is concise and easy to scan.
+Use short to medium sentences. Keep language clear and inclusive.
+Present steps, rules, or instructions in bullet points or numbered lists.
+Remove unnecessary words, repetition, or flourish, while keeping a natural, welcoming flow.
+Use the active voice and direct phrasing.
+Avoid slang, sarcasm, or heavy humour.
+Provide enough context to be understandable for mixed audiences (IT and non-IT). Avoid jargon unless explained.
+Always use Oxford English spelling (e.g., organise, recognise, analyse).
+Ensure content is logically structured with consistent formatting (headings, lists, sections).
+Provide the documentation content only.”
+
+# Writing Rules
+# Tone
+Professional and approachable — warm, but not casual.
+Inclusive — avoid jargon unless explained.
+No slang, sarcasm, or heavy humour.
+
+# Clarity
+Use short to medium sentences.
+Present steps or rules in bullet points or numbered lists.
+Provide enough context to be understandable by IT and non-IT audiences.
+
+# Conciseness
+Remove unnecessary words, repetition, or filler.
+Keep explanations brief, but don’t strip away essential meaning.
+Focus on what readers need to know/do.
+
+# Consistency
+Use active voice and direct phrasing.
+Keep formatting uniform (headings, lists, sections).
+Ensure logical flow: introduction → details → outcome.
+
+# Spelling & Grammar
+Always use Oxford English spelling (e.g., organise, recognise, analyse).
+Maintain correct grammar and punctuation.
+
+# Avoid
+Long, dense paragraphs.
+Overly formal or rigid tone.
+Overly casual tone (slang, emojis, playful humour).
+Redundant explanations or wordiness.
+
+# Quick Test Questions
+
+Is this concise and approachable?
+Could both IT and non-IT readers understand it quickly?
+Does it use active voice, clear lists, and logical structure?
+Am I following Oxford English spelling?

apps/design-system-docs/docs/tone-guide/friendly-professional.md

@@ -0,0 +1,47 @@
+# Prompt
+Rewrite/ write the (following) content in a Friendly Professional style.
+Use approachable, inclusive, and clear language that balances warmth with professionalism.
+Write for a mixed audience (developers, designers, QAs, and non-IT staff) — avoid jargon where possible, but do not oversimplify technical details.
+Always use the active voice and direct phrasing.
+Focus on helping the reader succeed by offering practical advice and actionable steps.
+Use short to medium length sentences (avoid long, complex structures).
+Keep the tone welcoming and collaborative, without being casual or playful.
+Avoid slang, sarcasm, or heavy humour.
+Ensure consistency, readability, and accessibility for all users.
+Always follow Oxford English spelling (e.g., organise, recognise, analyse).
+Only use lists or bullet points when the content is naturally a list(e.g., steps, rules, dos/don'ts).
+
+# Writing Rules
+# Tone
+Friendly but professional — Use clear, warm, approachable language that welcomes and supports the reader, not casual language.
+Inclusive — use language that makes everyone feel welcome. Address the reader directly when appropriate, using “you” and “we” to foster connection.
+Use positive, constructive phrasing to guide and motivate.
+Avoid slang, sarcasm, or heavy humour.
+
+# Clarity
+Active voice (“Do X”, not “X should be done”).
+Short to medium sentences — avoid long or overly complex structures.
+Only use bullet points or lists when the content is naturally a list(e.g., steps, dos, don'ts, comparisons).
+Structure content with clear headings, lists, and logical flow.
+Review for clarity, accuracy, and tone; ensure every sentence adds value.
+
+# Consistency
+Use clear, direct phrasing (no jargon unless explained).
+Keep formatting consistent (headings, lists, code snippets).
+Ensure accessibility (plain language, logical flow).
+
+# Spelling & Grammar
+Always use Oxford English spelling (e.g., organise, recognise, analyse).
+Use correct grammar and punctuation throughout.
+
+# Avoid
+Overly casual tone (slang, memes, excessive emojis).
+Long, dense paragraphs that are hard to scan.
+Jargon or abbreviations without explanation.
+Switching between styles — keep one consistent voice.
+
+# Quick Test Questions
+Does this sound warm and professional at the same time?
+Could someone outside of IT still understand it?
+Are the sentences clear, active, and scannable?
+Am I following Oxford English spelling?

apps/design-system-docs/docs/tone-guide/index.md

@@ -1,6 +1,6 @@
 # Documentation Tone and Style
 
-Our documentation should sound consistent, clear and approachable. To achieve this, we've agreed on two official styles: Sprout-inspired and Minimalist. 
+Our documentation should sound consistent, clear and approachable. To achieve this, we've agreed on three official styles: Friendly-Professional and Minimalist and a blend of both. 
 These styles will be used as the foundation for all documentation.
 
 
@@ -55,4 +55,32 @@ Calm and understated: The tone is quiet, confident, and avoids hype or persuasiv
 Accessible: Language is simple, avoiding jargon and complex sentence structures.
 
 Overall, minimalist documentation prioritizes clarity, ease of use, and a clean reading experience,
-helping users find what they need quickly without distraction.
+helping users find what they need quickly without distraction.
+
+
+
+# 3. Blend: Friendly-Minimalist Style
+
+The friendly-minimalist tone blends warmth and inclusivity with clarity and brevity.
+It aims to make documentation approachable and professional while keeping it concise and easy to scan.
+This style balances the supportive voice of Friendly-Professional with the streamlined efficiency of Minimalist, ensuring content is welcoming without being wordy.
+The goal is to create documentation that is accessible to all readers, reduces cognitive load, and still feels human.
+
+Its tone is:
+
+Approachable but concise: Content is warm and inclusive, but sentences are short and to the point.
+
+Clear and scannable: Uses paragraphs as the default, with bullet points or lists only when the content naturally calls for them (e.g., steps, rules).
+
+Professional yet friendly: The voice is confident and supportive, without being casual or playful.
+
+Efficient but contextual: Provides enough explanation to be clear to both IT and non-IT readers, while avoiding unnecessary detail.
+
+Active and direct: Sentences use active voice and straightforward phrasing.
+
+Consistent: Terminology, structure, and formatting remain uniform, ensuring readability.
+
+Oxford English: Always follows Oxford English spelling conventions (e.g., organise, recognise, analyse).
+
+Overall, the friendly-minimalist tone creates documentation that is both approachable and efficient —
+it supports readers with a professional, human voice while delivering information in a clean, concise way.

apps/design-system-docs/docs/tone-guide/minimalist.md

@@ -0,0 +1,49 @@
+# Prompt
+Rewrite/ write the (following) content in a Minimalist style.
+Focus only on the essential information — remove all extra words, explanations, or flourish.
+Use short, clear and concise sentences or bullet points.
+Structure information in a way that is easy to scan quickly and undestand.
+Avoid metaphors, stories, conversational tone, unnecessary details, embellishments, or emotional language.
+Keep language neutral and direct.
+Organize content with clear headings and lists.
+Ensure consistency and precision in terminology.
+Focus on usability and efficiency.
+Always use Oxford English spelling (e.g., organise, recognise, analyse).
+Present steps, rules, or instructions in a clear, numbered or bulleted list where appropriate.
+Provide the documentation content only.
+
+# Writing Rules
+# Tone
+Neutral, direct, efficient.
+No conversational flourishes, metaphors, or stories.
+Keep it factual and stripped down.
+Use gender-neutral language and avoid assumptions.
+
+# Clarity
+Use short, clear and simple sentences.
+Prefer bullet points or numbered lists.
+Structure content with clear headings, lists, and whitespace for easy scanning.
+Arrange steps logically for fast scanning.
+Make instructions actionable and easy to follow.
+
+# Consistency
+Use consistent terminology (no synonyms that create confusion).
+Keep formatting uniform across lists and steps.
+Focus on what readers must do/know — nothing more.
+Review for clarity and accuracy. Ensure every word adds value.
+
+# Spelling & Grammar
+Always use Oxford English spelling (e.g., organise, recognise, analyse).
+Ensure correct punctuation, but avoid complex structures.
+
+# Avoid
+Explanations, metaphors, or “friendly” padding.
+Long sentences or paragraphs.
+Emojis, humour, or casual tone.
+Extra details beyond the minimum required.
+
+# Quick Test Questions
+Can this be read and understood at a glance?
+Did I strip out every non-essential word?
+Are steps or rules written in bullet points or short lines?
+Am I following Oxford English spelling?