The "feed Windsurf your library docs" workflow

Open the documentation URL for whatever library Cascade is hallucinating against (https://library.dev/docs/api, a niche framework's migration guide, a private SDK reference). Open URL to Markdown, paste the URL, click Convert, download the .md file. Save it as docs/library-name.md at the root of the repo Windsurf has open. Within seconds Windsurf's indexer picks it up and Cascade can quote from it directly.

The unlock is one line in .windsurfrules: "When using library X, consult docs/library-name.md before suggesting code." Cascade then opens the relevant section autonomously before generating, and the resulting code uses real API signatures instead of training-data approximations.

Why URLs (not PDFs, not pasted prompts)

Library docs live on the web — versioned, searchable, regularly updated. Pasting docs into the Cascade chat works for one task, then evaporates with the conversation. Converting URLs to workspace Markdown gives you a snapshot you control: re-convert when the docs update, version-control the result with the code that depends on it, share with your team via the repo. Have PDFs to feed into Windsurf too? See PDF to Markdown for Cursor — same workflow, swap the converter.