No comments yet.
I built it because I got tired of rewriting the same “how I want the AI to code” rules every time I started a new repo. LynxPrompt generates and manages AI coding rules/config files in a portable way across IDEs and other AI-enabled coding tools. It also lets you save, share & discover blueprints (also called templates/AI configs/prompts — the industry has many names for these) made by other devs.
Honestly, I know: yet another AI tool. But my problem was very specific: keeping AI coding rules consistent across projects and tools without relying too much on “memory” features. LynxPrompt focuses on bootstrapping a repo config quickly and making those rules portable and versionable.
What it does:
- Wizard generator: bootstrap an AI config for an existing repo or a new project in minutes
- Portable rules: keep your AI coding preferences consistent across coding sessions
- Blueprints: publish/share (and optionally sell) your team or personal setup
One feature I like a lot is having the API enabled in LynxPrompt, so your AI of choice can self-update its coding rules and save/version them in the platform (also, if you configure it that way in the wizard).
I’m posting to get feedback (and ideally a few early users): Does the “portable AI coding rules” idea make sense? or what would you need to trust shared/paid blueprints (previews, diffs, versioning, ratings, etc.)?... What is your real pain here?
Links below. Thank you and "happy" vibe-coding — at least, we have LynxPrompt ;).
- First blog post: https://lynxprompt.com/blog/thrilled-to-welcome-you
- Docs: https://lynxprompt.com/docs
- Ideas/bugs/support (please, show some love): https://lynxprompt.com/support
- Wizard (requires sign-in—sorry, I decided to do this to prevent abuse): https://lynxprompt.com/wizard
