Slash Command

/til

Today I Learned — explore a specific technical rabbit hole. Start from a question, end with a dense, self-contained write-up.

npx claudepluginhub irfanabduhu/rune --plugin codemonk

Details

Argument[question or topic to investigate]

Prompt Preview

Investigate and write up: $ARGUMENTS

1. **The question** — state the precise question being investigated. If the input is vague, sharpen it into something answerable. Good questions have surprising answers.
2. **Research** — search documentation, source code, specifications, RFCs, and reputable technical writing. Follow the thread wherever it leads. Prioritize primary sources over blog summaries.
3. **The answer** — present findings in a logical progression. Lead with the key insight, then build the supporting evidence. Include code examples that demonstrate the behavior, links to authorit...

Command Content

Other plugins with /til

/til

Create a "Today I Learned" documentation note capturing the learnings from this coding session.

til

/til

Record TIL (Today I Learned) to Notion database

notion

/til

Save a TIL (Today I Learned) note to Obsidian knowledge base

4 tools

claude-toolkit

/til

Adds a TIL (Today I Learned) entry to the daily note, optionally creating a standalone note for deeper topics. Use when you learned something, TIL, today I learned, or want to note a quick discovery.

obsidian-bridge

Stats

Parent Repo Stars2

Parent Repo Forks0

Last CommitApr 11, 2026

Actions

View Source View Plugin View on GitHub View README

Investigate and write up: $ARGUMENTS 1. **The question** — state the precise question being investigated. If the input is vague, sharpen it into something answerable. Good questions have surprising answers. 2. **Research** — search documentation, source code, specifications, RFCs, and reputable technical writing. Follow the thread wherever it leads. Prioritize primary sources over blog summaries. 3. **The answer** — present findings in a logical progression. Lead with the key insight, then build the supporting evidence. Include code examples that demonstrate the behavior, links to authorit...

Investigate and write up: $ARGUMENTS

The question — state the precise question being investigated. If the input is vague, sharpen it into something answerable. Good questions have surprising answers.
Research — search documentation, source code, specifications, RFCs, and reputable technical writing. Follow the thread wherever it leads. Prioritize primary sources over blog summaries.
The answer — present findings in a logical progression. Lead with the key insight, then build the supporting evidence. Include code examples that demonstrate the behavior, links to authoritative sources, and any caveats or edge cases discovered.
Why it matters — connect the finding to practical implications. How does knowing this change what you'd do? What common misconceptions does it correct?
Further threads — list 2-3 related questions that emerged during research but weren't followed. These are the reader's next rabbit holes.

Output as til-[topic-kebab-case].md. Optimize for information density — this is a reference you'll grep for later. Include version numbers and dates where behavior is version-dependent.