Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

accessibility-review

Estrellas8

Forks1

Actualizado28 de junio de 2026 a las 21:45

Audit the project's changed Svelte components for accessibility issues (aria labels, decorative SVGs, label associations, live regions, German alt text, keyboard reachability) following AllerLeih's existing a11y patterns. Use when the user asks for an a11y/accessibility review of UI changes. Reports findings; does not edit code unless asked.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

share-open-sharing-infrastructure

share-open-sharing-infrastructure/share-mvp

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Analistas de garantía de calidad de software y probadoresOcupaciones informáticas y matemáticas·SOC 15-1253

SKILL.md

readonly

Más de este repositorio

mismo repositorio

write-tests

share-open-sharing-infrastructure/share-mvp

Write Vitest unit tests for the AllerLeih SvelteKit frontend, following this repo's conventions (co-located *.test.ts, mocked PocketBase, testing server functions and +page.server.ts load/actions). Use whenever the user asks to write, add, or improve tests, increase coverage, or "test this" for any server-side function, form action, or load function — even if they don't say "Vitest". Reach for it before merging logic that isn't covered.

2026-07-248

issue-to-pr

share-open-sharing-infrastructure/share-mvp

Drive a single issue through the full AllerLeih delivery pipeline as an interactive orchestrator: plan → code → review → fix-loop → test → manual-test gate → commit + PR. Each stage runs as a dedicated sub-agent and MUST consult the applicable project skills and CLAUDE.md guardrails. TRIGGERS: "address issue", "fix issue", "work on issue", "implement issue", or any GitHub issue number or URL handed over for delivery — invoke this skill immediately, before any research or coding. Two human gates: plan approval and manual-test OK.

2026-07-228

review-all

share-open-sharing-infrastructure/share-mvp

Multi-role review of the current AllerLeih change: four specialised reviewers (security & data protection, code quality, accessibility, conventions) run in parallel against the diff, then the findings are consolidated, deduped and fixed directly — with a change log that records what/where/ why for each fix. Use when a change should be reviewed from all angles and the findings fixed in one go, without opening a PR. Not for GitHub PR reviews (use /review for those) and without a browser test (use /review-and-test for that).

2026-07-228

review-and-test

share-open-sharing-infrastructure/share-mvp

Review-and-verify workflow for AllerLeih: review the current change for security & project correctness, and verify it end-to-end in a real browser — then report. Runs four specialised reviewer roles in parallel (security & data protection, code quality, accessibility, conventions) plus allerleih-tester for the browser + test drive via the Chrome DevTools MCP, and produces one consolidated report. READ-ONLY: it changes no code, runs no fix-loop, opens no PR. Use when you have a change on a feature branch (or uncommitted) and want it reviewed and browser-tested without shipping it.

2026-07-228

new-route

share-open-sharing-infrastructure/share-mvp

Scaffold a new SvelteKit route in AllerLeih the way this repo does it — +page.server.ts (load + form actions), +page.svelte (Svelte 5 runes, no data destructuring), a co-located test, and German strings in texts.ts — with the project's PocketBase guardrails baked in. Use whenever the user wants to add a new page, screen, or route, build a CRUD/form page, or "make a page for X", so the route lands consistent and isn't missing pb.filter, trust filtering, or server-side permission checks.

2026-07-198

schema-change

share-open-sharing-infrastructure/share-mvp

Coordinate a PocketBase schema change across both AllerLeih repos so nothing drifts — the backend migration (delegated to new-migration), the frontend TypeScript types, the data-model docs, and a public-view leak check. Use whenever the user adds/changes/removes a field on a collection, adds a collection, or changes a `*_public` view — anything that touches the schema. The point is to stop the frontend types, docs, and the privacy views from falling out of sync with the database.

2026-07-198

name	accessibility-review
description	Audit the project's changed Svelte components for accessibility issues (aria labels, decorative SVGs, label associations, live regions, German alt text, keyboard reachability) following AllerLeih's existing a11y patterns. Use when the user asks for an a11y/accessibility review of UI changes. Reports findings; does not edit code unless asked.

accessibility-review

Review the accessibility of changed UI for the AllerLeih app. This is a read-and-report skill — produce a findings list, and only edit code if the user explicitly asks.

Scope

Default to the diff against main:

git diff --name-only main...HEAD -- '*.svelte'

If there is no diff (or the user names files/areas), review those instead. Read each component fully before judging — context matters (a visually-hidden label may already exist).

Checklist

For each changed .svelte file, check:

Icon-only / unlabeled controls — every <button>/clickable with no visible text has an aria-label (German, sourced from src/lib/texts.ts where a string exists). Loaders/spinners too. Pattern reference: src/lib/components/AllerLoader.svelte.
Decorative graphics — purely decorative SVGs/icons/shimmer have aria-hidden="true" and no redundant label. Pattern reference: src/routes/search/SearchBar.svelte.
Form controls — every input/select/textarea has an associated <label> (for/id or wrapping). Error text is programmatically associated (e.g. aria-describedby) and not conveyed by color alone.
Status / dynamic regions — content that updates without navigation uses aria-live="polite" (and aria-busy while loading). Pattern reference: src/routes/conversations/[conversationId]/+page.svelte.
Images — <img> and item/profile images have meaningful German alt text (empty alt="" only for purely decorative images). Watch item-image components that may render no alt.
Keyboard & semantics — interactive elements are real buttons/links (not div/span with click handlers); aria-pressed/aria-expanded reflect toggle state (pattern: src/routes/users/[id]/ItemsSection.svelte); focus order is sensible; no positive tabindex.
Contrast / color-only meaning — flag obvious cases where state is signaled by color alone.

Output

Group findings by severity (Blocking / Should-fix / Nice-to-have). For each:

<file>:<line> — <issue>
  Fix: <concrete suggestion, referencing the matching existing pattern>

End with a one-line summary (e.g. "3 should-fix, 1 nice-to-have"). If the user wants the fixes applied, make minimal edits that follow the referenced patterns and pull strings from texts.ts.