Topic cluster strategy

The pillar / cluster blueprint for niki-nakamura.github.io/til/. On the premise that SEO works better by connecting "narrow and deep" with internal links than by going "wide and shallow".

Pillar / cluster map

Pillar 1: cognition

Pillar page: cognition/cognition-basics.md Pillar intent: an entry point to cognitive science as a whole Target KW: "what is cognition", "cognition"

Clusters:

• cognition/metacognition.md — metacognition
• cognition/procedural-and-conditional-knowledge.md — procedural knowledge
• cognition/executive-function.md — executive function
• (TODO) working memory — not started
• (TODO) attention control — not started

Pillar 2: thinking

Pillar page: thinking/systems-and-debugging-thinking.md Pillar intent: an introduction to classifying thinking styles Target KW: "systems thinking, debugging thinking", "types of thinking methods"

Clusters:

• thinking/adaptive-expertise.md — adaptive expertise
• thinking/resilience.md — resilience
• (TODO) dual-process theory — not started
• (TODO) abductive reasoning — not started

Pillar 3: git

Pillar page: git/git-history.md Pillar intent: practical use of git plus its history Target KW: "history of git", "how git works"

Clusters:

• git/stash-pull-rebase.md — stash → pull → rebase
• (TODO) recovery with reflog — not started
• (TODO) safe use of interactive rebase — not started

Pillar 4: design

Pillar page: design/better-ui-ux-workflow.md Pillar intent: the overall picture of the UI/UX flow in the AI era Target KW: "Claude Code design", "AI UI production flow"

Clusters:

• design/claude-code-design-process.md — observing Claude's decision-making
• design/elevenlabs-replication.md — ElevenLabs replication steps (new)
• (TODO) practical shadcn/ui — not started
• (TODO) visual verification with Playwright MCP — not started
• (TODO) Figma Dev Mode MCP — not started

Pillar 5: claude (new 2026-05-20)

Pillar page: claude/claude-agents-spec.md Pillar intent: the overall picture of the Claude Code ecosystem Target KW: "Claude Agents spec", "what is Claude Code"

Clusters:

• claude/orchestration-stack.md — starting from the orchestration layer
• (TODO) building your own Claude Code skill — not started
• (TODO) configuring Claude Code hooks — not started
• (TODO) configuring Claude Code MCP — not started
• (TODO) Claude Code worktree parallelism — not started
• (TODO) the correct pattern for spawning sub-agents — not started

Internal-linking policy

• pillar → cluster: at the end of the pillar, a "Related: ..." section links to every cluster
• cluster → pillar: at the top of the cluster, a back-link to the pillar saying "part of (pillar name)"
• cluster ↔ cluster: only when relevance is high. Do not overuse (avoid diluting link equity)

Decision flow for adding a cluster

When writing a new TIL, decide:

1. Will it be a cluster of an existing pillar? → Yes: write it under that pillar + bidirectional links
2. It does not fit an existing pillar, but is there a prospect of writing 3 or more related entries? → Yes: set it up as a new pillar
3. Neither → do not write it (or, exceptionally, write it as a one-off under thinking/)

Review cycle

• Monthly, cross-check against the Status in KEYWORDS.md and review the strategy of the cluster to which any "KW stuck on target" belongs
• Update pillar pages at least once a month (with "Last updated" at the top). Stale pillars tend to drop in ranking.