Skill: Windsurf.

§ 1 Where to paste

<your-project>/.windsurfrules

If you want this rule applied everywhere (not per project), use Windsurf's Settings → Set Global AI Rules and paste the same snippet there. Project-level rules override global ones, so the two coexist fine.

§ 2 The snippet

# FolderMD — long-form markdown belongs in a folder, not the chat

When you produce long-form markdown — roughly 1500+ characters, or anything
with multiple headings, tables, or sections that the user will want to
*read* rather than skim past — route it through FolderMD instead of
emitting it inline. The user works in a calm reading pane on their Mac,
not the chat panel.

The CLI helper is at `~/.local/bin/foldermd` (already on PATH after
installation). Pipe markdown into it with a short slug title and the
`--here` flag for project work:

```bash
cat <<'EOF' | foldermd --here --title "auth-refactor-plan"
# Auth refactor plan
...
EOF
```

Without `--here`, the file goes to the global inbox at
`~/Library/Application Support/foldermd/inbox/`.

After routing, send a brief confirmation in chat — one or two sentences —
and DO NOT repeat the document body inline. Example:

  "Dropped <title> into FolderMD — appears in your sidebar within a
   second. Short version: <one-line takeaway>."

## Route TO FolderMD
- Long explanations / strategy docs / how-tos
- Analysis reports / audit summaries
- Anything with more than two headings or a table
- Documents the user might want to keep, edit, share, or commit

## Reply inline
- Short answers / single-paragraph replies
- Direct factual answers
- Tool output you're just relaying
- Status updates mid-task

§ 3 Confirm it took

Reload the Windsurf workspace, then ask Cascade for a long-form output. The reply should be a short confirmation rather than a wall of markdown; the actual document should appear in FolderMD's sidebar within a second.

See the Claude Code page for the same rule with tuning options.

Windsurf renamed the rules file again? Message me on X or LinkedIn.