Cursor

This guide covers using Flow with Cursor, the AI-native code editor. You will learn:

• How to install the Flow harness for Cursor
• Where Flow writes its files in a Cursor project
• How to invoke Flow's skills

Overview

Flow installs into Cursor as a project rule and a set of skills. The harness docs index becomes an always-applied Cursor rule, and every Flow skill becomes a skill under .cursor/skills/.

This page covers only the Cursor specifics. If you have not added the Flow package to your project yet, start with the Installation guide.

Installing for Cursor

Run the harness installer and select Cursor at the agent prompt:

node ace flow:install

Flow detects Cursor automatically when a .cursor directory is present, so it is usually pre-selected. To target it directly and skip the agent prompt, pass the --agent flag:

node ace flow:install --agent=cursor

Where Flow writes its files

Installing for Cursor adds the following to your project:

• .flow/docs/ holds the harness docs. This location is the same for every agent.
• .cursor/rules/adonisjs-harness.mdc is the harness rule. It carries the docs index and project facts, and is created with alwaysApply: true so Cursor keeps the harness index in context for every request.
• .cursor/skills/ gains one directory per installed skill, each named flow-<skill>. The brief skill, for example, lands at .cursor/skills/flow-brief/SKILL.md, alongside any reference files that skill ships.

The .flow/docs/ directory and the flow- skill directories are added to .gitignore, because the harness is regenerated by re-running the installer.

Invoking skills

Flow's skills are invoked as slash commands. The skill directory name is also the command name, so the skill at .cursor/skills/flow-brief/ is invoked as /flow-brief:

/flow-brief checkout-redesign

Every spec-driven workflow skill follows the same /flow-<name> pattern: /flow-blueprint, /flow-assert, /flow-build, /flow-sync, /flow-archive. A skill name with a dot uses a dash in the command, so the build.tdd skill is /flow-build-tdd.

Invoking a skill explicitly is the intended way to drive the spec-driven workflow. It keeps you in control of when each step runs and lets you review the result before advancing.

Next steps

• Spec-driven development explains the workflow these skills implement.
• Knowledge base describes the harness docs Cursor reads from.