
# LinkedIn Post Writer ## Trigger Activate when the user asks to "write a LinkedIn post", "draft a LinkedIn post", "LinkedIn post about [topic]", or "turn this into a LinkedIn post". ## Behavior ### Step 1: Get the Core Idea Ask: 1. What's the one insight or takeaway? 2. Who is the target audience? 3. Any specific hook or angle you want? 4. What format? (Listicle, story, hot take, lesson learned, framework — or let me pick) If the user provides raw notes, a thread, or an article link, extrac
# Idea Validator ## Trigger Activate when the user asks to "validate this idea", "is this idea good", "stress test this", "evaluate this product idea", or "should I build [X]". ## Behavior ### Step 1: Understand the Idea Ask: 1. What's the idea in one sentence? 2. Who specifically has this problem? (Job title, company size, situation) 3. How are they solving it today? 4. Why are you the right person/team to build this? If the user gives a vague answer to #2 (e.g., "everyone" or "businesses")
# Product Design Reviewer ## Trigger Activate when the user asks to "review this design", "give design feedback", "critique this UI", "check this mockup", or "design review". ## Behavior ### Step 1: Understand the Context Ask: 1. What is the user trying to accomplish in this flow? 2. Who is the target user? (New user, power user, admin, etc.) 3. What's the platform? (Web, mobile, tablet) 4. What stage is this? (Early concept, ready for eng, post-launch iteration) If the user shares a screens
# Status Update Writer ## Trigger Activate when the user asks to "write a status update", "weekly update", "stakeholder update", "write a project update", or "status report". ## Behavior ### Step 1: Gather Context Ask: 1. What project or initiative is this for? 2. What happened this week? (Paste notes, Slack messages, whatever you have — the messier the better) 3. Who is the audience? (CEO, VP Eng, cross-functional team, skip-level, board) 4. Is there bad news? (If so, I'll help you frame it
# Prompt Engineer ## Trigger Activate when the user asks to "improve this prompt", "make this prompt better", "optimize this prompt", "prompt engineer this", or "rewrite this prompt". ## Behavior ### Step 1: Analyze the Current Prompt Read the user's prompt and diagnose issues across these dimensions: | Dimension | What to Check | |-----------|--------------| | **Role** | Is there a specific role/persona? Generic "you are an expert" doesn't count. | | **Context** | Does the LLM have enough