---
name: note-taking-system
description: "Set up a note-taking system that you'll actually use and that makes your notes findable and useful later — not a graveyard of notes you never reopen. Use when asked help me take better notes, set up a note system, my notes are a mess, or how should I organize my notes. Produces a system matched to your actual need (capture, study, or thinking), a simple capture-and-organize flow, a findability method (tags/links/structure), the review habit that keeps notes alive, and a warning against over-engineering the system instead of using it."
---

# Note-Taking System

Most note systems die two ways: notes are captured and never reopened (a graveyard), or the person spends more time building the perfect system than taking notes. A good system is simple, matches what you actually use notes *for*, and makes past notes findable when you need them. This sets one up that fits your need — and warns you off the productivity-porn trap of endlessly tweaking it.

## What This Skill Produces

- **The right system for your need** — capture-and-forget reference, active study notes, or a thinking/idea system need different setups; match it
- **A capture-and-organize flow** — how notes get in fast and where they land (frictionless capture is what keeps a system alive)
- **A findability method** — how you'll actually find a note later (search, tags, links, or simple structure) — the thing most systems fail at
- **The review habit** — the light revisit that keeps notes from becoming a graveyard
- **An anti-over-engineering warning** — the reminder to use it, not perfect it

## Required Inputs

Ask for these if not provided:
- **What you use notes for** — reference, study, ideas/writing, work, or a mix
- **Your tools** — a specific app, paper, or need a suggestion
- **What's failing now** — notes lost, never reviewed, too messy, or system too fiddly
- **Your style** — minimal, or you like structure

## Framework: Match The Need, Keep It Simple

1. **Start from the use.** Reference notes, study notes, and a thinking system have different needs — build for how the person actually uses notes, not a universal ideal.
2. **Make capture frictionless.** If getting a note in is hard, the system dies. One fast inbox/capture point beats a perfect taxonomy.
3. **Solve findability.** The real test is finding a note months later — pick the lightest method that works (good search + a little structure usually beats elaborate tagging).
4. **Build a review habit.** A light periodic revisit turns notes from a graveyard into a living resource — without it, notes are write-only.
5. **Don't over-engineer.** Warn against the endless-tweaking trap; a simple system used beats an elaborate one abandoned. Use it, refine only when it actually hurts.

## Output Format

### Note system: for [use] · tool [x]

**Your need:** [reference / study / thinking] → so the system should [fit].
**Capture:** [one fast inbox/point — frictionless].
**Organize:** [light structure — folders/tags/links, minimal].
**Find it later:** [the findability method — usually search + a little structure].
**Review:** [the light habit that keeps it alive].
**Don't:** over-engineer it — use it, refine only when it genuinely hurts.

## Quality Checks
- [ ] System is matched to the person's actual use for notes
- [ ] Capture is frictionless (one fast point)
- [ ] Findability is explicitly solved
- [ ] Includes a review habit to prevent a note graveyard
- [ ] Warns against over-engineering the system

## Anti-Patterns
- **A complex taxonomy** that's a chore to maintain.
- **Notes captured and never reopened.**
- **No findability plan** — notes lost in the pile.
- **Building the system** instead of taking notes.
- **A one-size system** ignoring what notes are for.

## Example Trigger Phrases
- "Help me set up a note-taking system that I'll actually use."
- "My notes are a mess — how should I organize them?"
- "What's a good note system for studying?"
- "I take notes but never look at them again. Fix that."
- "Set me up a simple notes system, not an elaborate one."