Sdh Claude Skills

WCAG 2.2 AA accessibility audit with 4-principle framework, automated checks, color contrast analysis, keyboard navigation testing, and ARIA pattern validation. Triggers on "accessibility audit", "WCAG audit", "a11y audit", "accessibility check", "screen reader test", "keyboard accessibility", or "accessibility compliance".

Phlex view component conventions — Atomic Design structure, class_variants, Stimulus, Turbo. Use when building Phlex (Ruby) view components.

Rails backend conventions — models, controllers, service objects, Panko serializers, Sidekiq jobs, PostGIS. Use when writing or reviewing Ruby on Rails API code.

Web interface design review for accessibility, performance, and UX compliance. Fetches its rule set at run time from an upstream URL (requires WebFetch); falls back to the pinned local accessibility skills when that fetch is unavailable. Use when reviewing UI code, auditing design implementation, checking accessibility, or validating web UX. Triggers on "review UI", "check accessibility", "audit design", "review UX", "web design guidelines", or "UI compliance check". Also reviews flows for storytelling / narrative UX (StoryBrand, narrative arc, emotional beats) alongside component-level rules.

Clean Architecture conventions — layer separation, dependency direction, boundary violations across Rails and frontends. Use when structuring services or reviewing architecture.

Python query performance — N+1 prevention in Django ORM and SQLAlchemy, bulk operations, keyset pagination, indexing, EXPLAIN, connection pooling, Redis caching. Use when writing or reviewing Python ORM queries or data-access code.

Clarify vague requirements, discover hidden assumptions, and produce scoped user stories with acceptance criteria. Use when requirements are ambiguous, incomplete, or when starting a new feature, epic, or project. Also trigger when someone says "what should we build", "scope this feature", "break this down", "write user stories", "acceptance criteria", "requirements gathering", "feasibility check", or mentions unclear specifications.

Core engineering standards and tech stack for a Software Development House — Rails + Phlex backend, Python (FastAPI/Django) for AI/ML and data services, React Native, ReactJS (Vite), Next.js, PostgreSQL/PostGIS, Redis/Sidekiq, Terraform on AWS/Vercel. Use whenever writing, reviewing, planning, or scaffolding code in this stack, choosing a library, or setting up a project. Detailed per-area conventions live in the std-* skills (each scoped by file path — load the one that fits the task); specialized work routes to the agents.

Terraform HCL conventions — file structure, provider version constraints, resource naming, required tags, security minimums, state/backend. Use when writing Terraform.

React Native and Expo performance best practices with 36 rules across 14 categories. Use when optimizing list performance, implementing animations with Reanimated, reviewing React Native code for performance, or working with native modules. Triggers on "React Native performance", "list optimization", "FlashList", "Reanimated best practices", "mobile performance", or "React Native best practices".