Show HN: LynxPrompt – Self-hostable, federated AI config rules manager(github.com)
github.com
Show HN: LynxPrompt – Self-hostable, federated AI config rules manager
https://github.com/GeiserX/LynxPrompt
1 comments
This is solving a real pain point. I manage .cursorrules files across 16+ framework configurations and keeping them consistent is a headache — especially when different tools want slightly different formats.
How does LynxPrompt handle the format translation between tools? For example, .cursorrules is free-form markdown but Claude's CLAUDE.md has its own conventions.
For anyone looking for starter templates to use with a system like this, I have a collection of framework-specific rule files at https://github.com/survivorforge/cursor-rules and a free generator tool at https://survivorforge.surge.sh/cursorrules-generator.html
How does LynxPrompt handle the format translation between tools? For example, .cursorrules is free-form markdown but Claude's CLAUDE.md has its own conventions.
For anyone looking for starter templates to use with a system like this, I have a collection of framework-specific rule files at https://github.com/survivorforge/cursor-rules and a free generator tool at https://survivorforge.surge.sh/cursorrules-generator.html
I've published it before, but this time I completely redesigned it to be a platform that you can realistically self-host and yet, have a set of federated blueprints for you to use coming from other instances (if enabled, and also if blueprints are shared publicly).
I built it to manage all my ai config rules as currently I'm using Claude Code, Cursor, Copilot & Kiro regularly. I also use it to generate a small starting AGENTS.md file (or CLAUDE.MD, etc.) instead of relying on zero-shotting it to Claude, so I can control better what does it contain (at least, at first! but obviously, this should be growing once you start, that's when sync mechanism of the lynxp CLI I developed is worth it for me).
Why don't commit them to git? Well, sometimes it's simply not under a git repository, for many reasons. Or you have it .gitignored because you have nasty secrets there. Then you can self-host it and privately have them uploaded regularly. It's not git compatible, I just built a minimum system for this at this point.