What I do
I guide you through creating and publishing visually-rich blog posts in this SvelteKit markdown blog. I ensure proper file structure, header images, frontmatter format, image handling, and markdown syntax.
When to use me
Use this skill whenever you need to:
- Create a new blog post with header image
- Add a blog to the static/blogs/ directory
- Publish content with proper metadata and visuals
- Organize blog images in the correct folder structure
- Enhance posts with images, diagrams, and visual content
Personal Blogger Tone
Write as a genuine human being sharing your thoughts, discoveries, and experiences—not as a company, marketer, or thought leader. Simon Willison's blog is the ideal model: personal, curious, humble, and practical.
Key Characteristics
- Be yourself: Write in your natural voice. Use "I" freely and share personal experiences. Don't adopt a corporate or "influencer" tone.
- No hype or sales pitch: Avoid promotional language like "game-changing," "revolutionary," "must-have," or "transformative." Simply explain what something is and why you found it interesting or useful.
- Embrace learning: Share what you just learned, what surprised you, what confused you. Celebrating even basic discoveries is empowering for you and your readers.
- Stay humble: You don't have all the answers. Acknowledge uncertainty, share incomplete thoughts, and be open about what you don't know.
- Document your process: Explain how you do things, what tools you use, what didn't work. This is genuinely useful content.
- No pressure to be unique: You don't need to say something no one has ever said. Write about what you learned, what you built, what you found interesting.
- Credit others: Always link to and name the creators, authors, and projects you reference. It's generous and useful.
What to Avoid
- Clickbait titles or sensational claims
- "Influencer" language ("Let me tell you why this is HUGE...")
- Selling anything (products, courses, newsletters)
- Pretending to be an expert on everything
- Writing to impress rather than to share
What to Embrace
- "Here's what I just figured out..."
- "I tried X and here's what happened..."
- "This confused me at first, but..."
- "I'm not sure about this, but..."
- "I learned this from [person/project]..."
- "Here's how I do X..."
Mandatory Web Search Before Writing
ALWAYS perform a web search BEFORE writing any blog content.
This is a mandatory requirement for every blog post. Before writing:
- Search for current information on your topic using relevant search terms
- Check for recent news, announcements, or developments
- Find official sources (company blogs, documentation, research papers)
- Verify information is up-to-date and accurate
- Gather links to cite and reference in your content
This ensures your blog posts are current, accurate, and provide value with fresh perspectives.
Blog Post Format
File Location
static/
├── blogs/ # Blog markdown files
│ ├── getting-started.md
│ └── my-first-blog.md
- Blog markdown files go in:
static/blogs/
- Use kebab-case for filenames:
my-first-blog.md
Frontmatter (Required Metadata)
Every blog post must start with YAML frontmatter with a header image:
---
title: Your Blog Title Here
date: 2025-01-15
category: 'Category Name'
description: 'A short description for SEO and blog previews'
header: https://example.com/header-image.jpg
llm: 'Anthropic/Claude Opus 4'
---
Frontmatter fields:
title (required): The blog post title
date (required): Publication date in YYYY-MM-DD format
category (required): Category in quotes (e.g., "Guides", "Journal", "Tech")
description (required): Brief description for SEO and blog previews
header (recommended): External URL to header image for the blog card
llm (required): The specific LLM used to generate this blog post (e.g., "Anthropic/Claude Opus 4", "OpenAI/GPT-4o", "Google/Gemini 2.0")
Content Structure
Write your content below the frontmatter using Markdown syntax. Use images to enhance readability.
- Header Image: External image link immediately after front matter
- Opening: Start with a hook or introduction
- Main Sections: Use
## for main sections, ### for subsections
- Steps: Use numbered lists (
1., 2.) for sequential instructions
- Notes: Use bullet points for additional info, tips, or clarifications
- Code Blocks: Use triple backticks with language for syntax highlighting
- Closing: End with encouragement, next steps, or a call to action
Images
Header Image: Every blog must have a header image at the top that is directly related to the topic. Use an external image link from the actual source.
Source Images from Relevant Sites: Find images from the websites directly related to your topic:
- If writing about an OpenAI model → find images from OpenAI's announcement blog or post
- If writing about Anthropic's work → find images from Anthropic's news/blog
- If writing about a research paper → find images from the paper or author blogs
- If writing about a product → find images from the official product page or documentation
- If writing about a competition or event → find images from the official site
In-Content Images: Include images throughout the blog when they add value—visual explanations, screenshots, diagrams, examples, or relevant media. Source these from the same relevant sites.
How to Find Images:
- First, search for the official announcement, blog post, or documentation about the topic
- Browse those pages for hero images, diagrams, screenshots, or infographics
- Use the image URLs directly from those sources
- If images are embedded in the page, extract the direct image URL
Image Links: Always use external image URLs rather than downloading images to static/blog-images. Link to images from their original sources.
No Image Reuse: Do not use the same image more than once in a single blog post. Each image should be unique and serve a distinct purpose. If you need to reference a concept again, find a different visual representation or explain it in text.
Image Syntax: Use Markdown image syntax with descriptive alt text:

Visual Examples
Blog Card Preview
┌─────────────────────────────────────────────────────┐
│ [Header Image: 1200x630px] │
│ │
│ Title: Getting Started │
│ Date: 2025-11-06 | Category: Guides │
│ │
│ Description: Quick start guide to configure... │
└─────────────────────────────────────────────────────┘
Supported Markdown Syntax
Headings
# Heading 1
## Heading 2
### Heading 3
Text Formatting
**Bold text**
_Italic text_
~~Strikethrough~~
`inline code`
Images


Links
[Link Text](https://example.com)
Lists
- Unordered item 1
- Unordered item 2
1. Ordered item 1
2. Ordered item 2
Code Blocks
console.log('Hello World');
// Syntax highlighting is automatic
Blockquotes
> This is a blockquote
> Multiple lines work too
Tables
| Header 1 | Header 2 |
| -------- | -------- |
| Cell 1 | Cell 2 |
Math (KaTeX)
This blog supports LaTeX math rendering:
Inline: $E = mc^2$
Block:
$$
\sum_{i=1}^n i^2 = \frac{n(n+1)(2n+1)}{6}
$$
Example Blog Post with Header Image
---
title: My First Blog Post
date: 2025-01-15
category: "Guides"
description: "A comprehensive guide on how to write and publish blog posts in this project"
header: https://example.com/header-image.jpg
llm: "Anthropic/Claude Opus 4"
---

## Introduction
Welcome to my new blog! This is an example of how to write visually-rich posts with header images and inline screenshots.
## Getting Started
Here's how you get started with step-by-step visuals:

1. Fork the repository
2. Clone it locally
3. Run `pnpm dev`

## Code Example
```typescript
function greet(name: string): string {
return `Hello, ${name}!`;
}
```
## Architecture

## Conclusion
That's it! Happy writing with images.
Step-by-Step Process
- Determine the blog name: Use kebab-case (e.g.,
my-first-post)
- Create the markdown file:
static/blogs/<BlogName>.md
- Add frontmatter: Include title, date, category, description, header URL, and llm field
- Find header image: Locate an external image URL from official sources related to your topic
- Write content: Use Markdown syntax with images to enhance readability
- Add supporting images: Use external image URLs from relevant official sources
- Save and verify: The blog will automatically appear in the feed with the header image
Research Before Writing
Before writing any blog post, conduct thorough research from multiple authoritative sources:
1. Plan Structure and Sections
Before starting to write, research what sections and subtopics should be included:
- Search for how other blogs and articles structure content on similar topics
- Look at table of contents from books, documentation, and comprehensive guides on the subject
- Identify the key concepts, components, and areas that need coverage
- Consider what a reader would need to know to fully understand the topic
- Group related concepts into logical sections
- Plan the flow from foundational concepts to advanced topics
- Create an outline with main sections and subsections before writing
2. Source Research
Once you have your structure, research each section:
Simon Willison's Blog: Always check simonwillison.net for his latest posts, experiments, and insights on AI, LLMs, and related technologies. He frequently shares unique perspectives and timely analysis.
Reddit: Search relevant subreddits (r/MachineLearning, r/LocalLLaMA, r/ClaudeAI, r/ChatGPT, r/programming, etc.) for real-world discussions, problems people are solving, community insights, and emerging trends.
Current News: Search for recent news articles, announcements, and developments from reputable tech news sources (The Verge, TechCrunch, Ars Technica, etc.). Stay current with the latest releases and industry changes.
Company Blogs: Read official blog posts and documentation from companies directly involved with your topic:
- Anthropic (anthropic.com/news)
- OpenAI (openai.com/blog)
- Google DeepMind (deepmind.google/blog)
- Meta AI (meta.ai/blog)
- Hugging Face (huggingface.co/blog)
- And any other relevant companies
Research Papers: Check arXiv for the latest papers on your topic. Link to relevant papers in your "Further Reading" section.
Content Quality
Be Exceptionally Detailed: Dive deep into every aspect of your topic. Don't just scratch the surface—explore the nuances, edge cases, and underlying principles. Readers should finish your blog knowing significantly more than when they started.
Provide Exceptional Insights: Offer unique perspectives that readers won't find elsewhere. Connect dots between different sources, synthesize information, and provide analysis that adds genuine value. Share your own experiments, findings, and conclusions.
Use Your Research: Weave insights from Simon Willison, Reddit discussions, company announcements, and news into your narrative. Credit sources and provide links so readers can explore further.
Include Specific Examples: Whenever possible, link to specific projects, products, papers, or implementations. Include screenshots, code snippets, or concrete demonstrations.
Stay Current: Reference the latest developments and explain how they change or inform the topic. Date your references so readers know how recent your information is.
Go Beyond Surface Level: If explaining a technology, explain how it works under the hood. If discussing a trend, explain why it's happening and where it's headed. If covering a tool, show advanced use cases and workflows.
Keep Blogs Up to Date
Research Latest News: Before writing, search for recent news articles, announcements, and developments on your topic. Check multiple sources to understand the current state of things.
Integrate Latest Tweets: Search for relevant tweets from key figures, companies, and researchers. Tweets often contain timely insights, announcements, or debates that are valuable to include. When integrating tweets:
- Quote the tweet and explain why it's significant
- Add context—don't just drop a link
- Tie it to your broader narrative
- Credit the author and link to their profile
Use Current Information: Incorporate the latest releases, updates, and changes. If something has changed recently, mention it and explain how it affects the topic.
Date Your References: When referencing news, tweets, or papers, include the date so readers know how recent the information is.
Acknowledge Changes: If a topic has evolved or if new developments have emerged since something was written, acknowledge this and update accordingly.
Refresh Old Content: If you're updating an old blog post, note what has changed and add new information at the top or in an "Updates" section.
Example of Integrating Latest News/Tweets
Instead of just linking to a news article, write:
Anthropic released a new update to Claude on [date]. In their announcement tweet, they mentioned [key point]. This is significant because [your analysis of why it matters].
Or:
I was browsing through the Anthropic blog last week and noticed [something new]. Here's what they said about it:
[Quote from announcement]
I've been testing this feature and here's what I found...
Language Patterns
- Use em dashes freely (—) for asides and emphasis
- Use ellipsis (...) to create suspense or indicate continuation
- Wrap asides and clarifications in parentheses
- Bold key terms and concepts for emphasis
- Occasionally use exclamation points for genuine enthusiasm
- Include personal opinions, recommendations, and preferences
- Use rhetorical questions to engage the reader
Content Approach
- Start with a header image that sets the visual tone for the topic
- Use images throughout to illustrate concepts, show examples, or break up text
- Provide context before diving into details
- Include specific examples, links, and references
- Share personal experiences and projects
- Create showcase sections highlighting work (your own or others)
- Tell readers what to look for, click on, or explore next
- Be generous with credit and links to collaborators
- Balance technical depth with accessibility
Formatting Conventions
- Use code formatting for technical terms, model names, and commands:
base-models, Claude Opus 4.5
- Italicize book titles, movie names, and special terms: Chain-of-Thought Prompting
- Embed links naturally in relevant nouns rather than using "click here"
- Use blockquotes for direct quotes from sources or yourself
- Reference dates and timelines to ground the reader in context
Examples
Opening: "In this blog I am going to take you on a journey through..." or "Let me tell you about..."
Transitions: "Now before we move on...", "With that out of the way...", "Before proceeding..."
Engagement: "I need you to skip to the [section] and checkout...", "No, seriously, you have to go check them out!"
Enthusiasm: "This is where vibe-coding shines...", "It was very impressive...", "This is wonderful isn't it?"
Closing: End with encouragement, next steps, or a call to action. Sign off personally.
Verification
After creating a blog post:
- The header image appears on the blog listing card
- Posts are sorted by date (newest first)
- The description appears in blog previews
- All external images load correctly
- Social media previews show the header image
1---2name: write-blog3description: Write and publish blog posts in the SvelteKit markdown blog with header images, proper frontmatter, and organized media files.4---56## What I do78I guide you through creating and publishing visually-rich blog posts in this SvelteKit markdown blog. I ensure proper file structure, header images, frontmatter format, image handling, and markdown syntax.9101112## When to use me1314Use this skill whenever you need to:1516- Create a new blog post with header image17- Add a blog to the static/blogs/ directory18- Publish content with proper metadata and visuals19- Organize blog images in the correct folder structure20- Enhance posts with images, diagrams, and visual content2122## Personal Blogger Tone2324Write as a genuine human being sharing your thoughts, discoveries, and experiences—not as a company, marketer, or thought leader. Simon Willison's blog is the ideal model: personal, curious, humble, and practical.2526### Key Characteristics2728- **Be yourself**: Write in your natural voice. Use "I" freely and share personal experiences. Don't adopt a corporate or "influencer" tone.29- **No hype or sales pitch**: Avoid promotional language like "game-changing," "revolutionary," "must-have," or "transformative." Simply explain what something is and why you found it interesting or useful.30- **Embrace learning**: Share what you just learned, what surprised you, what confused you. Celebrating even basic discoveries is empowering for you and your readers.31- **Stay humble**: You don't have all the answers. Acknowledge uncertainty, share incomplete thoughts, and be open about what you don't know.32- **Document your process**: Explain how you do things, what tools you use, what didn't work. This is genuinely useful content.33- **No pressure to be unique**: You don't need to say something no one has ever said. Write about what you learned, what you built, what you found interesting.34- **Credit others**: Always link to and name the creators, authors, and projects you reference. It's generous and useful.3536### What to Avoid3738- Clickbait titles or sensational claims39- "Influencer" language ("Let me tell you why this is HUGE...")40- Selling anything (products, courses, newsletters)41- Pretending to be an expert on everything42- Writing to impress rather than to share4344### What to Embrace4546- "Here's what I just figured out..."47- "I tried X and here's what happened..."48- "This confused me at first, but..."49- "I'm not sure about this, but..."50- "I learned this from [person/project]..."51- "Here's how I do X..."5253## Mandatory Web Search Before Writing5455**ALWAYS perform a web search BEFORE writing any blog content.**5657This is a mandatory requirement for every blog post. Before writing:58591. Search for current information on your topic using relevant search terms602. Check for recent news, announcements, or developments613. Find official sources (company blogs, documentation, research papers)624. Verify information is up-to-date and accurate635. Gather links to cite and reference in your content6465This ensures your blog posts are current, accurate, and provide value with fresh perspectives.6667## Blog Post Format6869### File Location7071```72static/73├── blogs/ # Blog markdown files74│ ├── getting-started.md75│ └── my-first-blog.md76```7778- Blog markdown files go in: `static/blogs/`79- Use kebab-case for filenames: `my-first-blog.md`8081### Frontmatter (Required Metadata)8283Every blog post must start with YAML frontmatter with a header image:8485```yaml86---87title: Your Blog Title Here88date: 2025-01-1589category: 'Category Name'90description: 'A short description for SEO and blog previews'91header: https://example.com/header-image.jpg92llm: 'Anthropic/Claude Opus 4'93---94```9596**Frontmatter fields:**9798- `title` (required): The blog post title99- `date` (required): Publication date in YYYY-MM-DD format100- `category` (required): Category in quotes (e.g., "Guides", "Journal", "Tech")101- `description` (required): Brief description for SEO and blog previews102- `header` (recommended): External URL to header image for the blog card103- `llm` (required): The specific LLM used to generate this blog post (e.g., "Anthropic/Claude Opus 4", "OpenAI/GPT-4o", "Google/Gemini 2.0")104105### Content Structure106107Write your content below the frontmatter using Markdown syntax. Use images to enhance readability.1081091. **Header Image**: External image link immediately after front matter1102. **Opening**: Start with a hook or introduction1113. **Main Sections**: Use `##` for main sections, `###` for subsections1124. **Steps**: Use numbered lists (`1.`, `2.`) for sequential instructions1135. **Notes**: Use bullet points for additional info, tips, or clarifications1146. **Code Blocks**: Use triple backticks with language for syntax highlighting1157. **Closing**: End with encouragement, next steps, or a call to action116117## Images118119- **Header Image**: Every blog must have a header image at the top that is directly related to the topic. Use an external image link from the actual source.120121- **Source Images from Relevant Sites**: Find images from the websites directly related to your topic:122 - If writing about an OpenAI model → find images from OpenAI's announcement blog or post123 - If writing about Anthropic's work → find images from Anthropic's news/blog124 - If writing about a research paper → find images from the paper or author blogs125 - If writing about a product → find images from the official product page or documentation126 - If writing about a competition or event → find images from the official site127128- **In-Content Images**: Include images throughout the blog when they add value—visual explanations, screenshots, diagrams, examples, or relevant media. Source these from the same relevant sites.129130- **How to Find Images**:131 1. First, search for the official announcement, blog post, or documentation about the topic132 2. Browse those pages for hero images, diagrams, screenshots, or infographics133 3. Use the image URLs directly from those sources134 4. If images are embedded in the page, extract the direct image URL135136- **Image Links**: Always use external image URLs rather than downloading images to `static/blog-images`. Link to images from their original sources.137138- **No Image Reuse**: Do not use the same image more than once in a single blog post. Each image should be unique and serve a distinct purpose. If you need to reference a concept again, find a different visual representation or explain it in text.139140- **Image Syntax**: Use Markdown image syntax with descriptive alt text:141142```markdown143144```145146## Visual Examples147148### Blog Card Preview149150```151┌─────────────────────────────────────────────────────┐152│ [Header Image: 1200x630px] │153│ │154│ Title: Getting Started │155│ Date: 2025-11-06 | Category: Guides │156│ │157│ Description: Quick start guide to configure... │158└─────────────────────────────────────────────────────┘159```160161## Supported Markdown Syntax162163### Headings164165```markdown166# Heading 1167168## Heading 2169170### Heading 3171```172173### Text Formatting174175```markdown176**Bold text**177_Italic text_178~~Strikethrough~~179`inline code`180```181182### Images183184```markdown185186187```188189### Links190191```markdown192[Link Text](https://example.com)193```194195### Lists196197```markdown198- Unordered item 1199- Unordered item 22002011. Ordered item 12022. Ordered item 2203```204205### Code Blocks206207```javascript208console.log('Hello World');209// Syntax highlighting is automatic210```211212### Blockquotes213214```markdown215> This is a blockquote216> Multiple lines work too217```218219### Tables220221```markdown222| Header 1 | Header 2 |223| -------- | -------- |224| Cell 1 | Cell 2 |225```226227### Math (KaTeX)228229This blog supports LaTeX math rendering:230231```markdown232Inline: $E = mc^2$233234Block:235236$$237\sum_{i=1}^n i^2 = \frac{n(n+1)(2n+1)}{6}238$$239```240241## Example Blog Post with Header Image242243````yaml244---245title: My First Blog Post246date: 2025-01-15247category: "Guides"248description: "A comprehensive guide on how to write and publish blog posts in this project"249header: https://example.com/header-image.jpg250llm: "Anthropic/Claude Opus 4"251---252253254255## Introduction256257Welcome to my new blog! This is an example of how to write visually-rich posts with header images and inline screenshots.258259## Getting Started260261Here's how you get started with step-by-step visuals:2622632642651. Fork the repository2662. Clone it locally2673. Run `pnpm dev`268269270271## Code Example272273```typescript274function greet(name: string): string {275 return `Hello, ${name}!`;276}277```278279## Architecture280281282283## Conclusion284285That's it! Happy writing with images.286287````288289## Step-by-Step Process2902911. **Determine the blog name**: Use kebab-case (e.g., `my-first-post`)2922. **Create the markdown file**: `static/blogs/<BlogName>.md`2933. **Add frontmatter**: Include title, date, category, description, header URL, and llm field2944. **Find header image**: Locate an external image URL from official sources related to your topic2955. **Write content**: Use Markdown syntax with images to enhance readability2966. **Add supporting images**: Use external image URLs from relevant official sources2977. **Save and verify**: The blog will automatically appear in the feed with the header image298299## Research Before Writing300301Before writing any blog post, conduct thorough research from multiple authoritative sources:302303### 1. Plan Structure and Sections304305Before starting to write, research what sections and subtopics should be included:306307- Search for how other blogs and articles structure content on similar topics308- Look at table of contents from books, documentation, and comprehensive guides on the subject309- Identify the key concepts, components, and areas that need coverage310- Consider what a reader would need to know to fully understand the topic311- Group related concepts into logical sections312- Plan the flow from foundational concepts to advanced topics313- Create an outline with main sections and subsections before writing314315### 2. Source Research316317Once you have your structure, research each section:3183191. **Simon Willison's Blog**: Always check simonwillison.net for his latest posts, experiments, and insights on AI, LLMs, and related technologies. He frequently shares unique perspectives and timely analysis.3203212. **Reddit**: Search relevant subreddits (r/MachineLearning, r/LocalLLaMA, r/ClaudeAI, r/ChatGPT, r/programming, etc.) for real-world discussions, problems people are solving, community insights, and emerging trends.3223233. **Current News**: Search for recent news articles, announcements, and developments from reputable tech news sources (The Verge, TechCrunch, Ars Technica, etc.). Stay current with the latest releases and industry changes.3243254. **Company Blogs**: Read official blog posts and documentation from companies directly involved with your topic:326 - Anthropic (anthropic.com/news)327 - OpenAI (openai.com/blog)328 - Google DeepMind (deepmind.google/blog)329 - Meta AI (meta.ai/blog)330 - Hugging Face (huggingface.co/blog)331 - And any other relevant companies3323335. **Research Papers**: Check arXiv for the latest papers on your topic. Link to relevant papers in your "Further Reading" section.334335## Content Quality336337- **Be Exceptionally Detailed**: Dive deep into every aspect of your topic. Don't just scratch the surface—explore the nuances, edge cases, and underlying principles. Readers should finish your blog knowing significantly more than when they started.338339- **Provide Exceptional Insights**: Offer unique perspectives that readers won't find elsewhere. Connect dots between different sources, synthesize information, and provide analysis that adds genuine value. Share your own experiments, findings, and conclusions.340341- **Use Your Research**: Weave insights from Simon Willison, Reddit discussions, company announcements, and news into your narrative. Credit sources and provide links so readers can explore further.342343- **Include Specific Examples**: Whenever possible, link to specific projects, products, papers, or implementations. Include screenshots, code snippets, or concrete demonstrations.344345- **Stay Current**: Reference the latest developments and explain how they change or inform the topic. Date your references so readers know how recent your information is.346347- **Go Beyond Surface Level**: If explaining a technology, explain how it works under the hood. If discussing a trend, explain why it's happening and where it's headed. If covering a tool, show advanced use cases and workflows.348349### Keep Blogs Up to Date350351- **Research Latest News**: Before writing, search for recent news articles, announcements, and developments on your topic. Check multiple sources to understand the current state of things.352353- **Integrate Latest Tweets**: Search for relevant tweets from key figures, companies, and researchers. Tweets often contain timely insights, announcements, or debates that are valuable to include. When integrating tweets:354 - Quote the tweet and explain why it's significant355 - Add context—don't just drop a link356 - Tie it to your broader narrative357 - Credit the author and link to their profile358359- **Use Current Information**: Incorporate the latest releases, updates, and changes. If something has changed recently, mention it and explain how it affects the topic.360361- **Date Your References**: When referencing news, tweets, or papers, include the date so readers know how recent the information is.362363- **Acknowledge Changes**: If a topic has evolved or if new developments have emerged since something was written, acknowledge this and update accordingly.364365- **Refresh Old Content**: If you're updating an old blog post, note what has changed and add new information at the top or in an "Updates" section.366367### Example of Integrating Latest News/Tweets368369Instead of just linking to a news article, write:370371> Anthropic released a new update to Claude on [date]. In their announcement tweet, they mentioned [key point]. This is significant because [your analysis of why it matters].372373Or:374375> I was browsing through the Anthropic blog last week and noticed [something new]. Here's what they said about it:376>377> [Quote from announcement]378>379> I've been testing this feature and here's what I found...380381## Language Patterns382383- Use em dashes freely (—) for asides and emphasis384- Use ellipsis (...) to create suspense or indicate continuation385- Wrap asides and clarifications in parentheses386- Bold key terms and concepts for emphasis387- Occasionally use exclamation points for genuine enthusiasm388- Include personal opinions, recommendations, and preferences389- Use rhetorical questions to engage the reader390391## Content Approach392393- Start with a header image that sets the visual tone for the topic394- Use images throughout to illustrate concepts, show examples, or break up text395- Provide context before diving into details396- Include specific examples, links, and references397- Share personal experiences and projects398- Create showcase sections highlighting work (your own or others)399- Tell readers what to look for, click on, or explore next400- Be generous with credit and links to collaborators401- Balance technical depth with accessibility402403## Formatting Conventions404405- Use code formatting for technical terms, model names, and commands: `base-models`, `Claude Opus 4.5`406- Italicize book titles, movie names, and special terms: _Chain-of-Thought Prompting_407- Embed links naturally in relevant nouns rather than using "click here"408- Use blockquotes for direct quotes from sources or yourself409- Reference dates and timelines to ground the reader in context410411## Examples412413**Opening**: "In this blog I am going to take you on a journey through..." or "Let me tell you about..."414415**Transitions**: "Now before we move on...", "With that out of the way...", "Before proceeding..."416417**Engagement**: "I need you to skip to the [section] and checkout...", "No, seriously, you have to go check them out!"418419**Enthusiasm**: "This is where vibe-coding shines...", "It was very impressive...", "This is wonderful isn't it?"420421**Closing**: End with encouragement, next steps, or a call to action. Sign off personally.422423## Verification424425After creating a blog post:426427- The header image appears on the blog listing card428- Posts are sorted by date (newest first)429- The description appears in blog previews430- All external images load correctly431- Social media previews show the header image