diff --git a/README.md b/README.md
index b0dab8e..8ded4e2 100644
--- a/README.md
+++ b/README.md
@@ -44,6 +44,7 @@ How to contribute:
 - Use https://chirpy.cotes.page/posts/write-a-new-post/ for formatting and embedding media.
 - You can link your author profile to social accounts like Twitter/X, LinkedIn.
 - GitHub Copilot (especially with the Opus model) can assist with writing posts, but it may miss some conventions, so review the guide manually.
+- Learn how to use callout boxes: [Callout Boxes Guide](docs/CALLOUT-BOXES.md)
 
 Learn about writing new posts in Chirpy: [Writing a New Post](https://chirpy.cotes.page/posts/write-a-new-post/)
 
diff --git a/docs/CALLOUT-BOXES.md b/docs/CALLOUT-BOXES.md
new file mode 100644
index 0000000..98c5ff6
--- /dev/null
+++ b/docs/CALLOUT-BOXES.md
@@ -0,0 +1,250 @@
+# How to Use Callout Boxes in Blog Posts
+
+This guide explains how to properly use styled callout boxes in The Custom Engine blog posts.
+
+## Overview
+
+Callout boxes (also called "prompts" in the Chirpy theme) are special formatted blocks that highlight important information in your blog posts. They provide visual emphasis and help readers quickly identify different types of content.
+
+## Available Callout Types
+
+The blog supports four types of callout boxes:
+
+1. **`.prompt-info`** - For general information and helpful notes
+2. **`.prompt-tip`** - For tips, best practices, and helpful suggestions
+3. **`.prompt-warning`** - For warnings, important considerations, and caveats
+4. **`.prompt-danger`** - For critical security warnings and dangerous operations
+
+## Syntax
+
+The syntax for creating callout boxes uses Markdown blockquotes with a Kramdown attribute:
+
+```markdown
+> Your callout text goes here.
+{: .prompt-TYPE}
+```
+
+**Important:** 
+- The callout text must be a blockquote (start with `>`)
+- The attribute line `{: .prompt-TYPE}` must be on its own line immediately after the blockquote
+- There should be **no blank line** between the blockquote and the attribute line
+
+## Examples
+
+### Info Callout
+
+Use `.prompt-info` for general information that provides helpful context:
+
+```markdown
+> Teams chats are persistent by design, which means both opportunities and challenges for bot developers.
+{: .prompt-info}
+```
+
+**Rendered as:**
+
+> Teams chats are persistent by design, which means both opportunities and challenges for bot developers.
+{: .prompt-info}
+
+---
+
+### Tip Callout
+
+Use `.prompt-tip` for tips, best practices, and helpful suggestions:
+
+```markdown
+> Use OnKnowledgeRequested during development to verify query rewrites, then decide whether to keep it visible in production.
+{: .prompt-tip}
+```
+
+**Rendered as:**
+
+> Use OnKnowledgeRequested during development to verify query rewrites, then decide whether to keep it visible in production.
+{: .prompt-tip}
+
+---
+
+### Warning Callout
+
+Use `.prompt-warning` for important considerations, caveats, and non-critical warnings:
+
+```markdown
+> The current implementation is designed exclusively for single-session analysis.
+{: .prompt-warning}
+```
+
+**Rendered as:**
+
+> The current implementation is designed exclusively for single-session analysis.
+{: .prompt-warning}
+
+---
+
+### Danger Callout
+
+Use `.prompt-danger` for critical security warnings and dangerous operations:
+
+```markdown
+> Never commit access tokens or credentials to source control. Always use environment variables or secure credential stores, and implement proper token refresh logic.
+{: .prompt-danger}
+```
+
+**Rendered as:**
+
+> Never commit access tokens or credentials to source control. Always use environment variables or secure credential stores, and implement proper token refresh logic.
+{: .prompt-danger}
+
+---
+
+## Multi-line Callouts
+
+Callouts can contain multiple lines and even Markdown formatting:
+
+```markdown
+> Before deploying the tool, review the [requirements](https://example.com/requirements) to ensure your environment is compatible, then execute the [setup steps](https://example.com/setup) to configure the tool.
+{: .prompt-warning}
+```
+
+**Rendered as:**
+
+> Before deploying the tool, review the [requirements](https://example.com/requirements) to ensure your environment is compatible, then execute the [setup steps](https://example.com/setup) to configure the tool.
+{: .prompt-warning}
+
+---
+
+## Best Practices
+
+### ✅ DO:
+
+- Use callouts sparingly to maintain their impact
+- Choose the appropriate type based on the severity/nature of the information
+- Keep callout text concise and focused on a single point
+- Use Markdown formatting (links, bold, code) within callouts when appropriate
+- Ensure the attribute line immediately follows the blockquote (no blank lines)
+
+### ❌ DON'T:
+
+- Don't overuse callouts - too many reduce their effectiveness
+- Don't use `.prompt-danger` for non-security issues
+- Don't add blank lines between the blockquote and the attribute line
+- Don't use inline color styling (e.g., `<span style="color:magenta">`) as it creates accessibility issues
+- Don't use callouts for content that should be in the main text
+
+### When to Use Each Type:
+
+- **Info** (`.prompt-info`): Background information, explanations, context
+- **Tip** (`.prompt-tip`): Best practices, helpful suggestions, pro tips, recommendations
+- **Warning** (`.prompt-warning`): Important considerations, limitations, caveats, things to be aware of
+- **Danger** (`.prompt-danger`): Security risks, data loss risks, irreversible operations, critical issues
+
+---
+
+## Common Mistakes
+
+### ❌ Incorrect - Blank line between blockquote and attribute:
+
+```markdown
+> This is a callout.
+
+{: .prompt-info}
+```
+
+This will NOT render as a callout because of the blank line.
+
+### ✅ Correct - No blank line:
+
+```markdown
+> This is a callout.
+{: .prompt-info}
+```
+
+---
+
+### ❌ Incorrect - Using inline styling instead of callouts:
+
+```markdown
+<span style="color:magenta">
+This is important information.
+</span>
+```
+
+This creates accessibility issues and is not consistent with the blog's styling.
+
+### ✅ Correct - Use proper callout boxes:
+
+```markdown
+> This is important information.
+{: .prompt-info}
+```
+
+---
+
+## Accessibility Considerations
+
+- Callout boxes use semantic HTML and proper ARIA labels for screen readers
+- Color is not the only indicator - icons and backgrounds provide additional visual cues
+- Inline color styling (like `style="color:magenta"`) should be avoided as it may not meet WCAG contrast requirements
+- All callout types are keyboard accessible and work with assistive technologies
+
+---
+
+## Testing Your Callouts
+
+After adding callouts to your post:
+
+1. **Preview locally**: Run `bundle exec jekyll serve --livereload --baseurl /mcscatblog` and check the rendered output
+2. **Check responsiveness**: View on different screen sizes to ensure callouts display properly
+3. **Verify accessibility**: Ensure text is readable and has sufficient contrast
+4. **Review consistency**: Make sure callout types match the content appropriately
+
+---
+
+## Examples from Real Posts
+
+Here are some real examples from published posts:
+
+### Security Warning (from response-analysis-copilot-tool.md):
+```markdown
+> Never commit access tokens or credentials to source control. Always use environment variables or secure credential stores, and implement proper token refresh logic.
+{: .prompt-danger}
+```
+
+### Helpful Tip (from copilot-studio-teams-deployment-ux.md):
+```markdown
+> Clearing state on inactivity prevents the AI from hitting context length limits and avoids weird behaviors when users return later.
+{: .prompt-tip}
+```
+
+### Important Information (from copilot-studio-teams-deployment-ux.md):
+```markdown
+> Teams chats are persistent by design, which means both opportunities and challenges for bot developers.
+{: .prompt-info}
+```
+
+### Important Consideration (from response-analysis-copilot-tool.md):
+```markdown
+> The current implementation is designed exclusively for single-session analysis.
+{: .prompt-warning}
+```
+
+---
+
+## Additional Resources
+
+- [Chirpy Theme Documentation - Writing a New Post](https://chirpy.cotes.page/posts/write-a-new-post/)
+- [Kramdown Syntax Documentation](https://kramdown.gettalong.org/syntax.html)
+- Blog README: [README.md](/README.md)
+
+---
+
+## Quick Reference
+
+| Callout Type | Use Case | Example |
+|-------------|----------|---------|
+| `.prompt-info` | General information, helpful context | Explaining how a feature works |
+| `.prompt-tip` | Best practices, suggestions | Recommending an optimal approach |
+| `.prompt-warning` | Important considerations, limitations | Noting single-session design |
+| `.prompt-danger` | Security risks, critical warnings | Warning about credential storage |
+
+---
+
+**Remember:** Properly styled callout boxes enhance readability and help readers quickly identify important information. Use them wisely to make your technical content more accessible and effective!
diff --git a/docs/CALLOUT-EXAMPLES.md b/docs/CALLOUT-EXAMPLES.md
new file mode 100644
index 0000000..6e6362e
--- /dev/null
+++ b/docs/CALLOUT-EXAMPLES.md
@@ -0,0 +1,64 @@
+# Callout Box Examples
+
+This document demonstrates how each callout type appears when rendered.
+
+## Info Callout (`.prompt-info`)
+
+Used for general information and helpful context.
+
+> Teams chats are persistent by design, which means both opportunities and challenges for bot developers.
+{: .prompt-info}
+
+---
+
+## Tip Callout (`.prompt-tip`)
+
+Used for best practices, helpful suggestions, and tips.
+
+> Use OnKnowledgeRequested during development to verify query rewrites, then decide whether to keep it visible in production.
+{: .prompt-tip}
+
+---
+
+## Warning Callout (`.prompt-warning`)
+
+Used for important considerations, limitations, and caveats.
+
+> The current implementation is designed exclusively for single-session analysis.
+{: .prompt-warning}
+
+---
+
+## Danger Callout (`.prompt-danger`)
+
+Used for critical security warnings and dangerous operations.
+
+> Never commit access tokens or credentials to source control. Always use environment variables or secure credential stores, and implement proper token refresh logic.
+{: .prompt-danger}
+
+---
+
+## Multi-line Example
+
+Callouts can contain multiple lines and Markdown formatting like **bold**, *italic*, `code`, and [links](https://example.com).
+
+> Before deploying the tool, review the **requirements** to ensure your environment is compatible. Make sure to:
+> - Check system prerequisites
+> - Verify authentication settings
+> - Test in a development environment first
+> 
+> Then execute the setup steps to configure the tool properly.
+{: .prompt-warning}
+
+---
+
+## Syntax Reminder
+
+```markdown
+> Your callout text goes here.
+{: .prompt-TYPE}
+```
+
+Where `TYPE` is one of: `info`, `tip`, `warning`, or `danger`.
+
+**Important:** No blank line between the blockquote and the attribute line!
diff --git a/docs/README.md b/docs/README.md
new file mode 100644
index 0000000..460eb08
--- /dev/null
+++ b/docs/README.md
@@ -0,0 +1,85 @@
+# Callout Boxes Documentation - Summary
+
+## What's Been Created
+
+This documentation provides comprehensive guidance on using properly styled callout boxes in The Custom Engine blog.
+
+## Files Created
+
+1. **`docs/CALLOUT-BOXES.md`** - Complete documentation guide with:
+   - Overview of callout boxes
+   - All four available types (info, tip, warning, danger)
+   - Proper syntax and usage
+   - Multi-line examples
+   - Best practices and common mistakes
+   - Accessibility considerations
+   - Real examples from published posts
+   - Quick reference table
+
+2. **`docs/CALLOUT-EXAMPLES.md`** - Visual examples showing:
+   - How each callout type renders
+   - Multi-line callout example
+   - Syntax reminder
+
+3. **Updated `README.md`** - Added link to callout boxes guide in the Authoring tips section
+
+## Quick Start
+
+To use callout boxes in your blog post:
+
+1. Write your text as a blockquote (start with `>`)
+2. On the next line (no blank line!), add `{: .prompt-TYPE}`
+3. Replace TYPE with: `info`, `tip`, `warning`, or `danger`
+
+### Example:
+
+```markdown
+> This is important information for readers.
+{: .prompt-info}
+```
+
+## The Four Types
+
+| Type | Class | Use For |
+|------|-------|---------|
+| **Info** | `.prompt-info` | General information, helpful context |
+| **Tip** | `.prompt-tip` | Best practices, suggestions, tips |
+| **Warning** | `.prompt-warning` | Important considerations, limitations |
+| **Danger** | `.prompt-danger` | Security risks, critical warnings |
+
+## Key Points
+
+✅ **DO:**
+- Use callouts sparingly
+- Keep text concise
+- No blank line between blockquote and attribute
+- Choose appropriate type for content
+
+❌ **DON'T:**
+- Don't use inline color styling (e.g., `<span style="color:magenta">`)
+- Don't add blank lines before the attribute
+- Don't overuse callouts
+- Don't use `.prompt-danger` for non-security issues
+
+## Why This Matters
+
+The previous blog post review identified that:
+- Inline color styling (like `<span style="color:magenta">`) creates accessibility issues
+- It's inconsistent with the blog's styling
+- Properly styled callout boxes are the correct approach
+
+This documentation ensures all contributors know how to:
+- Use callout boxes correctly
+- Maintain accessibility standards
+- Keep consistent styling across all posts
+
+## Where to Find Help
+
+- **Full Documentation**: [docs/CALLOUT-BOXES.md](CALLOUT-BOXES.md)
+- **Visual Examples**: [docs/CALLOUT-EXAMPLES.md](CALLOUT-EXAMPLES.md)
+- **Chirpy Theme Docs**: https://chirpy.cotes.page/posts/write-a-new-post/
+- **Blog README**: [README.md](../README.md)
+
+---
+
+**Next Steps:** When writing blog posts, refer to `docs/CALLOUT-BOXES.md` for complete guidance on using callout boxes properly!