Cursor migrates from .cursorrules to .cursor/rules/

Cursor v0.48+ now reads project rules from .cursor/rules/*.md files instead of the root .cursorrules file. The old format is still supported but deprecated. Each .md file in the rules directory acts as a scoped rule set with optional glob patterns in YAML frontmatter.

Run `markdowning migrate --from cursorrules --to cursor-rules-dir` to convert automatically, or manually create .cursor/rules/ directory and move your rules content into individual .md files.

Claude Code adds @-import support in CLAUDE.md

CLAUDE.md files now support `@filename.md` directives to include content from other files. Imports are resolved relative to the file containing the directive and are expanded at parse time. This enables modular project instructions that can be composed from shared snippets across monorepo packages.

agentconfig.ing CLI v2.4.0 released

New CLI release adds `markdowning diff` command for comparing config file versions, `markdowning lint` for validating config files against known schemas, and improved `markdowning migrate` with dry-run support. Also fixes a bug where YAML frontmatter in .mdc files was not parsed correctly.

GitHub Copilot adds copilot-instructions.md support

GitHub Copilot now reads project-level instructions from `.github/copilot-instructions.md`. The file uses standard Markdown and is scoped to the repository. Instructions are included as system context for all Copilot interactions within the project, including chat, completions, and code reviews.

Windsurf .windsurfrules format fully documented

The Windsurf rules file format has been reverse-engineered and documented with full coverage of supported directives, section structure, and interaction with workspace settings. The file uses Markdown with optional YAML frontmatter for metadata and supports cascading rules from global to project scope.

Cline memory bank pattern gains community traction

The Cline memory bank pattern — a structured set of Markdown files in `.cline/` that persist context across sessions — has been widely adopted by the community. The pattern uses productContext.md, techContext.md, activeContext.md, and progress.md files to maintain project state without relying on conversation history.