David Dias

Audit account settings, privacy pages, and API routes for a complete data deletion flow. Check browser storage cleanup, server deletion requests, and user confirmation, then identify missing pieces and guide implementation.

• Audit account deletion flows
• Check browser storage cleanup
• Review server deletion requests

Audit PDFs linked from a website by checking file sizes and response headers, the information returned by the server. Flag large downloads for compression review and suggest HTML versions when the content needs a searchable web page.

• Auditing report and white paper download links
• Reviewing large PDFs for compression
• Considering HTML versions of PDF content

Review HTML lists for incorrect child elements and nesting, then identify fixes that help screen readers, tools that read page content aloud, announce item counts and positions accurately.

• Reviewing HTML list structure
• Fixing nested lists
• Checking screen reader announcements

Review HTML list structure so screen readers can identify lists and announce item counts. Find list items without valid containers, check custom accessibility roles, and guide fixes to markup used for navigation or styling.

• Review list markup split across components
• Fix navigation lists with invalid nesting
• Check parent roles for custom lists

Audit URL capitalization and help standardize paths to lowercase. Review routes, internal links, and sitemaps, then check that uppercase variants permanently redirect to the lowercase address to reduce duplicate page URLs.

• Auditing uppercase letters in URL paths
• Planning lowercase URL handling for a new site
• Verifying 301 redirects for mixed-case URLs

Audit a business website for inconsistent names, addresses, and phone numbers. Compare visible page content with structured data, then standardize spelling and formatting to support accurate business information in local search.

• Check business details across a local website
• Standardize address and phone number formats
• Compare structured data with visible contact details

Review links so their destinations are clear even without surrounding text. Identify vague wording, improve names announced by screen readers, and check keyboard behavior and download details such as file type and size.

• Replace vague link text with clear destination names
• Review links for screen reader users
• Check download links for file type and size

Inspect compressed JavaScript bundles, the files that package application code, to find excessive size and loading costs. Recommend splitting code, removing unused portions, and reviewing dependencies based on measured effects on page responsiveness.

• Finding JavaScript files over 200KB after compression
• Investigating delays before a page becomes interactive
• Reducing bundle size through code splitting

Review JavaScript loops and replace suitable ones with standard array and object methods. Make transformations, filtering, and aggregation easier to understand, with practical explanations and browser checks to confirm that changes preserve the intended behavior.

• Refactoring manual loops into array methods
• Clarifying data transformation, filtering, and aggregation
• Reviewing object transformations and deep copying

Check that HTML declares the correct page language and marks sections written in other languages. Find missing, empty, or invalid language tags and suggest corrections that support screen reader pronunciation, browser translation, and spell checking.

• Checking the language declared for a page
• Marking language changes in multilingual content
• Reviewing language settings for screen reader pronunciation

Review HTTP Content-Type headers, which identify file formats, across web pages and static assets. Find mismatches that can block stylesheets or scripts, and identify server configuration changes needed to serve resources correctly.

• Investigating stylesheets or scripts that fail to load
• Auditing server settings for static assets
• Checking character encoding and nosniff headers

Audit informational pages so AI assistants can extract and understand their content. Review headings, HTML structure, content availability without JavaScript, and structured data, then suggest changes that make individual sections clearer when read on their own.

• Review pages intended for AI-generated answers
• Make headings and sections understandable on their own
• Check whether key content is available without JavaScript

Find TypeScript values that bypass type checking through any, including inferred types and assertions. Suggest unknown, generics that preserve type relationships, or Zod validation for external data, with the checks needed where each value is used.

• Addressing ESLint warnings about explicit any
• Reviewing type safety around external API data
• Checking functions that pass any to their callers

Evaluate whether tests catch defects in business logic, calculations, or state machines. Using Stryker, the skill introduces small code changes, reviews which changes escape detection, and helps strengthen tests where important behavior is insufficiently checked.

• Checking test quality beyond code coverage
• Introducing Stryker for a single module
• Strengthening tests for critical calculations

Audit page URLs for long paths, deep nesting, redundant words, and unnecessary dates or dynamic values. Suggest shorter addresses and the redirects and link updates needed when changing existing URLs.

• Creating concise URL slugs from article titles
• Auditing long or deeply nested URLs
• Reviewing URL patterns in a CMS or router

Inspect page HTML for metadata tags placed outside the head section, where page settings belong. Identify misplaced tags and guide fixes to templates or scripts that insert them into the body.

• Checking metadata placement after CMS plugin changes
• Finding metadata inserted into the body by JavaScript
• Reviewing robots, description, OG, and canonical placement

Review a page to ensure it has exactly one main landmark, the region identifying its primary content. Find missing or duplicate main regions and get corrections that give assistive technology users a clear navigation target.

• Checking the main region in a page template
• Fixing duplicate main regions in combined layouts
• Reviewing navigation to primary content with a screen reader

Review whether interactive web elements work with keyboard navigation. Check Tab order, hidden elements, and focus traps where users cannot move away, then identify specific fixes and ways to verify behavior with browser accessibility tools or assistive technology.

• Check whether all controls are reachable with Tab
• Align keyboard focus order with the visual reading order
• Remove hidden content from the Tab sequence

Audit and write page titles for search results and browser tabs. Check that each page has one descriptive title, an appropriate length, a unique wording across the site, and its main keyword near the beginning.

• Auditing title tags before publishing pages
• Finding duplicate titles across a site
• Writing titles around a main keyword

Audit slow page loads by measuring LCP, the time until the largest visible content appears. Identify bottlenecks in images, server responses, and rendering, then recommend changes supported by measurements.

• Find why a page's main content appears slowly
• Review hero image loading
• Prioritize fixes using Lighthouse measurements

Audit and improve `/llms.txt`, a curated starting point for AI tools browsing documentation. Check its location, the usefulness and accessibility of linked pages, and its separation from existing crawl and indexing controls.

• Audit llms.txt on a public documentation site
• Select useful API references and getting-started guides
• Check documentation links for availability

Check the HTML delivered to browsers for broken internal, external, anchor, and email links. Locate errors and unintended redirects, suggest URL updates or replacements, and help introduce automated checks and ongoing monitoring.

• Checking links on documentation or e-commerce sites
• Reviewing links produced by shared components
• Adding automated link checks to CI/CD

Review website navigation markup so screen reader users can identify and jump between navigation areas. Check nav elements, descriptive labels, and skip links, then pinpoint issues in the HTML delivered to the browser.

• Reviewing accessibility of main and footer navigation
• Adding distinct labels to multiple navigation areas
• Checking navigation markup from shared components

Audit web pages for excessive keyword repetition in body text, titles, metadata, and image descriptions. Report frequent terms and their density, identify hidden keyword text, and help rewrite repetitive passages into natural language focused on readers.

• Checking articles for excessive keyword repetition
• Editing repetitive AI-generated content
• Reviewing titles, meta descriptions, and image alt text