notebooklm-second-brain
NotebookLM Second Brain
Policy: Query the relevant NotebookLM notebook before web search or dumping full docs into context.
Description
This skill enforces a "Notebook First" retrieval policy. Instead of loading entire markdown files or running web searches for architecture decisions, debugging patterns, or security knowledge, the agent queries purpose-built NotebookLM notebooks via the nlm CLI. This keeps the agent context window lean and retrieval fast.
When to Apply
| Scenario | Notebook | Why |
|---|---|---|
| "How does auth work?" | project_sot |
Architecture decisions live here |
| "Why is this test failing?" | debug_kb |
Error patterns and debugging playbooks |
| "Is this input sanitised?" | security_handbook |
OWASP patterns and security reviews |
| "Explain the codebase" | repo_onboarding |
Codebase atlas and mind maps |
| After successful build/verify | project_sot |
Auto-sync implementation notes |
More from cleanexpo/unite-hub
tdd
Use when implementing any feature or bug fix. Hard gate — no production code without a failing test first. Applies to vitest (apps/web/) and pytest (apps/backend/). Triggers on "implement", "add feature", "fix bug", "new component", "new endpoint", or any code-writing task.
1idea-to-production
Plain-English pipeline from idea to production — routes user requests to the right phase and agent
1oauth-flow
OAuth 2.0 and OIDC integration with PKCE, Supabase Auth providers, and redirect URI validation
1health-check
>-
1csv-processor
>-
1vector-search
>-
1