Build Insights Logger Marketplace
Preserve non-trivial coding discoveries and decisions in .claude/insights and fold durable lessons into CLAUDE.md during complex builds.
Overview
build-insights-logger-marketplace is a plugin marketplace for the Build phase that installs a skill to log coding insights to .claude/insights and sync key learnings into CLAUDE.md.
What is this marketplace?
- build-insights-logger skill (MIT v1.0.0) for session-time insight capture
- Writes meaningful learnings to .claude/insights/ during non-trivial work
- Covers edge cases, design decisions, patterns, and implementation detail
- Designed to promote durable entries into CLAUDE.md for agent continuity
- Keywords span insights, logging, documentation, and institutional knowledge
- 1 plugin (build-insights-logger v1.0.0)
- MIT licensed skill from nathanonn/claude-skill-build-insights-logger
Community signal: 9 GitHub stars.
What problem does it solve?
Complex solo builds leak context between sessions because important discoveries live only in chat history instead of durable project docs.
Who is it for?
Indie developers on long-running Claude Code projects who hit recurring edge cases and want repo-local institutional knowledge without a separate wiki.
Skip if: Tiny throwaway repos or builders who already enforce full ADRs and a team-wide knowledge base with strict review gates.
What do I get? / Deliverables
You get a structured insights log and a clearer CLAUDE.md so agents and future you reuse decisions instead of rediscovering the same pitfalls.
- Timestamped insight files under .claude/insights/
- Curated durable guidance reflected in CLAUDE.md
- Recorded patterns and edge-case notes for complex features
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
The bundled skill activates while you implement hard features—the canonical shelf is Build/docs because that is where institutional knowledge first needs structured capture. Logging edge cases, patterns, and design rationale is documentation and knowledge management, not runtime monitoring or distribution work.
How it compares
Session insight-capture skill marketplace, not an MCP server or production error monitoring tool.
Common Questions / FAQ
Who is Build Insights Logger Marketplace for?
It is for Claude Code users building complex code who need to preserve non-trivial learnings for themselves and their agent across sessions.
When should I use Build Insights Logger Marketplace?
Enable it when implementation work surfaces decisions and edge cases worth keeping, especially before handing the repo to another agent thread or future sprint.
How do I add Build Insights Logger Marketplace to my agent?
Add the marketplace plugin build-insights-logger from Nathan Onn’s repo, activate the skill during coding sessions, and write insights under .claude/insights then promote essentials to CLAUDE.md.