quality-engineering
Skill1 starsChanged 7 days agoMITView on GitHub
Empirical quality assurance, automated testing, and verification discipline for AI coding agents. Enforces test-driven development (TDD) with 80%+ coverage, Playwright E2E automation, formal evaluation harnesses, pre-completion verification checklists, delivery gates, and documentation grounding. Use when writing tests, verifying bug fixes, or running pre-completion gates.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- formal-you/agent-skills-suitetheir own version, first seen Oct 20, 2026
- foreturn/product-studiotheir own version, first seen Oct 14, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- foreturn/product-studio★ 3same name
- formal-you/agent-skills-suite★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository62 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/skills/humanizer/AGENTS.mdAGENTS.md
- agentshieldSkill
- asd-ste100Skill
- autonomous-agent-engineeringSkill
- awwwardsSkill
- backend-engineeringSkill
- boarduiSkill
- design-systemsSkill
- frontend-engineeringSkill
- interface-designSkill
- jurySkill
- karpathy-guidelinesSkill
- last30daysSkill
- lemo-opuscarSkill
- motionsites-web-builderSkill
- rev-engineerSkill
- scraplingSkill
- security-auditSkill
- skillforgeSkill
- stageshowSkill
- technical-documentationSkill
- agentshieldSkill
- anti-vcodeSkill
- arenaSkill
- asd-ste100Skill
- autonomous-agent-engineeringSkill
- awwwardsSkill
- backend-engineeringSkill
- boarduiSkill
- courtSkill
- designsSkill
- design-systemsSkill
- diagram-designSkill
- frontend-engineeringSkill
- humanizerSkill
- impeccableSkill
- interface-designSkill
- jurySkill
- karpathy-guidelinesSkill
- last30daysSkill
- lemo-opuscarSkill
- logo-designSkill
- model-routerSkill
- motionsites-web-builderSkill
- ponytailSkill
- quality-engineeringSkill
- rev-engineerSkill
- rigorSkill
- sanzo-wada-colorsSkill
- scraplingSkill
- secure-auditSkill
- security-auditSkill
- skillforgeSkill
- socraticSkill
- stageshowSkill
- stealSkill
- tasteSkill
- technical-documentationSkill
- threeuiSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 30
Write tests first (RED). Run tests to verify failure.
- Distinctive: line 35
Use Playwright Page Object Model for critical user journeys.
≈ “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
Quality Engineering
Consolidated capability for empirical test-driven development, automated end-to-end verification, eval harnesses, and rigorous completion gates.
When to Activate
- Authoring unit, integration, or E2E tests before or alongside code changes.
- Enforcing test-driven development (RED -> GREEN -> REFACTOR) with 80%+ test coverage.
- Building or running Playwright end-to-end test suites with Page Object Model.
- Executing pre-completion verification checklists before declaring tasks finished.
- Enforcing mechanical delivery gates against hallucinated task completion.
When NOT to Activate
- Pure UI design review (use
interface-design). - Codebase vulnerability or penetration audits (use
security-audit).
Core Execution Workflow
- Test-Driven Development (TDD):
- Write tests first (RED). Run tests to verify failure. Implement minimal code to pass (GREEN). Refactor cleanly.
- Enforce Arrange-Act-Assert (AAA) test structure and descriptive test naming.
- Consult references/test-driven-development.md.
- End-to-End Testing & Evals:
- Use Playwright Page Object Model for critical user journeys.
- Formulate eval harnesses for agent tasks with clear scoring rubrics.
- Consult references/playwright-e2e-testing.md and references/eval-driven-development.md.
- Empirical Grounding & Completion Gates:
- Zero hallucinated completion: never declare work done without executing real tests on disk and verifying exit code 0.
- Consult references/empirical-verification-rigor.md and references/pre-completion-verification.md.
Modular Reference Directory
| Reference Module | Primary Focus | Source Provenance |
| test-driven-development.md | TDD workflow, AAA structure, test isolation, 80%+ coverage | affaan-m/ECC (tdd-workflow) |
| playwright-e2e-testing.md | Playwright E2E patterns, Page Object Model, CI/CD integration | affaan-m/ECC (e2e-testing) |
| eval-driven-development.md | Formal evaluation harness, benchmark suites, agent testing | affaan-m/ECC (eval-harness) |
| empirical-verification-rigor.md | Documentation grounding, verifiable task ledgers, exit code proof | hamzzaqureshi/gravidex (rigor) |
| pre-completion-verification.md | Comprehensive pre-completion checklist, sanity gates | affaan-m/ECC (verification-loop) |
| delivery-gate-enforcement.md | Mechanical stop hook preventing premature completion | affaan-m/ECC (delivery-gate) |
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.