acceptance-patterns
Testing patterns (Arrange-Act-Assert, Playwright E2E, React Testing Library) and WCAG 2.1 AA accessibility checklist. Load when reviewing test coverage, writing acceptance tests, or auditing accessibility.
- License 许可
- AGPL-3.0
- 最近更新
- 2026-11-14
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- acceptance-patterns
- description
- Testing patterns (Arrange-Act-Assert, Playwright E2E, React Testing Library) and WCAG 2.1 AA accessibility checklist. Load when reviewing test coverage, writing acceptance tests, or auditing accessibility.
02 资源文件 2
- 参考文档references/accessibility-checklist.md5.1 KB
- 参考文档references/testing-patterns.md7.3 KB
03 SKILL.md 正文
Acceptance Patterns
Two reference documents for acceptance-test authoring and accessibility auditing.
References
references/testing-patterns.md— JavaScript/TypeScript testing patterns: Arrange-Act-Assert structure, naming conventions, common assertions, mock discipline, React/component testing, API/integration testing, Playwright E2E, and test anti-patterns. Stack-agnostic principles with JS/TS-specific syntax.references/accessibility-checklist.md— WCAG 2.1 AA compliance checklist: keyboard navigation, focus management, ARIA patterns, live regions, testing tools (axe-core, pa11y, Lighthouse), and common anti-patterns.
When to load
- Writing or reviewing acceptance tests for a feature
- Auditing a deployed page for WCAG 2.1 AA compliance
- Reviewing test coverage gaps (unit → integration → E2E ladder)
- Verifying Playwright locator discipline (getByRole/getByLabel over CSS selectors)
Output contract
Produce a findings report with:
- Test coverage assessment — which acceptance criteria have tests, which don't, gaps in the unit→integration→E2E ladder
- Accessibility findings — WCAG 2.1 AA violations with severity (critical/serious/moderate), element selector, and remediation
- Verdict —
PASS|FAIL (N critical, M serious)|UNPROVEN (insufficient test coverage)
04 同仓库更多 Skills
boucle
The boucle protocol — the labels, markers, state machine and handoff rules a boucle loop speaks. Use when interacting with a boucle loop on any consumer repository: reading or writing boucle:* labels, emitting or parsing <!-- boucle:* --> markers, posting a SHA-anchored verdict, driving an issue through triage/worker/reviewer/e2e, or answering "what is this loop waiting on". Runtime-agnostic and forge-agnostic (GitLab and GitHub).
wrangler
Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
web-design-guidelines
Web platform design and accessibility guidelines. Use when building web interfaces, auditing accessibility, implementing responsive layouts, or reviewing web UI code. Triggers on tasks involving HTML, CSS, web components, WCAG compliance, responsive design, or web performance.
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
wayfinder
Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always