Feature Description
It would be great if lola could install assistant configuration directories — like .claude/ for Claude Code — from the plugin's content into the target project, alongside skills, commands, and agents.
Problem or Use Case
Some plugins need to pre-configure the assistant when installed — for example, pre-approving specific tools or setting defaults so users aren't interrupted with prompts every time the plugin runs. Right now there's no native way to do this, so the workaround is a post-install hook that manually writes and merges files. It works, but it's boilerplate that every plugin author has to reinvent, and lola doesn't track those changes — so lola uninstall doesn't clean them up.
Proposed Solution
If a plugin's content directory includes a .claude/ folder (or .cursor/, .gemini/ etc. for other targets), lola could copy or merge it into the target project's equivalent directory during install, and remove it on uninstall. This keeps the approach consistent with how lola already handles skills and agents — just extended to config directories.
Alternatives Considered
Post-install hooks as a workaround — but they're manual, not tracked, and not cleaned up on uninstall.
Category
Installation/Update workflow
Complexity Estimate
Medium
Feature Description
It would be great if lola could install assistant configuration directories — like
.claude/for Claude Code — from the plugin's content into the target project, alongside skills, commands, and agents.Problem or Use Case
Some plugins need to pre-configure the assistant when installed — for example, pre-approving specific tools or setting defaults so users aren't interrupted with prompts every time the plugin runs. Right now there's no native way to do this, so the workaround is a post-install hook that manually writes and merges files. It works, but it's boilerplate that every plugin author has to reinvent, and lola doesn't track those changes — so
lola uninstalldoesn't clean them up.Proposed Solution
If a plugin's content directory includes a
.claude/folder (or.cursor/,.gemini/etc. for other targets), lola could copy or merge it into the target project's equivalent directory during install, and remove it on uninstall. This keeps the approach consistent with how lola already handles skills and agents — just extended to config directories.Alternatives Considered
Post-install hooks as a workaround — but they're manual, not tracked, and not cleaned up on uninstall.
Category
Installation/Update workflow
Complexity Estimate
Medium