Opinionated preferences for building framework-agnostic, accessible custom elements with the Web Components standards.
Performs WCAG compliance audits and accessibility remediation for web applications. Use when: 1) Auditing UI for WCAG 2.1/2.2 compliance 2) Fixing screen reader or keyboard navigation issues 3) Implementing ARIA patterns correctly 4) Reviewing color contrast and visual accessibility 5) Creating accessible forms or interactive components
Compares an OpenAPI YAML/JSON spec to a list of implemented routes and flags drift: missing operations, extra routes, method mismatches, and path-parameter shape differences. Use when reviewing API PRs, before a release, or asking "does our code still match the OpenAPI?". Includes a stdlib Python checker with --self-test.
Audits foreground/background color pairs for WCAG 2.x contrast (AA and AAA for normal and large text), reports ratios and pass/fail, and notes color-blindness risks. Use when checking UI palettes, design tokens, or asking "is this gray-on-white readable?". Includes a stdlib Python contrast checker with --self-test.
Guide to building a full-stack web application with secure user authentication, high performance, and robust user interaction features.
Plans a major framework upgrade step by step, such as React, Next.js, Django or Rails: reads the breaking changes, maps what in your code they hit, and splits the work into small safe pull requests.
Finds code nobody uses anymore: unused files, exports, routes, styles and dependencies, with proof for each one, and suggests small safe pull requests to remove them.
Ships UI issues as small PRs with screenshots. Made for the Lean Software Factory team.