By landonia
Logs every Claude Code prompt and response to a local JSONL history file with timestamps and session IDs, so you can trace which input led to which output.
Personal Claude Code plugin marketplace.
In Claude Code, run:
/plugin marketplace add landonia/claude-plugins
Logs every Claude Code prompt and response to ~/.claude/interaction_history.jsonl.
Install:
/plugin install interaction-logger@landonia-plugins
Injects Java coding patterns, conventions, and best practices (naming, design patterns, package structure, testing, logging, etc.) into the agent context whenever Java code is being written or reviewed.
Install:
/plugin install java-guidelines@landonia-plugins
Based on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimInjects Java coding patterns, conventions, and best practices into the agent context whenever Java code is being written or reviewed.
npx claudepluginhub landonia/claude-plugins --plugin interaction-loggerLogs all Claude Code hook invocations to a JSON file with automatic rotation
Auto-captures Claude Code sessions as narrative worklogs and detects user steering patterns
Auto-capture development command output and search/analyze with Claude Code
Continuous memory for Claude Code. Extracts, summarizes, and compresses conversations into tiered daily logs. Claude remembers what you did yesterday.
Persistent local memory for Claude Code. Every tool call, every file edit, every thinking block from every session — stored verbatim on your machine. Semantic recall in ~126ms with zero API calls.
Ultra-compressed communication mode. Cuts ~75% of tokens while keeping full technical accuracy by speaking like a caveman.