v3.3.0 — Code Quality & E2E

Code Quality & E2E

Four new skills since v3.2.0 — three focused on code/docs quality, one on end-to-end testing.

Added

• e2e-playwright-testing v1.0.0 — End-to-end browser testing with Playwright. 8 rules across 6 categories (locator strategies, authentication reuse via storageState, React form gotchas, web-first assertions, test organization, reliability). Stack detection for React/Inertia/Vue projects.

• technical-debt v1.0.0 — Debt audit and prioritization framework. 42 rules across 10 categories (code, security, design, deps, test, performance, data, docs, infra, process). Produces a ranked debt ledger (effort × impact, P0–P3). Scoped to PHP/Laravel (MySQL) + Node/TypeScript/React.

• project-docs v1.0.0 — Documentation lifecycle skill. 25 rules across 6 categories (structure, naming, essential files, quality, cleanup, lifecycle). Bootstrap, audit, and reference modes. Detects AI-generated junk files (PLAN.md, IMPLEMENTATION-SUMMARY.md) and AI-slop in prose content.

• code-slop v1.0.0 — Taste-level code-quality enforcement. 24 rules across 6 categories (comments, naming, over-engineering, defensive overdose, test slop, style fingerprints). Verdicts: CLEAN / SUSPICIOUS / INFLATED / CRITICAL. Pairs with technical-debt (taste audit + metric audit).

How code-slop and technical-debt differ

The root README includes a side-by-side comparison table so users know which to pick:

• code-slop — taste check. "Is this clean code, or sloppy patterns to reject?"
• technical-debt — metric audit. "What should we refactor first?"

Run both for a full audit.

Other

• Move code-slop next to technical-debt in the root README for adjacency with the comparison table
• Shorten technical-debt entry description in root README

Total: 23 skills.