Stop maintaining `.windsurfrules` in every repository separately. Keep one source of truth in forgein, generate the rules block, and paste it wherever Windsurf's Cascade needs it.
Free adapter · No plugin needed·Works with all Windsurf plans
.windsurfrules
# .windsurfrules# forgein: work context | 4 files | 2026-07-10## StackNext.js 15 (app router), Postgres,Drizzle ORM, Express. TypeScript strict.## Conventions- Conventional commits (feat/fix/chore)- Drizzle eq() / and() — never raw SQL- Named exports only, no default exports- No comments on self-explanatory code## Sprint 14 (ends Jul 18)Billing + org members. Auth freeze in effect.Do not suggest auth changes this sprint.# Managed by forgein · app.forgein.ai
Why forgein for Windsurf
One .windsurfrules file per repo is the wrong granularity.
Your conventions span every repo. Maintaining them across N separate files means they drift the moment you change anything.
01 — FILES
One .windsurfrules file per repo
Windsurf Cascade reads `.windsurfrules` from the repo root to understand project conventions. If you work across repos, you maintain separate files that drift the moment your actual practices change.
02 — CASCADE
Cascade only knows what you tell it
Windsurf's Cascade AI is powerful — but only if it understands your codebase conventions. Without rules, it generates technically correct code that doesn't match your team's style, naming patterns, or current sprint constraints.
03 — SYNC
One edit. Every repo updated.
Keep your Cascade rules in forgein. Edit once — your stack, conventions, sprint context. Regenerate and paste into any repo in under a minute.
Setup
Four steps. One file to maintain.
No extensions, no settings to configure. Just a generated file that Windsurf Cascade already knows how to read.
01
Create account
Sign up at app.forgein.ai. Free for individual developers. Work context + Windsurf adapter included.
02
Build your context
Add memory files for your stack: framework preferences, naming conventions, import order, team decisions. Edit in browser or via CLI.
03
Get Windsurf rules
Open Contexts in the dashboard. Click "Get Windsurf Rules". One block ready to paste — exactly the format Cascade expects.
04
Write to your repo
Paste into .windsurfrules at your repo root. Cascade picks it up immediately — no restart, no plugin required.
What forgein generates
The Windsurf adapter outputs a single rules block formatted for `.windsurfrules`. Cascade reads it from the repo root to understand how it should behave — it applies to every file Cascade touches in that repo.
—Stack section: your tech, versions, key libraries
## StackNext.js 15, Postgres, Drizzle, Express.TypeScript strict. pnpm workspaces.## Code styleNamed exports. No default exports.Conventional commits. No inline commentson self-explanatory code.## Current sprintBilling + org members. Auth freeze —do not suggest auth changes until Jul 18.Managed by forgein · app.forgein.ai
Multi-repo workflow
Update once. Paste into N repos.
If you work across multiple repositories, forgein keeps the rules consistent. Change a convention once — regenerate, paste, done.
#RepoLast updatedStatus
1forgein-platform2 min ago✓ current
2forgein-api2 min ago✓ current
3forgein-docs2 min ago✓ current
4internal-tools3 days ago⚠ stale
⬡
Windsurf also supports MCP
Cascade can pull context live from the forgein MCP server — no file writes, no paste step. If you prefer context that updates automatically without regenerating .windsurfrules, connect via MCP instead.