Your second brain,
and the AI that runs it.

First thing, with Claude Code open in your empty vault folder.

You are looking at an empty Obsidian vault folder. I run [your business] and I also want to keep my personal life in here. Build me a tidy starter structure as plain markdown files and folders, directly in this folder.

Please create:
1. Top-level folders that fit me: an Inbox for quick unsorted capture, plus folders for Business, Personal brand, Writing, Health, Resources, People, and Archive. Adjust these to suit [your business] if a different set makes more sense, and tell me what you changed and why.
2. A Daily notes folder, and a daily-note template note inside it with headings for Today's focus, Notes, and Tasks.
3. A Home dashboard note at the top level that links to each main folder, so I have one note to start from each day.
4. A short README note explaining what each folder is for in plain English, so future me remembers the system.

Use simple folder and file names with no special characters. After you create everything, give me a one-paragraph summary of the structure and one tip for keeping it tidy.

When you keep writing the same kind of note (meetings, people, projects) by hand.

Create a reusable note template for [meetings / people / projects] in my Obsidian vault, saved in a Templates folder (create the folder if it does not exist).

Put sensible fields at the very top of the note inside a frontmatter block (the section between two lines of three dashes), because the Dataview plugin reads those fields to build live tables. For a [people] template, include fields like name, relationship, birthday, and last contact. For [meetings], include fields like date, attendees, and project. For [projects], include fields like status, owner, and due date. Pick whatever fields actually suit [meetings / people / projects].

Below the fields, add a clear body with headings I can fill in each time. Explain each field in one line in your reply so I know what to type, and show me one example Dataview table I could paste into my Home note to list these.

When you are not sure how to organise the vault and want Claude to coach you.

I want help designing the folder structure for my new Obsidian vault before we build anything. Do not create any files yet.

First, interview me. Ask me up to eight short questions about how I actually work: what [your business] does, what I produce day to day, what I need to find again later, and how I think about personal versus work notes. Ask them a few at a time, not all at once.

Then propose a folder structure for me. Mention whether you are leaning on PARA (Projects, Areas, Resources, Archive) or LYT (Linking Your Thinking, a more linked, map-of-content approach), and explain in plain English why that fits my answers. Keep it simple, no more than about eight top-level folders.

Only once I reply with approved should you create the folders and a short README explaining the system, directly in this vault folder.

Run once a day to empty your capture inbox.

Read my inbox note at [path to your inbox note, e.g. Inbox/Inbox.md]. For each separate idea, task, person, or topic in it, create a clean new note in the right folder for my vault (use [your folder list, e.g. Projects, People, Areas, Reference]). Give each note a clear title, a short summary, and link related notes to each other using [[wikilinks]]. When you are done, list the new notes you created and where you filed them, then remove the items you processed from the inbox note. Ask me before deleting anything you are unsure about.

When you have just typed a fast, messy dump and want it tidied.

Here is a raw brain-dump about [topic, e.g. my new product launch]:

[paste your messy notes here]

Turn this into clean notes for my vault. Split it into one note per distinct topic, each with a clear heading and tidy bullet points. Then pull out every action into a single task list, written as Obsidian checkboxes, and add a due date where I hinted at one (write the date as YYYY-MM-DD). Save the notes into [the folder, e.g. Projects/[project name]] and put the task list at the top. Tell me which notes you created.

End of day, from a few rough bullets about what happened.

Create today's daily note for [today's date, YYYY-MM-DD] in [your daily notes folder, e.g. Daily]. Build it from these rough bullet points:

[paste your bullets here]

Structure the note with three headings: What happened, Decisions made, and Open follow-ups. Under Open follow-ups, write each one as an Obsidian checkbox. Link any people or projects I mention using [[wikilinks]]. Keep it plain and short, no filler.

Friday or Sunday, to close the loop on the week.

Read all my daily notes from the past 7 days in [your daily notes folder, e.g. Daily]. Write a weekly review note in [your reviews folder, e.g. Reviews] covering: a short summary of the week, a list of everything I finished, and every open follow-up or promise I made that is still not done. For each open item, link back to the note where it came from using [[wikilinks]]. End with the 3 things that look most important to handle next week.

Right after a meeting, when the note is a wall of raw text.

Read my meeting note at [path to the note]. Turn it into three sections:
1. A short summary in plain English, no more than five sentences.
2. Decisions made, one bullet each.
3. Action items as a checklist, with an owner named in square brackets after each one, like [owner name].

Keep it tight. If something is unclear or has no owner, flag it as [needs owner] rather than guessing. Write the result back into the same note under a heading called Summary, at the top, and leave my original notes below it untouched.

When the source material for a deliverable is spread across several notes.

Using @[note-1] @[note-2] @[note-3], draft a [proposal / email / brief] for [client name].

Pull the relevant points from each note. Do not invent facts. If the notes disagree or a key detail is missing, list those gaps at the bottom under Open questions instead of filling them in.

Match my plain, direct tone: short sentences, no fluff. Save the draft as a new note called [draft for client name] and tell me which note each main point came from so I can check it.

Before a call or follow-up, to remember where things stand with someone.

Search my whole vault for every mention of [client or topic]. Then give me a one-paragraph summary of where things stand right now: the latest status, anything outstanding, and what I said I would do next.

Under the paragraph, list the notes you found it in as links, newest first, so I can jump straight to the source. Do not change any of my notes, just read and report.

When a note has grown into a long, unstructured dump you want cleaned up.

Turn on Plan Mode first (Shift+Tab), then plan a tidy-up of this note before changing anything.

Restructure it with clear headings, group related points together, and add a short summary at the top. Keep all my facts and wording where it matters, just organise it. Do not delete content, only reorder and add headings.

Show me the full plan and the diff of what you will change, and wait for my approval before you touch the note.

Right after installing, to create the empty wiki structure.

Run /wiki to scaffold a new wiki in this vault. I want to use the [PARA / LYT / Zettelkasten / generic] style. My vault is about [what your notes cover, e.g. running my plumbing business in Geelong]. Set up the folder structure and the index page, then show me what you created and how it is organised.

To turn a single report or article into linked pages.

Ingest the document at [path to a report or article in my vault] and turn it into interlinked wiki pages. Pull out the key people, concepts, and facts as separate linked notes, then update the wiki index so I can navigate to everything. Start with just this one file.

When your wiki has gaps you want filled in with web research.

Run /autoresearch on [topic, e.g. local SEO for trade businesses] to fill the gaps in my wiki. Do a few rounds of web research, then file the findings as new pages and link them into the existing notes. Tell me which sources you used.

Before you start trusting the wiki, or every few weeks.

Lint the wiki and show me a report of: orphan pages that nothing links to, dead links, topics that look like gaps, and any contradictions between my sources. List the worst issues first and tell me which ones to fix by hand.

To wire a one-off note into the wiki properly.

Read my note at [path to a meeting or idea note] and add it to the wiki. Create the right linked pages for it, connect it to related notes already in the vault, and update the index. Do not change my original note, just build the wiki pages around it.

First, to build the file every future session will read. Works the same in the Claudian panel inside Obsidian.

I want to create a CLAUDE.md master context file at the very top of my Obsidian vault. This is the file you will read first in every session so you always know who I am and how I work.

Before you write anything, interview me briefly. Ask me a few short questions, a couple at a time, about: who I am and what I do, the business or work I am focused on, how I like to write (tone, length, words or punctuation I avoid), how I like you to work with me, and any firm rules you should always follow.

Then create CLAUDE.md at the top level of this vault with clear headings for: About me, What I do, How I write, How I like to work, and My rules. Keep it tight and skimmable, a page at most. Add a Changelog section at the very bottom with today's date ([today's date, YYYY-MM-DD]) and a one-line note that you created the file.

When you are done, show me the file and remind me to keep it updated as things change.

Right after the master file exists, to make Claude remember sessions on its own. Works the same in Claudian.

Open my CLAUDE.md at the top of this vault and add a new section called Session memory.

In it, instruct yourself to do the following at the end of any working session with me: append a short dated summary to a note at [my Inbox folder, e.g. Inbox/claude-memory.md], creating that note if it does not exist. The summary should be a few bullets covering decisions we made, what we built, and any new facts about me or my work that came up.

Spell out the exact heading format you will use for each entry so it is consistent every time. Use a level-two heading with the date, like '## 2026-07-01 session', followed by the bullets underneath. Show me the section you added and one example entry so I can see what it will look like.

At the end of a good chat that cannot see your vault, so the next session inherits it. Also works from the Claudian panel.

Before we finish, summarise everything we decided and built in this conversation so my next session has the context.

Write it as a short, skimmable set of bullets: the decisions made, anything we created, and any new facts worth remembering. Keep it tight, no filler. Then append it to my memory note at [my memory note, e.g. Inbox/claude-2026-07-01.md] under a level-two heading with today's date, like '## 2026-07-01'. If you cannot write to that note directly, give me the text in a code block so I can paste it in myself.

Every few weeks, to keep the master file current without rewriting it. Works the same in Claudian.

Review my recent notes in [the folders to scan, e.g. Inbox, Business, and Daily] and update my CLAUDE.md at the top of this vault with anything new about me, my business, or how I work.

Merge the new details into the right sections. Do NOT remove or rewrite anything that is already there without checking with me first: if you think something is out of date or contradicts a note, list it and ask me before changing it. Add a dated line to the Changelog at the bottom ([today's date, YYYY-MM-DD]) describing what you added.

When you are done, show me a short summary of what changed and any conflicts you want me to settle.

Use first, before you wire anything up, to get a setup matched to your kit.

I want my meetings to record themselves and end up as clean notes in my Obsidian vault. Interview me one question at a time about: 1) what voice recorder or app I use to capture meetings, 2) what calendar I use and whether attendees are listed on each event, 3) where my Obsidian vault lives and which folder meeting notes should go in, and 4) how technical I am with automation tools. Once you have my answers, propose the SIMPLEST possible pipeline to get a meeting summary into [my vault folder, e.g. Meetings] using a recorder plus a no-code trigger like Zapier. Then describe the next step up I could add later for speaker labels and richer summaries. Keep it plain English and do not assume I know any of the tools yet.

Use when you're ready to add the smart layer in n8n.

Write the logic for an n8n code node that does speaker identification and summarisation by calling the Claude API. The node receives three inputs: 1) the raw meeting transcript text, 2) the list of calendar attendees for that meeting, and 3) a roster of known people (name plus a short note on each, like their role). Have the node build a prompt that asks Claude to label who said what using the attendees and roster as the candidate speakers, and then write a structured summary with sections for decisions, action items, and open questions. Output clean Markdown ready to save as an Obsidian note. Explain clearly where each of the three inputs plugs into the node, and leave a clearly marked placeholder for [my Claude API key] rather than inventing one. Do not include any real keys or secrets.

Use last, once speaker ID works but sometimes guesses wrong.

Design a Telegram confirmation step for my meeting pipeline. When the Claude API is unsure who a speaker is, I want a Telegram message sent to me with one-tap inline buttons, one button per likely person from the meeting's attendees plus an Other option. Describe: 1) what the message text should say so I can decide quickly, 2) how the tap buttons should be laid out, and 3) what should happen after I tap, specifically how the chosen name gets written back so the saved Obsidian note is corrected in place. Describe the flow and the message structure in plain English. Use [my Telegram bot] and [the note path] as placeholders and do not include any real bot tokens, chat IDs, or webhook URLs.

Use after you drop one exported WhatsApp chat into your vault.

I've put an exported WhatsApp chat with [person] at [path to the export .txt file]. Read it, then create or update their note at [path to their person note in my People folder].

Pull out and add: any life events (new job, move, baby, breakup, health), things I should follow up on, gift ideas, and their interests and important relationships. In the frontmatter set last_contact to today's date ([today's date]) and fill birthday if it's mentioned.

Rules: only ADD and MERGE. Do NOT overwrite or delete anything I wrote by hand. If you're unsure about a detail, put it under a 'To confirm' bullet rather than stating it as fact. Keep my existing structure and headings. Show me a short summary of what you changed.

Use once the manual version is working and you want it automated.

Write me a script (in [your preferred language, e.g. Node or Python]) that reads a WhatsApp export text file and creates or updates one markdown note per person in my People folder at [path to my People folder].

For each person it should: create the note if it doesn't exist using my template at [path to my person template], fill simple frontmatter fields (name, last_contact as the date of their most recent message, message_count), and append the raw messages under a dated '## Chat log' heading WITHOUT touching any other section. If the note already exists, only update those frontmatter fields and add the new log, never overwrite my hand-written notes.

Make it safe to run repeatedly (idempotent), skip messages already logged, and print a summary line per person at the end. Walk me through how to run it before you write the whole thing.

Use to make the sync run on its own every night.

Set up a [Windows Task Scheduler / Mac cron] job that runs my WhatsApp sync script at [time, e.g. 2am] every night and writes the output to a log file at [path to a logs folder] with the date in the filename.

Give me the exact steps and any commands or config I need to paste, explain in plain English what each part does, and tell me how to test it runs correctly once before I trust it overnight. Also tell me how to check the log and how to turn it off if I need to.

Use after raw messages are syncing in and you want them summarised.

I have a nightly job that drops raw WhatsApp messages into each person's note in [path to my People folder] under a '## Chat log' heading. Add a step that, for each note changed today, reads the new messages and updates a '## Summary' section with: recent life events, open follow-ups, and gift ideas.

Use a small fast model for this and keep it cheap. The step must ADD and MERGE only: never edit my hand-written notes, never delete the chat log, and never restate something as fact if it's only a guess (flag guesses under 'To confirm'). Make it skip notes that haven't changed so it stays fast and low-cost, and log what it touched.

Use once your person notes have last_contact and birthday filled in.

Create a Dataview dashboard note in my vault called 'Relationships'. It should read the frontmatter from every note in my People folder at [path to my People folder] and show three tables:

1) Birthdays in the next 30 days, sorted by date.
2) People I'm losing touch with: anyone whose last_contact is more than [number, e.g. 60] days ago, sorted oldest first.
3) Open follow-ups: people who have a follow_up field set, with the follow-up text.

Give me the full Dataview code blocks ready to paste, and explain in one line above each table what it's showing so a non-technical person gets it at a glance.

You want a capture source flowing into your vault but do not know how to wire it up.

I want to get [emails / voice memos / form responses / a folder of PDFs] into my Obsidian vault automatically. My vault is at [path to your vault folder]. Before you build anything, interview me one question at a time about the tools and accounts I already have, so we reuse them instead of signing up for new ones. Then propose the simplest possible pipeline in plain English, explain the trade-offs, and once I approve, build the first working piece and show me how to test it with one real item.

You have a source and want each item saved as its own tidy note.

Write a small script that takes [items from this source, e.g. files in the folder at [path]] and saves each one as a separate markdown note in [path to the target folder in my vault]. Each note should have sensible frontmatter at the top: a title, the date, the source, and a couple of tags that fit my setup. Use a clear filename based on the date and a short title. Keep the code simple and commented. When it is done, explain in plain English what the script does, where you saved it, and the exact step to run it once so I can check one note looks right.

The script works once and you want it to keep working unattended.

Add error handling and a simple log file to this script so one bad item does not stop the whole run. Write a short line to the log every time it runs: when it ran, how many items it processed, and any it skipped and why. Then tell me, in plain English, exactly where the log lives and what I should look for to know it is still working, plus the warning signs that mean it has quietly stopped.

You are ready for it to run on its own in the background.

Set this script up to run automatically on a schedule on my [Windows / Mac] machine, running [every morning at 7am / once an hour / pick a sensible default and tell me why]. Walk me through the setup step by step. Then explain how I check it is still running, how I see the last time it ran, and how I pause or remove the schedule if I ever need to.