CHRISTINE Never Lose What a Great Session Taught You
Field Notes turns what you built or learned with Claude into a numbered, one-page reference card — the same five sections every time, written so plainly you can pick it up cold in three months and immediately use it.
← Back to the Skills LibraryInstalled in under a minute. No tech skills required.
You don't need to know how to code, and you don't need to set anything up. There are two blocks below. If you can copy and paste, you can install this.
Paste the instruction
Copy the first block and paste it into a brand-new Claude conversation. Don't hit send yet — it's the note that tells Claude what to do.
Paste the skill underneath, then send
Copy the full skill block and paste it right below the instruction. Send it. Claude builds the skill, personalizes it to your business, and confirms when it's ready.
Install the skill below for me. Keep the skill text exactly as written, then personalize its defaults from what you already know about me — my business, my voice, my priorities, and the places I keep my notes and files. Confirm when it's installed and show me exactly how to run it.
--- name: field-notes description: Generate structured one-page Field Notes that capture what was learned or built during a Claude session. A Field Note is a clean, stackable reference card written in plain language for non-technical entrepreneurs. Use this skill when you say "write a field note," "create a field note," "field note this session," "log this as a field note," or any variation of wanting to capture a session as a Field Note. Also trigger when you mention your Field Notes system or reference capturing a session as a reference card. --- # Field Notes Generate structured, one-page Field Notes that capture what was learned or built during a Claude session. Each Field Note is a reference card, written so a non-technical entrepreneur can pick it up and immediately use it. ## Trigger Phrases - "write a field note" - "create a field note" - "field note this session" - "log this as a field note" - Any variation referencing capturing a session as a Field Note ## Workflow ### Step 1: Identify the Subject If it is clear from the conversation what was built or learned, proceed to Step 2. If it is not obvious, ask: > What did we build or learn this session that you want to capture? Keep the question short. Ask one question only. ### Step 2: Determine the Field Note Number Field Notes are numbered so they stack in sequence over time. Look at your Field Notes collection, wherever you keep it (Notion, a doc, a folder). Find the highest number already in use. The new Field Note gets the next number in sequence. If you cannot see the collection or no previous Field Notes exist, ask once: what number is this Field Note? Then remember it for the session so you do not have to ask again. ### Step 3: Generate the Field Note Write the Field Note in clean markdown using the exact structure below. Every Field Note follows this format with no exceptions. --- **FIELD NOTE TEMPLATE:** ``` # Field Note #[NUMBER]: [DESCRIPTIVE TITLE] **Date:** [YYYY-MM-DD] --- ## The Big Idea [One sentence. What is the core concept or thing we built? Keep it plain. No jargon.] --- ## The Daily Flow [Step-by-step process. Exactly what to do, in order. Written like you are telling a friend over coffee. Number each step. Use plain language. If a 5th grader could not follow it, rewrite it.] 1. [Step] 2. [Step] 3. [Step] ... --- ## Key Terms | Term | What It Means | |------|--------------| | [Term] | [Plain-language definition] | | [Term] | [Plain-language definition] | --- ## What to Log and Where | What | Where | |------|-------| | [Item] | [Location or file] | | [Item] | [Location or file] | --- ## The One Key Takeaway [One sentence or short paragraph. The single habit, insight, or mental model that makes this stick. Write it like advice you would give yourself tomorrow morning.] ``` --- ### Step 4: Present for Review Show the full Field Note to the user in markdown. ### Step 5: Route to Destination Ask: > Here is your Field Note. Want me to save it to your Field Notes collection? Tell me where you keep them, or just say the word and I will hand you the markdown to paste in yourself. - If the user names a destination you can write to, save it there. - If the user only wants the markdown, hand them the clean markdown to paste wherever they keep their Field Notes. ### Step 6: Save or Hand Off Save the Field Note to whichever destination the user selected in Step 5. If you cannot write to that destination, let the user know and provide the markdown so they can paste it manually. ## Voice and Tone Rules Write every Field Note like you are handing a reference card to a client who has never used AI before. **Do this:** - Simple, direct sentences - Plain language a non-technical entrepreneur can follow - Active voice - Short paragraphs and bullet points - Specific and concrete (name the files, name the tools, name the steps) **Never do this:** - Never use these words: delve, unlock, craft, foster, tapestry, embarking, unleash, unveil, realm, boasts, revolutionize, tenets - Never use semicolons - Never use em dashes. Use periods, commas, or break into separate sentences instead - Never use contrastive framing - Never write it like a blog post, marketing copy, or thought leadership piece - Never be vague when you can be specific
From then on, just finish a session and say "Field note this session."
Want to go further than skills?
Skills like this are how Christine runs her own business every day. In the Heart-Led AI Signature Group Coaching, she teaches you the whole system — live, in plain English, at your pace.
Explore Signature CoachingOne page. Five sections. Numbered to stack.
Every Field Note follows the exact same structure, no exceptions — numbered in sequence with the notes before it, dated, and written for the version of you who reads it cold later:
1 · The Big Idea
One sentence. The core concept or the thing you built, in plain words. No jargon allowed.
2 · The Daily Flow
The step-by-step process, numbered, written like you're telling a friend over coffee. The skill's own standard: if a 5th grader couldn't follow it, it gets rewritten.
3 · Key Terms
A simple two-column table — each term you touched this session, and what it actually means in plain language.
4 · What to Log and Where
Another table, and a lifesaver later: exactly what to record, and the specific file or location where it lives. Named, not gestured at.
5 · The One Key Takeaway
The single habit, insight, or mental model that makes the whole thing stick — written like advice you'd give yourself tomorrow morning.
You see it before it's saved anywhere.
Field Notes shows you the full card first, then asks where you keep your collection — Notion, a doc, a folder. If Claude can write there, it files the note for you. If it can't, it says so honestly and hands you the clean markdown to paste in yourself. Either way, you end the session holding the card.
Keep stacking: pairs beautifully with Knowledge Library
Field Notes captures one session as a single clean card; Knowledge Library takes a whole messy collection of notes and distills it into organized, searchable wisdom with through-lines.
Get Knowledge Library →Because you won't remember. Nobody does.
You end a session buzzing, sure you'll remember how it all worked. Two weeks later you're re-learning your own system. Field Notes exists so the knowledge survives the session.
The structure never changes
Every note is the same five sections in the same order, no exceptions. That consistency is the feature: months from now, you know exactly where on the card to look.
It's written for a beginner on purpose
Simple, direct sentences. Active voice. Specific and concrete — name the files, name the tools, name the steps. A card you can only decode on a good day isn't a reference card.
The numbering builds a library
Each note takes the next number in your sequence, so your collection stacks over time. The skill checks your collection for the highest number in use — and only asks you once if it can't see it.
The banned-words list keeps it human
No delve, no unlock, no tapestry. No semicolons, no em dashes, no marketing-speak. A Field Note reads like a reference card from a smart friend, never like a blog post.