القائمة
Use when the user wants to check accessibility, run an a11y review, verify WCAG 2.1 AA compliance, or add axe-core tests to a UI component or page.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when working inside an api-cp-* repo and the user wants to publish/expose their API docs, "add my API to the catalog", set up the publish-api-docs workflow, or get a hmcts.github.io docs site. Wires the current repo into the amp-catalog Swagger UI pipeline, handles the two one-time GitHub Pages admin gaps that fail silently otherwise, and verifies the live site. This is the per-repo counterpart to the catalog-publisher agent, which only touches amp-catalog/docs/apis.json.
Wire up auto-dev and auto-SIT deployment CI for a service-cp-* repo after Azure provisioning and cp-vp-aks-deploy registration are complete. Idempotent — safe to invoke again if the jobs already exist. Use when a service-cp-* repo is missing the deploy-dev and deploy-sit jobs in its ci-build-publish.yml, or when setting up a newly bootstrapped service for the first time.
Start a new HMCTS API-Marketplace API specification repo using the canonical HMCTS template (api-hmcts-crime-template) as master source. Use when creating a new api-cp-* repo (OpenAPI-first, spec-only) distinct from a runtime service-cp-* service.
Stand up a new HMCTS API-Marketplace service-cp-* using the canonical HMCTS template (service-hmcts-crime-springboot-template) as master source. Use when creating a new Spring Boot service for the Common Platform.
Bootstrap the gitignored .claude/CLAUDE.md for any api-cp-* or service-cp-* repo with three @import lines pointing to hmcts-apim-sdlc-orchestrator context standards. Runs automatically on every session start via the SessionStart hook — invoke manually only to force an update.
Use when the user wants to review, audit, or check an OpenAPI v3 spec — applies HMCTS data-sharing policy (UK GDPR/DPA 2018), infrastructure SLA (Azure APIM/AKS), API standards, and security standards (OAuth 2, TLS, input validation). Returns a scored report with Critical/Warning/Info findings.
| name | accessibility-check |
| description | Use when the user wants to check accessibility, run an a11y review, verify WCAG 2.1 AA compliance, or add axe-core tests to a UI component or page. |
Ensure any user-facing output meets WCAG 2.1 AA. Combines automated checks (axe-core) with the manual checks that cannot be fully automated.
Add the following assertion to the integration test for every new page or component.
// Java / Selenium example
AxeBuilder axeBuilder = new AxeBuilder();
Results results = axeBuilder.analyze(driver);
assertThat(results.getViolations()).isEmpty();
// Node / Playwright example
const { checkA11y } = require('axe-playwright');
await checkA11y(page, null, { runOnly: { type: 'tag', values: ['wcag2a', 'wcag2aa'] } });
# Python / Playwright example
from axe_playwright_python.sync_playwright import Axe
results = Axe().run(page)
assert results.violations_count == 0
Automation catches ~30% of issues. The rest need a human:
| Check | Guidance |
|---|---|
| Keyboard navigation | Tab through all interactive elements — logical order? |
| Focus visible | Is the focus ring visible on all interactive elements? |
| Screen reader (VoiceOver/NVDA) | Are form labels, error messages, and headings announced? |
| Colour contrast | 4.5:1 for normal text, 3:1 for large text |
| Error identification | Errors linked to fields via aria-describedby |
| Timeout warnings | User warned before session timeout with option to extend |
| Severity | Action |
|---|---|
| Critical | Block deployment — must fix before merge |
| Serious | Block deployment — must fix before merge |
| Moderate | Log as an issue — fix within the current sprint |
| Minor | Log as an issue — fix in the next sprint |
For the PR / deployment artefact: