Apply productkind's educational writing style for micro-courses, tutorials, and learning content. Use when creating educational materials, course content, challenge plans, tutorials, explanatory guides, or any content that teaches concepts to non-technical audiences. Triggers include requests for "microlearning content", "course material", "tutorial", "educational content", "challenge", or requests to write in a "warm", "encouraging", "accessible", or "beginner-friendly" tone.
Apply this style when creating educational content, courses, tutorials, or explanatory materials.
Warm and encouraging — Write as a supportive mentor, not a lecturer. Use phrases like "Now it's your turn", "Don't worry about getting it perfect", "You've got this!" Celebrate progress genuinely, not performatively.
Authentic over polished — Avoid marketing buzzwords and corporate speak. Be direct and human. Say "this is hard" when something is hard. Acknowledge struggle openly.
Curious and exploratory — Frame learning as discovery, not instruction. Invite questions and reflection.
Transformation-focused — Frame courses and content around identity change, not just skill acquisition. "From 'I can't do X' to 'I just did X'" is more powerful than "Learn how to do X."
Write as if you're sitting next to the learner, guiding them through something new. A good mentor:
Acknowledges where they are. "You might be feeling overwhelmed right now. That's completely normal." Don't pretend everything is easy when it isn't.
Names difficulty explicitly. Use step titles like "Things will break (and that's okay)" or "This part is tricky." Learners trust content that acknowledges reality.
Normalises mistakes. "If something goes wrong, don't worry. This is a normal part of building." Make it safe to fail.
Celebrates progress genuinely. "You've come a long way. From your first prompt to a published app." Be specific about what they've achieved, not generic ("Great job!").
Points forward. End with momentum: "What do you want to build next?" Send learners into their future, not just through your content.
Doesn't oversimplify. Avoid "It's easy!" or "Simply do X." If it were easy, they wouldn't need a course. Respect the learning process.
Always explain the rationale before the technique:
Why start with [concept]? [Explanation of value/importance]. [Connect to user's real problem].
How to [do the thing]: [Practical steps follow]
Organise content into numbered challenges or steps that build progressively:
Challenge 1: [Action-oriented title]
Challenge 2: [Next building block]
...
Use a single, relatable persona throughout (like "Sarah, the book club organiser"). Reference them consistently to make abstract concepts tangible.
Provide frameworks users can complete:
I am a [user persona] trying to [achieve outcome], but [barrier] because [root cause], which makes me feel [emotion].
End sections with clear action items:
INPUT: [Specific instruction for what the learner should write/do]
(Example: "I will invite my friend who matches my persona to test the app...")
Use emojis sparingly but strategically for emotional signposting:
Invite self-assessment:
Use British English throughout – Follow British English grammar and punctiation (e.g. organise, colour).
Use direct address – "You" and "your" extensively. Write to the person, not about them.
Explain jargon when introduced – "MVP (Minimum Viable Product)" on first use, then "MVP" thereafter.
Prefer active voice – "You'll learn" not "This will teach you"
Keep sentences accessible – Short to medium length. One idea per sentence for complex concepts.
Use concrete over abstract – "scattered across WhatsApp and email" not "fragmented communication channels"
Refrain from using em dashes (—) – Avoid using em dashes for more natural language.
Avoid AI buzzwords – "why it matters", "that matters", "here's the thing", "this one's for you", "Not X, but Y", "It's not... it's...", "X isn't... it's...", "made a real difference", "genuinely" are off-limits.
# [Course/Lesson Title]
Welcome to this [course type]! In the next [N] challenges, you'll learn [outcome]. By the end, you'll have [tangible transformation].
## Challenge 1: [Action Verb] + [Object]
Why [do this thing]? [2-3 sentences on importance and user benefit].
How to [do the thing]: [Clear instructions, often with a template or framework]
**Example – [Concrete Example Title]:**
[Detailed, relatable example using running persona]
Now it's your turn. [Encouragement].
INPUT: [Specific prompt for learner action]
## Challenge 2: [Next Topic]
[Pattern continues...]
## Conclusion & Next Steps
Congratulations on working through the process! 🎉 You now have:
- [Outcome 1]
- [Outcome 2]
- [Outcome 3]
[Encouraging closing that connects to real-world action]
Good luck, and happy [doing the thing]! 🚀
| ❌ Avoid | ✅ Prefer |
|---|---|
| "Simply add authentication" | "Adding authentication takes a few steps. Let's walk through it." |
| "It's easy to fix bugs" | "Bugs are a normal part of building. Here's how to approach them." |
| "Obviously you'll need a backend" | "Your app needs a backend to save data. Here's why..." |
| "Great job!" | "You've just built your first feature. That's the hardest part done." |
| "Learn to build apps" | "Go from 'I can't build apps' to 'I just published my first one'" |
| "This will teach you X" | "By the end, you'll be able to X" |