# Your AI Coding Rules Should Not Live in Cursor Rules

DevFeed: [Your AI Coding Rules Should Not Live in Cursor Rules](<https://devfeed.tech/articles/your-ai-coding-rules-should-not-live-in-cursor-rules-25170.md>)

Original publisher: [Read original article](<https://www.ivanmorgillo.com/2026/05/29/ai-coding-rules-should-not-live-in-cursor-rules/>)

Author: Ivan Morgillo

Published: 2026-05-29T16:42:19Z

Content type: opinion

Language: en

Sources: [Ivan Morgillo](<https://devfeed.tech/sources/ivan-morgillo.md>)

Topics: [Rails](<https://devfeed.tech/topics/rails.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [Flutter](<https://devfeed.tech/topics/flutter.md>), [Markdown](<https://devfeed.tech/topics/markdown.md>), [coding](<https://devfeed.tech/topics/coding.md>)

Tags: [ai-coding](<https://devfeed.tech/tags/ai-coding.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [maintenance](<https://devfeed.tech/tags/maintenance.md>), [markdown](<https://devfeed.tech/tags/markdown.md>), [rails](<https://devfeed.tech/tags/rails.md>)

## AI overview

The author argues that AI coding instructions should not be maintained separately in editor-specific files. Instead, shared development standards for Rails and Flutter projects should live in versioned Markdown files, while tool-specific files act as adapters and local project rules handle exceptions.

## Source excerpt

I stopped treating editor-specific AI rule files as the source of truth and moved my Rails and Flutter standards into plain Markdown that Cursor, Claude, Codex, Copilot, and future agents can all discover.