factory-community
Copilot instructions2 starsChanged 53 days agoApache-2.0View on GitHub
Installing or setting up Factory — read skills/factory-setup/SKILL.md and follow it exactly. It is the single copy of that runbook; every supported agent points at it. Removing Factory — read skills/factory-uninstall/SKILL.md and follow it exactly. It keeps the user's data by default and names the command for anything that is theirs. Pointing an agent at Factory over MCP — read skills/factory-mcp-install/SKILL.md and follow it exactly. It asks where before it writes anything, and defaults to everywhere on the machine. skills/factory-mcp-uninstall/SKILL.md…
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- factory-mcp-installSkill
- factory-mcp-uninstallSkill
- factory-setupSkill
- factory-uninstallSkill
- factory-mcp-installSkill
- factory-mcp-uninstallSkill
- factory-setupSkill
- factory-uninstallSkill
The file
We split this copilot-instructions.md into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Every guard is broken deliberately and watched to fail before it is trusted.
- Very specific: line 24
Before pushing: pnpm typecheck && pnpm lint && pnpm test, and pnpm --filter @factory/web test:e2e if the board changed.
≈ “Common” is an estimate: at least 1 in 5 of the 3,827 Copilot instructions files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Working in this repository with Copilot
Installing or setting up Factory — read skills/factory-setup/SKILL.md and follow it exactly.
It is the single copy of that runbook; every supported agent points at it.
Removing Factory — read skills/factory-uninstall/SKILL.md and follow it exactly. It keeps the
user's data by default and names the command for anything that is theirs.
Pointing an agent at Factory over MCP — read skills/factory-mcp-install/SKILL.md and follow
it exactly. It asks where before it writes anything, and defaults to everywhere on the machine.
skills/factory-mcp-uninstall/SKILL.md is the other direction; it removes no Factory data.
Changing anything here — read CONTRIBUTING.md first. Three rules decide
whether a change is acceptable, and none of them is guessable:
- The
.featurefiles are the specification. A behaviour change begins with a scenario, written in the language of the problem, not of the implementation. - Every guard is broken deliberately and watched to fail before it is trusted. A test that has never failed is a test nobody has checked.
- The open core never imports commercial code, and every path flows from
packages/config/src/scopes.ts—process.cwd(),os.homedir()andos.tmpdir()are banned elsewhere, by lint.
Before pushing: pnpm typecheck && pnpm lint && pnpm test, and
pnpm --filter @factory/web test:e2e if the board changed. CI runs all of it on macOS and Linux.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

