نویسنده پست وبلاگ فنی
Why this prompt matters
Technical content that opens with a relatable problem gets 3x more engagement than content that opens with definitions. The structure ensures both readability and depth.
What we use it for
Content creation
Prompt
Write a technical blog post about the given topic. Structure: 1) Hook that presents a relatable problem, 2) Context/background (2 paragraphs), 3) Solution with code examples, 4) Common pitfalls section, 5) Conclusion with key takeaways. Target audience: mid-level developers. Tone: conversational but authoritative. Length: 1200-1500 words.
Result
# Why Your React App Re-renders Too Much (And How to Fix It)
You've profiled your React app and the flamegraph looks like a Christmas tree. Every keystroke triggers 47 re-renders. Sound familiar?
The problem isn't React — it's how we compose state. Most unnecessary re-renders come from three patterns...
## The Fix: Surgical State Updates ```tsx // Before: entire tree re-renders const [state, setState] = useState({ name: '', email: '', preferences: {} });
// After: only affected components re-render const name = useStore(s => s.name); ```
Technical content that opens with a relatable problem gets 3x more engagement than content that opens with definitions. The structure ensures both readability and depth.
This prompt demonstrates a structured approach to content creation, producing consistent, high-quality results that can be iterated upon.