Comment by silcoon
5 hours ago
Thanks for your reply. Mine wasn't a critique but a genuine curiosity. I was interested to see what where the base instructions used for a rust project.
> The .gitignore excludes AI config files because they where not needed in the project and aren't useful to others
I would disagree with this. Since it's an open-source project it would be beneficial to everyone, especially to future contributors, to agree in good code practices and conventions when using LLMs. I would say they're really useful.
You raise a fair point, and I've thought about this a bit since you mentioned it. What those files actually are:
The files you noticed (AGENTS.md, GEMINI.md, CLAUDE.md, etc.) are auto-generated scaffolding from Task Master AI, a task management tool I use. They contain MCP (Model Context Protocol) configuration for various AI coding assistants — essentially boilerplate instructions for how different AI tools should connect to the task system. They're not really "coding conventions" so much as tool-specific wiring.
That said, you're right that it would be useful to share the actual conventions and rules I use, especially for an AI-generated project.
What I'd be happy to share:
My Cursor system prompt — I have a general coding principles prompt I use across projects. It's not Ferrite-specific but covers code style, architecture preferences, etc. Happy to share this.
Project-specific rules — I do have .cursor/rules/ files with Task Master workflow conventions. These could be included if contributors want to use similar AI-assisted workflows.
The actual workflow — How I structure tasks, iterate on implementations, and the back-and-forth with AI. This might be more useful than config files.
Why I excluded them initially: Honestly, most of those files are boilerplate MCP configs that would only matter if someone wanted to use the exact same tooling stack (Cursor + Task Master + specific MCP servers). I wasn't sure that would be useful to most contributors, and I didn't want to clutter the repo with tool-specific noise. But I take your point about setting conventions for AI-assisted contributions.
Let me know if there's interest, and I can:
Add a CONTRIBUTING_AI.md or similar with the actual conventions and workflow
Share my system prompt in the docs
Un-ignore some of the rules files if they'd help
What would be most useful to you?