wct-acceptance
Skill0 starsChanged 3 months agoMITView on GitHub
Build and verify WCT's Python-native Gherkin acceptance pipeline. Use for feature specifications, scenario outlines, generated acceptance tests, IR duplication, hardcoded examples, G-ACCEPT failures, or acceptance mutation.
In this repository31 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/wct.mdcCursor rule
- wct-acceptanceSkill
- wct-adoptSkill
- wct-architectureSkill
- wct-crapSkill
- wct-dependenciesSkill
- wct-doctorSkill
- wct-drySkill
- wct-gateSkill
- wct-hardeningSkill
- wct-mutateSkill
- wct-ratchetSkill
- wct-reviewSkill
- wct-securitySkill
- wct-test-honestySkill
- wct-adoptSkill
- wct-architectureSkill
- wct-crapSkill
- wct-dependenciesSkill
- wct-doctorSkill
- wct-drySkill
- wct-gateSkill
- wct-hardeningSkill
- wct-mutateSkill
- wct-ratchetSkill
- wct-reviewSkill
- wct-securitySkill
- wct-test-honestySkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Write deterministic externally observable behavior in features/*.feature.
- Very specific: line 9
Run uv run wct accept parse <feature> then uv run wct accept ir-dry <feature>.
- Very specific: line 11
Run uv run wct accept generate <feature> and uv run wct accept run <feature> sequentially.
- Very specific: line 12
Run uv run wct accept mutate <feature> and require zero surviving example-value mutations.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
Verify acceptance behavior
- Write deterministic externally observable behavior in
features/*.feature. - Run
uv run wct accept parse <feature>thenuv run wct accept ir-dry <feature>. - Reuse regex-shaped step handlers for wording that differs only by values.
- Run
uv run wct accept generate <feature>anduv run wct accept run <feature>sequentially. - Run
uv run wct accept mutate <feature>and require zero surviving example-value mutations.
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.

