mr-onion

Skills

This directory holds Claude Code skills generalized from Mr Onion’s own testing and engineering judgment, plus material Martin proposed directly (code-structure, refactor-audit) and one ported from a sibling repo (plan-to-specs). It’s split into two categories so the distinction stays structural as more skills land, rather than flat and increasingly mixed — see docs/decisions/phase-18-skills-taxonomy-backlog.md for why. Neither category has a flagship, and none of these are positioned as secondary to another — see ROADMAP.md for full detail on what each one generalizes from and how it was verified.

As of Phase 22, 12 skills are built: the 11 discussed since docs/REIMAGINING.md first raised the question, plus crawl-and-classify-pages, added once TFP-036’s spike (Phase 22) confirmed introspect/crawl was real, non-duplicated capability rather than something Playwright MCP already provided. None are pure agent judgment with nothing to check against: each names the real case it generalizes from, and most were run against a real target before being called done.

Invoking a skill for real

As of Phase 21 (TFP-051), these are real Claude Code plugin skills, not just files to open and follow by hand. skills/.claude-plugin/plugin.json declares both testing/ and engineering/ as skill directories, packaged as the mr-onion-skills plugin and registered via a local marketplace (.claude-plugin/marketplace.json) that .claude/settings.json enables automatically for anyone with this repo trusted — no manual install step.

Invoke any skill by its plugin-scoped name, e.g.:

/mr-onion-skills:write-playwright-test
/mr-onion-skills:code-structure

Verified directly (claude plugin install, then a fresh session’s own Skill tool — not opened and read manually): both produced their documented worked-example output exactly, through the real invocation path.

Testing judgment

Skills about what a test should cover and what it actually proves. Lives in skills/testing/.

Engineering concerns

Skills about how code is structured and where it’s likely to break, as distinct from what a test covers. Lives in skills/engineering/.

Release engineering (SRE ch. 8) was deliberately not added as a twelfth candidate — it’s already covered by the existing verified-release-pipeline account skill, not duplicated here.

Provenance, in one place

Every skill above traces to something real rather than a generic best practice: five to Emil’s own prior incidents and write-ups (TA-227, TA-230, DESKTOP_STABILITY_MATRIX.md), two to Martin’s own proposed drafts, one to Martin’s own unmerged branch on a sibling repo, three to named chapters of the Google SRE book, one directly to the ISTQB testing taxonomy, and one (crawl-and-classify-pages) to Mr Onion’s own introspect/crawl source, via TFP-036’s spike against Playwright MCP’s real tool list. Full citation and verification detail for each is in ROADMAP.md and the Phase 17-20 decision records under docs/decisions/.

Known gaps / open questions

What’s next

Phase 19’s dogfooding (TFP-040/041/042) — running TestForge’s actual app and write-playwright-test directly against test-assist, and comparing both to its existing hand-written suite — was deliberately blocked on this set being real rather than aspirational. It resumes now.