ProductFeaturesWork

Coding instructions

Share your project's coding rules, connect your coding tool, and keep the team working from the same instructions.

Coding instructions tell your coding agent how your team works: which commands to run, how to structure changes, and which project rules to follow. Keep files such as AGENTS.md, CLAUDE.md, skills, rules, and supporting scripts together, then connect your tool to the project in Fabric.

Start with a short entry file that names your team's coding conventions, the actual build and test commands, and any changes that need review. Put longer guidance in supporting files. Use the filenames and folder structure your coding tool expects.

Open your project's instructions

Choose Projects in the sidebar, open your project, and select Coding Instructions.

If your team has already connected a repository or published an upload, select a file in the tree to read it. For repository instructions, the branch and commit tell you which version you are reading. Commits opens the repository history; Download lets you take a copy of the instructions.

The Coding Instructions tab for an example project, showing the main branch, a file tree with AGENTS.md selected, the instruction content, and the Commits, Download, and More controls.

The illustrations use example project and repository data. Setup commands in your own dialog are specific to your project and Fabric address.

See what changed since your last visit

When you come back to the tab after something changed, the Since your last visit panel shows what happened since the time it names in Last seen:

  • each new version, with who published it, or the branch and commit it was synced from;
  • the files that differ between the version you last saw and the current one, marked Added, Changed or Removed. The first 10 are listed, followed by how many more there are;
  • new lessons, which are files added under a Lessons/ folder;
  • proposals that were approved or rejected, and by whom.

Choose Mark all as seen to clear the panel. On your first visit, or when nothing is new, Fabric records the visit without showing the panel. If the version you last saw is no longer kept, the panel says so instead of listing the changed files.

Add instructions to a project

If you only need to use instructions your team has already set up, skip to Connect your coding tool.

Use a Git repository

Use this option when your team already keeps its instructions in Git.

  1. Connect the repository to your project if it is not connected yet.
  2. In Coding Instructions, choose Sync from repository. To change an existing connection, open More → Settings and choose Change in the repository section.
  3. Choose the repository and branch. Select the folder that contains the instructions, or the whole repository if that is where you keep them, in the file tree. Review any excluded paths.
  4. Choose Save connection. Open a file to check that you selected the right folder and branch.

Ticking a folder in the tree includes everything inside it, including files added to it later. A folder that is partly left out shows a dash. A row you cannot tick says why. Above the tree you can search, choose Show only selected to keep only ticked and left-out rows and the folders that lead to them, or use Collapse all, Select all and Select none. Show only selected works together with search.

The tree is a single stop when you press Tab. Use the arrow keys, Home and End to move, Enter to open or close a folder, and Space to tick or untick a row. Type the start of a name to jump to it.

The files stay in Git. After someone commits or merges changes, use More → Refresh to load the latest branch version. Fabric reports Up to date. or Updated to the new commit.

Upload a folder

Use an upload when you have a folder of instructions to share without connecting its repository.

  1. Choose Upload folder, then Choose folder or Choose files. You can add more files before uploading.
  2. In Review what will be uploaded, check the included files and greyed-out exclusions. A .fabricignore file can exclude files your agents do not need.
  3. Resolve any rejected-file warning. Credential files do not belong in an instruction upload.
  4. Leave Publish as soon as the upload passes checks selected for the usual setup, then choose Upload with the displayed file count. Wait until the version is published before asking teammates to use it.

The upload review for an example instruction folder: AGENTS.md, a skill, and a test script are included, tasks/session.log is excluded by a default rule, and Publish as soon as the upload passes checks is selected above Upload 3 files.

If your browser cannot choose a folder, use Choose files or try a browser that supports folder selection, such as Chrome or Edge.

Start from your organization's template

An organization can keep one project's coding instructions as a starting point for its other projects. An organization admin or owner chooses that project in Settings → General → Coding instructions template. The list offers only projects whose instructions are uploaded to Fabric. Projects with published instructions come first, and a project that has nothing published yet is marked. The template project's own Coding Instructions tab is where the template is changed, so uploads, checks, versions and history work as they do for any project.

In another project that uploads its instructions, choose Start from the organization template in an empty Coding Instructions tab, or More → Add files from the organization template once the project has files. You need permission to upload to the project; you do not need access to the template project.

  • Fabric creates a new version of your project with the template's published files, checks it like an upload, and publishes it when the checks pass.
  • Your project's own files always win. Only files your project does not have yet are added, and a file that would clash with one of yours is left out.
  • The template's .fabricignore is not copied. Your project's own ignore rules decide what is left out, and credential files are never copied.
  • When it finishes, Fabric lists how many files were added and each file it left out, with the reason.
  • Later changes to the template are not copied automatically. Choose the action again to add files the template has gained since.

Projects whose instructions come from a Git repository are not offered the template; change their files in the repository.

Use separate instructions for different repositories

When code repositories need different rules, for example a mobile app and a web service, split the project's instructions into instruction sets. Open Instruction sets on the Coding Instructions tab, choose New set, name it, and choose the code repositories it applies to. A repository can be in more than one set.

Each set is a folder in your project's instructions: the files of a set named Mobile apps live in instructions/mobile-apps/, laid out the same way as the instructions at the root. The project's existing instructions become the default set: everything outside the other sets' folders. Keeping one instructions source means syncing, proposals, review, and published versions work as before and cover every set at once.

When a project has sets, a code repository gets only the instructions of the sets it is in. A repository in no set gets none, and the Instruction sets panel names it. Renaming a set keeps its folder. Deleting a set removes it from Fabric only; its files stay in your instructions.

When you connect your coding tool inside a code repository, setup picks the set that repository belongs to. If it belongs to several, choose one, or pass --set <folder name> to the setup command. Each set gets its own plugin, which also lists the set's code repositories in REPOSITORIES.md.

Connect your coding tool

Open Connect your agent from the Coding Instructions tab. The dialog is called Connect your coding tool. Choose the tool you actually use; the instructions and setup line change with that choice.

For Claude Code or Codex:

  1. Make sure Node.js 22 or later is installed.
  2. For repository instructions, choose No clone (recommended) if you want the project's plugin to deliver the instructions without a separate instructions checkout. Choose Already cloned if you already work in that repository, or Clone it for me to create a checkout.
  3. Copy the setup line from your own dialog. Run it in your terminal, in the folder indicated by the dialog. Use the whole line; it includes the correct project and Fabric address.
  4. Approve the sign-in in your browser, then return to the terminal and finish the plugin or hook steps shown for your tool.

The Connect your coding tool dialog with Codex selected: No clone is the recommended repository choice, followed by the generated setup line, browser approval, and the Codex plugin setup step.

With No clone, the plugin supplies the instructions when a coding session starts. Claude Code may ask you to approve the plugin installation in your own terminal. Follow the dialog's /mcp and Authenticate steps to let it use Fabric tools. For Codex, the setup installs the project plugin and prints a fallback command if it cannot finish. In both Codex setup modes, trust the folder when asked and run /hooks once to trust the project hook.

The plugin carries project skills, agents, commands, and the Fabric MCP connection. Fabric also delivers the project's rules and session instructions. Supporting files inside a skill travel with it. The generated fabric-instruction-access skill provides a catalog of every instruction path and tells the agent how to read relevant files on demand. Rules beyond automatic delivery limits remain in the plugin as reference files. Standalone scripts, settings, and knowledge files remain cataloged and can be read as text through Fabric MCP when access and file limits allow. See Instructions as a plugin for the supported layout and tool-specific setup.

With a native checkout, the session-start hook can fast-forward a clean matching checkout to the configured branch. It reports when it cannot update the checkout. Keep local edits safe and resolve any reported Git issue before trying again.

If Fabric says one-line setup is unavailable, follow the MCP connection instructions shown in that same dialog. Other tools, including Cursor and VS Code, have their own connection steps there.

Check that your agent can use them

Start a new coding session after setup. Ask:

Read this project's coding instructions before changing code. Summarize the rules and test commands that apply to the change I am about to make.

Check that the answer names the files and rules your team expects. If the tool cannot read them, check its Fabric connection and project access before starting the change.

Save specs and notes to Living Memory

The plugin also includes the fabric-living-memory skill. It tells your agent where to save specs and task notes so Fabric can send them to the project's repository and bring them back as Living Memory for other agents.

Choose where files go

A project administrator sets this up once:

  1. Connect a repository to Living Memory in the project's Context tab.
  2. Open the menu beside Sync now, choose Write folders, then Add a write folder.
  3. Choose a folder inside the repository selection, such as docs/ai. Keep it separate from the coding instructions folder. If you type a path, choose Use to select it.
  4. Keep Pull request for review before files join the branch. Choose Index for AI search if project search and summaries should use the files, or Store only to keep them readable without adding them to search and summaries.
  5. Choose Add write folder. Developers then run the No clone setup in the folder where their coding agent works, or start a new session if that folder is already set up.

The Write folders form for an example repository, with docs/ai selected, Pull request chosen for review, Index for AI search selected, and the Add write folder action.

Project admins and owners can enable Push directly instead, which commits files without review. The write-folder settings guide explains that choice, folder restrictions, and Store only.

Write, review, and resume

Add the intended output path to your team's coding instructions so skills and agents save their work in a configured write folder. For example, if docs/ai is configured, ask:

Write a spec for password reset and save it to docs/ai/specs/password-reset/spec.md. Use this project's Living Memory instructions.

The agent writes an ordinary local file. The same path is used in the repository, and the setup keeps the mirrored files out of your own commits. Files outside the configured write folders stay on your machine.

ToolWhen files are sent
Claude CodeThe hook sends changes when the agent's turn ends.
CodexThe hook sends changes when the next session starts.

To check delivery, run memory status with the same CLI launcher and Fabric address used by your setup line, from the folder you set up. For example, if setup began with npx -y <tgz>, use that same prefix before memory status. The result reports pending changes, pull-request links, and any conflicts or refusals. Codex users who need to send changes before the next session can run memory push with that same prefix.

Open any reported pull request, review it, and merge it through your Git provider. A file in an open pull request becomes Living Memory after the merge and repository sync. Use Sync now in the Context tab to refresh it, then check the file there. The next coding session brings the committed files into the local mirror; an agent can also read them through Fabric's memory tools, including files marked Store only.

Local edits are preserved if a remote change conflicts with them. Read the CLI's report before resolving the conflict. See Save specs and notes to the repository for delivery checks, supported file types, conflict recovery, and a complete example of a teammate resuming the work.

Change instructions with your team

Instructions kept in Git

Edit in your normal Git checkout, or open a file in Fabric and choose Edit if you have permission. After editing in Fabric:

  • Commit to the displayed branch writes the change to that branch. Enter a commit message and check the branch before committing.
  • Suggest as a pull request sends the change for review. Open More → Your proposals to see the Pull requests dialog, then follow the link to review and merge it in your Git provider.

An instruction file being edited, with a commit-message field and separate Commit to main, Suggest as a pull request, and Cancel actions.

After a change lands, refresh the tab and start a new coding session to use the updated instructions. A Git-backed project uses the repository's commits and pull requests; it does not need a separate Fabric upload publication.

Your proposal branch

When you suggest changes to instructions kept in Git, they go to your own branch in the project's repository, one commit each, with one pull request for all of them. Open More → Your proposals to follow that pull request.

Files your branch changes lists every file the branch adds, changes or deletes. A file that only your branch has is marked Only on your branch. In the file tree, these files carry a your branch, changed on your branch or deleted on your branch tag. For each file you can:

  • choose Restore published version to add a change that puts the published file back;
  • choose Delete from my branch for a file the published version does not have;
  • choose Edit, change the file, then Suggest change to add another commit.

If someone commits to your branch outside Fabric, the panel shows Your branch has commits made outside Fabric. Fabric does not overwrite those files while the pull request is open: a new suggestion that touches them is refused with the paths it would overwrite. Make that change on the branch in the repository, or wait until the pull request merges. Fabric also does not start your branch over while it has such commits. Close pull request withdraws your changes and deletes the branch only if Fabric made every commit on it.

View and restore a Git file

Open a file in Coding Instructions and choose History. Fabric reads that file's history from Git when you open the dialog. Select a commit to compare its file contents with the current branch. Use Refresh from Git to check for newer commits.

To restore a version:

  1. Check the displayed repository, branch, and file path.
  2. Select the commit containing the version you want, then review the diff.
  3. Choose Restore this file and wait for the Git result. If Fabric opens a pull request, follow its link and complete the usual review and merge.
  4. Reopen the file to check the committed contents.

The Git history dialog for AGENTS.md in an example repository: two commits are listed, the older one is selected and compared with the current branch, and the Restore this file action sits below the diff.

Restoring creates a new change for that file. Other files and earlier commits stay intact. Fabric follows the file's exact path, so history from an earlier filename remains in your Git provider. Binary files, incomplete text, and unavailable versions cannot be restored here. If the branch changes while you review, refresh and compare again before restoring.

Instructions uploaded to Fabric

Editors can upload a new version or edit a file and choose Save and publish. To keep a change unpublished, use Save as a new version. If you can suggest changes but cannot publish them, submit a proposal for someone with review permission. Review proposals opens those suggestions; History lists uploaded versions and their download or publication actions. In History a proposal is labelled by its review state: Proposed while it waits, Replaced by version N once a rebased proposal took its place, Proposal rejected after a reviewer declined it, or Proposal closed when it ended without a review. History reads the list again each time you open it.

Review a proposal

Review proposals shows each changed file. A Markdown file is shown rendered by default, with additions and removals marked in the text. Switch to Raw lines to see the line diff; your browser remembers the choice. Other files always show the line diff. When a Markdown file's frontmatter also changed, the rendered view says so, and Raw lines shows the frontmatter change.

Know when a new version is published

Each time a new version of the instructions is published, Fabric sends one notification, Coding instructions vN published. It names who published it, or the repository sync and the branch and commit, and says how to update your copy: run fabric instructions sync --project <id> for uploaded instructions, or pull the branch for instructions kept in Git. The notification links to the Coding Instructions tab.

It goes to the project owner and to project members who can read the instructions, except the person who published the version. This applies whether someone published directly, a proposal was approved, or the version was published automatically. Roll back to this version in History sends nothing for a version that was already announced.

To stop these notifications, turn off Sync & integrations in Settings → Account → Notifications. Email and webhook delivery follow your delivery settings on that page.

Set how many approvals a proposal needs

For instructions uploaded to Fabric, people who can change coding instructions can set the review policy. Open the tab's settings and find Proposal review. Everyone else can see the policy but not change it.

  • Approvals required sets how many approvals publish a proposal, from 1 to 10. The default is one: the first approval publishes the proposal, and someone who can review may approve their own.
  • Above one approval, the person who proposed a change cannot approve it.
  • Only selected members can approve limits approvals to the people you list. Each must be able to change coding instructions. List at least as many people as the approvals you require, and one more when you require more than one, so a listed person's own proposal can still be approved.

An approval counts only while the person who gave it can still change coding instructions. A policy change applies to the next approval of every open proposal, so proposals already open follow the new rule.

The policy does not apply to instructions kept in Git, whose proposals are pull requests reviewed under your Git provider's own rules, or to a change someone publishes directly.

Remove coding instructions

A project administrator can remove a project's uploaded coding instructions entirely and start over. Open the tab's settings and choose Remove coding instructions. The confirmation names the published version and how many other versions are deleted with it, counting proposals and rejected or failed uploads, including ones you do not see in History. Type the project name to confirm.

Fabric then deletes every version, including the published one, and their stored files. Nothing is published afterwards: coding agents, the Fabric tools and teammates see the project as one that never had coding instructions, and a developer's next fabric instructions sync reports that nothing is published. The sync leaves their local copy as it is. Your ignore rules and review policy are kept, and the next upload becomes version 1. The audit log records the removal with the number of versions and the version that was published. This cannot be undone.

Fabric refuses the removal, and deletes nothing, while any of the following is true. The button is then unavailable, and the reason is shown beside it:

  • the project keeps its instructions in a repository. Switch back to upload mode first. The repository and its sync history are not changed;
  • a move of the instructions into a repository is open;
  • an upload or an edit is still being received or checked. Wait for it to finish, or delete it from History;
  • a proposal waits for review, or a proposal's pull request is still open or being closed. Approve or reject it, or wait for the pull request to be merged or closed.

When something is missing or out of date

What you seeWhat to do
No instructions yetAsk the person managing the project to connect the instructions repository or publish an upload.
The folder is emptyCheck the configured branch, folder, and exclusion rules.
Repository sign-in expiredReconnect the repository in the project's repository settings, then refresh.
An upload is rejectedRead the file-level reason, remove the rejected content, and choose the files again.
Your agent uses older rulesStart a new coding session. If you use a checkout, also read the session hook's update result.
Claude Code's Fabric tools need authenticationRun /mcp, pick the plugin's Fabric server, and choose Authenticate. Older setups may need this once more after the server name changes to plugin:fabric-<id>:fabric; see the plugin setup details. This is separate from the setup sign-in used by the memory mirror.
A spec is still missing from Living MemoryCheck that it is in a configured write folder, read memory status with your setup's CLI launcher, and check any reported pull request. In Codex, sending waits until the next session unless you run memory push. Merge the pull request and sync the repository before looking for the file in Context.
You cannot see a setup, editing, or review actionAsk a project administrator to check your access. Available actions depend on project permissions; guests cannot use this connection dialog.