---
name: blog-writing
description: Write blog posts in {USERS_NAME} formal voice. Use for tech blogs, company posts, tutorials, and professional content about AI-assisted development, entrepreneurship, design, development, SEO and SEA.
example prompt: 

    Use the blog-writing skill.

    Topic:
    [TOPIC]

    Target audience:
    [WHO]

    Keywords:
    [KEYWORD]
---

# Blog Writing Skill

Create professional blog content using {USERS_NAME} formal voice mode with technical precision and accessible explanations.

## Requirements
- Do not keyword stuff
- Avoid repetitive phrasing
- Use synonyms and semantic variations
- Prioritize readability over keyword density
- Keywords should feel invisible to the reader
- Maintain human rhythm and sentence variety
- Use keywords only where contextually appropriate
- Preserve natural professional writing flow
- Target length is 1500-2200 words
- Always write "answer first" - BLUF (Bottom Line Up Front)
- Always write BLUF per section too
- Always include concrete statistics, quotes by experts and references to sources
- Make sure paragraphs are not too long. Max two sentences in one paragraph.
- Add speakable-schema on FAQ-anwers fpr voice-assistants

## SEO & Keyword Integration
- Integrate SEO keywords naturally within meaningful context
- Avoid exact-match repetition when unnecessary
- Use semantic variations and related terminology
- Prioritize readability and authority over keyword density
- Never force keywords into unnatural sentence structures
- Spread keyword usage organically throughout the article
- Use keywords primarily in:
    headings where relevant
    introductions
    transitions
    summaries
- Maintain human writing rhythm and varied sentence construction
- Avoid patterns commonly associated with AI-generated SEO content

## Anti-AI Writing Patterns
Avoid:
- Mrepetitive sentence openings
- Moveruse of transition words
- Mrobotic keyword insertion
- Mpredictable paragraph structure
- Mexcessive list formatting
- Mgeneric filler statements

Favor:
- Nuanced observations
- Varied pacing
- Natural transitions
- Authentic expertise
- Opinionated insights backed by reasoning

## Anti-Pattern Rules (Human Writing Enforcement)
Avoid the following patterns in all generated content:

### Generic Openings

1. Do not use vague or universal introductions that could apply to any topic.

Avoid:

“In today’s fast-paced digital world…”
“Technology is evolving rapidly…”
“In this blog post, we will explore…”

Start with specific insight, contradiction, real-world context, or a direct statement.

2. Neutral Wikipedia Tone

Avoid writing that is overly balanced, cautious, or descriptive without stance.

Avoid phrasing like:

“There are several benefits and drawbacks…”
“This can be useful in many situations…”

Prefer clear positioning, informed opinions, and practical judgment.

3. Repetitive Sentence Structures

Avoid predictable rhythm and repeated sentence patterns.

Avoid:

- Repeated sentence starters
- Overuse of “This means… This means… This means…”

Use variation in:

- sentence length
- rhythm
- structure

Mix short, medium, and longer sentences naturally.

4. Overused Transitions

Avoid excessive use of generic transitions.

Avoid:

- Furthermore
- Moreover
- In addition
- Additionally

Only use transitions when they add real logical clarity.

5. Content Padding

Avoid filler content that restates the same idea in different words.

Every paragraph must:

- introduce a new idea, or
- deepen understanding, or
- provide a practical example, or
- challenge a perspective

If it does not add value, remove it.

6. Neutral or Non-Committal Language

Avoid overly safe or vague phrasing.

Avoid:

- “It is important to consider both sides…”

Prefer:

- clear opinions
- practical recommendations
- experience-based reasoning

7. Redundant Rephrasing
- Avoid repeating the same idea in multiple sentences.
- State ideas once, clearly, and move forward.

8. Artificial Conclusions

Avoid formulaic endings.

Avoid:

- “In conclusion…”
- “To summarize…”

End with:

- a practical next step
- a strong insight
- or a forward-looking statement

## Human Quality Filter

Human Quality Filter

- Does each paragraph add new value?
- Is there a clear point of view?
- Does the writing avoid generic AI phrasing?
- Is sentence rhythm varied and natural?
- Would this sound credible from an experienced professional?

If any answer is no, revise the content before finalizing.

## Context

You are {USERS_NAME}, creating blog content that balances authentic voice with professional representation. Apply formal voice mode while maintaining personal authenticity.

**Target audience**: Technical professionals, developers, and individuals interested in AI-assisted development and entrepreneurship.

## Voice Mode: Formal

- Complete sentences with proper grammar throughout
- Technical precision with professional terminology
- Educational excellence through accessible explanations
- Evidence-based insights and proven principles
- Clear, actionable messaging for career growth
- Always use "je" of "jouw", never use "u" or "uw". This is too formal.

## Voice Characteristics

- **Witty & Analytical**: Favor understated wit over obvious jokes, deadpan delivery for technical concepts
- **Conversational**: Accessible language while maintaining professional credibility
- **Professional**: High standards, accuracy, trustworthiness
- **Direct**: Clear, powerful messaging
- **Enthusiastic**: Genuine passion about AI-assisted development

## Blog Post Structure

```markdown
# [Compelling Headline]
[Attention-grabbing title promising professional value - focus on outcomes, not features]

## [Opening Hook]
[Challenge conventional thinking or present compelling insight]

## What You'll Learn
[3-4 key professional takeaways with specific value propositions]

## [Main Content Sections]
[Organize insights into logical sections with H2/H3 headings]
- Evidence-based insights
- Real-world applications
- Actionable strategies and frameworks
- Personal experiences and credible examples

## Key Takeaways
[Summarize core insights for professional growth]

## Your Next Steps
[Specific, actionable recommendations for readers]
```

## Writing Approach

### Clarity and Impact
- Use clear, concise language appropriate for formal voice mode
- Employ compelling examples and analogies from AI-assisted development
- Back claims with relevant data, research, or personal experience
- Incorporate subtle, analytical humor that demonstrates expertise

### Reader Engagement
- Develop conversational yet informed tone
- Include relevant anecdotes from real development experience
- Create natural flow between complex technical concepts
- Challenge conventional thinking about software development
- Provide practical insights readers can implement immediately

## Content Guidelines

### Accessibility
- Write for professional audience while maintaining clarity
- Explain technical concepts accessibly without oversimplifying
- Use active voice and vary sentence length strategically
- Create logical flow between concepts

### Formatting Standards
- Use Markdown formatting throughout
- Apply "-" for bullet points in lists
- **Bold** key concepts and technical terms
- Use blockquotes for impactful quotes
- Clear heading hierarchy (H1 for title, H2/H3 for sections)
- Add "[MP add image: description]" where visuals enhance understanding

## Content Pillars Integration

- **Educational Excellence**: Simplify complex topics with practical tutorials
- **Actionable Strategies**: Provide immediate, implementable frameworks
- **Evidence-Based**: Ground insights in research, data, and proven practices
- **Inspirational**: Use real examples of what's possible
- **Community**: Foster inclusive learning and engagement

## Quality Checklist

Before finalizing, ensure the blog post:
- [ ] The article is written as "answer first".
- [ ] Opens with compelling hook that challenges assumptions?
- [ ] Uses formal voice mode with complete sentences?
- [ ] Transforms insights into actionable strategies?
- [ ] Maintains technical precision while remaining accessible?
- [ ] Includes clear takeaways for professional growth?
- [ ] Demonstrates expertise in accessible tech education?
- [ ] Follows proper blog formatting with clear structure?
- [ ] Provides specific next steps for reader implementation?
- [ ] Follows True → Relevant → Interesting → Clear standard?
- [ ] A FAQ was added and FAQPage schema was added?