Cursor3 min read

Using Lazy Flow with Cursor

Cursor's power is edit-speed; its weakness is context. A Lazy Flow workspace fixes the weakness: an AGENTS.md at the repo root carries your conventions into every edit.

Setup

Three steps:

  • Extract the workspace into your repo root (or drop the folders into an existing repo).
  • Open the folder in Cursor — it picks up AGENTS.md from the root automatically.
  • Pin AI Instructions/ in your context so chat sessions see the full navigation map, not just the rules file.

What the instruction file does

The workspace's AGENTS.md tells Cursor how this project is organised, which files are generated (never touch), which docs are authoritative, and what conventions the codebase follows. It turns Tab-completion from plausible to correct.

For rules that should only apply to certain files, Cursor's own project rules live in .cursor/rules/ as .mdc files, where frontmatter can scope a rule to a glob or set it to apply always. AGENTS.md is the plain-Markdown option — no frontmatter, and every other agent reads it too.

If you already have a .cursorrules file at the root it still works, but Cursor's documentation calls it legacy and slated for deprecation. The migration is to move its contents into a rule under .cursor/rules/ set to always apply, then delete the original.

First task

Prove the context is live before real work:

TRY THIS PROMPT
Review the Product folder and propose the next roadmap milestone, citing the documents you used.
NEXT UPWorkspace file types