agentleFS
xaedalonxaedalon/factory-community/.claude/skills/factory-setup/SKILL.md

factory-setup

Skill2 starsChanged 53 days agoApache-2.0View on GitHub

Install Xaedalon Factory on this machine and leave it running — prerequisites, build, user scope, daemon, and a board that answers. Use when the user asks to install, set up, or get Factory working, or invokes /factory-setup. Not for using Factory once it runs (that is `factory setup`, `factory doctor`, and the board).

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Setting up Factory

The runbook is skills/factory-setup/SKILL.md, at the root of this repository. Read it now and follow it exactly.

It lives there rather than here because three agents are supported — Claude Code, Codex and Copilot — and the steps must not exist in three places. The one at the root is the only copy; this file is how Claude Code finds it.

Two things it says that are worth knowing before you open it: explain the whole plan to the person before running anything, and never accept Factory's security disclaimer on their behalf.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.