Results for “quality-audit”

Scaffolds fullstack projects (Next.js, FastAPI, MERN, Django) and analyzes code quality with security and complexity scoring.

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

Audit AEM Edge Delivery Services pages for content quality, SEO, accessibility, performance, and EDS best practices, producing a prioritized fix list with remediation steps.

Audits UX quality of a codebase or validates implementation against design mockups, then fixes issues and commits changes.

Run a comprehensive SEO audit across technical SEO, on-page SEO, schema, sitemaps, content quality, AI search readiness, and GEO. Orchestrates 12 specialized sub-skills and 7 subagents for full-site analysis.

Aesthetic assessment and design scoring across 6 dimensions. Use for UI critique, design review, visual quality assessment, remix suggestions. Activate on "design critique", "aesthetic review", "UI assessment", "visual quality", "design score", "remix this design". NOT for implementation (use frontend-developer), accessibility-only audits (use color-contrast-auditor), or brand identity creation.

Scans a codebase for security, database, deployment, code quality, AI/LLM, dependency, frontend, and observability issues before deployment. Intercepts deploy commands and blocks until critical items pass.

Runs a broad SEO audit covering technical SEO, on-page SEO, schema, sitemaps, content quality, AI search readiness, and GEO, with a weighted health score and prioritized action plan.

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.

Runs comprehensive SEO audits and analysis for websites, covering technical SEO, content quality, schema markup, Core Web Vitals, local SEO, and AI search optimization using browser automation tools.

Audits and upgrades existing websites and apps to premium quality by identifying generic AI patterns and applying high-end design standards without breaking functionality.

Run multiple AI agents against a product, SDK, or docs site to score setup friction, speed, efficiency, error recovery, and doc quality from a minimal prompt.

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.

Audit images across AEM Edge Delivery Services pages for SEO and performance, checking alt text quality, dimensions, lazy loading, fetch priority, file naming, and decorative image handling, and generate per-page reports with fix instructions.

Reconstruct a product flow, then audit how usable it is — whether it makes sense, where users get confused or stuck, whether the copy and instructions are clear, and where friction causes drop-off. Produces a prioritized, severity-weighted findings report. Works from three inputs: frontend code in a repo, a live running app driven via a browser, or a written flow / spec / screenshots. Use this skill whenever the user asks for a UX review, usability audit, "is this flow confusing", "does this signup/onboarding/checkout make sense", "why are people dropping off", "audit this form", "where's the friction", or hands over a flow and asks whether it's user-friendly. Trigger even on casual phrasings ("is my checkout any good?") — it imposes the structure ad-hoc UX opinions miss. Audits flow usability and friction; for visual polish and interface quality the impeccable audit/critique skills apply instead.

Review a built frontend against its chosen direction, catch drift back to generic AI defaults, enforce state coverage, ethical patterns, UX heuristics, and polish, and check contrast with APCA (not the legacy WCAG ratio). Produces specific, prioritized fixes — never vibes-based feedback. Works with pasted screenshots or Playwright MCP automated capture. Load when the user asks to review a UI, audit a design, check if a frontend looks generic or vibecoded, evaluate visual quality or polish, says "review this UI", "is this design good", "audit my frontend", "does this feel like [product]", "design QA", or when frontend-design routes here. Sub-skill of frontend-design.

Audits an EXISTING UI/codebase for generic AI patterns and applies targeted craft fixes — layout, interactivity, content, iconography, and code quality — without discarding the project's own identity. Use when a UI looks flat, generic, or "AI-slop" and there is code to improve, not build from scratch. Triggers on: "improve the design", "looks generic", "not polished enough", "redesign this", "elevate the UI", "it looks boring", "make it better looking", "apply taste", "design review". Works with any CSS framework. For designing a NEW project's identity from a brief, use `taste-skill` instead — this skill only upgrades what's already built. Source: github.com/Leonxlnx/taste-skill (redesign-skill), restored to the full checklist + the project-identity rule the earlier port had dropped.