Beyond the samples above, these are the prompt structures I reach for. Notice the pattern: real context, hard constraints, a demand for tradeoffs, and an explicit "no fluff" instruction. That instruction discipline is the core of what I teach.
startup strategyAct as a brutally honest startup advisor. Zolarux started as buyer protection and evolved into trust infrastructure for social commerce in Nigeria (₦2M+ processed, now seeking ₦7.4M for a marketplace pilot). Tell me: what is real vs wishful thinking, whether this is truly scalable or just an operational service, the biggest existential risk, and a "pivot or double down" call. No encouragement — only clarity.
positioningHelp me define what Zolarux is NOT, as much as what it is. Compare the marketplace model vs the infrastructure model in plain terms, show where Zolarux fits and where it doesn’t, surface hidden contradictions in my current direction, and give me the cleanest 1–2 sentence positioning statement.
execution systemsDesign a weekly execution system for someone building a startup solo in Nigeria with limited money and a high-distraction environment. I want a realistic (not idealistic) weekly structure, what to prioritise when everything feels urgent, a "minimum viable productive week", and rules to prevent burnout. No motivational talk — only operational structure.
creator systemsBuild a content engine for "The Tech Serial" that can run for 6 months without burnout. Constraints: no heavy editing, consistent weekly output, content that feels like a series. Give me a repeatable episode template, a weekly production pipeline, an idea-generation method, and how to repurpose one idea into multiple posts. Think like a system designer, not a content coach.
technical SOPMy iPhone XS isn’t detected by iTunes even though the PC chimes on connect. Don’t just give steps — structure it like a diagnostic system: break down failure points (hardware, drivers, cable, mode), rank them by likelihood, give a step-by-step elimination process, and tell me exactly when to stop troubleshooting. Think like a technician, not a support article.
decision frameworksBuild me a decision framework that separates reversible vs irreversible decisions, prevents emotional decision-making, gives me a default rule set for common choices, and helps me act faster under uncertainty. Keep it simple enough to use daily.