メニュー
Use this whenever durable knowledge should be written to or found in Notion — PRDs, decisions, runbooks, briefs, learnings — or the user says "save this", "document this", "add to the wiki". Notion writes need approval. NOT for task status — that's Linear.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | notion-brain |
| description | Use this whenever durable knowledge should be written to or found in Notion — PRDs, decisions, runbooks, briefs, learnings — or the user says "save this", "document this", "add to the wiki". Notion writes need approval. NOT for task status — that's Linear. |
Notion is the durable knowledge base. This skill governs what goes there, how it's structured, and how it stays clean.
Maintain Notion as the single durable source for PRDs, decisions, runbooks, operating logs, briefs, and project memory. Prevent it from becoming a duplicate task list or a chat dump.
Reads from:
CLAUDE.md: project conventionsWrites to:
If your workspace doesn't have this structure yet, this skill can propose it. Don't restructure without explicit approval.
AI Operating Workspace
├── Projects
│ ├── [Project A]
│ │ ├── PRDs
│ │ ├── Decisions
│ │ ├── Runbooks
│ │ ├── Daily briefs
│ │ └── Weekly reviews
│ ├── [Project B]
│ │ └── (same structure)
│ └── [other projects]
├── Cross-project
│ ├── Operating manual
│ ├── Skill backlog
│ ├── Pattern library
│ └── Meta-decisions
├── Clients (if agency work)
│ └── [Per-client space, isolated]
└── Reference
├── Stack documentation
├── Convention library
└── External research
Different types live in different places and have different templates:
| Content type | Lives in | Template |
|---|---|---|
| PRD | Projects/[project]/PRDs | Idea-to-PRD output |
| Decision | Projects/[project]/Decisions | ADR template |
| Runbook | Projects/[project]/Runbooks | Step-by-step ops |
| Daily brief | Projects/[project]/Daily briefs | Daily template |
| Weekly review | Projects/[project]/Weekly reviews | Weekly template |
| Pattern | Cross-project/Pattern library | Pattern template |
| Operating manual update | Cross-project/Operating manual | (in-place edit) |
| Imported memory | Project-specific OR Pattern library | After sanitization |
Before writing new content:
Don't create duplicates. Update or supersede.
For PRDs: link Linear project, GitHub repo, Figma file, related decisions. For decisions: link the PRD or issue that triggered it. For runbooks: link the GitHub automation source. For briefs: link the source data (Linear queue, PR list, etc.).
Notion content is for future-you. Optimize for readability later, not for thoroughness now.
Rules:
[?] or TBD)Notion is durable. So:
If it's transient, it stays in chat or local notes — not Notion.
For decisions and runbooks that may decay:
Notion's value is the graph, not individual pages. Always:
When a page no longer reflects current state:
Use existing templates when adding to a database. Don't reinvent structure each time.
If a template doesn't exist for a content type you're using often, propose one (separate approval).
For non-trivial content:
For tiny updates (a single line, a status change), drafting is overkill — but the skill should still note what it did.
# Notion operation — [action] — [target]
## Content type
[PRD / Decision / Runbook / etc.]
## Destination
[Page or database path]
## Action
[Create / update / supersede / archive]
## Summary
[1-2 sentences on what's being added or changed]
## Linked artifacts
- Linear: [link]
- GitHub: [link]
- Related decision: [link]
## Notion content (draft)
---
[Full Notion-ready markdown]
---
## Review trigger
[Date or condition, if applicable]
## Approvals needed
- [ ] Approve content
- [ ] Approve writing to Notion
Tier 1 (read-only) — querying Notion, summarizing pages: always allowed.
Tier 2 (draft) — drafting content for chat: always allowed.
Tier 3 — needs approval:
Tier 4 — needs explicit approval:
archive/skills/memory-import-sanitizer/)Never auto:
archive/skills/memory-import-sanitizer/)idea-to-prd-tracer — produces PRDs that this skill writesdecision-log-adr — produces decisions that this skill writesautomation-sre — produces runbooks that this skill writesdaily-brief — produces briefs that this skill writesskill-creator — produces patterns that this skill writeslinear-operator — task status lives in Linear, never Notionarchive/skills/ holds memory-import-sanitizer, system-of-record-governance, and client-boundary-guard checklistsNotion becomes a chat archive — Pages full of "I think we should..." and "let me explore..." Notion is for durable. Move exploration to chat or scratch notes.
Duplicate PRDs — Two PRDs for the same feature because no one searched. Always check before creating.
Stale runbooks — Runbook says do X, but reality is now Y. Add review triggers. During weekly review, check runbooks against actual practice.
No cross-linking — Pages exist but you can't find them. The graph is the value. Link aggressively.
Notion competes with Linear — Tasks live in Notion as bullet points. They drift from Linear. Linear is the task system. Notion only describes tasks at the project level (in PRDs, decisions, briefs).
Client data in general workspace — A project PRD references client X by name. That's a leak. Keep client names out of the general workspace (checklist: archive/skills/client-boundary-guard/).
Death by template — Every template creates 8 sections, most empty. Templates should encode minimums, not exhaustive structure.
Use this whenever a PR has a Vercel preview URL and needs browser QA against acceptance criteria — happy path, errors, empty states, responsive behavior, a11y basics — even if the user just says "check the preview". Requires a preview URL. NOT for release/deploy-readiness checks (no preview needed there) — use deploy-ready.
Plan and split work into parallel worktree sessions. Use whenever the user wants to work on multiple tasks at once, mentions parallel sessions, worktrees, "split this up", "dispatch", or lists several independent tasks for one work session.
Use this skill when implementing or reviewing UI that needs semantic HTML, keyboard navigation, focus management, ARIA labels, color contrast, reduced motion, forms, modals, or public-facing pages. Do not use as a standalone product-planning or backend workflow; pair it with design-system-ui, responsive-ui, or vercel-preview-qa when broader UI review is needed.
Use this skill when working across client, agency, consulting, or personal projects where code, data, credentials, prompts, or reusable patterns could leak between contexts. Do not use for ordinary single-project work with no cross-client or cross-workspace boundary risk.
Use this skill when creating components, implementing Figma designs, cleaning inconsistent styling, adding or reviewing tokens, spacing, typography, or component variants. Do not use for backend work, feature scoping, or visual QA that requires a live preview instead of design-system decisions.
Use this skill when importing ChatGPT or Claude exports, old Notion databases, local notes, or messy knowledge dumps into a durable knowledge system after redaction, deduplication, and classification. Do not use for live project planning, raw unredacted client data, or content that should remain out of Notion.