Stop maintaining `.github/copilot-instructions.md` in every repository separately. Keep one source of truth in forgein, generate the instruction block, and paste it wherever Copilot needs it.
Free adapter · No extension needed·Works with all Copilot tiers
.github/copilot-instructions.md
<!-- forgein: work context | 4 files | 2026-07-05 -->## 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.
Why forgein for Copilot
One instruction 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 — INSTRUCTIONS
Copilot forgets everything between repos
GitHub Copilot's workspace instructions live in `.github/copilot-instructions.md` — one file per repo, written once, never kept current. Across ten repos, you have ten stale, inconsistent instruction files that diverge the moment your actual practices change.
02 — CONTEXT
Convention drift is a real cost
Your team settled on a new error-handling pattern three sprints ago. Half the repos know, half don't. Copilot suggestions in the old repos follow the old pattern. forgein propagates changes to every repo at once — one source of truth, not N.
03 — SYNC
Manage once. Deploy everywhere.
Keep your Copilot instructions in forgein. Edit them in one place — your stack conventions, naming rules, import order preferences, context-specific constraints. Push to as many repos as you work in. Any change propagates in under a minute.
Setup
Four steps. One file to maintain.
No extensions, no VS Code settings to configure. Just a generated file that GitHub Copilot already knows how to read.
01
Create account
Sign up at app.forgein.ai. Free forever for individual use. Work context + Copilot adapter included.
02
Build your context
Add memory files for your stack: TypeScript preferences, naming conventions, import order, team decisions. Edit in browser or sync via CLI.
03
Get Copilot instructions
Open Contexts in the dashboard. Click "Get Copilot Instructions". One block generated, scoped to your Copilot workspace instruction limit.
04
Write to your repo
Paste into .github/copilot-instructions.md at your repo root. Copilot picks it up immediately — no restart, no plugin required.
What forgein generates
The Copilot adapter outputs a single markdown block formatted for `.github/copilot-instructions.md`. Copilot reads it as workspace-level context — it applies to every file Copilot touches in that repo.
—Stack section: your tech, versions, key libraries