Namishsaxena Lore
namishsaxena-lore is a Claude Code plugin for the Build phase that gives agents scoped, queryable project knowledge instead of oversized static context files.
by namishsaxena · github.com/namishsaxena/lore
Give Claude Code scoped, queryable project knowledge instead of dumping entire context files into every session.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install namishsaxena-lore@namishsaxena/loreBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:namishsaxena/lore") and the paste-ready config with skillselion.get_install_config("plugin:namishsaxena/lore").
What it does
namishsaxena-lore is a Claude Code plugin that implements Lore as a knowledge memory layer for AI agents. Solo builders drowning in AGENTS.md, copied architecture notes, and oversized CLAUDE.md files can store facts in scoped entries and let the agent query what matches the open files and active task. The bundle advertises MCP support, native tooling, and selective retrieval so integration work stays in the build phase rather than becoming a manual paste ritual each session. It targets indie developers who run Claude Code daily on real repos and need durable, structured memory without maintaining a second wiki. Install it when context rot slows you down or when multiple features share overlapping but not identical background. It is not a full vector database product; it is an opinionated memory plugin meant to replace bloated static context with something the agent can pull on demand. Expect setup around database or storage configuration per the upstream repo, then query-driven use as you iterate features.
Highlights
- Scoped knowledge entries tied to files and tasks instead of monolithic context dumps
- Queryable retrieval returns only relevant lore for the current work
- MCP and native Claude integration for agent-side memory access
- Selective context loading to cut noise and token bloat
- Documentation and integration hooks packaged as a single Claude Code plugin
Why builders use it
Every session you re-feed the same huge context files and still miss the one rule that matters for the file you are editing.
After you register Lore, the agent pulls only task-relevant knowledge entries so sessions stay focused and context stays maintainable.
At a glance
- Type - Plugin in AI Agents.
- Adoption - 0 installs, 3 stars, 0 votes.
FAQ
Who is namishsaxena-lore for?
Indie and solo developers using Claude Code who need structured, queryable repo knowledge instead of pasting large context files into every chat.
When should I use namishsaxena-lore?
Use it during Build when you are standardizing agent tooling, especially once static CLAUDE.md or AGENTS.md files grow unwieldy across modules and tasks.
How do I add namishsaxena-lore to my agent?
Add the namishsaxena/lore Claude Code plugin from the repo marketplace entry, complete any Lore database or MCP setup in the upstream docs, then query lore from Claude during coding tasks.
Comments
Share how you use namishsaxena-lore, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.