A modern commonplace book that auto-gardens into an MCP-connected knowledge base. Capture idea fragments from any MCP client or via Telegram — the system structures, embeds, and links them into a searchable knowledge graph you own. Your memory, your database, any agent.
Command Claude Code
Extract project-relevant insights from user-provided input. The user brings material — a session write-up, product feedback, a captured fragment, an error log, a design sketch, a conversation transcript — and you turn it into actionable artifacts: GitHub issues, issue comments, doc updates, ADRs, or memory entries.
Command Claude Code
Analyze recent real-world captures against the product's design philosophy. Surface gaps between what the system promises and what it delivers, then recommend concrete improvements.
Command Claude Code
Search an Obsidian vault for notes related to a topic, decompose them into idea fragments re-voiced in the user's natural capture style, and interactively capture approved fragments into ContemPlace.
Command Claude Code
Search the ContemPlace corpus for captured thoughts about ContemPlace itself, PKM, and related topics. Cross-reference with open GitHub issues. Surface ideas worth acting on — as new issues, comments on existing ones, or notes that a prior idea has evolved.
Command Claude Code
You are the orchestrator agent. You do not write code or investigate issues yourself. You manage parallel Claude sessions running in separate cmux workspaces, each with its own git worktree for isolation.
Command Claude Code
Turn raw experience reports from using the product into agent-ready GitHub issues at the right maturity. The user arrives wearing the user hat — "here's what happened when I used the thing" — and shifts to the product hat to make decisions about maturity, framing, and priority.
Command Claude Code
Session-closing ritual. Review what happened, find what could be better, improve the system that produces the work — not just the work itself.
Command Claude Code
Execute the full planning-before-implementation workflow for a GitHub issue. The user provides an issue number or description — you handle the rest.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: