Stop maintaining `.cursorrules` in every repository separately. Keep one source of truth in forgein, generate the rules block, and paste it wherever Cursor needs it.
Free adapter · No extension needed·Works with all Cursor plans
.cursorrules
# .cursorrules# 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 Cursor
One .cursorrules 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 .cursorrules file per repo
Cursor reads `.cursorrules` from the repo root to understand how the AI should behave. If you work in five repos, you have five copies — and they diverge the moment you update your conventions.
02 — DRIFT
Convention updates don't propagate
You rename a module, adopt a new hook pattern, or change how you handle errors. The file in one repo gets updated. The others stay stale. Cursor in those repos keeps giving you yesterday's suggestions.
03 — SYNC
One edit. Every repo updated.
Keep your Cursor rules in forgein. Edit once — your stack, naming conventions, current sprint focus. Regenerate and paste. Under a minute from change to every repo updated.
Setup
Four steps. One file to maintain.
No extensions, no settings to configure. Just a generated file that Cursor already knows how to read.
01
Create account
Sign up at app.forgein.ai. Free for individual developers. Work context + Cursor adapter included.
02
Build your context
Add memory files for your stack: language preferences, naming conventions, import order, team decisions. Edit in browser or via CLI.
03
Get Cursor rules
Open Contexts in the dashboard. Click "Get Cursor Rules". One block ready to paste — scoped to what Cursor actually uses.
04
Write to your repo
Paste into .cursorrules at your repo root. Cursor picks it up immediately — no restart, no extension reload needed.
What forgein generates
The Cursor adapter outputs a single rules block formatted for `.cursorrules`. Cursor reads it from the repo root to understand how the AI should behave — it applies to every file Cursor 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
⬡
Cursor also supports MCP
Cursor can pull context live from the forgein MCP server — no file writes, no paste step. If you prefer context that updates without regenerating .cursorrules, connect via MCP instead.