Claude

Transform these meeting notes into structured action items: **Meeting Notes:** {{paste your meeting notes, transcript, or rough notes here}} Please produce: 1. **Meeting Summary** (3-5 bullet points) - Key decisions made - Important context shared 2. **Action Items Table** | # | Task | Owner | Deadline | Priority | Dependencies | |---|------|-------|----------|----------|-------------| For each action item: - Make it specific and measurable - Assign clear ownership - Suggest realistic deadlines - Flag dependencies between items 3. **Open Questions** - Unresolved items that need follow-up - Who should answer each question 4. **Parking Lot** - Topics raised but not addressed - Suggested meeting/channel for each 5. **Follow-up Email Draft** - Professional summary email ready to send - Include all action items with owners

Create a deeply detailed character for a {{genre}} story. **Character Foundation:** - Full name and any aliases - Age, background, and cultural context - Physical description (distinct features, mannerisms, style) - Voice pattern (speech quirks, vocabulary level, cadence) **Psychology:** - Core motivation (what drives every decision) - Greatest fear (and how they mask it) - Fatal flaw that creates conflict - Moral code (3 rules they live by, 1 they'd break) - How they behave under extreme stress **Relationships:** - Key relationship dynamics (ally, rival, mentor, love interest) - How they treat strangers vs. trusted friends - Communication style in conflict **Story Potential:** - Character arc summary (where they start vs. where they could end) - 3 scenes that would reveal their depth - Secret they keep from everyone - The choice that would break them Make this character feel like a real person with contradictions, not a trope.

You are an expert code reviewer. Analyze the following code for: 1. **Bugs & Logic Errors** - Identify potential runtime errors, off-by-one errors, null pointer issues 2. **Security Vulnerabilities** - Look for injection risks, improper input validation, exposed secrets 3. **Performance Issues** - Spot N+1 queries, unnecessary re-renders, memory leaks 4. **Code Style** - Check naming conventions, function length, DRY violations 5. **Best Practices** - Suggest modern patterns, better abstractions, improved error handling For each finding, provide: - Severity (Critical / Warning / Info) - Line reference - Clear explanation of the issue - Suggested fix with code example Code to review: ``` {{paste your code here}} ```