---
name: note
description: "Append a one-off research note, brainstorm, or insight to aiwiki/raw/{date}.md with a timestamp. Zero schema, zero friction — capture first, dream consolidates later. Use during Phase 1-2 research, ad-hoc exploration, or any thought worth remembering that doesn't yet fit a typed page (decision/gotcha/convention)."
---

# /note — Capture to aiwiki/raw

Append the user-supplied text to `aiwiki/raw/{YYYY-MM-DD}.md` under a timestamped header. No schema, no judgment — just capture. The wiki-lint hook fires automatically on save (no-op for raw/ since raw has no schema). `support-dream` consolidates raw entries at phase-close and PreCompact (~85% context), promoting anything that matches a typed schema to `aiwiki/proposed/{dream_id}/` for review.

## Steps

1. **Note text** = everything after `/note ` in the user's invocation. If the argument is empty, ask the user what they'd like to capture and wait for the reply.
2. **Check aiwiki state.** Read `project.aiwiki_enabled` from `.claude/CLAUDE.md` (treat missing key as `true` for backwards compatibility with existing projects, but treat explicit `false` or absent `aiwiki/` directory as disabled). If disabled, surface to the user and stop:
   ```
   aiwiki disabled — /note would normally append to aiwiki/raw/{date}.md.
   The note was NOT saved. Options:
     - Re-run /setup and pick Y to enable the knowledge layer
     - Paste the note into your own scratch file
   ```
   Do not write anywhere else (no fallback to `.forge/`). /note is the aiwiki entry point; without aiwiki it has nowhere correct to land.
3. **Today's date** = `$(date +%Y-%m-%d)`.
4. **Target file** = `aiwiki/raw/{date}.md`. Create the directory if needed: `mkdir -p aiwiki/raw`.
5. **If the file doesn't exist**, start it with: `# Raw notes — {date}` followed by a blank line.
6. **Append a section**:
   - Header: `## {HH:MM} — {first ~60 chars of the note, no trailing punctuation}`
   - Blank line
   - The full note body
   - Blank line
7. **Confirm to the user**: "Captured to `aiwiki/raw/{date}.md`."

## Example

User: `/note Considering Tailwind v4 — oxide engine fast but plugin ecosystem still broken in 2026; revisit in Q3`

Resulting `aiwiki/raw/2026-05-15.md`:

```markdown
# Raw notes — 2026-05-15

## 14:23 — Considering Tailwind v4 — oxide engine fast but plugin ecosystem

Considering Tailwind v4 — oxide engine fast but plugin ecosystem still broken in 2026; revisit in Q3
```

## When to use

- During **Phase 1 (concept)** or **Phase 2 (wireframe)** when research or brainstorm yields an insight worth remembering — neither phase auto-captures to aiwiki, so `/note` is the manual hook.
- During any phase when a thought doesn't yet fit a typed page (it's not yet a decision, not yet a confirmed gotcha, not yet an established convention).
- When deferring a decision: "considered X, need more info before committing."

## When NOT to use

- The content is a **decision** → write to `aiwiki/decisions/` directly using the decision schema. Future agents read that folder for ADRs; raw notes there won't be retrieved predictably.
- The content is a **confirmed gotcha** (with reproducible failure mode) → write to `aiwiki/gotchas/` directly so gotcha-hunter can find it.
- The content is an **established convention** → write to `aiwiki/conventions/` so harden and code-reviewer can enforce it.

`/note` is for the in-between — research, hypotheses, half-formed thoughts that haven't earned a typed page yet. Dream consolidation will promote anything that matures into a typed shape.

## I/O Contract

| Field | Value |
|---|---|
| **Requires** | `aiwiki/` directory (scaffolded by `/setup`) |
| **Produces** | New or appended `aiwiki/raw/{YYYY-MM-DD}.md` |
| **Triggers** | `wiki-lint` PostToolUse hook (no-op for raw/) |
| **Feeds into** | `support-dream` at phase-close and PreCompact — raw entries that match typed schemas get promoted to `aiwiki/proposed/{dream_id}/` for user review |

## Do NOT

- Do NOT edit prior entries. The point is append-only history. If a note turned out wrong, append a correction with the new timestamp.
- Do NOT structure the note. Plain prose. Schema-fitting is dream's job, not yours.
- Do NOT use `/note` for things that already fit a typed schema — write the typed page directly instead.