Expert guidance for creating technical blog content about AI-assisted development with authentic voice, practical examples, and production-ready code. Based on Jeff Blankenburg's 31-day series teaching experienced developers how to use AI coding tools effectively.
A comprehensive skill for maintaining context and voice when working on the "31 Days of Vibe Coding" blog series. This skill helps AI assistants write authentic, technical content that teaches experienced developers how to use AI coding tools to ship faster without sacrificing quality.
This skill provides session-to-session context for creating content in the 31 Days of Vibe Coding series. It ensures consistency in voice, maintains project structure, and keeps technical content production-ready while avoiding common AI writing tells.
When working with this project, always follow these principles:
1. **Observability First** - AI-generated code needs monitoring, logging, and metrics more than hand-written code
2. **Trust but Verify** - AI is a tool, not a replacement for developer judgment
3. **Practical over Perfect** - Real examples beat theoretical concepts
4. **Production-Ready** - Everything must work in production, not just demos
**NEVER use:**
**Pronoun usage:**
Every article must:
1. **Review context files first:**
- Read `/VOICE.md` for complete voice guidelines
- Check the outline in `/outlines/weekN.md` for the specific day
- Review previous articles for consistency
2. **Structure the article:**
- Opening scenario or problem
- Why it matters
- Practical techniques with real code
- Actionable takeaway
- Brief next article setup
3. **Write in Jeff's authentic voice:**
- Be conversational but technical
- Share real experiences and failures
- Avoid AI writing tells (see style rules above)
- Keep it practical over theoretical
4. **Include production-ready examples:**
- Real code, not toy demos
- Show error handling and edge cases
- Connect to observability concepts
- Make it immediately usable
5. **Save the article:**
- Place in `/articles` directory
- Use clear, descriptive filename
1. **Locate the README.md file**
2. **Find the commented-out entry for the day being published**
3. **Uncomment that day's line in the table of contents**
4. **Keep formatting simple and consistent**
**Content organization:**
**Vibe Coding** - Staying in creative flow while using AI as a pair-programming partner. Not about outsourcing thinking, but accelerating iteration.
**The AI is your junior developer** - This framing matters. You (the developer) are still the architect. The AI helps you move faster.
**Observability as a safety net** - When shipping faster with AI, you need confidence through monitoring and metrics.
1. **Don't make it too polished** - Authentic voice beats marketing polish
2. **Don't use dashes to break up sentences** - Major AI tell
3. **Don't use em dashes (—)** - NEVER
4. **Don't use editorial "we"** - Use "I" for Jeff's voice
5. **Don't write hype or marketing copy** - Stay technical and honest
6. **Don't forget observability themes** - Core to the series
7. **Don't make demo-only examples** - Must work in production
8. **Don't write theory without practice** - Always actionable
Before considering any article complete, verify:
"Write Day 5 article following the outline in /outlines/week1.md. Remember to use Jeff's authentic voice, include production-ready code examples, and connect to observability themes. Avoid all AI writing tells."
"Publish Day 5 by uncommenting its entry in README.md. Keep the formatting consistent with published days."
"Review this draft article for AI writing tells, voice consistency, and ensure it meets all requirements from the 31 Days of Vibe Coding guide."
Leave a review
No reviews yet. Be the first to review this skill!
# Download SKILL.md from killerskills.ai/api/skills/31-days-of-vibe-coding-guide/raw