Useful Prompts

End-of-Session Prompts

Session —> Obsidian

Compile all information from this session into structured Markdown notes for my Obsidian notebook. Please organize the notes with clear headings for different topics. Use bullet points for key details, decisions, and action items. If possible, suggest relevant tags or keywords for each section.

-- OR --

I need to distill our current conversation into comprehensive notes for my Obsidian vault. Please process the entire session and generate a Markdown document with the following structure:

- **Title:** (Suggest a concise title for the note)
- **Date:** (Today's date: May 14, 2025)
- **Summary:** (A brief 2-3 sentence overview of the session's main purpose and outcome)
- **Key Topics & Discussion Points:** (Use H2 or H3 headings for each main topic. Under each, use bullet points to detail important information, questions asked, answers given, and insights shared.)
- **Decisions Made:** (List any decisions reached during the session.)
- **Action Items:** (List any tasks or follow-ups, ideally noting who is responsible if discussed.)
- **Key Takeaways/Conclusions:** (Summarize the most important learnings or conclusions from the session.)
- **Potential Tags:** (Suggest 3-5 relevant tags, e.g., `#projectX #meeting #AI #research`)
- **Potential Links:** (If any topics strongly relate to other concepts that might be separate notes in Obsidian, suggest them in `[[double bracket link]]` format.)

Ensure the output is clean Markdown, ready to be copied and pasted directly into Obsidian

Session —> Blog Post Chunk/Summary

As we wrap up this session about [Specific topic, e.g., 'debugging the API integration'] for [Overall Project Name, e.g., 'Project Phoenix']: Please help me identify potential material _from this specific conversation_ that could be useful for future blog posts. Specifically, list:

1. **Main Theme/Contribution of THIS Session:** What was the core blog-relevant topic we covered?
2. **Key Insights or 'Aha!' Moments:** Any new understandings or interesting points that arose _in this discussion_?
3. **Significant Decisions/Progress/Problems Solved:** What concrete outcomes or resolutions came from _this session_?
4. **Noteworthy Quotes or Phrasing:** Any memorable statements made _during this session_? (Verbatim if possible).
5. **Emerging Narrative Elements:** Any brief stories, challenges highlighted, or learning experiences _from this session_ that might engage a blog reader?

The goal is to capture the blog-worthy essence of _this particular discussion_.

-- OR --

> This session focused on [firmware patches to remove the need for authentication from webmgnt] for [the RVlink reverse engineering project]. Before we conclude, please provide a 'Blog Contribution Snapshot' based _solely on our interaction in this session_. I need:
> 
> - **Session Headline for Blog Notes:** A very brief title summarizing this session's main blog-relevant point (e.g., "Q3 Marketing: Focus on Community Stories").
> - **Key Discussion Points with Blog Potential:** Bullet points of specific ideas, data, arguments, or examples from _this session_ that could be expanded into blog content.
> - **Problem/Solution Arc (if any):** Did we discuss a particular problem and brainstorm or arrive at solutions _in this session_ that would make an interesting point for a blog?
> - **Key Takeaways for an External Audience:** What are 1-2 key messages _from this session_ that someone outside the project (e.g., [Target Audience, if known, like 'potential customers' or 'industry peers']) might find valuable or interesting?
> - **Any Striking Analogies or Examples Used:** Were there any particularly clear or creative explanations or comparisons made _in this session_?
> 
> This will help me collect building blocks for blog posts over time."

_Why it's most comprehensive for an individual session:_

- Asks for a "headline" to easily categorize this session's contribution.
- Focuses on the "problem/solution arc," a classic storytelling device.
- Prompts thinking about an "external audience" early on.
- Captures specific communication techniques like analogies.

Editing Down a Blog Post

Please process the following consolidated text from our sessions about [Project Name/Topic, e.g., 'our community garden initiative']. My aim is to generate material for blog posts with a [Desired Tone, e.g., 'warm and inspiring'] tone for [Target Audience, e.g., 'local residents and potential volunteers'].

Distill the information into usable chunks by identifying:

1. **Potential Blog Post Titles/Angles (suggest 2-3 for each distinct idea).**
2. **Core Message/Thesis for Each Angle:** What is the main takeaway or story for each potential post?
3. **Supporting Details & Examples:** List bullet points of facts, achievements, processes, or illustrative examples from the text that support each core message.
4. **Human Interest Elements:** Extract any personal stories, challenges faced by the team/project, or moments of discovery/learning.
5. **Key Achievements or Milestones Reached:** Highlight progress points suitable for sharing.
6. **Calls to Action (Implicit or Explicit):** Were there any mentions of next steps, how people can get involved, or further exploration that could be turned into a call to action?

-- OR --

I am submitting a consolidated text from [Number of Sessions] sessions focused on [Project Name/Topic, e.g., 'the Alpha phase of Project Chimera']. My objective is to create an engaging blog post targeting tech enthusiasts with a technical but exciting tone.

Please break down the provided text and generate 2-3 detailed content briefs or structured outlines for a potential blog post. provide:

1. **Catchy Title Suggestions (3-5 options):**
2. **Targeted Keyword Ideas (3-5 for SEO):**
3. **Core Narrative/Angle:** What story are we telling with this post?
4. **Introduction Hook Ideas:** How can we draw the reader in immediately?
5. **Key Sections/Subheadings (with bullet points under each for):**
    - Relevant facts, data, and statistics from the text.
    - Key insights, learnings, or 'aha!' moments.
    - Anecdotes, examples, or case studies (even brief ones).
    - Direct quotes or strong paraphrased statements.
    - Problems encountered and solutions developed.
6. **Potential Visuals:** Suggest points in the narrative where a diagram, screenshot, photo, or chart might be effective (e.g., "Consider a flowchart for the new workflow here").
7. **Conclusion Summary & Potential Call to Action:** What's the final takeaway, and what should the reader do next?

Format the output so each potential blog post brief is clearly separated. We can select one and proceed to create the post from there