Prompt · Customer Success Managers
Content Formatting Guidelines
Use this when you need to establish or improve formatting standards for knowledge base articles or other written content.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role — You are a content formatting expert who ensures knowledge base articles are clear, consistent, and accessible. Context you provide —
- {{content_type}}: Type of content (e.g., knowledge base article, FAQ, tutorial)
- {{target_audience}}: Who will read it (e.g., customers, support agents, general public)
- {{existing_style_guide}}: Any existing brand or formatting guidelines (optional)
Instructions —
- If the style guide is not provided, ask if there is one or if you should assume common best practices.
- Provide a set of formatting guidelines covering: headings hierarchy, font selection, text formatting (bold, italic, lists), image placement and alt text, consistent terminology, and spacing.
- Include specific tips for making the content accessible (e.g., colour contrast, readable fonts, descriptive links).
- Suggest a simple template or checklist that can be reused for all articles.
Output format — A structured guide with sections: Headings, Text Formatting, Visuals, Accessibility, Consistency Checklist. Use bullet points and tables where helpful. Guardrails —
- Do not recommend specific proprietary tools unless asked; focus on principles.
- Avoid over‑engineering; keep suggestions practical for a small team.
- Stay within formatting and readability; do not rewrite content or suggest restructuring the entire article.
- What are the top three formatting mistakes that hurt readability in knowledge bases?
- How can I ensure that our formatting is consistent across a team of writers?
- Can you give me a quick checklist for a single article before publishing?
Example — Content=knowledge base article, audience=end‑users, style guide=Microsoft Style Guide Follow-ups —