Results for “image-audit”

Audit AEM Edge Delivery Services commerce product pages for search engine crawlability and indexing, then remediate issues with meta tags, structured data, canonical URLs, and image optimization.

Audit a component or page for accessibility issues and fix them

Audit a component or page for accessibility issues and fix them

Audit a component or page for accessibility issues and fix them

Audits a website from three perspectives—design, SEO/technical, and LLM/AI-search visibility—and produces a scored, evidence-bound report with prioritized improvements.

Audits design quality across accessibility, performance, theming, and responsiveness, producing a prioritized report with severity ratings and fix recommendations.

Audits any movemental.com page across UI, content, architecture, UX, and conversion, then writes a markdown report and a standalone fix prompt.

Audits a page or component against the Digital Curator design spec and movemental conventions, checking visual quality, accessibility, token compliance, and consistency before shipping.

Audits colour decisions on a screen for contrast ratios, palette coherence, semantic meaning, and accessibility, flagging deviations and recommending specific corrections.

Runs comprehensive SEO audits and analysis for any website, covering technical SEO, content quality, schema markup, sitemaps, images, and GEO, with industry-specific detection and actionable recommendations.

Perform comprehensive audit of interface quality across accessibility, performance, theming, and responsive design. Generates detailed report of issues with severity ratings and recommendations.

Audits and enforces web interface standards covering accessibility, performance, UX, and code quality from Vercel Engineering's Web Interface Guidelines. Use this skill when reviewing UI code, checking accessibility compliance, auditing design implementations, running pre-merge frontend checks, or when someone asks to "review my UI", "check accessibility", "check my site", "audit design", or "is this component correct". Apply proactively when writing form elements, interactive components, images, animations, or anything that users directly touch — these guidelines prevent common mistakes before they reach production.

Audits and fixes responsive design issues across breakpoints, including fixed widths, missing media queries, non-responsive images, undersized touch targets, and horizontal scroll, with framework detection and verification at mobile, tablet, desktop, and wide viewports.

any input (code, docs, papers, images) → knowledge graph → clustered communities → HTML + JSON + audit report. Use when user asks any question about a codebase, project content, architecture, or file relationships — especially if graphify-out/ exists. Provides persistent graph with god nodes, community detection, and BFS/DFS query tools.

Analyze a website page's UI for obvious oddities: the same information repeated multiple times (a phone number shown three times in the header, a '24/7' badge in two places, a bullet list restating the paragraph above it), duplicated or near-duplicate copy and sections, stray/orphaned text near CTAs, copy that doesn't match the business or section subject, placeholder text, overcrowded heroes, misaligned elements, and imagery that doesn't fit the business. Use this whenever the user asks to check, audit, review, sanity-check, QA, or 'look over' a web page, landing page, or UI — whether they give a live URL, a localhost/dev-server URL, a screenshot, or HTML/JSX/template files — even if they only say something casual like 'does this page look right?', 'find anything weird on this page', or 'anything off about my landing page?'.