Good engineering.
A shared practice.
The best workflows get better in the open. Help us make coding agents more thoughtful, more consistent, and easier to trust.
Improve a workflow.
Refine a skill, clarify an instruction, or propose a useful new workflow. Bring a concrete problem and a focused change.
Share what didn’t work.
Open an issue with your agent, the task, what happened, and what you expected. A reproducible example is a contribution.
From idea to pull request.
Start with the problem.
Read the README and the skill you want to change. Check existing issues first. For a new workflow or a larger change, open an issue to discuss the use case.
Fork, clone, and branch.
Fork the repository on GitHub, then clone your fork. Replace YOUR-USERNAME with your GitHub username.
$ git clone https://github.com/YOUR-USERNAME/factory-skills.git$ cd factory-skills$ git switch -c improve-skill-workflowMake a focused change.
Each skill ships independently and cannot read another skill’s files. Keep instructions useful on their own. Shared standards live in shared/; edit them there, then sync the copies into the skills.
$ bash scripts/sync-shared.shVerify what you changed.
Check that shared copies are up to date. For behavior changes, review the fixtures and evaluations in evals/, then run the relevant checks.
$ bash scripts/sync-shared.sh --check$ bash scripts/eval.shBehavior evaluations use claude plugin eval against evals/fixtures/acme-shop. These are real, billed model runs in a sandbox. Review the script and your provider setup before running them. Keep demo changes grounded in behavior the skills have actually shown.
Open a pull request with evidence.
Explain the problem, the change, and how you checked it. Include a before-and-after example when it helps. Be clear about anything you could not verify. Keep the pull request small enough to review.
Open a pull request