Use case
Engineering team members onboarding to or modifying an existing codebase encode team conventions, build scripts and framework rules into in-repo custom instructions, agent skills and MCP configuration so Copilot generates cross-file changes that follow them, then review and merge.
The old way is documenting conventions in wikis or verbal handover, pasting context manually into each conversation, or simply writing the change by hand.
Every new task requires re-explaining the same standards, scripts and workflows; otherwise generated changes break existing project patterns and need manual rework, while team conventions stay scattered across docs, verbal handover and personal habits.
xOcto's call
Demand is evidenced
The trend is that coding assistants now compete on how repository context is captured rather than raw model ability; the opening is packaging a legacy project's conventions, scripts and review rules into reusable configuration, sold per project to teams inheriting old systems.
Reason to use it
Why users would choose it
Compared with pasting context each time, fixing conventions and scripts into repository configuration makes the assistant apply them automatically when generating changes, removing the step of re-explaining and correcting non-conforming code; this is an inference that teams inheriting legacy projects with scattered conventions would choose it.
Where the easy answer breaks down
The tension worth following
An English validation note will follow from the public evidence.
If this is your job
Investigate further. Compared with pasting context each time, fixing conventions and scripts into repository configuration makes the assistant apply them automatically when generating changes, removing the step of re-explaining and correcting non-conforming code; this is an inference that teams inheriting legacy projects with scattered conventions would choose it.
Entry and what to borrow
The trend is that coding assistants now compete on how repository context is captured rather than raw model ability; the opening is packaging a legacy project's conventions, scripts and review rules into reusable configuration, sold per project to teams inheriting old systems.