Code Decisions: Open Source Claude Plugin Captures Technical Decisions
Code Decisions is a Claude Code plugin that addresses the problem of Claude forgetting technical decisions between sessions, whether working solo with parallel sessions or collaborating with a team. The plugin captures decisions made during normal conversation and persists them for future reference.
How It Works
When you make a technical decision in conversation with Claude—for example, saying "use raw SQL for dashboard queries" or "use Redis, Sidekiq is too heavy"—the plugin detects decision language and writes a markdown file to .claude/decisions/. Each file includes an affects field pointing to the files it governs. When anyone on the team (including future-you) edits those files, the decision automatically surfaces in their Claude session.
Key Features
- Zero configuration, zero dependencies (stdlib-only Python)
- Always advisory—provides nudges but never blocks
- Markdown files serve as the source of truth (not a database)
- Decisions commit to git and travel with the repository
- Decisions appear in pull requests
Manual Control Commands
The plugin includes a /decision command for manual control:
/decision authsearches past decisions about authentication/decision --tagsbrowses decisions by topic/decision undoreverts the last captured decision
The plugin is MIT licensed and available on GitHub at https://github.com/zimalabs/code-decisions.
📖 Read the full source: r/ClaudeAI
👀 See Also
MCP + Skills Framework: Guiding AI Agents for Efficient Data Science Workflows
A practical approach using MCP server + skills framework to constrain Claude/GPT agents toward platform-aware, efficient data science workflows — avoiding client-heavy code and unnecessary data movement.
Claude Code documentation includes excessive React components inflating token counts
Analysis of Claude Code's LLM documentation reveals that MDX files contain massive inlined React components, with context-window.md using 18,501 tokens but only 551 tokens of actual documentation content.
Benchmark: MLX vs Ollama Running Qwen3-Coder-Next 8-Bit on M5 Max MacBook Pro
A benchmark comparing MLX and Ollama backends running Qwen3-Coder-Next 8-bit quantization on an M5 Max MacBook Pro with 128GB RAM shows MLX achieving approximately 72 tokens per second, roughly double Ollama's throughput across various coding tasks.
AI Subroutines: Deterministic Browser Automation with Zero Token Cost
rtrvr.ai's AI Subroutines let you record browser tasks once as callable tools that replay inside the webpage context with auth propagated for free, eliminating LLM inference costs and non-determinism for repetitive tasks.