vault backup: 2026-01-27 15:17:32
This commit is contained in:
31
_NoteCompanion/Templates/enhance.md
Normal file
31
_NoteCompanion/Templates/enhance.md
Normal file
@@ -0,0 +1,31 @@
|
||||
1. **Use Headings and Subheadings**: Clearly define sections with headings (e.g.,
|
||||
```
|
||||
#
|
||||
```
|
||||
,
|
||||
```
|
||||
##
|
||||
```
|
||||
,
|
||||
```
|
||||
###
|
||||
```
|
||||
) to organize content hierarchically.
|
||||
|
||||
2. **Bullet Points and Lists**: Use bullet points or numbered lists to break down information into digestible parts.
|
||||
|
||||
3. **Consistent Spacing**: Ensure consistent spacing between sections and paragraphs for better readability.
|
||||
|
||||
4. **Highlight Key Points**: Use bold or italics to emphasize important information or key terms.
|
||||
|
||||
5. **Tables for Structured Data**: Use tables to organize data that fits into rows and columns for clarity.
|
||||
|
||||
6. **Quotes and References**: Use blockquotes for quotes and reference links for sources.
|
||||
|
||||
7. **Code Blocks**: Use code blocks for any code snippets or technical instructions.
|
||||
|
||||
8. **Images and Diagrams**: Include images or diagrams where applicable to visually represent information.
|
||||
|
||||
9. **Linking and Cross-referencing**: Use internal links to connect related notes or sections within your vault.
|
||||
|
||||
10. do not use ``` markdown
|
||||
124
_NoteCompanion/Templates/flash_cards.md
Normal file
124
_NoteCompanion/Templates/flash_cards.md
Normal file
@@ -0,0 +1,124 @@
|
||||
Please create an Obsidian note with interactive flashcards using native Obsidian HTML features. The note must include:
|
||||
|
||||
1. Frontmatter (at the top) with the following properties:
|
||||
|
||||
---
|
||||
|
||||
total: {{number of flashcards created}}
|
||||
|
||||
topics: ["{{topic 1}}", "{{topic 2}}", "{{topic 3}}"]
|
||||
|
||||
created: "{{current date in YYYY-MM-DD format}}"
|
||||
|
||||
---
|
||||
|
||||
2. Interactive flashcards using HTML details/summary tags (below the frontmatter).
|
||||
|
||||
**Instructions:**
|
||||
|
||||
- Extract key concepts, facts, definitions, relationships, and important information from the content
|
||||
- Identify all testable knowledge points: definitions, concepts, facts, formulas, relationships, processes, dates, names, theories, principles, etc.
|
||||
- Extract 3-7 main topics or themes from the content for the topics array in frontmatter
|
||||
- **CRITICAL: Randomize the order of flashcards - mix different topics, difficulty levels, and question types together. Do NOT follow the original content order or group by topic. Create a varied, shuffled study experience.**
|
||||
- Create 10-30 flashcards depending on content length and density
|
||||
- Prioritize information that is:
|
||||
- Fundamental to understanding the topic
|
||||
- Frequently referenced or important
|
||||
- Easy to forget (dates, numbers, specific details)
|
||||
- Part of a sequence or process
|
||||
- A definition or key concept
|
||||
|
||||
- Maintain the exact markdown syntax for the frontmatter block (`---` at the top and bottom).
|
||||
- Each property in frontmatter must be on its own line with proper YAML indentation
|
||||
- Topics should be an array: topics: ["Topic 1", "Topic 2", "Topic 3"]
|
||||
- Total should be a number without quotes
|
||||
- Created should be a string in quotes with format "YYYY-MM-DD"
|
||||
|
||||
- Format each flashcard using HTML details/summary tags:
|
||||
- Each flashcard must be a separate <details> block with class="flashcard"
|
||||
- The <summary> tag must have class="flashcard-question" and contain the question
|
||||
- The answer must be wrapped in <div class="flashcard-answer">
|
||||
- Leave a blank line after </summary> and before </details> for proper spacing
|
||||
- Answers can include markdown formatting (bold, italic, lists, links, etc.)
|
||||
- Answers can span multiple paragraphs
|
||||
|
||||
- Questions should test understanding, not just recall
|
||||
- Answers should be complete but concise (typically 1-4 sentences, but can be longer if needed)
|
||||
- Include context and examples when helpful
|
||||
- Use clear, specific language
|
||||
- Make questions specific and focused (avoid overly broad questions)
|
||||
- Include [[internal links]] to related notes or concepts when relevant
|
||||
- Use **bold** for key terms in answers
|
||||
- Group related information in answers using lists or structured formatting
|
||||
|
||||
- Do not use ``` code blocks or markdown code formatting in the output
|
||||
- Focus on accuracy and completeness based on the actual content provided
|
||||
|
||||
**Example Output Format:**
|
||||
|
||||
---
|
||||
|
||||
total: 3
|
||||
|
||||
topics: ["Cell Biology", "Energy Production", "Molecular Biology"]
|
||||
|
||||
created: "2025-01-09"
|
||||
|
||||
---
|
||||
|
||||
<details class="flashcard">
|
||||
<summary class="flashcard-question">What is the primary function of mitochondria?</summary>
|
||||
|
||||
<div class="flashcard-answer">
|
||||
|
||||
Mitochondria are organelles that produce ATP (adenosine triphosphate) through cellular respiration. They are often called the "powerhouse of the cell" because they generate most of the cell's energy supply.
|
||||
|
||||
Related: See also [[Chloroplasts]] for plant cell energy production.
|
||||
|
||||
</div>
|
||||
|
||||
</details>
|
||||
|
||||
<details class="flashcard">
|
||||
<summary class="flashcard-question">What is the difference between DNA and RNA?</summary>
|
||||
|
||||
<div class="flashcard-answer">
|
||||
|
||||
- **DNA**: Double-stranded, contains thymine, stores genetic information
|
||||
- **RNA**: Single-stranded, contains uracil, involved in protein synthesis
|
||||
|
||||
</div>
|
||||
|
||||
</details>
|
||||
|
||||
<details class="flashcard">
|
||||
<summary class="flashcard-question">How does photosynthesis work?</summary>
|
||||
|
||||
<div class="flashcard-answer">
|
||||
|
||||
Photosynthesis occurs in two stages:
|
||||
|
||||
1. **Light-dependent reactions**: Chlorophyll absorbs light energy, splits water molecules, and produces ATP and NADPH
|
||||
2. **Calvin cycle**: Uses ATP and NADPH to convert carbon dioxide into glucose
|
||||
|
||||
</div>
|
||||
|
||||
</details>
|
||||
|
||||
Important Notes:
|
||||
- ALWAYS include frontmatter with total, topics, and created date
|
||||
- Each property in frontmatter must be on its own line (no nesting, flat structure like the YouTube template)
|
||||
- Topics should be an array: topics: ["Topic 1", "Topic 2", "Topic 3"]
|
||||
- Created should be a string in quotes: created: "2025-01-09"
|
||||
- Total should be a number without quotes: total: 15
|
||||
- Use proper HTML syntax - ensure all tags are properly closed
|
||||
- Output the actual HTML tags directly (NOT inside markdown code blocks)
|
||||
- Each flashcard should be separated by a blank line for readability
|
||||
- **RANDOMIZE THE ORDER: Mix topics, difficulty levels, and question types - do not follow source material order**
|
||||
- Include [[internal links]] to related concepts when relevant
|
||||
- Answers can include markdown formatting like **bold**, *italic*, lists, and [[internal links]]
|
||||
- If content is very long, focus on the most important concepts
|
||||
- If content is technical, ensure definitions are clear
|
||||
- Maintain the original meaning and accuracy of the source material
|
||||
- All flashcards will be in one note - users can click to reveal answers
|
||||
- This format works natively in Obsidian without requiring any plugins
|
||||
32
_NoteCompanion/Templates/meeting_note.md
Normal file
32
_NoteCompanion/Templates/meeting_note.md
Normal file
@@ -0,0 +1,32 @@
|
||||
Contextual Extraction of Discussion Points and Action Items
|
||||
|
||||
Instruction:
|
||||
Analyze the provided content, which includes:
|
||||
• Transcript 1: The first transcript of the discussion.
|
||||
• Transcript 2: The second transcript of the discussion.
|
||||
• Written Notes: Notes taken by a participant summarizing the discussion.
|
||||
|
||||
Task:
|
||||
Extract the following while prioritizing the notes written by the participant to infer emphasis and key takeaways:
|
||||
1. Discussion Points: Summarize the key topics, ideas, or issues discussed. Prioritize points that appear in the written notes and cross-reference with the transcripts for completeness.
|
||||
2. Action Items: Identify specific tasks, responsibilities, or decisions agreed upon. For each action item, include:
|
||||
• A brief description of the task.
|
||||
• The person(s) responsible, if mentioned.
|
||||
• Any deadlines, if stated.
|
||||
|
||||
Output Format:
|
||||
|
||||
**Discussion Points:**
|
||||
1. [Point 1]
|
||||
2. [Point 2]
|
||||
...
|
||||
|
||||
**Action Items:**
|
||||
1. [Task description] - [Responsible person(s)] - [Deadline]
|
||||
2. [Task description] - [Responsible person(s)] - [Deadline]
|
||||
...
|
||||
|
||||
**Supporting Context:**
|
||||
- Key excerpts from Transcript 1: [Relevant excerpts related to discussion points and action items].
|
||||
- Key excerpts from Transcript 2: [Relevant excerpts related to discussion points and action items].
|
||||
- Key highlights from Written Notes: [Direct quotes or summaries from notes].
|
||||
97
_NoteCompanion/Templates/research_paper.md
Normal file
97
_NoteCompanion/Templates/research_paper.md
Normal file
@@ -0,0 +1,97 @@
|
||||
---
|
||||
|
||||
title: "[Full paper title]"
|
||||
|
||||
authors: ["Author 1", "Author 2", "etc"]
|
||||
|
||||
year: [Publication year]
|
||||
|
||||
journal: "[Journal name]"
|
||||
|
||||
volume: "[Vol. number]"
|
||||
|
||||
issue: "[Issue number]"
|
||||
|
||||
pages: "[Page range]"
|
||||
|
||||
doi: "[DOI number]"
|
||||
|
||||
url: "[Direct URL to access paper]"
|
||||
|
||||
tags: ["academic", "paper", "[field]", "[specific subtopic]"]
|
||||
|
||||
research_question: "[Exact question/objective as stated by authors]"
|
||||
|
||||
significance: "[Why this research matters in 1-2 specific sentences]"
|
||||
|
||||
keywords: ["Keyword 1", "Keyword 2", "etc"]
|
||||
|
||||
citation: "[Complete citation in APA/MLA format]"
|
||||
|
||||
---
|
||||
|
||||
## 1. Key Arguments & Evidence
|
||||
|
||||
- **Argument 1**: [Specific claim made by authors] ([p.X])
|
||||
- Evidence: [Concrete data, statistics, or examples supporting this claim] ([p.X])
|
||||
- Methodology used: [Specific methods used to gather this evidence] ([p.X])
|
||||
- Theoretical basis: [Named theory or framework] ([Author Year, p.X])
|
||||
- **Argument 2**: [Continue with same detailed format]
|
||||
- **Argument 3**: [Add as many as needed with same detailed format]
|
||||
|
||||
## 2. Methodology Details
|
||||
|
||||
- **Research design**: [Exact type - e.g., "longitudinal cohort study" not just "quantitative"] ([p.X])
|
||||
- **Data collection methods**: [Specific techniques used - e.g., "semi-structured interviews using protocol X"] ([p.X])
|
||||
- **Sample characteristics**: [Exact details - e.g., "128 participants: 64 female, 64 male, ages 18-35, from University X"] ([p.X])
|
||||
- **Key variables**: [Named variables with operational definitions] ([p.X])
|
||||
- **Analytical techniques**: [Specific statistical tests or qualitative approaches with software used] ([p.X])
|
||||
- **Ethical considerations**: [Any ethics committee approvals or considerations mentioned] ([p.X])
|
||||
|
||||
## 3. Substantive Findings
|
||||
|
||||
- **Primary finding**: [Most significant result with exact statistics/p-values/effect sizes] ([p.X])
|
||||
- **Secondary findings**: [Additional results with specific data points] ([p.X])
|
||||
- **Unexpected results**: [Any surprising outcomes with authors' explanations] ([p.X])
|
||||
- **Null findings**: [What didn't work or wasn't supported] ([p.X])
|
||||
- **Limitations acknowledged**: [Specific constraints identified by authors] ([p.X])
|
||||
|
||||
## 4. Scholarly Context
|
||||
|
||||
- **Builds on**: [[Author Year]] - [Named works this paper extends] ([p.X])
|
||||
- **Contradicts**: [[Author Year]] - [Specific research this challenges] ([p.X])
|
||||
- **Resolves**: [Specific debates this settles] ([p.X])
|
||||
- **Theoretical framework**: [Named theory/framework the paper operates within] ([p.X])
|
||||
- **Research gap addressed**: [Explicit gap identified by authors] ([p.X])
|
||||
|
||||
## 5. Key Quotes
|
||||
|
||||
- **Central argument**: "[Direct quote]" ([p.X])
|
||||
- **Methodology**: "[Direct quote]" ([p.X])
|
||||
- **Main finding**: "[Direct quote]" ([p.X])
|
||||
- **Implications**: "[Direct quote]" ([p.X])
|
||||
- **Future research**: "[Direct quote]" ([p.X])
|
||||
|
||||
## 6. Explicit Recommendations & Applications
|
||||
|
||||
- **Direct recommendations**: [List all specific recommendations made by authors] ([p.X])
|
||||
- **Policy implications**: [Any policy changes suggested] ([p.X])
|
||||
- **Practice implications**: [How practitioners should change behavior] ([p.X])
|
||||
- **Industry applications**: [Business or commercial applications] ([p.X])
|
||||
- **Educational implications**: [Teaching or learning applications] ([p.X])
|
||||
- **Future research directions**: [Specific suggestions for further study] ([p.X])
|
||||
|
||||
## 7. Critical Reference Mapping
|
||||
|
||||
- [[Author Year]] - [Title] ([p.X in reviewed paper]) - [Precise role in paper's argument]
|
||||
- [[Author Year]] - [Title] ([p.X in reviewed paper]) - [Precise role in paper's argument]
|
||||
- [[Author Year]] - [Title] ([p.X in reviewed paper]) - [Precise role in paper's argument]
|
||||
|
||||
## 8. Personal Research Notes
|
||||
|
||||
- **Relevance to my work**: [Specific ways this connects to your research]
|
||||
- **Methods I could adapt**: [Specific techniques that could be applied]
|
||||
- **Gaps I could address**: [How your work might extend this research]
|
||||
- **Potential citations**: [Where in your own writing you might cite this]
|
||||
- **Related papers in vault**: [[Paper 1]], [[Paper 2]]
|
||||
- **Related concepts**: [[Concept 1]], [[Concept 2]]
|
||||
83
_NoteCompanion/Templates/youtube_video.md
Normal file
83
_NoteCompanion/Templates/youtube_video.md
Normal file
@@ -0,0 +1,83 @@
|
||||
Please create an Obsidian note using the video link and any available transcript or additional context. The note must include:
|
||||
|
||||
1. Frontmatter (at the top) with the following properties:
|
||||
|
||||
---
|
||||
|
||||
title: "{{video title - extract from YouTube Video Information section or transcript}}"
|
||||
|
||||
channel: "{{channel name if available, otherwise leave empty}}"
|
||||
|
||||
date_published: "{{video publication date if available in transcript or metadata, otherwise leave empty}}"
|
||||
|
||||
topics: ["{{relevant topic 1}}", "{{relevant topic 2}}"]
|
||||
|
||||
tags: ["youtube", "{{any other relevant tags based on content}}"]
|
||||
|
||||
summary: "{{short summary of the video's main theme and key takeaways}}"
|
||||
|
||||
---
|
||||
|
||||
2. A YouTube video embed in the following format (Obsidian will automatically embed the video):
|
||||
|
||||
|
||||
|
||||
3. A comprehensive, detailed summary of the key points from the video (below the embed link).
|
||||
|
||||
**Instructions:**
|
||||
|
||||
- Extract the video title from the "YouTube Video Information" section if provided, or infer from the transcript content.
|
||||
|
||||
- Extract topics by analyzing the main themes discussed in the transcript. Use 2-5 specific, relevant topics.
|
||||
|
||||
- Generate tags based on the video content. Always include "youtube" and add 2-4 additional relevant tags. Tags in frontmatter should NOT include the "#" symbol (only use "#" for inline tags in the content body). **CRITICAL: Tags must have NO spaces between words. Use hyphens or underscores to connect multi-word tags (e.g., "web-development" or "machine_learning", not "web development" or "machine learning").**
|
||||
|
||||
- Create a concise summary (1-2 sentences) that captures the video's main theme and key takeaways.
|
||||
|
||||
- If a full transcript is provided in the "Full Transcript" section, use it to create an accurate, detailed summary below the embed link.
|
||||
|
||||
- Extract the publication date if mentioned in the transcript or metadata. If not available, leave date_published empty.
|
||||
|
||||
- Maintain the exact markdown syntax for the frontmatter block (`---` at the top and bottom).
|
||||
|
||||
- Extract the video ID from the YouTube URL in the content, then create the embed using Obsidian's embed syntax:
|
||||
- Format:  (replace VIDEO_ID with the actual video ID)
|
||||
- This will automatically embed the YouTube video player in Obsidian
|
||||
|
||||
- In the main body, provide a comprehensive summary with bullet points covering all major points from the video transcript.
|
||||
|
||||
- **IMPORTANT: Exclude all sponsor mentions, promotional content, and advertisement segments from the summary. Focus only on the main educational or informational content of the video.**
|
||||
|
||||
- Do not use ``` code blocks or markdown code formatting in the summary.
|
||||
|
||||
- Focus on accuracy and completeness based on the actual transcript content provided.
|
||||
|
||||
**Example Output Format:**
|
||||
|
||||
---
|
||||
|
||||
title: "How to Build a React App in 2024"
|
||||
|
||||
channel: "Tech Tutorials"
|
||||
|
||||
date_published: "2024-01-15"
|
||||
|
||||
topics: ["React", "Web Development", "JavaScript", "Tutorial"]
|
||||
|
||||
tags: ["youtube", "react", "webdev", "tutorial"]
|
||||
|
||||
summary: "A comprehensive guide to building modern React applications with hooks, context API, and best practices for 2024."
|
||||
|
||||
---
|
||||
|
||||
|
||||
|
||||
## Detailed Summary
|
||||
|
||||
- Introduction to React fundamentals and modern development practices
|
||||
- Setting up a new React project with Vite
|
||||
- Using React Hooks for state management
|
||||
- Implementing Context API for global state
|
||||
- Best practices for component structure and organization
|
||||
- Performance optimization techniques
|
||||
- Deployment strategies and recommendations
|
||||
Reference in New Issue
Block a user