Capture solved problems as structured YAML-frontmatter markdown files after debugging success or confirmation, then retrieve relevant past solutions via fast grep search on metadata before new debugging, feature planning, or code exploration to leverage institutional knowledge and prevent repeated mistakes. Persist feedback on capture/retrieval behaviors across sessions and initialize knowledge directory structure.
npx claudepluginhub joshuaoliphant/claude-plugins --plugin compound-knowledgeCapture this solution NOW — use immediately after solving non-trivial problems, completing debugging sessions, or when the user confirms something works ("that worked", "it's fixed", "finally"). Do NOT wait to be asked — if a debugging session just ended successfully, proactively invoke this. Also trigger on: "document this solution", "capture this pattern", "save this for next time", "we should remember this". Saves structured YAML-frontmatter files for grep-based retrieval. Not for searching — use compound-retrieve for that.
Use when starting debugging, planning features, encountering errors, making design decisions, or working in unfamiliar code. Searches past solutions and engineering principles captured by compound-capture to surface institutional knowledge and prevent repeated mistakes. Trigger phrases include "have we seen this before", "check knowledge", "search for solutions", "this looks familiar", "check if we've solved this", "any past experience with this", "before I start, check for existing solutions", or any time past experience might inform the current task. Not for capturing new solutions — use compound-capture for that.
MUST check before starting any debugging session, investigating unfamiliar code, or planning a feature that might have been attempted before. Searches past solutions in knowledge/solutions/ to prevent repeated mistakes. Designed to be fast (<30s). Trigger proactively: before ANY bug investigation, before implementing patterns that feel like they should already exist, or when the user says "this looks familiar", "have we seen this", "check knowledge". Not for capturing — use compound-capture for that.
Save knowledge capture/retrieval feedback proactively. MUST trigger when the user corrects capture behavior ("don't capture that", "wrong category", "too verbose", "not enough detail") or confirms a good capture ("yes, exactly like that"). Also trigger on explicit requests: "save this feedback", "show my feedback", "clear feedback", "knowledge preferences", "consolidate feedback", "bake in my preferences". Feedback loaded by compound-capture and compound-retrieve across sessions.
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimPersonalized coding tutorials that use your actual codebase for examples with spaced repetition quizzes
I (Claude) act as you - Build knowledge base from your notes.
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
Comprehensive startup business analysis with market sizing (TAM/SAM/SOM), financial modeling, team planning, and strategic research
Comprehensive .NET development skills for modern C#, ASP.NET, MAUI, Blazor, Aspire, EF Core, Native AOT, testing, security, performance optimization, CI/CD, and cloud-native applications
Semantic search for Claude Code conversations. Remember past discussions, decisions, and patterns.
A collection of Claude Code plugins for productivity and learning workflows.
# Add this marketplace
/plugin marketplace add joshuaoliphant/claude-plugins
# Install any plugin
/plugin install <plugin-name>@oliphant-plugins
Create evidence-based spaced repetition flashcards using cognitive science principles from Andy Matuschak's research. Applies the 5 properties of effective prompts (focused, precise, consistent, tractable, effortful) to ensure cards actually work for long-term retention.
Features: Quality validation, knowledge-type workflows (factual, conceptual, procedural, salience), anti-pattern detection, template support, deck management, batch operations.
Requirements: Mochi.cards account + MOCHI_API_KEY environment variable.
/plugin install mochi-creator@oliphant-plugins
export MOCHI_API_KEY="your_api_key_here"
Adaptive autonomous SDLC with 5 skills covering the full development lifecycle:
bd commands) with explicit dependencies/plugin install autonomous-sdlc@oliphant-plugins
Build web applications where an AI agent dynamically generates HTML UI using hexagonal/ports-and-adapters architecture with HTMX for interactivity and MCP tools for data operations.
Stack: Claude Agent SDK + FastAPI + HTMX + Tailwind CSS.
/plugin install hexagonal-agents@oliphant-plugins
export ANTHROPIC_API_KEY="your_key_here"
Capture solved problems and retrieve past solutions as structured YAML-frontmatter files for grep-based retrieval across sessions and projects.
/plugin install compound-knowledge@oliphant-plugins
Generate autonomous experiment loops that iteratively improve code by editing, running, measuring a scalar metric, and keeping improvements via git commit/reset. Based on Karpathy's autoresearch pattern.
Generates: program.md + auto/run.sh with tiered quality gates, ready to run with claude --dangerously-skip-permissions.
/plugin install autoloop@oliphant-plugins
Contributions are welcome! Feel free to submit issues or pull requests.
MIT